Getting promoted without playing the game

I almost didn't get my first promotion because my manager at the time told me I was 'too heads-down.'

I'd shipped three major features that quarter. Zero incidents. My code review turnaround was under four hours. I thought I was crushing it.

I wasn't. Not in the way that actually gets you promoted.

The thing nobody tells you about visibility

Visibility isn't about making sure people know what you did. That's self-promotion. It's gross and everyone can smell it.

Real visibility is making your work easy to understand for people who weren't in the room.

In 2021, I was a senior IC at a fintech doing about $2B in annual transaction volume. We had a Slack culture where engineers would drop their wins in a #shipped channel. Half the team did it performatively. The other half just shared context: 'deployed the retry logic fix, p99 latency on the payments endpoint dropped from 840ms to 210ms, Datadog dashboard here if you want to watch it live.'

Guess which half got promoted faster.

The second group wasn't bragging. They were narrating. There's a difference.

Your manager can't promote you alone

This one surprised me when I became a manager. Promotions aren't a conversation between you and your direct manager. They're a conversation your manager has with five other managers about whether you're already operating at the next level.

Your manager needs ammunition. Not a list of your PRs. Stories they can retell.

When I was an IC, I'd have a monthly 15-minute sync with my manager where I'd share two or three things I was proud of, framed as problems I'd solved. Not 'I shipped X.' More like: 'The mobile team was blocked on the auth flow for two weeks. I found the contract mismatch on Thursday, fixed it Friday, and they unblocked their entire sprint.' That's a story. My manager could tell that story in a room I wasn't in.

As a manager now, I can't overstate how much this matters. I'm fighting for you in rooms where you have no voice. Give me something to fight with.

The coworkers who actually decide your promotion

This is the uncomfortable one.

Your peers write calibration feedback. Their perception of you carries real weight. And the fastest way to tank that perception isn't bad code. It's making people feel small.

I had an engineer, brilliant, who'd respond to design docs with three-paragraph critiques that were technically correct but read like a takedown. Every time. His peers started leaving him off review requests. By the time promo season came, the feedback was brutal. Not about his skills. About working with him.

One conversation I had with him: 'You're not wrong. But being right in a way that makes people defensive means the right thing doesn't happen.' He started leading with questions instead of conclusions. Got promoted six months later.

What to actually do tomorrow

Pick one thing you're working on right now. Write two sentences about it in whatever async tool your team uses, Notion, Linear, Slack, whatever. Frame it as: problem, what you did, what changed. Tag one person who was affected.

Not to show off. To make your work legible.

Do that consistently for 90 days and I promise your manager will have better answers in your next calibration meeting than they did before.

Promotion isn't about politics. It's about making your impact impossible to miss without making it about you.

That's the whole trick.