Asking for a raise in a 1on1 at Google is not about passion — it’s about timing, data, and internal alignment. The most successful requests occur between Q3 planning and comp cycle lock-in, typically late October to mid-November. You must anchor your case in documented impact, peer benchmarking, and manager readiness — not tenure or effort. Most employees who fail do so because they treat the 1on1 as a negotiation, not a confirmation of prior groundwork.
How to Ask for a Raise in a 1on1 Meeting at Google: Exact Script
TL;DR
Asking for a raise in a 1on1 at Google is not about passion — it’s about timing, data, and internal alignment. The most successful requests occur between Q3 planning and comp cycle lock-in, typically late October to mid-November. You must anchor your case in documented impact, peer benchmarking, and manager readiness — not tenure or effort. Most employees who fail do so because they treat the 1on1 as a negotiation, not a confirmation of prior groundwork.
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 guide is for Google L4–L6 individual contributors in engineering, PM, or UX roles who have delivered visible results in the last 12 months and are approaching comp cycle timing but have not yet initiated formal salary discussions. If your last promotion or significant raise was 18+ months ago and you’ve exceeded expectations in at least two review cycles, this script applies. It does not apply to new hires under 12 months or those with underperforming peer feedback.
How Do You Know if It’s the Right Time to Ask for a Raise?
The optimal window to bring up compensation is 3–6 weeks before your manager submits comp recommendations, typically between October 15 and November 20 for most teams. If your 1on1 falls outside this window, the conversation will be logged but unlikely to move the needle. In a typical debrief, a hiring committee rejected a raise packet because the employee had raised it in July — too early to influence budgeting.
Timing isn’t about urgency; it’s about synchronization with Google’s financial calendar. Not when you feel undervalued, but when your manager has bandwidth to advocate. If your manager hasn’t started comp planning, they cannot commit.
The signal isn’t your performance — it’s your manager’s comp bandwidth. Not effort, but calendar alignment. Not merit, but timing leverage. You don’t create urgency — you exploit existing cycles.
What Should You Say in the First 60 Seconds of the 1on1?
Lead with intent, not emotion: “I’d like to discuss my compensation in the context of my recent impact and market alignment. I’ve prepared a brief summary and want to understand what would be needed to secure a salary adjustment in this cycle.”
This framing does three things: declares the goal, references evidence, and invites collaboration. In a 2022 People Ops review, managers flagged 87% of failed raise conversations as starting with vague dissatisfaction — “I feel underpaid” or “I’ve been here a long time.” These trigger defensive positioning.
You are not appealing to fairness — you are aligning with process. Not “I deserve more,” but “Here’s what I’ve delivered, and here’s how it maps to comp bands.” The first minute sets whether your manager sees you as strategic or emotional.
Not grievance, but governance. Not pressure, but partnership. Not entitlement, but evidence.
What Evidence Do You Need to Bring to the Conversation?
You need three things: documented impact, peer benchmarking, and role evolution. Impact must be in manager-scored areas — OKRs, promotion packets, skip-level feedback. One L5 engineer in Ads Quality included a quantified reduction in latency (18%) tied to revenue uplift ($2.3M annualized) — that number appeared in their manager’s comp justification.
Peer benchmarking isn’t about external data — it’s internal alignment. Saying “L5s in Search make 15% more” is useless. But “Three L5s on similar technical scope in my cluster are at Band 5D, and my recent project scale matches theirs” is actionable. Google pays relative to internal ladders, not market rates.
Role evolution means your current scope exceeds your level’s typical responsibilities. An L4 PM who onboarded two new markets independently should document scope creep. One PM in G Workspace used a side-by-side comparison of their responsibilities vs. the L5 role matrix — the manager escalated within 48 hours.
Not tenure, but trajectory. Not hours worked, but scope expanded. Not loyalty, but leverage.
How Do You Handle a “No” or “Not Now” Response?
A “no” is not a rejection — it’s a conditional deferral. Respond with: “I appreciate the transparency. Can you clarify what would need to change for this to be possible in the next cycle? Is it scope, visibility, or timing?”
This forces specificity. In a 2023 HC meeting, a manager cited “lack of headroom” as reason to deny a raise — but when pressed, admitted the real issue was insufficient skip-level exposure. The employee scheduled two skip-level 1on1s within the month and re-escalated successfully in Q1.
Never accept vague blockers. If the answer is “budget constraints,” ask: “Is this team-wide, or specific to my trajectory?” The former is temporary; the latter is a red flag.
One L6 in Cloud revised their approach after being told “no” in 2022. They secured a $45K adjustment six months later by tying a critical migration to exec visibility — proving that “not now” often means “make it unavoidable.”
Not persistence, but precision. Not repetition, but refinement. Not pleading, but proof-building.
Should You Mention Competing Offers or External Market Rates?
Only if you have a signed offer. Google rarely matches external offers preemptively — but they act when flight risk is confirmed. In a 2021 policy update, People Ops mandated that managers escalate retention cases only when a resignation or offer letter is on the table.
Saying “I have offers at $X” without proof triggers skepticism. One L5 in Mountain View mentioned “interest from Meta” — their manager logged it but took no action. When they returned three months later with a signed offer at 22% above current salary, comp was revised in 10 days.
External benchmarks alone don’t move needle. One UX designer compiled a detailed market analysis showing 18% undervaluation — the manager responded, “We don’t benchmark to Apple.” Internal equity dominates external pressure.
But — if you’re willing to leave, use the offer as leverage. Not hint, but hand. Not suggestion, but signal. Not negotiation, but necessity.
Preparation Checklist
- Map your impact to quantified business outcomes (e.g., latency reduction, revenue contribution, scale metrics)
- Gather peer comp data from trusted internal sources — focus on same Ladder, similar scope
- Align timing with comp cycle — target 1on1s between October 15 and November 20
- Draft a one-pager summarizing impact, scope evolution, and ask range
- Work through a structured preparation system (the PM Interview Playbook covers comp negotiation at Google with real debrief examples from L4–L6 cases)
- Rehearse the first 90 seconds of the conversation — clarity beats emotion
- Identify potential objections and prepare evidence-based responses
Mistakes to Avoid
BAD: “I’ve been here four years and haven’t had a real raise.”
This frames the request as entitlement. Managers hear “I’m tired,” not “I’m valuable.” In a 2022 HC review, this justification was cited in 7 of 10 rejected cases.
GOOD: “My ownership of the real-time bidding integration expanded beyond L4 scope, delivered $1.8M in efficiency gains, and aligns with Band 5C in comparable teams. I’d like to discuss alignment in this cycle.”
This anchors to impact, scope, and internal parity — the trifecta of approval.
BAD: Sending a compensation email the night before a 1on1.
One engineer in YouTube did this in 2023 — the manager rescheduled, calling it “high-pressure.” Google values collaborative tone. Surprises undermine trust.
GOOD: Sharing a one-pager 24 hours in advance with a note: “Prepared this for our 1on1 tomorrow — open to feedback.”
This gives processing time and positions you as prepared, not pushy.
BAD: Focusing on cost of living or personal needs.
“I need more to afford housing in SF” was raised in a 2021 case — the manager noted “personal circumstances not comp factors” in the rejection. Google evaluates role, not need.
GOOD: “Three peers at L5 with similar project scope are compensated at 5D. My recent delivery on Ads migration meets or exceeds their impact thresholds.”
This uses internal equity — the only benchmark that matters.
FAQ
What’s the average salary increase when asking at Google?
Raises approved in cycle typically range from 8–15% for ICs at L4–L6, depending on band depth and stack rank. One-off adjustments outside cycle average 5–7% and require strong retention risk. Increases above 15% usually coincide with promotion. If you’re seeking more than 10%, you’re effectively asking for a level adjustment — frame it accordingly.
Should you involve HR before talking to your manager?
No. HR does not initiate comp adjustments — your manager does. In a 2023 policy reminder, People Ops reiterated that unsolicited HR inquiries are flagged as process violations. HR supports only after manager escalation. Going around your manager destroys sponsorship. Not partnership, but protocol.
How soon can you ask for a raise after your last one?
Typically, 18 months between significant adjustments for non-promotion cases. Exceptions require extraordinary impact — e.g., leading a critical product launch or averting a major outage. One L5 in Android secured a 12-month adjustment by owning a security rollout tied to executive OKRs. Normal performance, even strong, won’t override cycle timing. Not momentum, but magnitude.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.