How to Ask for a Promotion as a Software Engineer (Script Included)

Asking for a promotion is uncomfortable. It feels like bragging. Like you're putting your manager on the spot. Like you might get rejected and make things awkward.

So most engineers don't ask. They wait. They hope their work speaks for itself. And they watch less qualified people get promoted ahead of them.

This guide will help you have the promotion conversation effectively—with preparation frameworks, actual scripts, and strategies for handling any response.

When to Have the Conversation

Timing matters. The best time to discuss promotion is:

3-6 months before your target promotion date. Promotions don't happen in a single conversation. You need time to address gaps and build your case.

When you have evidence, not just tenure. "I've been here for two years" is not a promotion case. "I've consistently performed at the next level for six months" is.

When your manager isn't overwhelmed. Don't ambush them during crunch time or right before a reorg. Pick a moment when they can give you their full attention.

In a scheduled 1:1, not Slack. This is a real conversation, not a casual mention.

The Preparation Checklist

Before the conversation, prepare:

1. Know the Expectations

Get your company's engineering ladder or leveling rubric. If one doesn't exist, ask your manager to describe what the next level looks like.

You can't argue you've met the bar if you don't know what the bar is.

2. Assess Yourself Honestly

For each dimension in the rubric:

• Do you consistently exceed expectations?
• Can you point to specific examples?
• Do others see what you see?

Be honest. If you have gaps, you'll address them more effectively by acknowledging them upfront.

3. Gather Your Evidence

Compile specific accomplishments that demonstrate next-level work:

• Projects you led (not just contributed to)
• Impact you created (with numbers if possible)
• Behaviors you demonstrated (mentoring, cross-team work, technical leadership)
• Positive feedback from peers and stakeholders

4. Anticipate Objections

What might your manager say no to? Prepare responses for:

• "You're not ready yet"
• "The timing isn't right"
• "We don't have headcount"
• "You need to improve in X area"

The Conversation Framework

Here's a structure that works:

Step 1: State Your Intent (1 minute)

Be direct. Don't bury the ask.

Script:

"I wanted to talk about my career progression. I believe I'm ready for promotion to [next level], and I'd like to discuss what that path looks like and whether we're aligned."

Don't apologize. Don't hedge. State what you want.

Step 2: Present Your Case (3-5 minutes)

Share your evidence, organized around the expectations for the next level.

Script:

"Looking at the expectations for [next level], here's where I see myself. For [technical leadership], I've led the [project name], which [specific outcome]. For [mentorship], I've been guiding [names] on [topics], and [evidence of their growth]. For [scope], I've been operating beyond my immediate team by [examples]."

Don't recite your entire resume. Focus on the strongest examples that map to next-level expectations.

Step 3: Ask for Feedback (5-10 minutes)

Invite honest assessment.

Script:

"That's how I see it. I'd love to hear your perspective. Where do you see me meeting the bar for [next level]? Where do you see gaps?"

Listen more than you talk. Take notes. Don't get defensive.

Step 4: Align on Next Steps (2-3 minutes)

End with clarity, regardless of the answer.

If they agree you're ready:

"Great. What does the timeline look like? What do you need from me to support the case in calibration?"

If they think you have gaps:

"I appreciate the honesty. Can we put together a development plan? I'd like to close these gaps in the next [timeframe]."

If the timing is wrong:

"I understand. When would be the right time to revisit this? What should I focus on in the meantime?"

Handling Common Objections

"You're not ready yet."

Don't say: "But I've been here two years!" or "But so-and-so got promoted."

Do say: "I appreciate you being direct. Can you help me understand specifically where I'm falling short? I want to make sure I'm focused on the right things."

Get specifics. Vague feedback like "you need more experience" isn't actionable.

"The timing isn't right."

This might mean: budget constraints, reorgs, or genuine bad timing.

Do say: "I understand. I want to make sure I'm positioned for the next cycle. What would make my case undeniable when the time is right?"

Don't accept perpetual delay. If "not now" keeps happening, address that directly.

"We don't have headcount."

Promotion shouldn't always require headcount, but sometimes it does.

Do say: "I understand the constraints. A few questions: Is this a temporary freeze? Are there ways to recognize my work in the meantime? What happens if headcount opens up?"

"You need to improve in X area."

This is actually useful feedback—if it's specific.

Do say: "Thanks for being specific. Can we talk about what 'good' looks like in this area? What would demonstrate that I've closed this gap?"

Then create a plan to address it.

After the Conversation

If You Got a Yes

Celebrate (briefly), then focus on:

• What you need to do to support the promotion case
• When calibration happens and what the process looks like
• Continuing to perform at the level you've demonstrated

If You Got a No (With a Path)

This is actually a good outcome. You have clarity.

• Document the gaps you discussed
• Create a development plan with your manager
• Set check-in milestones
• Revisit in 2-3 months

If You Got a Vague No

This is the worst outcome. Push for clarity.

Follow up with: "I want to make sure I understand. Is promotion off the table for the foreseeable future, or are there specific things I can work on? I need to know how to focus my energy."

If you can't get clarity after multiple attempts, that's a signal about your manager or company.

The Promotion Case Document

For important promotion conversations, consider preparing a one-page document:

Header: Your name, current level, target level, date

Summary: 2-3 sentences on why you're ready

Evidence by Competency: For each dimension in the rubric, 1-2 bullet points with specific examples

Development: Any areas you're actively working on

Request: Clear statement of what you're asking for

Share this with your manager before or during the conversation. It helps them advocate for you in calibration.

What Most Engineers Get Wrong

Waiting to be noticed. Your manager has their own problems. They're not tracking your career as closely as you are. If you don't advocate for yourself, no one will.

Making it about time. "I've been at this level for three years" doesn't matter. What matters is whether you're performing at the next level.

Comparing to others. "But Sarah got promoted" is never a good argument. You don't know Sarah's full story, and it makes you look petty.

Getting emotional. Rejection stings, but reacting emotionally hurts your case. Stay professional, even if you're frustrated.

Not following up. One conversation is rarely enough. Regular check-ins on your development plan show commitment.

Related reading

• Am I Ready for Promotion? A Self-Assessment Guide — Use this before the conversation to make sure you're aiming at the right moment.
• How to Write a Self-Review That Gets You Promoted — The self-review is your manager's primary source material in calibration.
• How to Keep a Brag Document That Actually Gets You Promoted — Build the evidence base that makes the conversation easy.

Build Your Promotion Case

Seekersy helps you document your wins, track your growth, and prepare for promotion conversations with evidence instead of guesswork.

Start Building Your Case