How to Ask for a Promotion (And Actually Get One)

A LendingTree survey from October 2024 found that 82% of full-time workers who asked for a raise received one. Only 37% of workers believe that asking is the most effective path to higher pay – most assume strong performance alone will do it. That assumption is expensive.

I’ve seen this play out in a predictable way. Someone spends 2 years doing excellent work, assumes their manager is tracking it, and then watches a newer colleague get promoted first. The reason is almost always the same: the manager didn’t have the data. They manage 8 to 12 people. They’re not maintaining a running ledger of your specific wins.

Asking for a promotion isn’t a personality test. It’s a documentation and timing problem. Here’s how to handle both.

Build the case before you open your mouth

The conversation itself is maybe 10% of the work. The other 90% is what you do in the 3 to 4 months before it.

Start keeping a “brag sheet” – a running document you update every week with impact, not activity. “Shipped the authentication redesign” is activity. “Shipped the auth redesign that cut login failures by 31%, affecting 400K monthly active users” is impact. The distinction matters because your manager will need to justify your promotion to their manager, and impact statements are the currency they spend to do that.

Focus on these four categories when tracking your work:

• Revenue or cost: Did you ship something that drove growth or reduced spend? Tie the dollar figure to your work specifically.
• Scope increase: Are you owning systems, people, or decisions you weren’t responsible for 12 months ago?
• Cross-team influence: Who outside your direct team asks for your input? This is a proxy for senior-level behavior even before the title.
• Incidents you prevented: Unglamorous, but real. If you caught a data integrity issue before it hit prod, document it.

Don’t wait for performance review season to compile this. By then you’ll have forgotten three months of work, and so will your manager.

The conversation itself

Don’t ask: “I think I deserve a promotion.” That’s a demand dressed up as a question, and it puts your manager on the defensive immediately.

Ask instead: “I’ve been operating at the next level for about 6 months – I’d like to understand what the remaining gaps are, if any, so I can work toward closing them.” This framing does a few things. It presents your case implicitly rather than declaring it. It invites specific feedback rather than a yes/no. And it makes your manager a collaborator, not a gatekeeper.

After the meeting, send a follow-up email summarizing what you discussed – especially any gaps your manager mentioned. This creates a paper trail that benefits you. If your manager said “you need to lead a cross-functional initiative,” and you do that in the next quarter, you want that in writing somewhere.

Timing: when to have the conversation

Two windows work well. The first is 8 to 10 weeks before your company’s formal review cycle – early enough that your manager can build a case for you before headcount decisions are locked, late enough that your recent wins are fresh. If you don’t know your company’s review cycle, ask HR directly.

The second window is right after a visible win: a successful launch, a crisis you handled well, a quarter where your team outperformed. These moments create natural momentum. Your manager is already thinking about you positively. Capitalize on that.

What doesn’t work: asking during a stressful sprint, right after a difficult quarter, or when you’re visibly frustrated. I’d add one more situation nobody talks about – don’t ask during your own performance review meeting itself. That meeting is too constrained. Your manager is following a script. Schedule a separate conversation a week before or after.

What “no” actually means

A direct “no” is less common than people expect. What you’ll usually get is a non-answer: “not right now,” “let’s revisit in 6 months,” or some version of “keep doing what you’re doing.” These are not the same thing, and treating them as equivalent is a mistake.

If you hear “no” or a clear deferral, ask three follow-up questions before the conversation ends:

• What specific gaps need to close before a promotion would be on the table?
• What does “closing those gaps” look like in practice, with real examples?
• How will we measure progress, and when should we check in on it?

If your manager can’t answer any of those questions with specifics, that’s useful information. Vague answers after a clear deferral usually mean one of two things: the budget isn’t there, or the path upward is more limited than you thought. Either way, you now know something you didn’t before, and you can decide whether to keep investing in this role.

I’ll be honest: I don’t know how reliably managers follow through on “revisit in 6 months” promises when no one documented the conversation. My guess is less reliably than they intend. The follow-up email matters for this reason.

What we observe in promotion prep conversations

At LastRoundAI, we see candidates using mock interview practice to prep for more than just job interviews – increasingly, people use structured self-assessment to rehearse promotion conversations before having them with their actual manager. The pattern we notice: candidates who’ve articulated their impact out loud, even in a practice setting, give sharper, more confident answers when it matters. The act of verbalizing “here’s what I built and why it mattered” once before the real conversation seems to reduce the rambling that tanks otherwise strong cases.

This isn’t a controlled study, and I won’t pretend it is. It’s a pattern we see. Whether it holds for everyone is genuinely unclear.

One opinion that might be wrong

Most promotion advice focuses on making your case to your direct manager. I think this is the right place to start, but it’s often not enough – particularly at companies above 200 people. Promotions at those companies are usually calibrated across a committee, and your direct manager is one voice in that room. If they’re not well-connected or not assertive in those meetings, your strong case stays local.

Building relationships with skip-level managers and cross-functional leads isn’t political maneuvering – it’s making sure more than one person in the room has direct experience with your work. Others will disagree with this framing. Some people do get promoted through their direct manager alone. But in a company where calibration happens across a panel, having a single advocate feels like going into a vote with only one person in your corner.

You can also look at how compensation and leveling works at major tech companies to understand what “senior” or “staff” actually means in different organizations, which helps you frame your case in language that maps to your company’s criteria.

If you’re earlier in your career and thinking about career strategy alongside interview prep, understanding behavioral interview questions covers the same self-advocacy muscle in a different context – articulating impact, owning your work, and making your reasoning visible to someone evaluating you.