TL;DR
What should I actually say in the 1:1?
The raise conversation at Google usually dies in the first 20 seconds. It dies when the employee asks for “feedback” and the manager hears “I have not made a case.” In the room, softness looks like uncertainty, and uncertainty gets deferred.
I have watched this play out in calibration conversations and manager check-ins. The employee thinks the issue is pay. The manager hears scope, level, and timing. Those are not the same problem. The problem is not your worth, but your signal.
At Google, a 1:1 is not where compensation is invented. It is where the manager decides whether your case deserves air in the next review cycle. If you walk in with a vague sense of fairness, you lose. If you walk in with a clean decision request, you at least enter the room.
What should I actually say in the 1:1?
Ask directly, but ask like someone who understands the decision chain. The worst version is a performance-chat disguise. The best version is a compensation request with evidence attached.
In a real manager conversation, the employee who says “I wanted to talk about my growth” usually gets polite noise. The employee who says, “I want to talk about compensation because my current scope has outgrown my current base” changes the room. Not because the sentence is magical, but because it removes ambiguity. The manager now has to respond to a request, not a mood.
Use this script if you want the cleanest opening:
“I want to talk about compensation in this 1:1. My current scope is above my current pay, and I want to understand what would justify a raise. I am not asking you to decide it right now. I am asking what evidence you need to support it.”
That is the right shape. Not a complaint, but a decision request. Not gratitude, but calibration. Not “Do you think I deserve more?”, but “What would make the case defensible?”
The first counter-intuitive truth is that confidence matters less than precision. Managers do not reward emotional intensity. They reward a case that can survive a skeptical read from people who were not in your meetings. In one Q3 calibration, a manager did not argue about effort. He asked whether the employee’s work was visible outside the immediate team. That was the real test. The raise conversation was never about effort alone.
If you need a second line, use this:
“I do not want this to stay abstract. If you think I am underpaid for my scope, I want the path to a correction. If you do not, I want the exact gap.”
That sentence does one useful thing. It forces the manager to choose between support and deferral. Deferral is not neutral. Deferral is a decision.
When is the wrong time to ask?
The wrong time is when you have no recent evidence, no recent leverage, and no recent opening. A raise ask is not illegal in a bad quarter, but it is weak if you cannot point to a fresh reason for the company to move.
In a manager check-in after a rough product cycle, I have seen people ask for compensation as a morale repair. That is a mistake. Compensation is not therapy. If your launch slipped, your team missed a target, or your project was absorbed by another org, the manager is already defending the current comp picture. Asking then without a stronger case is not bold. It is premature.
Not “when you feel undervalued,” but when you can describe a current mismatch between scope and pay. Not “after enough time has passed,” but after a visible step-up in ownership. Not “after the next review,” but before the next review has already been informally decided.
The second counter-intuitive truth is that timing is less about calendar and more about narrative freshness. If you led a launch, absorbed an ambiguous cross-functional problem, or took over work that was previously shared by two people, the conversation is alive. If six months have passed with no new proof, the manager will push you into the next cycle and call it process.
Use this line when the timing is uncertain:
“I know compensation decisions run on a cycle. I also know my current scope changed materially in the last two quarters. I want to understand whether now is the right time to build the case, or whether I should anchor it to the next review.”
That wording is disciplined. It does not beg. It does not threaten. It asks the manager to state the decision window.
A late-quarter debrief tells the real story. The hiring manager or team lead will not fight for a raise packet that looks stale. The packet needs motion, not nostalgia.
📖 Related: Distillation vs Pruning: Best LLM Fine-Tuning on Google TPUs for Applied AI Engineers
What does a credible raise case look like at Google?
A credible case is built on scope, not sentiment. Google managers do not move compensation because someone worked hard. They move it because the employee is already operating at a harder level and the team can feel the gap if that person leaves.
The raise case usually needs three things. First, the work must be concrete. Second, the ownership must be visible beyond your immediate manager. Third, the impact must be hard to replace. Not “I did a lot,” but “I owned the thing other people kept routing back to me.”
In one compensation conversation, the employee came in with a list of tasks. The manager was unmoved. Then the employee reframed the work into three ownership points: the launch risk they prevented, the cross-functional dependency they untangled, and the recurring problem they absorbed without escalation. The manager changed immediately. The content had not changed. The framing had.
The third counter-intuitive truth is that a raise case often becomes stronger when it sounds less like self-promotion and more like risk management. A manager does not want to lose the person who silently stabilizes important work. They do not need a hero story. They need a replacement-cost story.
If you want the script for the evidence section, use this:
“Over the last two quarters, I have been operating at a scope that includes [project], [cross-functional ownership], and [unblocked dependency]. I am not asking for a reward for being busy. I am asking whether that scope is already above my current compensation band.”
That line is useful because it does not beg the manager to infer your value. It names the scope and asks for the band.
If you want to make the case more concrete, you can use a compensation frame like this: if your current base is $182,000 and the defensible adjustment is to $198,000, that is a conversation about calibration. If your current base is $182,000 and you are implicitly asking for something closer to $240,000 without a level change, you are no longer asking for a raise. You are asking for a re-leveling disguised as a raise. Those are different conversations, and managers know it.
A credible case is not X, but Y. Not “I’ve been here a long time,” but “my present scope is demonstrably larger than my current pay.” Not “I think I am underpaid,” but “here is the work that makes the current number hard to defend.” Not “I want more money,” but “I want the decision path to be explicit.”
How do I handle pushback without sounding defensive?
Treat pushback as information, not disrespect. If the manager resists, they are usually signaling one of three things: the case is weak, the timing is wrong, or they lack authority and need a better packet.
The room changes when the employee starts arguing emotionally. That is the wrong move. I have seen people talk themselves out of a future yes by trying to win the current no. The stronger move is to isolate the constraint.
Use this response when the manager says, “I understand, but I am not sure we can move anything right now”:
“What would have to be true for this to become a yes? I want the exact criteria, not a general encouragement.”
That sentence strips the fog out of the conversation. If the manager cannot answer, the issue is not your tone. The issue is that they do not have a real case for you yet.
Use this one when they say, “Let’s revisit this later”:
“I am fine revisiting it. What is the next decision point, and what evidence should be in front of you by then?”
That is not pushy. That is operational. It moves the conversation from vague sympathy to a date and a standard.
Use this one when they say, “Compensation is handled elsewhere”:
“I understand the process. I still need your view on whether my scope justifies a case. If you support it, I want to know what packet you need from me.”
That distinction matters. Not “Can you approve this?”, but “Will you sponsor the case?” A manager’s support is often more important than the formal mechanics. In practice, the sponsor does the quiet work before anyone else sees the number.
The fourth counter-intuitive truth is that pushback is often a gift. It tells you whether you are being delayed, denied, or redirected. Those are different outcomes. If the manager gives you real criteria, the door is open. If they give you vague encouragement, the door is not open yet. If they dodge the question entirely, you already have your answer.
📖 Related: Google PM vs Meta PM: Which AI Product Role Fits Your Skill Set?
Can I talk about numbers without making it awkward?
Yes, but numbers should come after scope, not before it. If you lead with a number, you make the conversation look transactional. If you lead with the work and then anchor the request, the number becomes a consequence, not a demand.
At Google, the cleaner internal conversation is usually not “I want $X more.” It is “Given this scope, what adjustment is defensible?” That is the sentence that sounds like an employee who understands calibration, not just aspiration.
If you need to bring in specifics, keep them tied to role and responsibility. For example: “If my current base is $182,000, I want to understand whether the current scope supports something closer to $198,000, or whether the right answer is a promotion path instead of a simple adjustment.” That frames the decision. It does not pretend every number is equally plausible.
If the manager offers total compensation context, listen carefully. Sometimes the base is tight, but the refresher equity or bonus path is the real lever. Sometimes the company cannot justify a large base jump, but can justify a retention-oriented package if the risk is real. The conversation is not always about one line item. It is about what the company can defend in front of its own process.
The useful script here is:
“I want to separate the number from the title. If the current scope supports a pay adjustment but not a level change, I want that made explicit. If it supports both, I want to know which route you would sponsor.”
That is the cleanest way to avoid a confused discussion. Not “What can you give me?”, but “Which decision is actually on the table?”
Preparation Checklist
Prepare the conversation as a decision memo, not a vibes conversation.
- Write one sentence that states the ask in plain English. If you cannot do that, you are not ready.
- List three pieces of recent work that changed your scope, not just your workload.
- Separate base, bonus, and equity before the meeting so you know what you are actually asking for.
- Rehearse the exact pushback response you will use if the manager defers.
- Decide what outcome you want if the answer is no: next review date, packet requirements, or a promotion path.
- Work through a structured preparation system (the PM Interview Playbook covers Google-specific calibration framing and real debrief examples) so your case sounds like a packet, not a complaint.
- Bring one short written summary after the meeting if the manager gives you a path, so the next conversation has a paper trail.
Mistakes to Avoid
The common failures are predictable, and they are usually self-inflicted.
- BAD: “I think I deserve a raise because I have been working hard.”
GOOD: “My current scope has expanded, and I want to understand what evidence would justify a compensation adjustment.”
- BAD: “I know the review is coming, so maybe we can figure something out then.”
GOOD: “I want to know whether now is the right time to build the case, and what the review process would need to see.”
- BAD: “I feel underappreciated.”
GOOD: “I want to separate appreciation from compensation and make the decision criteria explicit.”
The problem is not honesty, but structure. The problem is not humility, but vagueness. The problem is not that you asked, but that you asked in a way that gave the manager an easy escape.
FAQ
Should I ask for a raise in a 1:1 or wait for the review cycle?
Ask in the 1:1 if you have fresh evidence and a clear request. Waiting only helps if your manager has already signaled that the review packet is the right vehicle. If you wait without a case, you are just delaying rejection.
What if my manager says compensation is decided somewhere else?
Do not argue the process. Ask for sponsorship. The useful question is, “Do you support the case, and what evidence do you need from me?” If they will not answer that, they are not sponsoring you, and you should stop treating the conversation like a negotiation.
Is it better to ask for a raise or a promotion?
A raise is cleaner if the scope increase is real but not yet promotion-sized. A promotion conversation is better if your work already looks like the next level. If you ask for the wrong thing, you weaken both cases. The manager should not have to translate your ask for you.amazon.com/dp/B0GWWJQ2S3).
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.