“Outstanding.”
That was the mark on my performance review.
The text message version of the news was one sentence. Outstanding review. Raise. Sent from an iPhone.
I was proud of it.
The first nine months at Shutterstock had been busy in ways the original job description did not capture. We replaced network gear, rebuilt parts of the data center, investigated storage, handled outages, hired WebOps people, and started turning operations into a team instead of one large collection of emergencies.
We had also started connecting operations more directly to product work. Site speed, contributor uploads, API load, and storage were business problems with infrastructure inside them.
I had also complained, with some justification, that too much work was landing on me. Infrastructure, security, office systems, budgets, hiring, capacity, and every escalation were not a sustainable single role.
The review did not fix that problem. It did tell me the work was visible.
The word mattered because the year had not felt tidy from inside it. Plenty of systems still needed work. Some nights still ended at the data center. A strong review could include all of that without pretending every project was complete.
That mattered. Recognition is not the reason to stay awake during an outage, but a complete absence of it makes the next outage harder.
The raise made the review concrete. The exact number is less important here than what it represented: the company wanted me to keep building.
I wanted that too.
There was plenty left to clean up. Outstanding did not mean finished.
I sent the news to somebody close to me because good moments should leave the office too.
It meant the direction was right.