How to Get Promoted as a Software Engineer

You're shipping features. Your code reviews are clean. Your manager keeps telling you the work is solid. And yet another review cycle passed, and nothing changed. Same title. Same level. Same vague reassurance that you're "on the right track."

Meanwhile, someone who writes worse code than you just got promoted. They didn't even ship the biggest feature last quarter. But their name came up in the right room, at the right time, with the right story behind it. Yours didn't.

This is the part of the promotion system that nobody explains when you start your career: getting promoted as a software engineer has very little to do with how good your code is. The code is the floor. What gets you through the door is something else entirely.

How promotions actually get decided

At most tech companies, your promotion isn't decided by your manager alone. It's decided in a calibration meeting where a group of managers, sometimes with directors, sit around a table. Each manager presents their candidates. They get roughly five to ten minutes per person.

Your manager is pitching your case to a room full of people who have never read your code, never seen your pull requests, and have their own candidates to fight for. The room is essentially a competition: limited promotion budget, multiple advocates, and a bias toward saying no.

Your manager needs to answer questions like these on the spot:

• "What has this person done that is clearly at the next level?"
• "Could a strong engineer at their current level have done this same work?"
• "Where's the evidence of impact beyond their own output?"
• "Is this one strong quarter, or sustained performance?"

If your manager can't answer those cleanly, your case dies. Not because you aren't good enough. Because the people deciding your promotion have never met you, and the only version of you they'll ever know is the one your manager can articulate in five minutes.

There's a political dimension too. Managers with stronger relationships in the room get more benefit of the doubt. New managers face extra scrutiny. If your manager just changed, your promotion clock may have quietly reset because the new person has no context on your work. The same thing happens after parental leave or any extended absence — the evidence trail goes cold while you're away, and nobody restarts it for you.

A study by Scullen, Mount, and Goff (2000) in the Journal of Applied Psychology found that 62–65% of the variance in performance ratings was attributable to the idiosyncrasies of the individual rater, not to what the employee actually did. Only about 25% of a rating reflected real job performance. This isn't cynicism. It's what the data shows about how human evaluation works at scale.

What most engineers get wrong

Most of the advice about getting promoted boils down to "do better work." That's necessary. It's also wildly incomplete. Here's what actually trips people up.

Believing good work is self-evident. This is the single most expensive misconception in tech careers. You assume your manager sees what you do. They don't. The average engineering manager has eight to fifteen direct reports, their own deliverables, and their own review coming up. 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.

Michael Lynch, a former Google engineer, received "Superb" ratings (roughly the top 5% of all Google employees) and was still rejected by the promotion committee twice. The feedback wasn't that he lacked impact. It was that the committee couldn't see it. Same work. Different legibility.

Doing excellent work at your current level instead of the next one. Three years of outstanding performance at your current level is still current-level performance. Calibration committees don't promote the best performer at level N. They promote the person who's already operating at level N+1. If every artifact of your work (the projects you pick, the conversations you drive, the problems you solve) looks like your current role executed flawlessly, that's exactly where you'll stay.

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."

Never having the explicit conversation. A surprising number of engineers have never asked their manager: "I want to be promoted to [next level]. What specific gaps do you see?" They assume the manager is tracking it. Many aren't. Your manager benefits from promoting you. It shows they develop talent. But if they don't know you're targeting promotion, or if they see gaps they haven't communicated, the default is silence. That silence costs you cycles.

Working harder instead of working differently. Engineers who feel stuck often respond by shipping more, staying later, picking up more tickets. This almost never works. The promotion criteria at every level above mid-level involve something other than raw output: scope, ambiguity tolerance, team impact, technical leadership, cross-functional influence. Working harder at the same type of work is optimizing the wrong variable.

Choosing the wrong projects. Not all work is promotable. Maintenance, bug triage, and incremental improvements are valuable to the business but rarely build a promotion case. The engineers who get promoted consistently are the ones who find, or create, projects with enough scope, ambiguity, and organizational visibility to demonstrate next-level judgment. If you've been at the same level for too long, the projects you're choosing are often the reason.

How to build a promotion case on purpose

The gap between doing good work and getting promoted is a documentation and communication problem. Here's how to close it.

Make your goal explicit

Tell your manager you want to be promoted. Say the words. Then ask two questions:

