The most reliable way to ask for a promotion is to build the case before the conversation: operate at the next level visibly for several months, document it in your own language, and then ask in a way that gives your manager a clear path to advocacy. Many promotion conversations stall not because the person did not deserve it, but because the case was never built. Promotions are often budget decisions, and a manager usually has to advocate to skip-levels and comp committees who do not know the candidate — the work done before the conversation is what gives a manager the material to argue for someone when they are not in the room.
What does "operating at the next level" actually mean?
It often helps to pull the career-level rubric for both the current level and the next one. The promotion conversation usually turns on consistent behavior matching the next-level rubric — not just one heroic project. Many people identify 3-5 next-level behaviors and gather concrete examples of themselves already doing them.
Common next-level patterns:
- IC → Senior: Owning ambiguous problems end-to-end, mentoring more junior teammates, influencing design without authority
- Senior → Staff: Setting technical direction across teams, multiplying others' impact, driving cross-functional alignment
- Staff → Principal: Defining problems that did not exist as problems before, shaping org-wide patterns, mentoring senior ICs
- IC → Manager: Coaching, hiring, performance management, delivery accountability for a group
How do you ask for a promotion, step by step?
1. Get the rubric in writing
Where a company has career ladders, a common first step is to pull them. Where it does not, many people ask their manager for the criteria. Without a rubric, the conversation tends to have no anchor and reduces to vibes.
2. Build the brag doc, 3-6 months in advance
A common approach is to track in real time, recording each accomplishment in STAR format (Situation, Task, Action, Result) and tagging it to the rubric line it demonstrates. After several months, this often yields 8-15 entries, mapped to next-level criteria, with quantified outcomes.
3. Confirm scope with your manager early
"I'm targeting promotion to [level] in the next [cycle]. What does the rubric tell you I'm currently demonstrating, and where are the gaps?" Many people have this conversation 3+ months before the formal cycle. When the feedback is vague, a common move is to ask for specifics: "What would 'consistently' look like? Can you give me an example?"
4. Solicit peer endorsements
Promotion committees often weight peer feedback. A common step is to ask 3-4 senior peers who have seen your work: "I'm putting together a promotion case. Would you be willing to write a short note about [the specific project where you saw my next-level work]?" It often helps to make it easy by giving them an angle, not just "say nice things."
5. Make the formal ask 4-6 weeks before the cycle
"Based on the work over the past [period] — [3 specific examples mapped to rubric] — I'd like to be put forward for [level] in this cycle. Here is my brag doc. What else can I provide to support the case?" Many people find this framing reads as a partnership, not an ask-for-approval.
6. After the cycle, get specific feedback regardless of outcome
If promoted: many people ask what would help them start operating at the level after this one. If not promoted: a common step is to ask for the 2-3 specific rubric gaps, what work in the next 6 months would close them, and whether the case can be revisited before the next formal cycle.
What red flags should you watch for?
- Your manager says "you're doing great" but cannot point to specific rubric matches (suggests they have not advocated yet)
- The rubric does not exist or shifts each cycle
- Peers at your level with less visible impact get promoted while you are told to wait
- "It's a budget issue this cycle" without a clear plan for next cycle
- Your manager admits the case is strong but says the committee "isn't ready"
- After a long lead-up, the feedback at decision time is brand new and you had no chance to address it
- Promotion requires a sponsorship or champion outside your team that you cannot reach without your manager's help — and your manager is not helping
What if something is structurally off?
It can help to consider whether the issue is performance, budget, or bias:
- Performance: Specific rubric gaps that can be closed. Many people make a plan for the next cycle.
- Budget: The manager is advocating but losing the budget conversation. A common step is to push for a written commitment to the next cycle with clear criteria.
- Bias: A pattern of peers with similar impact getting promoted while you do not. Some people choose to raise this with a skip-level or HR. The EEOC, which enforces the federal anti-discrimination laws, generally describes promotion as one of the employment decisions where it is unlawful to discriminate on the basis of protected characteristics such as race, color, religion, sex (including pregnancy, sexual orientation, and gender identity), national origin, age (40 or older), disability, or genetic information (EEOC, Prohibited Employment Policies/Practices; see also Title VII of the Civil Rights Act of 1964). Whether a particular pattern amounts to unlawful discrimination depends heavily on your situation, and your state's laws may add further protections. Some people document the pattern in case discrimination claims later become relevant and talk to an employment attorney about their options.
For potential bias situations — especially where you may be in a protected class and the pattern looks clear — many people consult an employment attorney before raising the issue internally, since how and when a concern is raised can have real consequences and the specifics depend on your situation.