What 'Strong Promote' vs 'Promote' vs 'Promote with Reservations' Actually Means

You've seen the phrases on Blind. Someone posts: "Got SP from the committee" or "My manager said my case was 'promote with reservations' — what does that mean?" The replies range from congratulatory to ominous. Nobody defines the terms. Everybody seems to know what they mean.

Here's the thing most engineers miss: at most big tech companies, these labels don't formally exist. There is no checkbox on a committee form that says "Strong Promote." There is no official rating called "Promote with Reservations."

But the concept behind them is real. When a promotion committee or calibration room discusses your case, there is a temperature. A case can sail through in three minutes with head nods around the table, or it can trigger twenty minutes of debate before landing on a reluctant yes, a deferred decision, or a flat no. That temperature — the strength of the room's conviction — carries real consequences for your compensation, your reputation inside the organization, and how the next cycle goes.

Understanding what these informal labels actually map to, company by company, changes how you prepare.

Where "Strong Promote" comes from

The phrase almost certainly migrated from Google's hiring process. Google's interview rubric uses a seven-point scale from Strong No-Hire to Strong Hire, with gradations like Leaning Hire and On The Fence in between. Engineers who went through that system carried the language into conversations about promotions.

The problem is that Google's promotion committee doesn't use that scale. The committee votes yes or no on each packet. The outcome is binary: promoted or not promoted. There is no formal "Strong Promote" or "Lean Promote" option.

The same is true at Meta and Microsoft. Neither company uses a formal voting label for promotions. Meta's calibration room validates or pushes back on a manager's recommendation without casting named votes. Microsoft's "aunts and uncles" — peer managers who challenge promotion cases — either find the case convincing or they don't.

Amazon is the exception. Their promotion panel uses a formal three-tier voting system: Green (Inclined), Amber (Concerns to clarify), and Red (Not Inclined). The vote happens in two rounds, with two or more red votes in either round killing the case immediately.

So when someone on Blind says they got "Strong Promote," they're not quoting a company form. They're describing a feeling — or a signal their manager relayed after calibration — about how convincingly their case landed. That feeling, informal as it is, maps to something real.

What each level of conviction actually looks like

Even without formal labels, the strength of the room's response falls into recognizable patterns. Here is what each one looks like across companies and what it means for the engineer.

The clear yes

Your manager presents the case. Another manager in the room nods — they've seen your work on a cross-team initiative. A third asks one clarifying question and the answer is specific and immediate. The room moves on in under four minutes.

At Google, this is a unanimous or near-unanimous committee vote. At Amazon, it's all-green in the first round with no amber votes. At Meta, the calibration room validates the recommendation without pushback, and the VP approves without adjustment. At Microsoft, the "aunts and uncles" ask their challenge questions and the manager answers each one with concrete examples.

What it means for you:

• Compensation. You land in the new band. At Microsoft, where impact descriptors directly affect rewards points, an Exceptional Impact rating — the kind associated with a clear promote — results in meaningfully higher compensation adjustments than Successful Impact.
• Perception. Your manager emerges from calibration with credibility intact. They spent political capital and won cleanly. That makes the next conversation about your career easier.
• Next cycle. You start the new level with no baggage. No caveats following you. No whispered concerns from the committee that your manager has to manage.

The contested yes

Your manager presents the case. Another manager pushes back: "How is this different from solid L5 work?" Your manager answers, but not crisply. A ten-minute debate follows. Eventually the room agrees, but not enthusiastically. At Amazon, the first-round vote comes back with one or two amber votes, triggering a discussion phase. By round two, the ambers convert to green — but one red vote persists. The promotion goes through with a maximum of one red.

What it means for you:

• Compensation. You still get promoted. But the concerns raised in the room can affect where you land in the new band, especially at Amazon where your Organizational Leadership Review (OLR) rating going into the promotion affects band placement. At other companies, the impact is subtler — your manager may have less leverage to negotiate a strong equity refresh if their case wasn't clean.
• Perception. The red vote or the pushback gets documented as development areas. Your manager now carries a note that says "promoted, but the room had concerns about cross-team scope" or "passed, but feedback cited leadership gaps." That note doesn't disappear.
• Next cycle. You start the new level under a microscope. If the concerns the room raised don't get addressed, your first review at the new level can be rough. A contested promotion followed by a mediocre first review is a pattern that stalls careers.

The near-miss

Your manager makes the case. The room isn't convinced. At Google, the committee splits and the split resolves to no. At Amazon, two or more red votes appear in either round and the promotion is rejected immediately. At Meta, the calibration room pushes back hard enough that the VP doesn't approve it. At Microsoft, the aunts and uncles block the case with questions the manager can't answer.

This is the outcome most engineers experience when they hear "not this cycle."

What it means for you:

