Asking for a Raise Script in 1:1 Meetings at Google: A Step-by-Step Guide
TL;DR
Your manager cannot give you a raise on a whim; they can only advocate for one during the calibration cycle. The goal of the 1:1 is not to get a yes, but to secure a commitment that your current impact is mapped to the next pay grade. Success is measured by the manager's willingness to fight for you in the room where you are not present.
Running effective 1:1s is a system, not a talent. The 0-to-1 Quant Interview Playbook (2026 Edition) includes agenda templates and question banks for every scenario.
Who This Is For
This guide is for L4 to L6 Product Managers and Software Engineers at Google who have hit a performance plateau or are operating at the next level without the corresponding compensation. It is specifically for those who believe they are underpaid relative to their peer group but lack the political capital or the specific data points required to force a salary adjustment outside of the standard GRAD cycle.
How do I ask for a raise in a Google 1:1 without sounding entitled?
Frame the request as a gap analysis between your current compensation and your documented impact, not as a personal need. In a recent L5 calibration debrief, I saw a candidate fail because they focused on their tenure and market rates, which the committee viewed as a lack of ownership. The problem isn't your request for more money; it's your failure to provide the manager with the ammunition they need to justify the spend to their own VP.
At Google, compensation is a function of level and performance rating, not negotiation skills. You are not negotiating a salary; you are negotiating a perception of your impact. The conversation must shift from what you want to what you have already delivered that exceeds the expectations of your current level. This is not a request for a reward, but a request for a correction.
The most successful scripts follow a specific sequence: Evidence, Alignment, and Ask. You start by highlighting a specific win that moved a core KPI, align that win with the expectations of the next level, and then ask what the delta is between your current pay and that level's compensation. This removes the emotion and replaces it with a business case.
> 📖 Related: Google 1:1 vs Meta 1:1 Culture Comparison: Which Fosters Better Growth?
When is the best time to bring up compensation during the GRAD cycle?
Initiate the conversation 8 to 12 weeks before the formal calibration window opens to influence the narrative before the ratings are locked. I once had a PM wait until the actual review meeting to ask for a raise, only to be told the budget was already allocated. By the time you see your rating, the financial decisions are effectively finalized.
The window for influence is narrow. If you bring it up during the 1:1 immediately following a major launch, you have the highest leverage because your impact is fresh. However, the conversation must happen early enough that your manager can socialize your "exceeds expectations" narrative with other leads. This is not about timing the meeting, but timing the perception.
A common mistake is treating the 1:1 as the only place for this discussion. The 1:1 is where you signal the intent, but the shared doc is where the evidence lives. If your manager has to hunt for your achievements during the calibration meeting, they will likely default to a standard increase. You must make it impossible for them to forget your impact.
What is the exact script to use for a raise request at Google?
Use a script that forces the manager to define the specific requirements for a compensation adjustment. Start with: I have been reviewing my impact over the last two quarters, specifically the 15% increase in DAU from Project X, and it aligns with L6 expectations. I want to ensure my compensation reflects this level of contribution; what is the process for us to adjust my salary to match this impact?
The power of this script lies in the shift from "Can I have a raise?" to "What is the process?" The former is a yes/no question that a manager can easily deflect. The latter is a procedural question that requires a roadmap. It transforms the manager from a gatekeeper into a partner in your career growth.
If the manager responds with "it's not the right time," the counter-script is: I understand the timing constraints, but I want to agree on the specific milestones I need to hit so that by the next cycle, the raise is a formality. This is not a concession, but a trap. You are getting them to commit to a set of criteria in writing, which prevents them from moving the goalposts during the next review.
> 📖 Related: Google L5 PM vs Meta E5 PM Total Compensation: Which Pays More in 2026?
How do I handle a manager who says there is no budget for a raise?
Demand a transparent explanation of the budget constraints and a timeline for when those constraints will be revisited. In a Q3 leadership meeting, I watched a director claim there was no budget for a high-performer, only to find a way to approve a spot bonus two weeks later when the employee threatened to interview elsewhere. The problem isn't the budget; it's the priority.
When you hear "no budget," you must distinguish between a hard cap and a lack of will. Ask: Is this a global headcount freeze, or is there a performance-based pool that we haven't tapped into? This forces the manager to be specific. If it is a hard cap, you stop fighting for cash and start fighting for non-monetary equity, such as a more prestigious project or a title change.
The reality of FAANG compensation is that the most significant jumps happen through leveling or switching teams, not through incremental raises. If the budget is truly frozen, the conversation should pivot to: If the compensation cannot move today, what is the plan to ensure I am prioritized for the next available window? This signals that you are tracking the debt the company owes you.
What evidence should I provide to justify a salary increase?
Provide a "Brag Sheet" that maps your deliverables directly to the Google leveling rubric, focusing on complexity and influence rather than hours worked. I have sat in dozens of debriefs where managers said, "They work so hard," and the committee responded with, "Hard work is expected at this level; where is the systemic impact?"
The evidence must be quantitative and cross-functional. Do not list tasks; list outcomes. Not "I managed the API migration," but "I led the API migration across three teams, reducing latency by 200ms and saving $50k in monthly infra costs." This is not a list of duties, but a portfolio of value.
Furthermore, include testimonials from other L6+ leads. At Google, your manager's opinion is only one data point. The calibration committee looks for "peer validation." If you can show that a Director in another org relies on your judgment, you have successfully demonstrated that you are operating above your pay grade.
Preparation Checklist
- Audit your last 6 months of impact and map every win to the specific L-level rubric requirements.
- Gather 3 written testimonials from cross-functional partners (L6+) confirming your leadership on specific projects.
- Quantify your wins using the Google-standard metric format: Accomplished X as measured by Y, by doing Z.
- Schedule a dedicated 1:1 for "Career and Compensation Growth" so the manager is not blindsided.
- Work through a structured preparation system (the PM Interview Playbook covers the Google-specific leveling frameworks with real debrief examples) to ensure your language matches the committee's expectations.
- Draft a shared "Impact Doc" that serves as a living record of your achievements, updated weekly.
Mistakes to Avoid
- Comparing your salary to a peer.
BAD: My teammate is making 20k more than me for the same work.
GOOD: Based on the impact I've delivered on Project X, my contributions align with the compensation band of the next level.
(Judgment: Peer comparison signals insecurity and a lack of professionalism; impact comparison signals a business case.)
- Using personal reasons as leverage.
BAD: My rent increased and I'm having a hard time managing my expenses.
GOOD: My current output has increased the team's velocity by 20%, creating a value gap between my pay and my delivery.
(Judgment: The company is not a social service; they pay for value, not for your cost of living.)
- Accepting a vague "I'll see what I can do."
BAD: Thanks for looking into it, let me know when you hear back.
GOOD: I appreciate you advocating for me. Can we set a calendar invite for two weeks from today to review the feedback from your lead?
(Judgment: Vague promises are a polite way of saying no. Forced follow-ups create accountability.)
FAQ
Can I get a raise outside of the GRAD cycle?
Rarely. Out-of-cycle raises usually require a "critical retention" flag, meaning you have a competing offer or your departure would crash a Tier-1 project. Do not expect a random mid-cycle bump; focus on the calibration window.
Should I mention a competing offer to get a raise?
Only as a last resort. Using an offer as a lever is not a negotiation; it is an ultimatum. It may get you the money, but it destroys the trust with your manager and labels you as a flight risk in the eyes of the HC.
What if my manager is supportive but the committee says no?
Pivot to a "Gap Plan." Ask the manager for the exact feedback from the committee: what specifically was missing? Use that feedback to build a 3-month sprint of deliverables that directly address those gaps, making the next "no" impossible.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.