Most engineers fail to secure promotions during 1on1s because they treat the meeting as a status update, not a negotiation. The right agenda shifts focus from tasks completed to impact demonstrated and role alignment. You don’t need permission to act like the next level — you need evidence that you already are.
1on1 Meeting Agenda Template for Asking for Promotion at Google
TL;DR
Most engineers fail to secure promotions during 1on1s because they treat the meeting as a status update, not a negotiation. The right agenda shifts focus from tasks completed to impact demonstrated and role alignment. You don’t need permission to act like the next level — you need evidence that you already are.
Not sure what to bring up in your next 1:1? The SRE Interview Playbook has 30+ high-signal questions organized by goal.
Who This Is For
This is for mid-level software engineers and product managers at Google (L4–L5) who have delivered consistent results over 12–18 months and are preparing to ask for promotion during a 1on1 with their manager. It’s not for those whose last review was “Needs Improvement” or who haven’t led a cross-functional project in the past year. If your peer group has more L5s than L4s, and you’re doing L5 work without the title, this applies to you.
How should I structure a 1on1 agenda when asking for promotion at Google?
Frame the 1on1 as a calibration meeting, not a request. I sat in a Q3 HC where an L4 PM brought a 2-page agenda outlining six outcomes, four of which matched L5 scope — but opened with “I’d like to discuss my growth path.” The committee rejected the packet. Why? The manager hadn’t been primed.
Your agenda must signal inevitability, not aspiration. Start with impact: “Three wins that align with L5 expectations” — not “areas where I’d like to grow.” Use Google’s Career Ladder definitions verbatim. For L5, that means “driving medium-scale projects with cross-team impact.” Name the doc, cite the line.
Not “Can I be considered for L5?” but “Here’s how I’ve operated at L5 scope since Q1.” One engineer at Mountain View included a table mapping his shipping velocity (7 major releases in 10 months) to the L5 bar for “consistent delivery under ambiguity.” His packet passed HC on first submission.
Structure the agenda in four blocks:
- Impact summary (3–4 key results with metrics)
- Role alignment (mapping to next-level ladder criteria)
- Gap analysis (one acknowledged development area — no more)
- Next steps (promotion packet draft timeline, peer feedback plan)
The goal isn’t to persuade in the meeting — it’s to make refusal require justification.
What evidence do I need to bring to justify a promotion at Google?
Raw output isn’t evidence — narrative is. At a DPC (Design, Product, and Engineering Promotion Committee) debrief last November, a candidate had shipped 12 features but failed promotion because the manager said, “They executed well, but didn’t set the direction.” The committee ruled: “Delivery without leadership is not L5.”
Evidence must show scope, influence, and independence. For L4→L5, that means:
- At least one project requiring alignment across 2+ teams
- Metrics showing measurable business impact (e.g., 15% reduction in latency, 10% increase in user engagement)
- Documentation where you authored the design, not just implemented it
One L4 engineer included a slide showing he’d proposed the architecture for a new search indexing pipeline, led the rollout across three infra teams, and reduced query cost by $2.3M annually. That wasn’t just evidence — it was irrefutable.
Not “I helped launch Feature X” but “I initiated Project X after identifying a 20% efficiency gap, secured buy-in from Ads and Cloud, and shipped in 5 months.”
Quantify everything. If your work improved system reliability, state MTTR before and after. If it increased adoption, cite DAU/MAU lift. No metrics? No promotion.
How far in advance should I prepare for a promotion-focused 1on1?
Start documenting 6 months before the meeting. The strongest packets are built incrementally, not drafted overnight. In a hiring manager roundtable last June, one director revealed that 70% of successful L5 candidates began informal calibration with their manager 4–5 months before submission.
At Google, promotion cycles move slowly. DPCs meet quarterly. Drafts are due 6 weeks before the meeting. Peer feedback takes 2–3 weeks to collect. If you walk into a 1on1 cold, you’re already behind.
Begin with a private log: every project, decision, and conflict resolution — with dates and outcomes. Every 2 weeks, update a “promotion file” with new evidence. By the time you schedule the 1on1, you’ll have 10–12 concrete examples.
Not “I’ll prepare after my next project” but “I’m treating every sprint as a data point.”
Schedule the 1on1 8–10 weeks before the packet deadline. That gives 4 weeks to incorporate feedback, 2 weeks to gather peer input, and 2 weeks for final edits. Anything less risks rushed, thin packets.
How do I handle manager resistance when asking for promotion?
Assume resistance is procedural, not personal. In a Q2 HC, an L5 candidate was blocked because his manager wrote, “They’re ready, but we haven’t done peer feedback yet.” The committee responded: “Manager did not advocate.” The packet failed.
Resistance often stems from process gaps, not performance doubt. Your job is to reduce the manager’s workload, not increase it. Bring a complete draft — not a request for guidance. One L4 SWE at Ads prepared a 10-slide packet, pre-filled peer feedback forms for five colleagues, and proposed a 3-week review timeline. His manager approved it with one edit.
Not “Can we talk about my growth?” but “Here’s a draft for your review — I’ve scheduled feedback sessions with X, Y, Z.”
If the manager says “You’re not quite there,” ask: “What specific outcome, if achieved by [date], would meet the bar?” Force specificity. Vague feedback like “need more leadership” is a stall tactic.
One engineer was told “You need broader impact” — so he initiated a docs standardization project across three teams. Shipped it in 6 weeks. Got promoted that cycle.
The problem isn’t resistance — it’s failing to convert feedback into action items.
How can I use peer feedback to strengthen my promotion case?
Peer feedback isn’t support — it’s corroboration. At a recent DPC, a candidate had strong manager endorsement but weak peer feedback. One peer wrote: “I only interacted with them during reviews.” The committee concluded: “No organic influence.” Promotion denied.
Feedback must show you operate independently and influence without authority. Target 5–7 peers: 2 from your team, 3 from adjacent teams, 1–2 from leadership. Ask for specific examples — not general praise.
One L5 PM candidate circulated a feedback form with: “Describe a time I helped unblock your team” and “How did my work affect your roadmap?” Three peers cited her mediation in a API dispute between Android and Assistant. That became a key exhibit.
Not “Please say nice things” but “I’m compiling evidence for DPC — can you recall a moment my work impacted your team?”
Send requests 3–4 weeks before the packet deadline. Follow up in writing: “Per our chat, you mentioned I helped prioritize the auth overhaul — is that accurate?” That creates a paper trail.
Peer feedback that repeats manager points is useless. It must add new dimensions: collaboration, visibility, influence.
Preparation Checklist
- Document every major project outcome with metrics and dates — start 6 months in advance
- Map your work to the exact language in Google’s Career Ladder for the target level
- Schedule the 1on1 8–10 weeks before the DPC deadline to allow time for revisions
- Draft a promotion packet before the meeting — include slides on impact, scope, and peer feedback
- Identify 5–7 peers for feedback and initiate conversations 3 weeks pre-deadline
- Work through a structured preparation system (the PM Interview Playbook covers promotion packet strategy with real DPC debrief examples from Google L4–L6 cycles)
- Define one development area — no more — and pair it with a mitigation plan
Mistakes to Avoid
BAD: Starting the 1on1 with “I’d like to discuss my career growth.”
This frames you as uncertain. Managers hear it weekly. It triggers a coaching response, not a promotion discussion.
GOOD: Opening with “I’ve been operating at L5 scope since Q1 — here’s how. I’d like your feedback on my draft packet for this cycle.”
This assumes the frame. It shifts the conversation from “if” to “how.”
BAD: Submitting a packet with 10 projects and no clear narrative.
Volume without synthesis signals execution, not leadership. DPCs reject overloaded packets.
GOOD: Presenting 3–4 well-documented outcomes that map directly to ladder criteria.
One engineer used a single slide: “Three Projects, One Pattern” — showing how each demonstrated cross-team influence. It became a talking point in HC.
BAD: Relying solely on manager praise without peer corroboration.
One candidate had a glowing manager review but peer comments like “rarely interacted.” DPC ruled: “No evidence of influence beyond team.”
GOOD: Including peer quotes that highlight unplanned collaboration.
“Reached out when we hit a blocking issue” or “proposed a fix we hadn’t considered” — these prove organic impact.
FAQ
Is it appropriate to bring a promotion agenda to a regular 1on1?
Yes, if you’ve earned it. In a 1on1, agenda control signals confidence. The risk isn’t overreach — it’s poor timing. If your last review wasn’t strong, or you haven’t led a major project in 12 months, it will backfire. Bring data, not desire. One L4 waited until after shipping a core latency fix before introducing the agenda. It worked because the impact was fresh and measurable.
What if my manager says I’m not ready?
Ask for the specific gap in writing. “What outcome, if delivered by [date], would meet the bar?” Vague feedback is deflection. One engineer was told “need more ownership” — he responded with a proposal to lead the next quarter’s infra migration. Got approval. Shipped it. Promoted 4 months later. The issue wasn’t readiness — it was failing to convert feedback into action.
How detailed should my promotion packet be?
10–12 slides maximum. DPC members spend ~7 minutes per packet. Use the “slide test”: can the reviewer grasp your impact in 30 seconds? Include one slide on metrics, one on cross-team impact, one on leadership moments. One L5 candidate used a timeline showing decision points where he drove consensus. It became a model for others. Clarity beats comprehensiveness.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.