How to Ask for a Promotion: The 90-Day Plan That Works

Most people ask for a promotion the wrong way: they schedule a meeting, say they've been working hard, mention that it's been a while, and then feel blindsided when the answer is no — or worse, "let's revisit this next cycle." The problem isn't that they asked. It's that they asked without building a case first. A promotion isn't a reward for loyalty or effort. It's a business decision your manager has to justify to their manager. Your job is to make that justification easy. This guide gives you a concrete 90-day plan to do exactly that.

Promotions Are Approved Before the Conversation Happens

Here's the uncomfortable truth: by the time you're sitting across from your manager asking for a promotion, the answer is almost certainly already decided. Managers don't walk into those conversations undecided — they walk in having already formed a view based on months of observation, peer feedback, and their own political capital calculations. If you haven't been deliberately shaping that view, you've been leaving the outcome to chance.

The 90-day plan exists to shift that dynamic. Instead of lobbying in a single meeting, you're making the case continuously, so that when the formal conversation happens, your manager is basically confirming what they already believe — not being asked to take a leap of faith.

This also matters because most promotion decisions require sign-off from skip-level managers, HR, or a calibration committee. Your direct manager needs to advocate for you, not just agree with you. That means they need language, data, and conviction. Your job over 90 days is to give them all three.

Days 1–30: Diagnose the Gap and Align on Criteria

The first month is about intelligence-gathering, not action-taking. Before you can close a gap, you need to know exactly what the gap is.

Start with a direct conversation with your manager. Don't hint. Don't be coy. Say: "I'm targeting a promotion to [title] within the next six to twelve months. Can we talk about what that would require?" This does three things: it signals ambition (managers like knowing what their people want), it opens the door to honest feedback, and it puts the criteria on the table so you can be held accountable to them — and so can your manager.

What you're listening for:

• Specific gaps ("You need to be driving projects at a larger scope")
• Vague hedges ("It's about executive presence") — these need to be pushed into specifics
• Timeline signals ("We typically see people at your level for 18 months before promoting")
• Political context ("Headcount is tight right now, but that could change in Q3")

Also pull the formal leveling rubric if your company has one. Amazon, Google, Meta — most large tech companies publish internal leveling guides or have them available through HR. If you're at a smaller company, ask HR directly. These documents are gold because they give you objective language to use later.

By the end of month one, you should have a written list of three to five specific criteria that, if met, would make your promotion a straightforward decision.

Days 31–60: Execute Visibly at the Next Level

The single most common mistake ambitious engineers and ICs make is waiting to be promoted before doing the work of the next level. That's backwards. The promotion is the recognition of work you've already been doing — not a precondition for starting.

"Act at the level you want to be promoted to, and let the promotion catch up to you. If you wait for permission, you'll wait forever."

In month two, your goal is to create three to five concrete examples of next-level impact. What counts as next-level depends on your role, but in a software engineering context this typically looks like:

• Owning an ambiguous project end-to-end without being handed a spec
• Making a technical decision that materially affects the system architecture
• Unblocking or mentoring peers, not just completing your own tickets
• Driving cross-functional alignment (getting product, design, and engineering to agree on something hard)
• Proactively identifying and fixing a problem nobody asked you to find

The key word here is visibly. Doing great work in a vacuum is a career killer. You need to do the work and make sure the right people know about it. This isn't self-promotion in the cringe sense — it's documentation. Send a concise Slack message summarizing the outcome of the project you led. Write a brief post-mortem that gets shared with the team. Mention wins in your 1:1s not as bragging but as updates. Treat your career the way a product manager treats a product: ship it, then tell people what shipped.

Days 61–75: Build Your Evidence Package

Two-thirds of the way through your 90 days, stop executing for a moment and start documenting. You're building what I call the evidence package — the written record you'll bring into the promotion conversation and that your manager can literally copy-paste into their justification.

Here's the structure that works:

1. Impact summary: Three to five bullet points describing specific outcomes with numbers. Not "worked on the search ranking project" but "led the search ranking rewrite that reduced P99 latency by 35% and handled 10M+ daily transactions without incident."
2. Scope and ownership evidence: A list of projects where you had end-to-end ownership, including stakeholders involved and decisions made.
3. Peer and cross-functional feedback: Two or three quotes (with permission) from colleagues or stakeholders about your work. These don't need to be formal — a Slack message saying "Alex's architecture decision saved us three weeks" is perfectly usable.
4. Mentorship and leadership proof: If you've been coaching junior engineers, list who and what the outcome was.
5. Criteria checklist: Map each item from the criteria you established in month one to a specific piece of evidence. This is the most important part. It shows you listened, you executed, and you can prove it.

This document doesn't need to be pretty. It needs to be factual, specific, and scannable. One page of dense, concrete evidence beats five pages of narrative every time.

Days 76–85: Secure Advocates Before the Meeting

Your manager doesn't promote you alone. Even if they want to, they need cover — peer support, skip-level awareness, and sometimes HR sign-off. Which means you need advocates in the room you're not in.

This is where most people completely drop the ball. They focus entirely on their direct manager and ignore everyone else who influences the decision.

Here's what to do in days 76–85:

