Good Work Isn't Enough to Get Promoted

You've been shipping. The code reviews are solid. Your manager's feedback at every 1:1 is some version of "you're doing great." And yet another review cycle passed without a promotion. Someone on a different team, maybe someone who joined after you, just got one.

The frustrating part isn't the outcome. It's that you did what you were supposed to do. And it didn't work.

Here's what most engineers spend years refusing to accept: in the promotion system at most tech companies, good work is necessary but not sufficient. Not because the system is entirely broken (though parts of it are). Because it was never designed to measure what you think it's measuring.

Why this feels wrong (and it is)

The meritocracy promise felt real. In school, your grade on the midterm reflected your performance on the midterm. The rubric was visible. The evaluator had access to all the evidence. There was no politics in whether the answer to question 4 was correct.

Work doesn't operate this way, and nobody tells you that when you join.

A 2023 survey by INTOO and Workplace Intelligence found that 46% of employees say their manager doesn't know how to help them with career development. That's not cynicism. It's what managers themselves report when asked. The average engineering manager has eight to fifteen direct reports, their own deliverables, and their own performance review coming up. The time available for actively tracking your contributions is much smaller than you'd imagine.

This isn't your manager's fault. It's a structural reality. And once you understand it, the frustration starts to make more sense.

What's actually driving promotion decisions

The research here is worth sitting with.

A landmark study by Scullen, Mount, and Goff (2000), published in the Journal of Applied Psychology, analyzed how performance ratings actually work. They examined nearly 5,000 managers rated by multiple colleagues and found that 62–65% of the variance in performance ratings was attributable to the personal idiosyncrasies of the individual rater, not to what the employee actually did. Only about 25% of a rating reflected actual job performance. Deloitte cited this research when it scrapped its annual review system entirely.

That finding alone should change how you think about what's happening in the calibration room.

There's a second mechanism, less discussed but equally important. Organizational psychologists call it Leader-Member Exchange (LMX) theory. Research by Wayne et al. (1999) found that the quality of the relationship between a manager and employee is a direct predictor of promotability and salary progression beyond actual task performance. The mechanism is straightforward: managers who trust you, who feel aligned with your goals, who have a high-quality working relationship with you, are more likely to advocate for you in rooms you're not in. Not because they're playing favorites intentionally. Because advocacy requires conviction, and conviction comes from relationship.

Engineers who do excellent work but lack a strong connection with their manager end up with a weak advocate at calibration. Engineers who are both good and trusted get managers who fight for them in calibration.

The third mechanism is what actually happens at calibration. At most tech companies, your promotion isn't decided by your manager alone. It's decided in a committee meeting where your manager has to make a case for you against competing advocates for everyone else on the list. The committee often doesn't know you. They're hearing a secondhand account, for roughly 10 minutes, while deciding the fate of dozens of people.

Steve Huynh spent four consecutive years at Amazon receiving top-tier ratings before understanding this. His post-mortem was direct:

"Putting my energy into being an even better senior engineer wasn't getting me closer to becoming a principal engineer."

The work was excellent. What was missing was something else entirely.

And then there's Michael Lynch, a former Google engineer who received "Superb" ratings (roughly the top 5% of all Google employees) and was still rejected by the promotion committee twice. The committee's feedback: they couldn't see the impact he had on Google. Not that he hadn't had impact. That they couldn't see it.

Same work. Different legibility. Understanding what "Exceeds Expectations" actually requires in the calibration room makes clear why output quality and promotion outcome can come apart. And the informal signals managers actually use to decide who gets promoted go well beyond the official rubric.

Your work doesn't speak for itself goes deeper on the visibility gap: why great work stays invisible and the one habit that closes it.

The uncomfortable part

A lot of what determines whether you get promoted is within your control. Not all of it. Headcount freezes, promotion budgets, your manager's political capital, the composition of the committee: those operate independently of your performance. But the gap between the quality of your work and the strength of your promotion case? That part you can close.

What actually changes it

Build the relationship with your manager before you need it

LMX research is clear: the quality of your relationship with your manager predicts your promotability, not just your rating. And most of that relationship is built through regular, substantive communication. Not through delivering tickets.

This means treating your 1:1s as something other than status updates. Ask what your manager is most concerned about this quarter. Ask what would make their job easier. Understand what your organization's leadership is prioritizing and how your work connects to it.

None of this requires becoming political in some cynical sense. It requires treating your manager as someone with their own context, constraints, and goals, and making yourself legible within that context.

Have the explicit conversation about promotion

Most engineers have never asked their manager directly: "What does promotion to [next level] actually require, and what am I still missing?"

It sounds obvious. It's rarer than you'd think. And before you have that conversation, you first have to tell your manager you want a promotion at all, which most engineers never do.

Why your boss doesn't know you want a promotion covers that gap specifically, including what to say in your next 1:1 to make your goal visible.

Engineers on Team Blind who eventually got unstuck describe this moment consistently:

"I stopped waiting to be told what to do and started asking: 'What's missing from my case?' Most managers are relieved when someone finally treats promotion like a joint project instead of a secret lottery."

After the conversation, ask for the criteria in writing. Not to hold your manager accountable in some adversarial way, but so that you're both working from the same understanding of what "ready" means. Vague criteria drift. Written criteria are harder to move.

Work on things visible at the decision-making level

Not all good work registers equally in calibration. Work that your immediate team knows about but nobody above or outside your team can see doesn't carry much weight in a room full of people who don't know you. Why your manager doesn't recognize your work traces this gap specifically.

Work that unblocks multiple teams, work tied to something leadership visibly prioritizes, work that generates artifacts others can point to: that's what calibration committees remember. If your skip-level does not know your name, you are a stranger to the person who often breaks the tie.

Sean Goedecke, a staff engineer, observed that engineers are often frustrated their company doesn't seem to care about their refactoring or infrastructure work, and also frustrated they're not getting promoted. The two things are related. Work on what leadership prioritizes, and make sure the output is visible to people with promotion input. If you're remote, the bar for this is even higher — you're fighting a measured visibility deficit that in-office engineers don't face.

Find someone who will advocate for you in rooms you're not in

A Catalyst survey of 4,000+ high-potential employees found that having a sponsor (someone senior who actively advocates for you in leadership conversations) is more predictive of career advancement than performance ratings alone.

The distinction matters: mentors give advice. Sponsors spend political capital.

You don't manufacture a sponsor relationship. But you can create conditions for one. Be genuinely useful to senior engineers outside your team. Deliver on high-visibility projects. Write up the impact of your work so that someone who doesn't know you well can still make a credible case for you.

What people in the same position actually did

The pattern across Team Blind discussions and engineering career forums is consistent.

The engineers who got promoted after being stuck stopped treating promotion as something that would happen to them and started building a case for it. They had the explicit conversation with their manager about what the criteria actually looked like. They shifted some effort toward work that was visible beyond their immediate team. They built a running record of contributions updated weekly, not reconstructed the night before review season. A number of them found a senior colleague who would vouch for them in conversations they weren't part of. If you've already been passed over, what to actually do after getting passed over for promotion walks through those steps in detail.

The engineers who stayed stuck ran a different play: excellent execution, invisible output, and a quiet trust that the quality of the work would eventually be recognized on its own.

Good work is the prerequisite. It's not the whole answer. If you've already been passed over for promotion and are rebuilding your case from that specific moment, that article covers the recovery steps.

---

Your next review cycle doesn't have to look like the last one

CareerClimb tracks your wins and builds your promotion case automatically, so the next time calibration happens, your manager has everything they need to fight for you. Download CareerClimb