asking-for-raise-script-in-1on1-google

Asking for a Raise Script in 1:1 Meetings at Google: A Step-by-Step Guide

TL;DR

A raise ask at Google works only when it is framed as a scope and leveling conversation, not a plea for appreciation. Google’s public pay materials say compensation is tied to role, level, location, performance, and promotion history, and the company runs annual pay equity reviews (pay transparency policy, annual pay equity review).

The clean script is simple: state the scope change, state the evidence, state the ask, and ask what would make the decision sponsorable. Not confidence, but calibration. Not a performance monologue, but a decision conversation.

If you want real movement, do not ask when you feel underpaid. Ask when you can prove the work has already moved.

Who This Is For

This is for Googlers who have real scope, real manager trust, and still get soft feedback like “keep doing what you’re doing.” It is for PMs, engineers, TPMs, designers, and ops leads who have outgrown the last compensation conversation but have not yet translated that into a clean sponsor case.

It is not for someone who just wants more money because rent went up. It is for someone whose work has become harder, broader, or more visible over the last 60 to 90 days, and who needs a manager to acknowledge that the job has changed.

What Should I Say in a Google 1:1 When I Want a Raise?

The best script is direct, specific, and hard to misread. In a Q3 comp discussion, I watched a manager shut down a vague ask in 30 seconds because the employee led with feelings, not evidence. The people who got traction led with scope.

Use this shape:

“I want to talk about compensation relative to the scope I am carrying. Over the last 90 days, I have owned X, Y, and Z, and the work has moved closer to [next level / broader role]. I want to discuss a salary adjustment or the path to one. What would you need to see from me to sponsor that?”

That is the script. Not a performance speech, but a sponsor request. Not “I deserve it,” but “here is the evidence and here is the decision I want.” In Google rooms, that difference matters.

If you want to be even cleaner, close with one line: “If this is not the right cycle, I want the exact bar and the exact date we revisit it.” That forces the conversation out of vagueness and into accountability.

📖 Related: Google Front-Loaded RSU vs Meta Back-Loaded: L6 Compensation Comparison for Senior PMs

When Is the Right Time to Ask at Google?

The right time is after visible scope expansion, not after a personal expense spike. Managers move when the work has already changed, because they can defend that change in calibration without sounding emotional or arbitrary.

I have sat in manager conversations where the pushback was not “you are not good enough.” It was “I cannot sponsor this yet because the work has not been demonstrated long enough.” That is the real issue. Not timing as calendar trivia, but timing as proof density.

A practical window is 60 to 90 days after a meaningful change in scope. If you have one launch, one cross-functional rescue, or one ownership shift, that is not enough by itself. If you have a sustained pattern over a quarter, you have a case. Not one hero week, but repeated evidence.

Do not wait for annual review season if the work is already there. Do not ask during a crisis unless your crisis work is itself the evidence. A manager can often support a raise faster than a promotion, but only if the case is already legible.

What Evidence Does a Google Manager Take Seriously?

Google managers take scope, leverage, and comparability seriously. They do not move because you were busy. They move because the work has clear business consequence and maps to a higher level of responsibility.

In one calibration-style conversation, the hiring manager kept repeating the same line: “What changed because this person was here?” That is the question. Not activity, but impact. Not effort, but leverage. Not personal velocity, but org-wide usefulness.

The strongest evidence usually looks like this: You took ownership of a problem other people avoided. You closed a loop with a cross-functional partner without escalation. You reduced ambiguity for the team. You made other people faster. You operated as if you already held the next scope band.

If your manager cannot repeat your case in one sentence, your evidence is too fuzzy. If they can repeat it but cannot defend the jump in level or compensation, your ask is probably too large for the current cycle.

A $10k adjustment and a $40k correction are not the same conversation. The first is often a merit or retention adjustment. The second usually means scope, level, or market mismatch. Treat them differently or you will get a vague yes that goes nowhere.

