Asking for a promotion
Ask for the next level with evidence, and explain a 'not yet' so it motivates instead of hurts.
Case study: Siddharth's five years of waiting
Siddharth, a developer in Hyderabad, had been a Software Engineer 2 for five years. He fixed outages, reviewed code for the whole team and never complained. When he finally asked his Munich manager, Katrin, why he wasn't promoted, she was surprised. "I didn't know you wanted to be a senior. You never said." She opened the career framework and showed him the gap: senior engineers lead design reviews and drive work across teams. Siddharth had done neither, because nobody had asked him to. They agreed he would lead the next design review. Eleven months later he was promoted.
Takeaway: Promotions go to people who ask for them and work against the written criteria. Silence is not a strategy.
Many of us believe good work is automatically rewarded, and asking for a promotion feels pushy. In global companies, managers expect you to state your ambition and ask what the gap is.
Asking for promotion
Goal: State your ambition clearly and leave with the specific gaps, a plan and a timeline.
Step by step
- State the goal. Say clearly that you want the next level.
- Map to criteria. Show evidence against the written level expectations.
- Ask for the gap. What's missing, in their honest view?
- Agree a plan. Specific opportunities, a timeline and check-ins.
Say this, not that
| I'd like to be considered for promotion to senior engineer. | If possible, kindly consider me for some growth. | Vague wording lets the topic slip away. |
| Looking at the career framework, I'm already doing three of the five senior expectations. | I've been here five years, so it's my turn. | Criteria make it about evidence, not opinion. |
| In your honest view, what's the biggest gap between me and the next level? | The honest gap is the most useful thing you'll hear all year. | |
| Could I lead the next design review to build that experience? | I will try to improve on all fronts. | Ask for a specific opportunity, not general improvement. |
| Could we review progress every month and aim for the next promotion cycle? |
Model conversation
- You
- Katrin, thanks for the time. I'd like to be considered for promotion to senior engineer.
- Katrin
- Good to hear you're thinking about it. Tell me why now.
- You
- Looking at the framework, I already mentor two engineers, handle on-call for our service, and review most of the team's code.
- Katrin
- All true, and valuable. The gap I see is technical leadership across teams.
- You
- That's helpful. What would that look like in practice?
- Katrin
- Leading a design review, and driving a decision that involves the platform team.
- You
- Could I lead the design for the new notifications service? It touches the platform team.
- Katrin
- Yes, that's a perfect fit. Let's review progress monthly and aim for the October cycle.
Explaining 'not yet'
Goal: Be honest that they're not ready, name exactly what's missing, and commit to helping them get there.
Step by step
- Thank and validate. Recognize the ambition and the strengths.
- Be clear. Say 'not yet' plainly. Don't leave false hope.
- Name the gap. Specific missing skills, mapped to the criteria.
- Build the plan. Opportunities, a timeline and how you'll sponsor them.
Say this, not that
| Thanks for raising it. I'm glad you're thinking about the next step. | Promotions are not in my hands. | Deflecting makes people feel stuck and unsupported. |
| I don't think you're ready this cycle, and I want to be honest about why. | Let's see, maybe next time. | Vague hope breeds resentment when it doesn't happen. |
| Your code quality is senior level. What's missing is leading decisions across teams. | You need to show more ownership. | Strengths plus one clear gap is easy to act on. |
| I'd like you to lead the design for the next platform integration. | ||
| If that goes well, I'll put you forward in the October cycle, and I'll tell you honestly how it's going. |
Model conversation
- Siddharth
- I wanted to ask about promotion. I've been at this level for five years.
- You
- Thanks for raising it, Siddharth. I'm really glad you did. Can I be honest with you?
- Siddharth
- Yes, please.
- You
- I don't think you're ready this cycle. Your code and your reviews are senior level. The gap is leading technical decisions across teams.
- Siddharth
- But nobody ever gave me a chance to do that.
- You
- That's fair, and that's partly on me. So let's fix it. I'd like you to lead the design for the payments integration.
- Siddharth
- Okay. And if that goes well?
- You
- Then I'll put you forward in October, and we'll review progress every month until then.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.