1on1 at Google: How to Prepare for Promotion Discussion

Quick Answer

A Google promotion discussion is not a plea for approval; it is a proof test for whether your manager can defend a higher level in calibration. The person who treats it like a feelings conversation usually leaves with vague encouragement and no packet.

TL;DR

In practice, the real decision is usually spread across 3 rooms: your 1:1, your manager’s write-up, and the calibration table. The strongest case is not the loudest case. It is the one that makes the next-level scope obvious in 2 quarters of evidence, not 1 impressive launch.

If you want a clean judgment, this is it: if your manager cannot name the level jump in one sentence, you are not ready yet.

Running effective 1:1s is a system, not a talent. The Resume Starter Templates includes agenda templates and question banks for every scenario.

Who This Is For

This is for the Google PM, engineer, designer, or data leader who already has visible wins, but still needs a manager to turn those wins into a promotion narrative. It is also for the person who hears “you’re doing great” and mistakes that for sponsorship.

The reader here is usually sitting at L4 looking at L5, or L5 looking at L6, and wondering why the work feels bigger than the title. In a debrief, I watched this exact pattern: the candidate had real impact, but the story was too local, too recent, and too dependent on one manager’s enthusiasm. That is not promotion material. That is incomplete evidence.

What Is a Promotion Discussion at Google Really For?

It is a manager alignment meeting, not a courtroom argument. In a Google promo conversation, the manager is asking whether your current output already looks like next level scope, and whether they can defend that at calibration without sounding speculative.

The problem is not that candidates talk too much. The problem is that they talk at the wrong altitude. They describe activity, not elevation. They list projects, not scope shifts. They say they “owned” work, but they never show what changed because they owned it.

In one Q3 debrief, the hiring manager pushed back on a promotion packet because the candidate had one strong launch and three small follow-through tasks. The room did not see level change. They saw execution. Not performance, but pattern. Not effort, but organizational leverage.

A useful rule is simple: the 1:1 is where your manager decides whether the packet exists, not where the packet is judged. That is why the conversation has to sound precise. If the manager cannot repeat your case back in the language of level expectations, the rest of the process is already fragile.

What Evidence Does Google Actually Need?

Google does not promote the person with the most visible motion. It promotes the person whose work changes decisions, not just deliverables. That is the difference between being busy and being promotable.

The evidence has to show three things: repeatability, reach, and independence. Repeatability means the impact did not happen once by luck. Reach means it mattered outside your immediate lane. Independence means the result did not collapse when one sponsor stepped out of the room.

I have seen candidates lose a promo discussion because their strongest example was too dependent on a single launch. The manager liked the story. The calibration room did not. It looked like a spike, not a new operating level. Not one win, but a pattern. Not output, but transferability.

A stronger packet usually has 3 examples across 2 quarters. One example should show strategic judgment. One should show cross-functional influence. One should show that other people changed behavior because of your work. If all 3 examples live inside one team, the case is thin. If all 3 examples sound like task completion, it is weaker still.

This is where people misread the room. They think the question is “Did you do hard work?” It is not. The question is “Did you create enough organizational value that the next title is a clean description of reality?” That is why promotion is always partly psychological. Calibration is a social proof exercise disguised as process.

How Should You Frame Your Case in the 1:1?

You should frame it as a level-change thesis, not a self-advocacy speech. The manager needs to hear what is different now, why it matters at the next level, and what evidence already exists.

The worst opener is “I feel ready.” Feelings are not a packet. They are noise unless they are attached to specific scope shifts. Better language sounds like this: “Over the last 2 quarters, I moved from shipping features to changing team direction, and I want to know what evidence is still missing for the next level.”

That is not verbosity. That is precision. The problem is not your confidence. The problem is your judgment signal. Managers listen for whether you can separate ambition from evidence.

Not “I want to be promoted,” but “here is the case for a level change.” Not “I worked really hard,” but “I changed how a team decided.” Not “I deserve it,” but “this is already how the work functions.”

In the room, good candidates do not oversell. They anchor. They say what changed, who was affected, and what would break if they stopped doing the work tomorrow. That last question matters. If the organization would barely notice, the level change is not there yet.

What Timeline Should You Expect After the Conversation?