• Talk to your skip-level manager. You don't have to be explicit about the promotion. Ask for feedback on your work. Make sure they know your name and your impact. A 30-minute coffee chat where you share what you've been working on is enough.
• Tell peer advocates you're pursuing a promotion. Senior peers who respect your work can casually mention it in the right contexts. People do this for each other all the time — but only if they know it's needed.
• Request formal peer feedback if your company's review cycle allows it. Time it so the feedback is fresh when decisions get made.
• Ask your manager directly: "Is there anyone else whose input would be helpful in this decision? How can I make sure they have the right context?" This question is smart because it either surfaces blind spots or signals that you're organizationally savvy — both are good.

By the end of this phase, at least two people beyond your direct manager should know you're being considered for a promotion and should have positive things to say if asked.

Days 86–90: Have the Actual Conversation

Now you're ready for the formal ask. Schedule a dedicated 1:1 — not a casual end-of-meeting mention, a real block of time. Come in with your evidence package. Lead with specifics, not feelings.

The structure of the conversation:

1. State the ask clearly. "I'd like to discuss a promotion to [title]. I believe I've been operating at that level consistently and I want to make the formal case."
2. Walk through your evidence. Don't read it out loud — summarize it. "Over the past three months I led X, drove Y outcome, and mentored Z. Here's the written summary if it's useful for the review process."
3. Reference the criteria from month one. "Back in January we agreed the key criteria were A, B, and C. I want to walk through how I've addressed each."
4. Ask for a clear answer or a clear timeline. Don't accept "we'll see" without a date. "When can I expect a decision?" is a completely reasonable question.

If the answer is yes: great, get the details in writing — title, comp change, effective date.

If the answer is no or not yet: ask specifically what's missing and what the timeline looks like. If your manager can't answer those questions clearly, that tells you something important about whether this promotion will ever happen at this company.

If They Say No, You Have Options — Use Them

A no is only permanent if you accept it passively. If you've done the 90-day work honestly and the answer is still no, you now have three choices:

1. Reset and go again with a clearer criteria list and a new timeline. Some companies promote on 6-month cycles — missing one cycle isn't fatal.
2. Escalate or broaden your advocate network. Sometimes a direct manager is the bottleneck, not the committee. Understanding this changes your strategy.
3. Use the external market. A competing offer is still the fastest promotion tool in existence. If you've been operating at the next level and your company won't recognize it, another company will — often with a 20–40% comp increase attached. In 2026, Senior Software Engineer roles at major tech companies in the US are clearing $180K–$260K base, with Staff/Principal roles at $230K–$320K+. Know your market value and use it.

The 90-day plan also gives you something invaluable if you get a no: a documented record of your work that translates directly into interview talking points. You've already built your STAR stories. You're already ready to interview.

Next Steps

If you want to execute this plan, here's what to do in the next seven days:

1. Schedule a 1:1 with your manager this week specifically to discuss promotion criteria. Don't wait for your next regular check-in — book dedicated time and tell them what it's for.
2. Pull your company's leveling rubric. Find it in your internal wiki, ask HR, or look at external resources (Levels.fyi has level descriptions for most major tech companies). Read the description for the level above you, not your current one.
3. Start your evidence document today. Open a blank doc and write down every meaningful project you've touched in the last six months. Don't edit — just list. You'll refine it later, but the raw material needs to exist.
4. Identify two advocates outside your direct reporting line. Write their names down. Think about the last time they saw your work. Think about what you'd want them to say if asked about you.
5. Check your market value. Look at Levels.fyi, Glassdoor, and LinkedIn Salary for your title, location, and years of experience. If you're being underpaid relative to market, that context matters — both for the conversation and for your own decision-making if the answer is no.

The promotion conversation is the last ten minutes of a 90-day process. Do the work, document the work, make the case. The answer you get will reflect the preparation you put in — not the persuasiveness of a single conversation.

Related guides

• How Calibration Works in Tech in 2026 — What Happens Behind the Scenes of Your Review — Calibration decides ratings, promotion support, bonus outcomes, and sometimes who is considered low performer. This guide explains the 2026 tech review process and how employees can prepare without gaming it.
• Dual-state tax for remote work in 2026 — when you owe two states and how to plan — Remote tech workers can trigger tax obligations in more than one state. This guide explains residency, nonresident wages, convenience rules, withholding, credits, and the planning steps to take before a remote move.
• Gardening Leave vs Severance in 2026 — How to Tell the Difference and What to Ask For — Gardening leave and severance can both mean paid time away from work, but they differ on employment status, benefits, equity, bonus, restrictions, and when you can start the next job. This guide gives the questions and negotiation language to use before signing.
• PIP Survival Guide in 2026 — Surviving a Performance Improvement Plan When It Is Salvageable — A PIP is either a rescue plan or an exit track, and the first week is about telling the difference. This playbook shows how to clarify expectations, document progress, manage HR, and protect your downside.
• Return-to-Office Mandates in 2026 — Your Options, Your Leverage, and Your Exit Plan — Return-to-office mandates in 2026 are often about control, real estate, management preference, or attrition as much as collaboration. This guide explains how to assess your leverage, negotiate exceptions, protect your role, and build an exit plan if the mandate breaks your life.