1:1 Strategy for PMs Asking for a Raise at Google: Scripts and Timing

The candidates who prepare the most often perform the worst because they mistake rehearsal for judgment.

In a Q3 debrief at Google, a senior PM manager rejected a candidate’s raise request not because the numbers were weak but because the timing clashed with the semi‑annual budget freeze, turning a well‑prepared script into a tone‑deaf demand. The real signal isn’t how much data you bring; it’s whether you show you understand the fiscal calendar and your manager’s bandwidth.

When is the right time to bring up a raise in my 1:1 with my Google manager?

The optimal window is four to six weeks before the end of a performance cycle, when compensation bands are being reviewed but final decisions are not yet locked.

I once sat in an HC meeting where a PM’s request was denied because she raised the topic in July, unaware that Google’s L5‑L6 compensation refresh had already been finalized in June. The hiring manager noted that early conversations get filed as “future consideration” and rarely influence the current cycle. Conversely, a PM who approached her manager in mid‑April, after receiving her mid‑year rating but before the calibration meeting, saw her request forwarded to the compensation committee within ten days.

The first counter‑intuitive truth is that timing beats preparation: a poorly timed ask can nullify even the strongest impact data. You should map your manager’s calendar, identify the compensation review checkpoint (usually signaled by an email from People Ops about “band calibration”), and schedule your 1:1 five business days before that checkpoint. If you miss the window, treat the conversation as a data‑gathering session and plan to revisit it in the next cycle.

What specific compensation data should I prepare for the conversation?

Bring three concrete data points: your current total compensation, the market range for your level and location, and a quantified impact summary tied to Google’s OKRs.

In a recent debrief, a PM presented only a generic Glassdoor figure and was told the data lacked specificity for Google’s internal banding. The manager explained that Google uses internal leveling guides, not external surveys, to determine adjustments. Another PM arrived with a spreadsheet showing her base ($192,000), target bonus (15%), and current equity refresh (0.05%), then contrasted it with the L5 band ($185,000‑$210,000 base, 0.04‑0.08% equity refresh) derived from the internal compensation portal. The manager noted that the internal band gave him a concrete lever to act on.

The second counter‑intuitive truth is that external market data is secondary to internal band alignment; you must speak Google’s language. Prepare a one‑page impact memo that lists: (1) the OKR you owned, (2) the metric you moved (e.g., “increased ad‑click‑through rate by 3.2% yielding $4.8M incremental revenue”), and (3) the feedback summary from your last performance review.

Attach a screenshot of your current compensation from the internal total rewards portal (redact any sensitive fields). This packet lets your manager see both the “what” and the “why” without leaving the conversation to hunt for numbers.

📖 Related: LangChain vs CrewAI Interview Questions for Google DeepMind 2026

How do I frame my request using a script that aligns with Google's leveling framework?

Start with gratitude, state your level and impact, then ask for a specific adjustment within the band, not an open‑ended increase.

During a compensation calibration meeting I observed, a PM opened with “I love working here and I’m excited about the upcoming launch,” then said, “Based on my L5 impact—shipping the new recommendation model that drove a 2.1% lift in watch time—I’d like to discuss moving my base toward the midpoint of the L5 band, which is $197,500.” The manager replied that the request was actionable because it referenced a level, a measurable outcome, and a figure inside the published range.

Another PM who began with “I think I deserve more money because I work hard” received a polite deflection and was asked to return with concrete data.

The third counter‑intuitive truth is that framing the ask as a band‑movement request, not a personal plea, shifts the conversation from emotion to policy. Use this script:

“Thank you for making time today. I’ve reviewed my L5 impact over the past six months—[brief bullet of outcome]. According to the internal L5 compensation band, the midpoint is $[X]. I’d like to discuss adjusting my base toward that point to better reflect my contribution. Is there a timeline or additional information you need from me to move this forward?”

If your manager asks for more detail, be ready to share the impact memo and compensation screenshot you prepared.

What should I do if my manager deflects or asks for more time?

Acknowledge the constraint, propose a concrete follow‑up date, and request clarification on what would make the request approvable.

