How to have a career conversation with your manager about promotion
Promotion talk with manager?
Get coaching on exactly what to say.
Here's a number that should make you uncomfortable: surveys suggest only about 23% of professionals have ever had an explicit conversation with their manager about promotion.
Everyone else is waiting for it to come up naturally, assuming their manager can read what they want, or too worried about how it'll land to say anything at all. Meanwhile, managers walk into promotion calibration meetings without knowing their engineers' goals, or they go in to advocate but without anything concrete to work with.
This is fixable. Here's how to actually have the career conversation: what to say, when to say it, and how to make sure it moves your case forward instead of just producing a vague "let's circle back."
Why your manager probably doesn't know you want a promotion
About 6 in 10 managers say they don't know their direct reports' career goals. That's not because managers don't care. It's because most engineers never say anything directly.
Engineers get told from day one that good work gets noticed and rewarded. So they ship features, fix bugs, write solid code, and wait. They assume the manager is watching, tracking, connecting the dots.
The manager is handling incidents, running meetings, and managing six other people. They're not connecting your dots. You have to do that yourself.
One of the most upvoted pieces of advice on r/cscareerquestions on this topic captures it well: your manager goes into calibration fighting for you, but they can only fight as hard as the case you've built. If you haven't told your manager you want to be promoted, at what level, and with what timeline in mind, they can't build your case internally. They show up without ammunition.
When to have the conversation
Not during the two weeks before review submissions close. That's too late.
The right time is four to six months before the promotion cycle opens. Or at the start of a new project. Or right after you've gotten positive feedback on something significant. The goal is to start when there's enough runway to act on what you learn.
If you're new to a team or company, wait until you've shipped something real. Around 90 days is a reasonable window. You've proven you can do the work, and you have a concrete track record to point to.
A rough timing guide:
| Situation | When to have it |
|---|---|
| Promotion cycle opens in October | Start in March or April |
| Just joined or just wrapped a major project | Now is fine |
| Already in review season | Have it anyway, but set expectations. This cycle probably isn't the one. |
The biggest mistake is waiting until review season has already opened. By the time review deadlines arrive, calibration conversations are often already happening informally. You want your manager thinking about your case before those conversations start.
How to prepare before you walk in
Don't schedule this cold. Walk in with three things ready.
First, know the specific level you're targeting. Not "the next level" in the abstract. Know the actual title and designation: L5, Senior SWE, Staff Engineer. The more specific you are, the easier it is for your manager to assess where you stand.
Second, pull 3-4 concrete examples of work that demonstrates next-level impact. "I led the migration of our authentication service, which cut failed logins by 40% and reduced on-call volume for the team" is more useful than "I worked on backend infrastructure." Specific project, specific outcome, specific scope.
Third, prepare your main question: what's missing? This reframes the whole conversation. Instead of coming in and making a demand, you're asking for a gap analysis. "Here's what I think I've done. Where are the holes?" is much more productive, and managers respond to it better because it doesn't put them on the defensive.
Before the meeting, read your company's promotion criteria. Most large tech companies publish level expectations or have internal documentation on what the next level requires. Knowing that document well signals that you've done the work. It's easier for a manager to advocate for someone who can clearly articulate what level they're targeting and why they think they're ready. If you haven't mapped out what the next two or three levels look like at your company, the career pathing guide is worth reading before you walk into this conversation.
What to actually say
The conversation doesn't need to be a formal negotiation. It can be this simple:
"I want to talk about my career path. I'm targeting [level] this cycle, and I'd love your read on where I stand and what I should be focusing on to get there."
That opens the door without demanding an answer. It makes clear you've thought about this specifically, and it frames the conversation as collaborative rather than confrontational.
From there, two things usually happen.
Your manager already has thoughts. They've noticed the same gaps you suspect, or they're more optimistic about your readiness than you expected. Either way, you're getting actual signal instead of guessing.
Your manager hasn't really thought about it yet. They'll say something like "let me think about what you'd need to get there." That's also useful. You've triggered them to actively consider your promotion instead of defaulting to status quo.
Questions that produce useful answers
Vague questions get vague answers. Ask specific things:
- "What's the one area where I'm furthest from the next level right now?"
- "Is there a project or scope of work that would make my case obvious?"
One more worth asking, even if it's uncomfortable: "If the promotion cycle opened tomorrow, what would be the strongest objection to promoting me?"
That question is blunt. Some managers will hedge. But the ones who engage with it honestly give you the most useful answer you can get. They're basically telling you what you'll be up against in calibration, where other managers will try to poke holes in your case. Your manager preparing you for that conversation is exactly what you want.
If your manager is vague
Sometimes managers give answers like "just keep doing what you're doing" or "you're on a good path." Those answers mean nothing.
Push gently: "Can we get specific? What does the next three months need to look like for the promotion conversation to be easy?" If they still can't give you something concrete, that's information too. It might mean the criteria aren't well-defined at your company, or that your manager isn't sure how to advocate for you yet, or that there are factors beyond your individual performance at play. All of that is worth understanding before you invest another six months of work.
What your manager needs from you
Your manager is your advocate in the calibration process. But they need material to work with.
Give them a clear statement of your promotion goal (level and rough timeline). Give them your strongest pieces of evidence, framed around impact rather than activity. Give them regular updates between now and the cycle so they're not presenting stale information. And give them any context about your work that might not be visible to leadership. That includes cross-team projects, things you did for other teams, or situations where you went well beyond your defined scope.
If your manager knows you want L5 by the fall cycle, has three examples of your work mapped to L5 criteria, and has been getting updates from you for two quarters, they walk into calibration with an actual case. If they have none of those things, they're improvising.
For deeper context on how to build that case, the article on how to ask for a promotion as a software engineer covers the full promo packet framework.
After the conversation
The meeting itself doesn't do much if you don't follow up.
Send a short message that same day summarizing what you heard. Something like: "Thanks for the time. My understanding is that cross-team visibility is the main gap right now. I'm going to focus on [specific project] over the next two months. Should we check in again in April?" This confirms you were listening and creates a record you can point back to if things go sideways later.
Before you leave the room, also set a date for the next check-in. "Let's revisit this in 60 days" only works if you put it on the calendar before the conversation ends. Without a specific date, the conversation disappears. If the conversation reveals that the promotion timeline is longer than expected, this is also the right moment to raise compensation. How to ask for a raise covers how to have that conversation without derailing the promotion track.
After that, log what you're shipping between now and the follow-up. Every significant piece of work should be captured somewhere. Not for your self-review, but for your own tracking. When the next conversation happens, you want to be able to say "here's what changed since we last talked," with specifics.
The mistake that kills most of these conversations
Treating it as a one-time ask.
Engineers often have one promotion conversation, hear "not this cycle," and either give up or wait a year to bring it up again. Neither helps. "Not this cycle" is not a no. It's information. What specifically needs to happen? In what timeframe? With whom does it need to be visible?
If your manager says you're not ready, the follow-up is: "What would ready look like? Can we be specific?" Get a list. Get a timeline. Get agreement to revisit on a set date. Don't walk out of that conversation with nothing concrete.
If your manager genuinely can't define what readiness looks like, or if you keep having this conversation and nothing changes, that's a different problem. It might be a manager who doesn't have the influence to promote you, or structural issues with how your company handles promotion decisions. Both of those are solvable, but only once you've identified which one you're dealing with. When the issue is your manager's influence rather than your readiness, getting your manager to actively fight for your promotion is a separate skill worth building.
CareerClimb's AI coach Summit helps you prepare for exactly this kind of conversation. Before your next 1:1, you can talk through your case, figure out what evidence is strongest, and work out which questions to ask. Summit knows your specific situation, your manager's patterns, and what you've been working on. When the conversation happens, you'll have something real to bring to it. Download CareerClimb