The answer is usually slower than the candidate wants and more political than the manager admits. A clean promotion discussion can take 30 to 45 minutes in the 1:1, then 1 to 2 weeks of manager write-up, then 2 to 6 weeks of calibration and follow-up.

That lag is not a bug. It is the system working as designed. Promotions are not approved in the room because the room is too small. The room is for alignment. The decision is made after the manager has turned your work into an argument that survives other managers.

In a skip-level conversation I sat through, the manager was confident until one director asked for a second example outside the candidate’s direct team. That question changed the tone immediately. The case was not rejected. It was delayed. That is how weak packets die: not with a dramatic no, but with a request for more evidence that never arrives.

Do not confuse “no answer yet” with “yes.” Do not confuse “let’s revisit next cycle” with sabotage. Sometimes it is genuine timing. Sometimes it is a polite refusal. The difference is whether the manager names a specific gap and a dated checkpoint. If they cannot, the answer is effectively no.

When Does a Promotion Discussion Fail?

It fails when the manager cannot translate your work into next-level scope. That is the real failure mode, not a missing metric or one awkward meeting.

A lot of people assume their case failed because they were not assertive enough. Usually that is wrong. The case failed because the evidence was narrow, too recent, or too dependent on one heroic project. The manager may still like you. The packet still may not be ready.

In one debrief, the candidate had strong peer reviews and a polished narrative. The room still hesitated because all the impact lived inside the candidate’s immediate org. The calibration concern was simple: if this person disappeared, would the company still have proof of the next level, or just proof of good effort?

That is the organizational psychology behind promotion. Committees do not reward sincerity. They reward defensibility. Not warmth, but transferability. Not praise, but a case that another manager can repeat without embarrassment.

If your manager says “keep doing what you’re doing,” that is not a promotion decision. That is often a soft no. If they say “I need one more quarter of this kind of work,” that is also a no, but at least it is honest. If they say “here is the exact gap and here is the date we will revisit,” then you have a real process instead of a fog machine.

Preparation Checklist

A good 1:1 starts before the meeting. If you walk in without a level-change thesis, you are asking your manager to do the hard part for you.

Write a one-paragraph case for the next level. Current scope on one side, next-level scope on the other.
Bring 3 examples from the last 2 quarters. Each example should include the decision changed, the stakeholders involved, and the measurable outcome.
Pre-wire 2 peers who can describe your impact without manager translation. Praise is weak; specific examples are strong.
Ask your manager what evidence is still missing and when the packet will be revisited. If the answer is vague, force a date.
Prepare a one-sentence answer to “What would you stop, start, and keep at the next level?” That question exposes whether you understand scope.
Know the comp consequence. A level move can change total compensation by a $30,000 to $100,000 band in some cases, so treat timing as a real economic decision, not a social one.
Work through a structured preparation system (the PM Interview Playbook covers Google leveling, calibration, and packet storytelling with real debrief examples) before the conversation.

Mistakes to Avoid

The common errors are predictable. The damage comes from treating them as harmless.

BAD: “I’ve been working hard and I think I’m ready.”

GOOD: “Over 2 quarters, I moved from execution to decision-shaping, and here are the 3 examples that prove it.”

BAD: Turning the 1:1 into a negotiation about feelings or loyalty.

GOOD: Treating it as a calibration on evidence, scope, and timing.

BAD: Asking, “Am I ready?”

GOOD: Asking, “What exact evidence is missing, and by what date will we review it again?”

The difference matters because managers can work with evidence. They cannot calibrate around vague self-belief. Not enthusiasm, but defensibility. Not pressure, but packet quality.

FAQ

Should I ask for a promotion if my manager has been vague?

Yes, if you can state the next-level case clearly. Vagueness is not a reason to wait quietly; it is a reason to force specificity. If the manager still cannot name the gap after you ask directly, the issue is sponsorship, not your performance.

What if my work is strong but invisible?

Then your problem is not impact, it is traceability. Strong work that nobody can restate in calibration does not travel. You need examples that survive manager turnover, skip-level scrutiny, and cross-functional retelling. Visibility without defensibility is not enough.

Should I bring up compensation in the same conversation?

Yes, but only after the promotion path is clear. If you talk comp before the level case, you look transactional and unprepared. If the level changes, the comp conversation is part of the same economic reality. If the level does not change, compensation is a distraction.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.