A performance review or a promotion decision almost never happens in the room it's discussed in — it happens in the weeks beforehand, in whether your manager already has the evidence they need to make the case for you.
3 min read
By the time a formal review conversation happens, the outcome is usually already largely settled — through calibration discussions among managers, written self-assessments, and peer feedback collected in advance. Waiting until review week to think about what you accomplished means reconstructing months of work from memory, under time pressure, after most of the actual decision-making window has already closed. This is exactly why lesson 11's running progress log matters: it's the raw material this whole process depends on.
A promotion case is fundamentally an argument, made with evidence, that you're already consistently operating at the next level — not a request based on tenure or effort alone. Most leveling frameworks describe expected scope, autonomy, and impact at each level; a strong case maps specific, real examples from your recent work directly onto those specific criteria, rather than presenting a general list of accomplishments and hoping the mapping is obvious to whoever reviews it. Asking a manager directly, "what would 'operating at the next level' concretely look like for someone in my role?" turns a vague aspiration into an actionable checklist.
Many companies calibrate performance ratings and promotions across a whole team or org, meaning a strong individual case can still lose to budget, headcount for that level, or simply being compared against an unusually strong peer group in a given cycle. Understanding this doesn't make a rejected case sting less, but it does correctly separate "was my work good enough" from "did this specific cycle's constraints work in my favor" — conflating the two leads to overreacting to a single cycle's outcome.
Self-advocacy works best when it's specific and evidence-based — "I led the migration that reduced deploy time by 40% and mentored two new engineers onto the team" — rather than vague self-promotion ("I've been working really hard this quarter"). The same specificity that makes a resume bullet or a behavioral story land (lessons 4 and 6) is exactly what makes a self-assessment or promotion case land too — this is the same underlying skill, reused across every stage covered in this domain.
Some signals are worth taking seriously rather than rationalizing away: no real growth or new challenge for over a year despite raising it directly, a pattern of promises about scope or compensation that don't materialize, or a values misalignment that keeps resurfacing rather than resolving. None of these are decisive alone, and a single hard quarter isn't the same as a real pattern — but a genuine pattern, examined honestly, is worth acting on rather than waiting out indefinitely.
Every job search compounds on the last one: a stronger resume (lesson 4), a sharper portfolio (lesson 8), a better-stocked story bank (lesson 6), and a clearer sense of what you actually want in an offer (lesson 10) all carry forward and get refined further next time. Career growth, in that sense, isn't a separate skill from interviewing — it's the same handful of skills from this domain, practiced repeatedly and getting sharper with each real cycle.
Check your understanding
A quick comprehension check — not tracked, not graded, just for you.
1. Why is a performance review's outcome usually already largely settled before the review conversation happens?
2. What is a promotion case fundamentally an argument for?
3. What does calibration add as a real constraint on top of an individual's promotion case?
Interviewing & Career Growth