📖 Related: Meta vs Google PM Product Sense Questions: What’s the Difference?

How Do I Handle Pushback Without Losing Leverage?

Pushback is usually about proof, not rejection. When a manager says “not now,” the real question is whether they mean “not enough evidence” or “not enough budget.” Those are different problems, and you should force them to say which one they mean.

A calm response sounds like this: “What would need to be true for this to be a yes?” “Is this a timing issue, a scope issue, or a budget issue?” “Can we set a date 30 days from now to review the missing evidence?”

That is not confrontation. That is management. Not emotional pressure, but decision hygiene.

In Google-style organizations, people often hide behind soft language. “Let’s keep this in mind.” “You are doing great.” “We will see how things land.” Those phrases are not decisions. If the answer is deferred, get the missing bar, the owner, and the date. Otherwise the conversation dies in the hallway between meetings.

Do not argue your worth. Argue the evidence. Do not chase reassurance. Chase a sponsorable next step.

What Does a Clean Follow-Up Look Like After the 1:1?

A clean follow-up is a short written recap that makes the decision harder to forget. Send it within 24 hours. If you wait a week, the conversation turns into background noise and the manager’s attention moves on.

Keep the note to four parts: What you asked for. What evidence you referenced. What your manager said. When you will revisit it.

Example: “Thanks for the conversation today. I wanted to recap that I am asking to review compensation because my scope has expanded across X, Y, and Z over the last 90 days. You said you want to see more sustained ownership on A and clearer stakeholder alignment on B before sponsoring a change. I will come back with that evidence on [date].”

That is the move. Not a long essay, but an audit trail. Not a reminder, but a memory aid that creates accountability.

If your manager agrees to an action, put the action in writing. If they do not, write down the gap anyway. In politics-heavy environments, the written recap is often the only thing that survives the quarter.

Preparation Checklist

• Write one sentence that separates your current scope from the scope you want recognized.
• Gather three receipts from the last 60 to 90 days: one launch, one cross-functional win, one example of operating above your current level.
• Decide the ask before the meeting: salary adjustment, promotion path, or a date to revisit both.
• Rehearse the opener until it sounds plain, not dramatic.
• Prepare one sentence for pushback: “What would make this sponsorable, and by when?”
• Work through a structured preparation system (the PM Interview Playbook covers compensation framing, promotion packets, and debrief-style calibration examples with real manager dialogue).
• Draft the follow-up note before the meeting so you can send it within 24 hours.

Mistakes to Avoid

The common failure is not asking for too much. It is asking with no decision logic.

• BAD: “I’ve been working really hard, and I think I deserve more.” GOOD: “My scope has expanded to include X, Y, and Z, and I want to discuss compensation relative to that change.”

• BAD: “Can I get a raise this cycle?” GOOD: “I want to understand what would need to be true for a compensation adjustment or promotion sponsor.”

• BAD: “Everyone on my team probably makes more than me.” GOOD: “I want to keep this focused on my scope, my level, and the evidence I can point to.”

The problem is not your ambition. The problem is a weak signal. Managers do not sponsor fog.

FAQ

Most raise asks fail because they are vague about the decision, not because the wording is awkward.

1. Can I ask for a raise outside review season? Yes, if your scope changed enough to justify it and you can show recent evidence. If the work has not changed, the timing will not save you.

2. Should I name a number in the first meeting? Yes. A number makes the ask concrete. Without one, you sound unsure of the size of the gap you are trying to close.

3. What if my manager says no? Treat it as a request for specificity, not a final judgment. Ask for the missing evidence, the owner of the decision, and the exact date you should revisit it.amazon.com/dp/B0GWWJQ2S3).

Related Reading

• Google vs Amazon Layoff: Which Company Offers Better Severance for PMs?
• Google Tpm Vs Pm Which Career Path

---

Your next 1:1 doesn’t have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn’t great.