1. "What does the next level look like in concrete terms: what behaviors and outcomes would make my case obvious?"
2. "What are the specific gaps between where I am now and where I need to be?"

Write the answers down. Review them every month. If your manager can't give you specific gaps, that's a signal. Either they don't understand the rubric well enough, or they aren't invested in your promotion. Both are problems you need to address.

Keep a running evidence document

Your memory is terrible. The Ebbinghaus forgetting curve shows that humans forget roughly 70% of new information within 24 hours. By the time review season arrives, most of what you shipped in Q1 is gone, from your manager's memory and from yours.

Maintain a simple document (a brag doc, a wins log, whatever you want to call it). For each entry: what you did, why it mattered, and the measurable result. Update it weekly. When promotion time comes, your manager isn't building your case from scratch. They're editing a document you already wrote.

Manage up without feeling gross about it

Leader-Member Exchange (LMX) research by Wayne et al. (1999) found that the quality of the relationship between a manager and employee directly predicts promotability, beyond actual task performance. The mechanism is straightforward: managers who trust you and feel aligned with your goals advocate harder in calibration.

This doesn't mean sucking up. It means:

• Using your 1:1s for more than status updates. Ask what your manager is most concerned about this quarter. Understand what leadership is prioritizing. Connect your work to those priorities.
• Making your manager's job easier. When they need to pitch your case, give them the material. Send a brief summary of your wins before review season. Frame your work in terms of business impact, not technical effort.
• Building the relationship before you need it. The worst time to invest in your manager relationship is when you need their advocacy. The LMX research is clear: advocacy requires conviction, and conviction comes from relationship built over time.

Choose work that builds your case

Not all projects carry equal promotion weight. Seek work that:

• Has organizational visibility: multiple teams or leadership know about it
• Involves ambiguity: the problem isn't well-defined, and you have to figure out the right approach
• Creates leverage: it makes other people more effective, not just you faster
• Aligns with company priorities: it connects to Objectives and Key Results (OKRs) or strategic goals one or two levels above you

If your current team doesn't offer this kind of work, you have a structural problem. Some teams are promotion graveyards. The work is necessary but doesn't generate the scope or complexity to build a case at the next level.

Get your manager to fight for your promotion

Your manager has limited political capital and multiple direct reports competing for promotion slots. The engineers who get promoted are the ones whose cases are easiest to make. That means:

• No surprises. Your manager should know your promotion timeline months in advance.
• Pre-built packet. Don't make them build your case from memory. Give them the evidence document, the peer feedback highlights, and the impact narrative.
• Peer alignment. Collect peer feedback that specifically references next-level behaviors. Generic praise ("great teammate") doesn't survive calibration. Specific evidence ("drove the design review process that reduced our incident rate by 40%") does.

The uncomfortable math

If you've been at the same level for more than two to three years and the feedback keeps sounding like "you're close," something structural is off. The most common explanations:

• Your manager can't or won't advocate for you. Maybe they lack the political skill, the organizational capital, or the relationship with their director. This isn't something you can fix by shipping more code.
• The work on your team isn't big enough. No amount of perfect execution on small tasks demonstrates next-level scope.
• The company's promotion bar is higher than its hiring bar. This is one of the most uncomfortable truths in the industry. Engineers stuck at mid-level for three or more years at one company get offers at the next level from comparable companies. Internal promotion bars are often higher than external hiring bars because your current company knows your weaknesses. A new company only sees your strengths in a four-hour interview.

None of this means you should leave. But it does mean you should be honest about whether your current environment actually supports your promotion, or whether you're fighting a system that isn't designed to let you win.

The version of this that actually works

Promotions don't go to the best coders. They go to engineers whose work is visible, whose managers can articulate their impact, and whose evidence survives a five-minute pitch to a skeptical committee. The engineers who get promoted consistently aren't playing a different game. They're playing the same game with better information.

The system is imperfect. Parts of it are genuinely unfair. But the gap between the quality of your work and the strength of your promotion case is the part you can close. That's where the leverage is.

---

CareerClimb is an AI career coaching app that helps software engineers build their promotion case week by week. Summit, the AI coach, helps you document wins, identify gaps, and prepare the evidence your manager needs to fight for you in calibration. Start building your case today.