I Am Doing Everything Right and Still Not Getting Promoted

You hit every deadline. Your code reviews are thorough. The feedback from your manager has been some version of "great job, keep it up" for the past year and a half. And then the promotion list comes out, and your name isn't on it. Someone else's is. Maybe someone who joined after you.

The first time, you tell yourself it was timing. The second time, you start questioning everything. You replay conversations. You scan the rubric again. You try to figure out what you're missing. And you can't, because by every metric you can see, you've been doing it right.

That feeling isn't irrational. You probably are performing well. The problem is that "performing well" and "getting promoted" are connected by a set of mechanisms that nobody explains until you've already been passed over.

The gap you can't see from where you're standing

Here's the part that's hardest to hear when you're in this position: the belief that you're doing everything right is, itself, part of the pattern.

Psychologists Michael Ross and Fiore Sicoly ran a set of experiments in 1979 that found a consistent result across married couples, sports teams, and academic discussion groups. People reliably overestimated their own contributions to shared outcomes. Not because they were dishonest, but because their own actions were far more available in memory than anyone else's. You remember every late night, every problem you caught, every decision you made. The people around you remember a fraction of it.

This isn't a character flaw. It's how human memory works. And it creates a specific blind spot for engineers who feel stuck: your own contributions feel comprehensive and obvious. What you can't see is what your manager, your skip-level, and the calibration committee see (or don't see) when they look at your work from the outside.

The engineers who eventually break through describe a moment of realizing they were optimizing for the wrong variable. Not because their work was bad. Because "doing good work" was only one of several things the promotion system was evaluating, and the others were invisible to them.

Five structural reasons this happens

1. The visibility gap

You're shipping real work. But the people who decide promotions can't see it.

At most tech companies, promotions are decided in a calibration meeting where your manager pitches your case to a room of other managers. Most of those people don't know you. They've never seen your pull requests or your on-call incident response. They're hearing a secondhand account, for roughly ten minutes, and comparing it to every other secondhand account in the queue.

If your work lives entirely within your team's boundaries, there's nothing for those external voices to corroborate. Your manager says you're strong. Nobody else in the room has evidence to support that. A verified L6 engineer on Team Blind described it directly: "Nobody cares about team goals. When you deliver, understand how it impacts VP and Director goals."

The deeper mechanics of workplace invisibility explain why this gap is almost automatic and what specifically closes it.

2. The scope mismatch

This is the one that blindsides most engineers. You're doing excellent work at your current level. The problem: that's what keeps you at your current level.

Promotion committees aren't asking whether you're a strong L5. They're asking whether there's evidence you're already operating at L6 scope. The distinction matters more than almost anything else in the process.

Steve Huynh spent four consecutive years at Amazon receiving top-tier ratings before figuring this out. His conclusion:

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

Doing your current job well is the baseline, not the differentiator. What calibration committees look for is evidence of the next level: cross-team influence, ambiguous problem-solving, technical direction that shapes how other teams work. If every example your manager has is about how well you executed within your existing scope, the committee hears "strong at current level" and moves on.

3. The manager alignment gap

Your manager might not know you want a promotion. Or they might know but not be actively building your case.

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 a fringe complaint. It's nearly half the workforce. And most of that gap isn't because managers don't care. It's because they're managing eight to fifteen people while carrying their own deliverables and their own performance review.

A Capital One manager on Team Blind captured the dynamic: "If this is the first time your manager ever hears you're interested in a promotion, it's likely not going to happen soon."

Many engineers assume the desire for promotion is obvious. It isn't. And even when your manager knows, that doesn't mean they're spending their political capital to build a case. Making your manager fight for your promotion requires a different kind of work than making your manager think you're good at your job.

4. Calibration dynamics

Some of what's blocking your promotion has nothing to do with you.

Research by Scullen, Mount, and Goff (2000) analyzed how performance ratings actually work and found that 62–65% of the variance in ratings was attributable to the individual rater's tendencies, not to what the employee actually did. Deloitte cited this research when it scrapped its annual review system entirely.

Beyond rater bias, there are mechanical constraints: limited promotion slots per cycle, budget ceilings, headcount freezes, and the political standing of your manager in that room. A manager with limited capital or a weak reputation among their peers can advocate perfectly and still lose. Two equally strong candidates going up in the same cycle means one of them waits, and the deciding factor is rarely the quality of the work.

None of this is something you can fix directly. But recognizing it matters, because it means a single denial is not proof that something is wrong with your performance.

5. "Right work" vs. "right level work"

The work you're doing might be exactly what your team needs. That doesn't make it the work that gets you promoted.

Refactoring a module that reduces deployment risk is valuable. Coordinating a cross-team migration that unblocks three teams' quarterly goals is more legible to a calibration committee. Both are real contributions. Only one reads as next-level scope to a room full of managers evaluating whether to spend a promotion slot on you.

Michael Lynch, a former Google engineer who received "Superb" ratings (roughly the top 5% of all engineers at the company), was rejected by the promotion committee twice. The committee's feedback: they couldn't see his impact on Google. Not that he hadn't had impact. That his contributions weren't connected to something the committee recognized as organizationally significant.

The gap between good work and promotable work is where most stuck engineers lose time without realizing it.

What to do with this

Recognizing these five gaps is the starting point, not the destination. Here's what actually changes things.

Name the specific gap. Which of the five is most likely blocking you? If your manager gives you positive feedback but can't articulate what next-level looks like on your team, it's the alignment gap. If your work is strong but lives entirely within your team, it's visibility. If your wins are all about doing your current job better, it's scope. Be honest about where the disconnect actually is.

Have the conversation your manager is waiting for. Ask directly: "I want to get to [next level] this cycle. What am I missing, and what would you need to see to bring my case to calibration with confidence?" Get specifics. Vague encouragement is not a plan.

Document your work in business terms, weekly. Your manager's memory of your contributions fades. Research based on Ebbinghaus's forgetting curve confirms the pattern: without reinforcement, people retain about 25% of information after a week. A three-sentence impact update after each significant win keeps your contributions salient when calibration arrives.

Shift at least one project toward next-level scope. You don't need to overhaul your entire workload. Pick one initiative that has cross-team visibility or connects to a leadership priority. Make sure the output is documented and legible to someone who wasn't in the room when it happened.

Separate what you control from what you don't. Budget constraints, committee composition, and your manager's political capital are outside your hands. The strength of your documented case, the clarity of your manager's understanding of your work, and the scope of the projects you choose to take on? Those are yours.

---

Your documented case is the one thing you fully control

CareerClimb logs your wins throughout the year and frames them in the language calibration committees respond to, so when promotion decisions happen, the evidence is already built. Download CareerClimb