Most L5 PMs at Google fail to secure meaningful RSU refreshers because they treat the request as transactional, not strategic. The issue isn't asking—they all ask—it’s how they frame impact relative to comp band ceilings and promotion risk. You don’t need a template. You need a case: one that maps shipped outcomes to equity benchmarks observed in recent HC-approved promotions. Without it, your ask disappears into a spreadsheet.
PM RSU Refresher Request Template for Promotion Cycle: How to Ask for More Equity at Google L5
TL;DR
Most L5 PMs at Google fail to secure meaningful RSU refreshers because they treat the request as transactional, not strategic. The issue isn't asking—they all ask—it’s how they frame impact relative to comp band ceilings and promotion risk. You don’t need a template. You need a case: one that maps shipped outcomes to equity benchmarks observed in recent HC-approved promotions. Without it, your ask disappears into a spreadsheet.
This is one of the most common Product Manager interview topics. The 0→1 PM Interview Playbook (2026 Edition) covers this exact scenario with scoring criteria and proven response structures.
Who This Is For
This is for current Google L5 Product Managers in the promotion track (L5→L6) who are due for an RSU refresher and believe their total compensation lags behind peers with similar scope. It is not for new hires, not for those not in the promotion cycle, and not for engineers or TPMs assuming PM processes apply to them. If your manager has not confirmed your packet is in flight, stop here.
How do I know if I’m under-comped on RSUs at Google L5?
If your last RSU grant was below $450K over four years and you’ve launched a cross-functional initiative with revenue or engagement impact, you’re likely under-comped. At L5→L6, Google’s comp bands allow refreshers up to $600K–$700K for high-impact cases, especially if promotion is probable. The problem isn’t data—it’s benchmarking. Most PMs compare to vague peer rumors, not HC-approved cases.
In a Q3 promotion cycle debrief, a hiring committee rejected a strong candidate’s refresher because the manager cited “peer alignment” without providing HC-validated comparables. The HC lead shut it down: "We don’t benchmark against outliers. Show me two approved L5→L6 cases with similar scope and equity." The request failed—not due to performance, but lack of reference anchors.
Not all influence is equal. A PM who drove a 2pp engagement lift in Search results has more comp leverage than one who led a well-received UX redesign in a low-monetization surface. Google values scale, risk mitigation, and strategic control points. Your equity case must reflect that hierarchy.
The real benchmark isn’t your teammate’s offer letter. It’s what the HC recently approved for someone with comparable scope, timeline, and promotion viability. Not effort, but leverage.
What should my RSU refresher request actually include?
Your request must contain: (1) a summary of promotable impact, (2) HC-approved peer comparables, (3) current equity position vs. band midpoint, and (4) explicit linkage between promotion risk and retention need. Anything less is a memo, not a case.
During an L5→L6 packet review, one PM submitted a 12-bullet list of shipped features. The HC lead skimmed it, then asked, “Which of these made the org willing to lose you?” The manager hesitated. The request was deferred. The lesson: output isn’t evidence. Consequence is.
Not achievement, but trade-off. Frame every impact as a cost avoided or option gained. Example: “Delayed sunset of Ad Manager API, preserving $28M annual revenue, enabling pivot to next-gen platform.” That’s not delivery. That’s strategic control.
Your document should be one page. Top third: promotable impact. Middle: comp gap (e.g., “current equity at $380K vs. $550K HC-approved median for L5 promo cases”). Bottom: peer benchmarks (names redacted, roles and outcomes specified). No appendices. No timelines. No org charts.
The goal isn’t to inform. It’s to arm your manager to fight in HC. They won’t advocate for what they can’t repeat under pressure.
When is the best time to submit my RSU refresher request?
Submit your request 7–10 days before your packet enters HC review, not after promotion nomination. The window is narrow: once the nomination is in flight, comp discussions shift to reaction, not planning. Too early, and your impact isn’t framed by promotion context. Too late, and the comp committee has already set bands.
In a Q2 cycle, a PM submitted a refresher request three weeks post-promotion approval. The comp lead rejected it: “We don’t do retroactive refreshers for already-promoted employees.” The request wasn’t wrong—it was misaligned to process rhythm.
Not timing, but phase dependency. Google’s promotion and comp cycles are dual-track but interlocked. Your refresher must arrive when the HC is assessing “why this person, why now?”—not after the “why” has been settled.
Coordinate with your manager. Ask: “When does the HC packet lock?” Work backward. 48 hours before lock, deliver the document. Gives them time to absorb, push back, refine—not rewrite.
If you’re in the promotion cohort but haven’t seen your packet status, assume it’s 2–3 weeks out. Start now.
How do I find peer RSU benchmarks without overstepping?
You don’t gather benchmarks by asking peers directly. You infer them through manager alignment, comp band disclosures, and HC-adjacent signals. The safest path: ask your manager, “What’s the typical refresher range for L5s promoted with [X scope]?” Then cross-reference with what GAN (Google Advocacy Network) or skip-levels have shared in town halls.
One PM in Ads tried polling peers on Slack. Word reached comp. The request was flagged for “inappropriate benchmarking behavior.” Not because they asked—it was how. You don’t probe. You triangulate.
Not comparison, but inference. Google publishes comp bands in career ladders. L5→L6 refresher median is $500K–$550K in high-impact domains (Search, Ads, Cloud). Low-velocity areas (DVC, Internal Tools) see $350K–$420K. Your scope, not level, determines placement.
Ask your manager: “Has the comp team shared updated benchmarks for promotion-linked refreshers this cycle?” That’s a process question, not a personal one. It surfaces data without appearing entitled.
If you’ve attended HC prep sessions or skip-levels, cite generalized insights: “In last quarter’s leadership forum, it was noted that L5 PMs driving monetized AI integrations received refreshers in the $550K+ range.” That’s attribution without exposure.
How should I phrase the request to my manager?
Say this: “I’d like to align on my RSU refresher case ahead of HC review. I’ve summarized my promotable impact and comp position, plus recent peer benchmarks. Can we review it to ensure it’s positioned effectively for comp discussion?”
Not “Can you ask for more equity?” That’s naive. Managers don’t “ask.” They advocate. Your job is to give them a weapon they can use in a 90-second HC comp huddle.
In a recent debrief, a manager pushed for a $600K refresher. The comp lead asked, “Why this person over others?” The manager pulled up a one-pager with three bullets: (1) revenue at risk mitigated, (2) current equity at 30% below band, (3) two HC-approved comparables in same org. Approved in 48 hours.
Not persuasion, but compression. Your manager needs a defensible, repeatable narrative. If they can’t say it from memory, it’s too complex.
Avoid: “I’ve been here 4 years and haven’t gotten a big refresh.” That’s tenure, not leverage. Google pays for future risk, not past service.
Instead: “Without a competitive refresh, there’s material retention risk given external interest and scope expansion.” That’s not a threat. It’s a forecast.
Preparation Checklist
- Draft a one-page case linking promotion impact to equity need
- Identify 2–3 HC-approved peer comparables (scope, not name)
- Calculate current RSU position vs. $550K benchmark for L5→L6
- Align timing with HC packet lock date (7–10 days prior)
- Run draft by trusted mentor for HC plausibility check
- Work through a structured preparation system (the PM Interview Playbook covers promotion-aligned comp cases with real debrief examples)
- Schedule 30-minute review with manager using “positioning” language, not “ask”
Mistakes to Avoid
BAD: Submitting a 3-page document detailing every project from the last 3 years
GOOD: One page, three bullets, one benchmark, one number
BAD: Asking for “what my Facebook peer got”
GOOD: Citing “recent HC-approved L5→L6 in Cloud with similar P&L impact”
BAD: Sending request the day before HC review
GOOD: Delivering 7 days prior, allowing time for iteration and escalation prep
FAQ
Why won’t my manager just fight for me?
Managers don’t advocate without ammunition. In a Q4 HC, three L5s requested refreshers. Only one had a manager who presented a comp gap + benchmarked case. The other two got “will consider” and nothing. Your manager isn’t passive—they’re risk-averse. Give them a defensible position, or they’ll default to safe.
Is it too late if I’ve already been promoted?
Yes, effectively. Comp committees treat post-promotion refreshers as exceptions. One PM received a $200K refresh two months post-L6 promotion—but only after escalating to L7 skip-level with evidence of external offer and HC-approved peer grants. Retroactive cases require proof of material oversight, not just desire.
Can I use a template from online forums?
No. Templates from Blind or Levels.fyi lack HC context and often include disqualifying language (“market rate,” “I deserve”). One candidate used a Reddit-sourced template that said, “I’ve outperformed my level for 2 years.” The comp lead noted: “That implies we’ve under-managed them. We don’t reward mismanagement.” Use structure, not copy.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.