How to Ask for a Promotion as a Software Engineer
Ready to ask?
Get coaching on how to have the conversation.
You've been doing next-level work for months. You've led projects your peers wouldn't touch, unblocked teams outside your own, written the design docs your manager sends to other people as examples. You're not sure why you're still at the same level.
The reason, usually: you never asked. Knowing how to ask for a promotion as a software engineer is a skill, and most engineers never develop it because the conversation feels riskier than it is.
On Reddit's r/cscareerquestions, engineers who get passed over describe a consistent pattern. They assumed their manager noticed, assumed the work spoke for itself, assumed the system was watching. Then someone else got promoted and they found out their manager didn't have a documented case ready when nominations opened.
Asking for a promotion feels risky. It feels like admitting you weren't good enough to be noticed on merit. It feels like the conversation that could make things weird. So engineers avoid it and keep working harder, hoping the evidence piles up on its own.
Here's what actually happens when you don't ask: your manager goes into calibration without a prepared case. They reconstruct your wins from memory, under pressure, while defending you against skeptical peers. If they can't point to specific outcomes on demand, the nomination dies. You did the work. It just wasn't organized in a way anyone could use.
Why asking is easier than you think it is
The fear of looking entitled is almost never justified. Most managers want to promote people. A promotion means their report has grown, which reflects well on them. When an engineer comes in with a clear, evidence-backed ask, the manager's reaction is almost always relief. Now they have what they need.
What managers don't want is an engineer who demands a promotion without evidence, or who asks once and then gives up. A structured, patient conversation over several months is the opposite of entitled. It's professional.
The risk of asking is low. You either get alignment on what you need to do, or you confirm that your manager is already in your corner. Either outcome is better than silence.
When to have the promotion conversation
Timing is one of the most common things engineers get wrong. Asking too close to nominations (or after the window closes) puts your manager in an impossible position.
Most tech companies open promotion windows once or twice a year. Once nominations are submitted, the list is nearly locked. Walking into your manager's office two weeks before your performance review to mention you'd like a promotion isn't a promotion ask. It's information they can't act on.
| Timing | What to do |
|---|---|
| 6–9 months before the window | Have Conversation 1: get clarity on what the next level requires |
| 3–4 months before | Have Conversation 2: check whether what you're doing is landing as evidence |
| 4–6 weeks before nominations close | Have Conversation 3: make the direct ask |
| After nominations close | Too late for this cycle. Start building for next one. |
Find out when your company's promotion cycle opens. Ask your manager directly: "When do you need to submit names for promotion consideration?" That date is the anchor for everything else.
Three conversations, not one big speech
Most engineers imagine the promotion ask as a single high-stakes moment, the formal declaration that they're ready. That framing is why people avoid it. The stakes feel enormous, so the conversation never happens.
What actually works is three shorter conversations over several months. Each one is low-stakes. Together they add up to a manager who knows your case, has helped shape it, and walks into calibration prepared to defend it.
Conversation 1: Get clear on the bar
Six to nine months before the promotion window, schedule a dedicated career conversation. Tell your manager in advance what you want to discuss, not buried in a regular check-in. If you've never had this kind of conversation before, how to have a career conversation with your manager walks through the setup and questions that make it productive. Then be direct:
"I want to get to [next level] in the next 12-18 months. I want to make sure I'm working on the right things. What would you need to see from me to feel confident supporting a promotion case?"
You're not asking to be promoted. You're asking for clarity on what a strong case looks like.
What you learn here shapes the next six months. Your manager might say your scope is too narrow. You haven't owned anything at the scale the next level requires, which means volunteering for cross-team work. They might say your work is solid but not visible outside your immediate team. That means writing more design docs, presenting in broader engineering forums, sending weekly updates that get forwarded up. Or the gap is judgment: they want to see you make decisions without checking in for confirmation on things you could handle yourself.
If you get vague non-answers ("just keep doing what you're doing"), push:
"If I'm coming to you 12 months from now asking about promotion, what would I want to have done by then?"
That question forces specifics.
Conversation 2: Check whether it's working
Two to three months before the window, come back:
"I've been focused on [the things from Conversation 1] for the past few months. Where do you think my case is strongest right now? Where would you want more evidence before feeling confident putting my name forward?"
Two things happen in this conversation. Your manager surfaces gaps while there's still time to close them. And they start articulating your wins out loud, which is exactly the work they'll need to do in the calibration room.
If they say you're in good shape, ask them to be specific: "What would you point to as the strongest thing I've done this cycle?" If they can't answer quickly, you have a visibility problem, not a performance problem. There's still time to fix it.
Conversation 3: Make the ask
Four to six weeks before nominations close:
"I want to put my name forward for [next level] this cycle. This year I [2-3 specific contributions with outcomes]. I think this reflects sustained performance at the next level. Would you support me being considered?"
The ask is short. The preparation happened in Conversations 1 and 2. You're asking for a yes or a no. By now, nothing should surprise either of you.
If they say yes: find out what they need from you for the nomination packet, and when the window closes.
If they say "not yet": keep reading.
When the answer is "not yet"
Don't accept vague feedback. "Not yet" is not something you can act on.
Ask: "What would you need to see from me to say yes next cycle?"
If they give you concrete criteria, write them down and send a follow-up the next day:
"Based on our conversation, I'm planning to focus on X and Y before the next cycle. Does that match what you're thinking?"
This creates a record and makes the criteria harder to quietly shift.
If they stay vague despite your asking, push once more: "Can we agree on two or three specific things that would make you confident putting my name forward?"
A manager who won't name specific criteria is usually dealing with one of a few things: they haven't been paying close enough attention to your work, they don't have the organizational pull to get your nomination through calibration, or there's a concern they haven't said out loud. Ask: "Is there anything you've seen that's given you pause that we haven't talked about?" That question surfaces the real blocker.
After any of these conversations (including the ones that go well), send a short recap: "Based on what we discussed, my understanding is [X, Y, Z]." It creates a trail and makes any agreement harder to walk back.
The case that makes the conversation possible
These conversations only land if there's evidence behind them.
For each major contribution, you need to know what you did, what the scope was, and what changed as a result. When Conversation 3 arrives, you want to walk in with a short summary your manager can use directly, not something you reconstruct from memory over a weekend.
The difference matters in calibration. A manager can argue for "she led the API migration that cut timeout incidents by 40% and unblocked two dependent teams" in a room full of skeptical peers. They cannot argue for "she did really solid work this year." One survives a challenge. The other doesn't.
If you've been logging wins throughout the year, building that summary is mostly assembly work. If you haven't, you're starting from scratch against people who have been tracking everything.
The engineers who get promoted don't have better work. They have better documentation of the same caliber of work. And they had the conversation early enough for their manager to actually use it. If you haven't yet mapped where you want your career to go at a higher level, career pathing for software engineers helps you get that clarity before the promotion conversation.
CareerClimb's AI coach Summit helps you prepare for the promotion conversation with your specific situation in mind: your manager, your company, your gaps. Log your wins through the cycle and when it's time to ask, you'll have the evidence ready. Download the app to start building your case.
