1:1 Agenda Template for Asking Promotion at Google: With Script
TL;DR
Most engineers fail to get promoted at Google not because they lack impact, but because they treat the 1:1 as a status update, not a persuasion event. The right agenda forces the manager to advocate, not just listen. You need a structured script that surfaces credit risk, aligns narratives, and triggers sponsorship — not just feedback.
Running effective 1:1s is a system, not a talent. The 0-to-1 SRE DevOps Interview Playbook (2026 AI-Native Edition) includes agenda templates and question banks for every scenario.
Who This Is For
This is for L4–L6 engineers and PMs at Google who’ve delivered measurable projects but haven’t seen movement on career progression, especially those preparing for promotion season or entering a QBR cycle. If your manager says “you’re on track” but nothing changes, you’re operating at visibility, not influence.
How Do You Structure a 1:1 Agenda to Ask for a Promotion at Google?
Start with intent: the goal isn’t to ask “can I be promoted?” but to make your manager uncomfortable with the idea of not advocating for you. In a Q3 2023 debrief for an L5 PM candidate, the hiring committee rejected the packet not due to performance, but because the manager’s endorsement lacked urgency. The candidate had never forced the conversation.
Your agenda must do three things:
- Surface gaps in perception vs. reality
- Pre-brief promotion evidence as narrative, not data
- Lock in next steps that require manager effort
A winning 1:1 agenda has four sections:
- Objective: “Align on readiness for L5 promotion packet submission by [date]”
- Evidence Review: 3–5 key impacts, tied to ladder criteria
- Credit Risk Scan: “Where might stakeholders undervalue my role?”
- Next Steps: Specific, manager-owned actions
Not every impact counts — only those that map to scope, complexity, and cross-team influence. One L6 eng I reviewed had shipped a latency reduction of 40% but framed it as “optimization.” We repositioned it as “scaling critical search infrastructure during peak load,” which matched L6 scope. The packet advanced.
The problem isn’t your work — it’s how little of it is creditable. At Google, promotion is a storytelling problem, not a performance one.
> 📖 Related: Coffee Chat with an Apple PM vs. a Google PM: Navigating Different Corporate Cultures
What Should the Promotion Script Say in the 1:1?
Open with alignment, not request: “I want to make sure we’re synced on how my work maps to L5 expectations ahead of packet season.” This frames the conversation as calibration, not negotiation.
Then, deploy the script in three acts:
Act 1: Evidence Anchoring
“I led the latency reduction project — owned design, cross-team alignment with Ads and Infra, and drove the rollout under deadline. That hits L5 criteria on technical leadership and cross-functional execution.”
Not “I helped” or “we did” — use active voice to claim ownership. Passive language triggers discounting. In a hiring manager review I sat on, one candidate used “supported” eight times in their packet. The manager admitted they didn’t know what the candidate actually did.
Act 2: Perception Gap Probe
“I’d like your take: where do you think stakeholders might not fully see my role in this?”
This forces the manager to think beyond their own view. At Google, promotions fail when the manager hasn’t socialized credit. One eng believed their tech lead knew their contribution — but during calibrations, the lead said, “I assumed the infra team handled the hard parts.” The gap wasn’t performance; it was visibility.
Act 3: Sponsorship Trigger
“If we agree the evidence is there, can we lock in the packet draft by next week? I’ll send a write-up, but I’ll need your help shaping the narrative for the committee.”
Not “Can you review?” but “I need your help shaping.” This demands advocacy, not editing. The moment the manager invests language, they become a sponsor.
The script isn’t about getting approval — it’s about making silence costlier than action.
When Should You Raise Promotion in 1:1s at Google?
Three non-negotiable timing windows:
- 60 days before packet submission deadlines
- Within 2 weeks of a major project launch
- After positive peer feedback or kudos (especially from senior ICs)
In a Q2 2024 HC meeting, a candidate’s packet was deferred because the manager hadn’t briefed any peers. The work was strong, but the narrative hadn’t spread. The manager admitted they waited too long to start the conversation.
Never raise promotion in your first 1:1 after joining a team. It signals you care about ladder over learning. Wait at least 3–4 cycles to establish trust.
But don’t wait for “perfect” readiness. At Google, readiness is assessed after the packet is filed. The process rewards initiative, not patience.
One PM raised promotion 4 months post-L4 upgrade. Her manager pushed back: “You just leveled.” She responded: “I’m already operating at L5 scope — see the three cross-team initiatives I’ve unblocked.” She submitted the packet 8 weeks later. Approved.
The risk isn’t asking too early — it’s letting the manager define the timeline. Control the calendar, or they will.
> 📖 Related: Apple vs Google PM Interview: What Each Company Actually Tests
How Do You Prepare the Evidence for Your Promotion Ask?
Google’s ladder criteria are vague by design. “Increased scope,” “independent contributor,” “technical leadership” — these are judgment calls. Your job is to make the judgment obvious.
Map each impact to two ladder criteria. Example:
- Impact: Reduced login errors by 60% over 3 weeks
- L5 Criteria Met: Technical ownership (architected solution), cross-functional influence (coordinated SRE, UX, Trust & Safety)
Use the CAR framework — Challenge, Action, Result — but add a fourth element: Credit.
- C: Authentication failures spiking during holiday traffic
- A: Designed and drove rollout of fallback auth flow
- R: 60% error reduction, retained $2.3M in potential lost revenue
- Credit: Sole technical owner; presented outcome in Eng All-Hands
Not “what you did,” but “how easily others can attribute success to you.”
In a promotion packet I reviewed, an engineer listed “improved test coverage.” Boring. We reframed: “Prevented 15+ production rollbacks by building automated regression suite adopted by 3 core teams.” Now it’s influence.
Gather at least 3 pieces of social proof:
- Kudos in GChat or email (save them)
- Mentions in team updates
- Peer feedback in gReview
One eng had a senior director write: “This fix saved us from a major outage.” That quote made it into the packet — and the HC decision memo.
Evidence isn’t just what you did. It’s what others are willing to say you did.
How Do You Get Your Manager to Advocate, Not Just Approve?
Most managers default to feedback, not sponsorship. That’s a failure mode.
In a 2023 HC post-mortem, 7 of 12 rejected L5 packets had managers who wrote “solid contributor” but didn’t push for approval. One manager said: “I thought if the work was good, it would speak for itself.” It didn’t.
To convert approval into advocacy:
- Force the manager to name the ladder level
- Ask for specific language they’ll use in the packet
- Request pre-briefs with their skip or peers
Script:
“I want to make sure the packet reflects strong support. What words will you use to describe my readiness for L5? Will you call me ‘ready now’ or ‘close but needs more’?”
This makes vagueness impossible.
Then: “Are you comfortable pre-briefing [skip’s name] on my candidacy next week?”
If they hesitate, the answer is no.
Sponsorship means the manager risks their credibility. If they won’t, you’re not ready — or they don’t believe you’re worth the cost.
One PM had her manager agree to “highlight my role in the QBR.” Weak. We pushed for: “I’ll include a dedicated slide on her technical leadership and recommend promotion eligibility.” That’s sponsorship.
Not “they support you,” but “they’ll fight for you.”
Preparation Checklist
- Define the target level and align on packet deadline
- Map 3–5 key impacts to specific ladder criteria using CAR + Credit
- Collect at least 3 pieces of written peer or stakeholder feedback
- Draft a 1-page summary of promotion case for manager pre-read
- Script the 1:1 conversation using the three-act structure
- Identify 2–3 potential sponsors and plan pre-briefs
- Work through a structured preparation system (the PM Interview Playbook covers promotion packet writing with real debrief examples from Google L4–L6 cases)
Mistakes to Avoid
BAD: “I’ve been here 18 months — isn’t it time for a promo?”
GOOD: “My scope has expanded to lead cross-team architecture decisions — here’s how that meets L5 expectations.”
Rationale: Tenure isn’t a proxy for readiness. Google measures impact, not time served. One eng was denied twice despite 2-year tenure because their work stayed within team boundaries.
BAD: Sending a 10-slide deck the morning of the 1:1
GOOD: Sharing a 1-page summary 48 hours in advance with specific asks
Rationale: Managers need time to process. In a debrief, a hiring manager said: “I couldn’t endorse the packet because I hadn’t internalized the story.” Don’t ambush — pre-brief.
BAD: Asking, “Do you think I’m ready?”
GOOD: “Based on the work, I believe I’m at L5. Do you see any gaps in perception or evidence?”
Rationale: The first makes the manager judge you. The second makes them help you win. One candidate switched this phrasing — their manager went from passive to proactive in 2 days.
FAQ
The best time to ask is 60 days before packet deadlines — any later and the manager can’t influence the cycle. Google’s promotion windows are predictable: Q1 packets due in early April, Q3 in late September. Align your 1:1 timing to those dates, not your personal readiness calendar.
You should bring 3–5 evidence points tied to ladder criteria — not more. Hiring committees ignore bulk. One candidate included 12 projects. The HC noted: “No clear signal of what was truly impactful.” Focus beats volume.
If your manager says no, don’t argue — diagnose. Ask: “What specific behavior or outcome would change your assessment?” Then, lock in a 30-day check-in with measurable goals. One eng got rejected, set 2 clear milestones, and was promoted 10 weeks later. The delay wasn’t failure — it was data.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.