Navigating the Promotion Process to Senior Engineer
Getting promoted to senior engineer is rarely about a single breakthrough moment. It’s about consistently demonstrating senior-level behaviour until the organisation recognises it. This post explains how promotion processes work and how to navigate them effectively.
How Promotion Processes Work
Most companies follow a similar promotion structure:
Your Manager proposes your promotion based on your work over the review period. They write a promotion packet that includes your accomplishments, impact, and how they map to the senior level expectations.
A Promotion Committee (usually a group of senior+ engineers from other teams) reviews the packet. They don’t know you personally. They evaluate based on:
- The strength of the evidence
- Whether the scope of impact is senior-level
- Whether the achievements are sustained over time, not one-off
The Calibration Process compares your packet against other candidates at the same level across the company to ensure consistency.
This structure means two things:
- Your manager is your advocate, but they need evidence from you
- The evaluation is based on documented accomplishments, not day-to-day impressions
Building Your Case
Start Early
Don’t wait until promotion season. Begin building your case 6-12 months in advance. Keep a running document where you record:
- Projects completed with links to design docs, PRs, and results
- Measurable impact — metrics before and after your work
- Leadership examples — mentoring, design reviews, cross-team coordination
- Ambiguity handled — situations where you defined work that wasn’t scoped
Align With the Level Expectations
Print out your company’s senior engineer rubric (or find it in the internal wiki). For each bullet point, identify at least one concrete example from your work that demonstrates it. If you don’t have examples for a particular area, that’s your growth gap.
Common rubric areas:
- Technical leadership — Did you design a system that others are building on?
- Project management — Did you deliver a complex project with multiple dependencies?
- Mentoring — Did you help junior engineers grow?
- Business impact — Did your work move a metric that matters?
Quantify Everything
- “Improved API latency” → “Reduced p99 latency from 800ms to 120ms, improving user engagement by 12%”
- “Led migration” → “Led migration of 15 microservices from legacy platform, reducing infrastructure costs by 30%”
- “Mentored juniors” → “Onboarded 3 new engineers who were shipping independently within 6 weeks”
Numbers make impact concrete. If you don’t have numbers, ask yourself: how would I measure this? Then start measuring.
Working With Your Manager
Your manager is your primary advocate, but you need to make it easy for them to advocate for you.
Have regular career conversations:
- Every 1:1, spend 5 minutes discussing growth and trajectory
- Explicitly ask: “What would it take for me to be promoted to senior?”
- Share your running document and ask for feedback on what’s missing
Make your impact visible:
- Present your work in team meetings
- Write postmortems and design docs that others reference
- Get mentioned in other teams’ planning documents as a dependency or contributor
Understand the timeline: Ask your manager: “If I continue at my current trajectory, when do you think I’d be ready for promotion?” This gives you a concrete timeline to work toward.
Common Reasons Promotions Fail
Lack of sustained performance: A single great quarter followed by average performance doesn’t demonstrate senior-level readiness. The committee wants to see consistency over 6-12 months.
Impact isn’t visible: You might be doing senior-level work, but if no one outside your team knows about it, the committee can’t evaluate it. Write design docs, give presentations, get cross-team exposure.
Scope is too narrow: Senior engineers operate at team or org-level scope. If your impact is limited to your own tasks without affecting how others work, it’s not senior-level.
No evidence of leadership: Senior is not just about individual contribution. You need to demonstrate that you’ve made others more effective.
If You Don’t Get Promoted
A “not yet” is not a rejection. Ask for specific, actionable feedback:
- What exactly was missing from the packet?
- What would have changed the outcome?
- What should I focus on for the next cycle?
Then make a plan with your manager and execute it. Most senior promotions happen on the second or third attempt.
Key Takeaways
- Start building your promotion case 6-12 months in advance
- Document your accomplishments continuously with measurable impact
- Work closely with your manager to align your work with level expectations
- If you don’t get promoted, get specific feedback and execute a plan