• The committee may provide specific feedback — "needs more cross-team impact" or "track record at this scope is too short." Engineers who get specific feedback and address it directly often succeed next cycle.
• The committee may provide vague feedback — "not ready yet" or "strong but not there." This is the dangerous version. Without specifics, engineers spin their wheels for multiple cycles without knowing what to change. If you get vague feedback, push your manager to translate it into something concrete. What exactly did the room say? Which dimension was the gap?
• Budget and timing may have been the real blocker. Vince Sacks Chen, an engineering manager who wrote publicly about calibration, described how during tight budgets the same case that would pass in a growth year gets rejected. If your manager tells you the case was strong but the budget ran out, that's a different problem than a weak case — but it requires different preparation for next cycle (timing, not evidence).

Why the line between "clear" and "borderline" matters more than you think

You might think a promotion is a promotion. Either you got it or you didn't. But the strength of the yes — or the closeness of the no — shapes what happens next.

Borderline promotions create fragile starts. An engineer who barely squeaked through is starting the new level with documented concerns. Their first review at the new level carries implicit pressure to prove the committee wasn't wrong. That pressure can lead to the exact pattern that keeps people stuck: overworking on safe projects instead of taking the scope risks that demonstrate the new level.

Near-miss rejections can actually be the better outcome if the feedback is specific. An engineer who gets told "you need six more months of cross-team scope" and gets promoted cleanly next cycle starts the new level without caveats. The engineer who gets pushed through on a split vote starts under scrutiny.

The Pragmatic Engineer's analysis of promotion calibrations found that committees are designed to prevent false positives — promoting someone too early — not false negatives. The organizational cost of a mis-leveled employee (peer resentment, performance issues, having to manage them back down) is seen as higher than the cost of making someone wait an extra cycle. That asymmetry means borderline cases almost always lose.

What separates a clear case from a borderline one

The promotion panel isn't evaluating whether you're good at your job. Everyone being discussed is good at their job. The panel is evaluating whether the evidence for promotion is unambiguous enough that the room can say yes quickly and move on.

Here is what makes the difference:

Quantified outcomes, not activity descriptions. "Built the alerting pipeline" is activity. "Redesigned the alerting pipeline, reducing false pages by 70% and cutting mean-time-to-acknowledge from 12 minutes to 3" is an outcome. Outcomes survive follow-up questions. Activity descriptions invite them.

Sustained evidence, not a recent sprint. If your strongest project shipped last month, the panel doesn't have enough signal to assess lasting impact. Kevin London, an Amazon engineer, described his first promotion attempt being rejected because his strongest work had shipped too recently. Panels want two or more quarters of consistent next-level evidence.

A second voice in the room. When another manager has firsthand experience with your work, your manager's pitch gets validated by someone with no incentive to inflate it. When only your manager speaks, the room is being asked to trust one person's word. That's a harder sell. Cross-team projects, tech reviews, and incident responses that touch other teams all build this recognition.

A manager who can survive the follow-up questions. Other panelists will probe: "How is this different from what someone at the current level would do?" If your manager doesn't have specific, prepared answers, the case deflates in real time. This is why writing the documented case your manager can take into the room is the highest-leverage thing you can do before review season. You're not just building your case. You're arming your advocate.

Peer reviews that tell a consistent story. Susnata Basak, a former Google engineer who served on promotion committees, described how the strongest packets had peer reviews where multiple reviewers independently cited the same behaviors and impact. The weakest packets had generic feedback that could describe anyone at any level: "great teammate," "solid engineer."

How to shift your case from borderline to clear

If your manager has told you that you're close, or if you've been through a cycle and gotten vague "not yet" feedback, the gap is almost never about doing more work. It's about making the existing work legible to a room of people who don't know you.

Ask your manager what the room said, specifically. Not "what do I need to work on" — that gets you generic coaching. Ask: "What did the other managers push back on? Which dimension was the gap? What would they need to see next time?" If your manager can't answer, the feedback didn't reach them clearly enough to be useful, and making sure they're equipped to fight for you next time should be the focus.

Build the second voice before the next cycle. If your case was borderline because only your manager could speak to your work, the fix isn't working harder in your current scope. It's working on something that puts your name in front of another manager. A cross-team project. A technical review where adjacent teams see your output. An incident response where you lead the resolution and the postmortem reaches beyond your team.

Write the case document before your manager asks for it. Two weeks before review season, hand your manager a half-page with your two strongest projects, quantified outcomes, and a clear level claim. Most managers don't prepare well for calibration — not because they don't care, but because they're managing eight people and calibration prep is one of twenty things on their plate. The engineers who make their manager's job easy get promoted more cleanly than the ones who expect their manager to reconstruct six months of work from memory.

Address the documented concern directly. If last cycle's feedback said "needs more cross-team scope," your next six months should include a project that demonstrably involved other teams. If the feedback said "track record too short," don't rush to resubmit — let the evidence accumulate for one more cycle. A clear yes next time is worth more than a contested yes now.

---

The committee meets without you. CareerClimb makes sure the evidence speaks for itself — the app helps you capture wins as they happen, frame them as quantified outcomes, and build the documented case that makes the room's decision easy. Download CareerClimb and start building your case before the next panel convenes.