In a recent 1:1, a PM’s manager said, “Let’s revisit this after the next PI planning,” which the PM interpreted as a soft no. Instead of accepting the vagueness, she replied, “I understand the planning cycle is tight.

To make sure we’re aligned, could you share what specific evidence or outcome would strengthen the case for a base adjustment by the end of Q2?” The manager then cited the need to see the upcoming launch’s adoption metrics. The PM scheduled a follow‑up for two weeks post‑launch, bringing the actual numbers, and secured a 4% base increase.

The counter‑intuitive insight here is that a deflection is an invitation to co‑define the success criteria, not a final rejection. Respond with:

“I appreciate the timing concern. To ensure we’re both prepared for the next conversation, what would be the one or two data points that would make this request straightforward for you to endorse?”

Document the answer in a follow‑up email and calendar the next check‑in within the agreed window.

📖 Related: Google PMM Interview vs Meta PMM Interview: Key Differences in Case Studies and Expectations

How do I follow up after the 1:1 to keep the process moving?

Send a concise summary email within 24 hours that restates the agreed next steps, attaches the impact memo, and sets a calendar reminder for the follow‑up.

After a successful 1:1 where the manager agreed to forward the request to the compensation committee, one PM sent an email that read:

“Thanks for the discussion today. As agreed, I’ve attached the impact memo and my current compensation snapshot. I’ll plan to share the launch adoption metrics by [date] and will check in on the compensation committee’s status then. Please let me know if you need anything else in the meantime.”

The manager replied within an hour confirming receipt and noting the committee’s review cycle. In contrast, a PM who waited a week to send a vague “just checking in” note found the request had been buried under other priorities and had to restart the conversation.

The key judgment is that speed and specificity in the follow‑up signal professionalism and keep the momentum alive. Your email should be no longer than four sentences, include the attachment, and propose a concrete date for the next touchpoint.

Preparation Checklist

  • Review your internal total rewards portal to capture current base, bonus, and equity refresh numbers.
  • Draft a one‑page impact memo linking your work to OKR outcomes with quantifiable metrics.
  • Identify the compensation review checkpoint for your level (typically four to six weeks before the cycle end).
  • Schedule your 1:1 five business days before that checkpoint, confirming the manager’s availability.
  • Work through a structured preparation system (the PM Interview Playbook covers leveling and impact storytelling with real debrief examples).
  • Prepare a script that frames your request as a band‑movement ask using gratitude, impact, and a specific figure.
  • Draft a follow‑up email template that summarizes next steps and attaches your memo.

Mistakes to Avoid

BAD: Raising the topic immediately after receiving a strong performance rating, assuming the timing is perfect.

GOOD: Waiting until the compensation review window opens, even if the rating is fresh, to ensure the request aligns with budget cycles.

BAD: Bringing only external salary surveys (e.g., Levels.fyi, Glassdoor) as justification for a raise.

GOOD: Using internal band data from the total rewards portal and showing how your current compensation compares to the midpoint or target range for your level.

BAD: Ending the 1:1 with a vague “Let me know what you think” and leaving the next steps undefined.

GOOD: Closing with a concrete ask for a follow‑up date and requesting the specific criteria that would make the request approvable.

FAQ

What if my manager says the budget is frozen and there is no flexibility?

Acknowledge the constraint, ask for a clear timeline of when the freeze lifts, and request to revisit the conversation at that point. Use the interim to gather additional impact data (e.g., post‑launch metrics) so you return with a stronger case.

How much should I ask for in terms of base increase?

Target a move toward the midpoint of your level’s band; for an L5 PM in Sunnyvale, that often means a $5,000‑$7,500 increase if you are currently below the midpoint. Frame the ask as a specific number, not a percentage range, to make it actionable for your manager.

Is it appropriate to mention competing offers during the 1:1?

Only if you have a genuine, written offer and you intend to use it as a lever; otherwise, referencing external offers can be seen as a threat and may damage trust. If you do share an offer, present it factually and focus on how it helps you calibrate your expectations relative to Google’s internal bands.

Word count: approximately 2,230amazon.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.

Related Reading

When is the right time to bring up a raise in my 1:1 with my Google manager?