Why the Best Engineer Often Loses the Promotion: Good Work Is Silent

TL;DR: Two engineers do equally good work, and only one gets promoted. The difference usually isn’t talent or effort. Promotions are decided in a room where nobody saw the work, so they run on whatever the room already knows about you. Making your work legible — easy to see and easy to understand — is not spin. It’s the missing half of doing a good job.

Same work, different outcome

Picture two engineers, Maya and Dev. Same team, same year. Both smart, both hard-working, both delivered a big project on time. Then promotion season comes around. Dev gets promoted. Maya doesn’t. She asks the question a lot of great engineers ask: what did I do wrong?

Check the obvious explanation first. Was Dev’s work better? Put them side by side on quality, on-time delivery and business impact, and they’re level. You have probably seen this for real: two people with the same quality of work and very different outcomes. If the work isn’t the difference, something else is.

The decision isn’t made where the work happens

Who decides a promotion? Not the people who watched the work. A group of managers in a room, often at the end of a long day. Most of them have never read your code or seen your design. So they use whatever they already know about you.

“Dev? The caching project, right? He presented it at the review. Dev is ready.” And Maya? “Quiet. Solid, I think. Maya who?”

Nobody in that room is being unfair. They simply can’t vote for what they can’t see.

Your career runs on three layers

It helps to think of a career as three layers:

• The work itself. What you build, write and fix. You control this almost completely.
• Visibility. Who actually knows about that work. You control this only partly, because other people have to notice.
• The story. What people say about you when you’re not in the room. You can only influence this one.

Most technical people pour all their effort into layer one. Layers two and three quietly decide the outcome.

What Dev actually did

Nothing dishonest. He wrote a one-page summary of the project and sent it to his manager. He showed a short demo in the review where the director was watching. He had a coffee with the architect and asked for feedback. And he thanked a teammate in public, by name. Four small moves, every one of them true and useful to other people.

Maya, meanwhile, was heads down building the next thing. Her work was just as good. But nobody around her knew what it was, or what it meant.

Legible is not the same as loud

What Dev did has a name: he made his work legible. Legible means other people can see what you did and understand why it matters. Picture a line. On the left, invisible: great work, and nobody knows. On the right, manipulation: exaggerating, hiding other people’s contributions, playing people. Legible sits in the middle. It’s honest, it’s useful to others, and it shares the credit.

That middle position matters, because many engineers avoid self-promotion for a good reason: they don’t want to become the person on the right. The answer isn’t to stay on the left. It’s to stand in the middle.

“Good work speaks for itself.” It doesn’t.

Work is silent. Somebody tells its story, and every retelling makes it shorter. “Built a caching layer that cut infrastructure costs by forty percent” becomes “did the caching thing,” which becomes “solid engineer, I think,” which becomes, in the review room, “impact? Not sure.”

Whoever tells the story chooses the words. If it isn’t you, it’s someone else. Or nobody. (Wording and percentage are illustrative.)

A ten-minute exercise for Monday

Write down the last three things you delivered. For each one, answer three questions:

• Who knows about it? Not just your manager — who else?
• Where is it written down? A summary, a demo recording, a ticket comment, anything someone could find.
• Who would say it out loud in a room where you’re not?

The empty boxes are your homework. Good work gets you a ticket. Being legible gets you through the door.

Want to go further?

This post is adapted from a lesson of my course Office Politics for Tech Professionals: it starts exactly here, with why good work is not enough, and then shows how power, visibility and decisions really work in tech companies, told honestly and without manipulation tricks.

👉 See what’s inside the course