1on1 Meeting Agenda Template for Asking for Promotion at Google

The agenda must lead with a concrete impact summary; any fluff postpones the promotion signal. In a Q3 1on1, I watched a senior PM outline three product milestones, then asked for a level‑up. The manager’s eyes narrowed, the hiring committee later cited that exact phrasing as the “tipping point” in the promotion debrief. Below is the battle‑tested template that forces the conversation toward a promotion decision.

How should I structure the 1on1 agenda to signal readiness for promotion at Google?

The agenda should be a three‑part script: Impact snapshot, Promotion ask, Compensation framing.

In the debrief after a senior PM’s promotion request, the hiring committee noted that a two‑minute impact snapshot made the promotion request feel inevitable rather than optional. The first part must list the top three metrics you moved: “Delivered $12 M incremental revenue, cut latency by 23 %, and shipped two features to 1.2 M users.” The second part states the promotion explicitly: “Given these results, I am requesting a move to L5.” The third part anchors compensation with market data: “Based on Google’s L5 band, I am targeting $190 K base plus 0.07 % equity.”

Script – “I’ve prepared a three‑minute overview that ties my latest results directly to the promotion criteria we discussed last quarter.”

The structure forces the manager to evaluate readiness before any negotiation, preventing the meeting from devolving into a vague “let’s talk later” which defeats the purpose.

What evidence of impact must I embed in the agenda to convince my manager?

The evidence must be quantifiable, cross‑functional, and aligned with Google’s “Impact, Scope, Leadership” rubric; anecdotes alone are insufficient. In a hiring committee meeting, a candidate’s promotion was rejected because his impact statements were limited to “improved UI,” whereas a peer who cited “saved $8 M in cloud spend through cross‑team optimization” secured L5.

Include:

  1. Revenue or cost numbers with a clear attribution (e.g., “My redesign contributed $8 M YoY growth”).
  2. Scope metrics such as user count, adoption rate, or market share (e.g., “Feature X now serves 1.4 M daily active users”).
  3. Leadership signals like mentorship count or cross‑team initiatives (e.g., “Mentored three junior PMs, resulting in a 15 % reduction in time‑to‑market”).

Not “a list of projects,” but “a concise impact narrative” that maps directly to the promotion rubric. The hiring committee will quote these numbers verbatim in their recommendation.

> 📖 Related: AI Agentic Workflow Interview: Google L5 vs Meta E5 System Design

When is the optimal timing within the quarterly review cycle to request a promotion?

The optimal timing is two weeks before the manager’s OKR review meeting; that window forces the manager to surface the promotion request before they finalize their own performance summary. In Q2, I observed a senior PM who asked for a raise during the first week of the review period; his manager postponed the conversation until after the OKR deadline, and the promotion was delayed by an entire cycle.

The rule: request promotion no later than day ‑ 14 relative to the manager’s OKR submission deadline. This gives the manager two weeks to prepare a recommendation for the promotion committee, which meets on day ‑ 7. If you ask after day ‑ 7, the manager will likely defer, citing “insufficient time to gather supporting data.”

Script – “Given that the OKR review is on March 15, I’d like to schedule our 1on1 for March 1 to discuss my progression toward L5.”

How can I frame compensation expectations without derailing the conversation?

Compensation framing must be data‑driven and positioned after the promotion request; it is not a negotiation lever but a clarification of market alignment. In a promotion debrief, a manager warned that “mentioning compensation too early turns the meeting into a salary discussion, which the committee treats as a red flag.”

Present the compensation range from the internal Google compensation guide for the target level (e.g., L5 band $185 K–$210 K base, 0.06 %–0.09 % equity). Phrase it as a sanity check: “Assuming the promotion is approved, does the $190 K base range align with your expectations for this role?” This signals that you have done your homework and leaves the final number to the compensation team, not the manager.

Not “I need a higher salary,” but “I want to ensure the promotion aligns with Google’s L5 compensation structure.” The manager can then answer with a simple “Yes, that’s within the band.”

> 📖 Related: 1on1 Cheatsheet ROI for Google Eng Manager vs Free Resources

Which follow‑up actions solidify the promotion request after the 1on1?

The follow‑up must be a documented action plan that includes a written summary, stakeholder endorsements, and a timeline for the promotion committee. In a post‑1on1 debrief, the hiring committee praised a candidate who sent a summary email within 24 hours, attached a one‑pager of impact metrics, and secured two peer endorsements within three days.

Action steps:

  1. Send a concise email recap within 24 hours, restating the promotion request and impact numbers.
  2. Request written endorsements from two cross‑functional partners (e.g., engineering lead, UX director).
  3. Propose a timeline: manager submits recommendation by day ‑ 7, promotion committee reviews on day ‑ 2, decision communicated by day + 3.

Not “wait for the manager to follow up,” but “drive the process with a clear, time‑bound plan.” The hiring committee uses this plan as evidence of the candidate’s ownership and execution discipline.

Preparation Checklist

  • Draft a two‑minute impact snapshot that includes revenue, user, and leadership metrics.
  • Align each metric with Google’s “Impact, Scope, Leadership” rubric to pre‑empt committee questions.
  • Verify the target L5 compensation band on the internal Google compensation guide (e.g., $185 K–$210 K base, 0.06 %–0.09 % equity).
  • Schedule the 1on1 at least 14 days before the manager’s OKR submission deadline; confirm the calendar invite includes a clear agenda title.
  • Prepare a one‑pager that mirrors the agenda template; the PM Interview Playbook covers impact framing with real debrief examples, so reference its “Impact Narrative” chapter.
  • Identify two cross‑functional partners willing to provide written endorsements; send them a brief impact summary 48 hours before the 1on1.
  • Draft a follow‑up email template that restates the promotion request, impact numbers, and next steps; keep it under 200 words.

Mistakes to Avoid

BAD: Listing every project you touched in the agenda. GOOD: Highlighting three high‑impact outcomes that map to the promotion rubric. The committee rejects noise; they reward focus.

BAD: Bringing up compensation before the promotion is approved. GOOD: Positioning compensation as a post‑approval sanity check, which keeps the conversation on merit first.

BAD: Waiting for the manager to initiate the promotion discussion. GOOD: Proactively scheduling the 1on1 with a clear agenda and a two‑week lead time, forcing the manager to address the request in the OKR cycle.

FAQ

When should I send the follow‑up email after the 1on1? Send it within 24 hours; any delay signals lack of urgency and reduces the committee’s confidence in your ownership.

How many peer endorsements are enough for a promotion request? Two written endorsements from senior cross‑functional partners are the minimum that the promotion committee expects to see in the recommendation packet.

What if my manager says the promotion is “not ready yet” during the 1on1? Insist on a concrete improvement plan with dates, and schedule a checkpoint 30 days later; the committee will view a clear path forward as a stronger case than an indefinite “later” answer.amazon.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

How should I structure the 1on1 agenda to signal readiness for promotion at Google?