Google PM IC5 to IC6 Promotion Packet: Real Examples and Templates

Google PM IC5 to IC6 Promotion Packet: Real Examples and Templates

TL;DR

The IC5 to IC6 promotion packet at Google is a structured business case that proves sustained impact, leadership breadth, and readiness for larger scope—not a simple performance summary. Successful packets combine quantitative metrics, narrative storytelling, and clear evidence of cross‑functional influence, reviewed twice a year in the promotion cycle. Candidates who treat the packet as a strategic document, not a checklist, consistently earn the IC6 band.

Who This Is For

This guide is for Google‑employed Product Managers at IC5 (L5) who have delivered at least two major launches, own a product area with measurable KPIs, and are seeking the IC6 (L6) band within the next 12‑18 months. It assumes you have access to your performance data, stakeholder feedback, and the ability to draft a 5‑page packet plus supporting artifacts. If you are still in your first year at IC5 or lack clear impact metrics, focus first on building those foundations before using this framework.

What Does a Google PM IC5 to IC6 Promotion Packet Actually Include?

A promotion packet consists of five core components: impact summary, leadership examples, scope expansion, peer feedback, and a future‑oriented plan. The impact summary quantifies outcomes using Google‑specific metrics such as MAU growth, revenue lift, or cost savings, typically presented in a two‑page table with baseline, target, and actual figures. Leadership examples describe situations where you influenced without authority, such as driving a cross‑functional OKR that spanned three orgs, and must include the challenge, your actions, and the measurable result. Scope expansion shows how you have taken on responsibilities beyond your IC5 role, for example managing a product line that generates $15M ARR or mentoring four IC4 PMs. Peer feedback is collected via Google’s internal feedback tool and distilled into three thematic strengths with direct quotes. The future‑oriented plan outlines the next 18‑month vision for your area, aligning with org goals and proposing two to three stretch initiatives. Each component must be limited to one page unless the data tables require extra space, keeping the total packet to five pages plus an appendix of raw data.

How Do I Demonstrate Impact and Leadership for an IC6 Promotion at Google?

Impact is demonstrated by tying your work to business outcomes that exceed the IC5 bar by at least 30 % in magnitude or scope. For example, if your IC5 goal was to increase adoption of a feature by 10 %, an IC6‑level impact would show a 25 % increase that also reduced support costs by $500K annually. Leadership is shown through narratives where you set direction for teams you do not manage, such as aligning Android and iOS teams on a unified privacy framework that launched three months ahead of schedule. Use the STAR format but replace the “Result” with a quantifiable metric and a second‑order effect (e.g., “Result: 15 % uplift in daily active users, which enabled the sales team to close $2M in new enterprise contracts”). Include at least two leadership stories that involve influencing senior stakeholders (Director or VP level) and one story where you resolved a conflict between two orgs with competing priorities.

What Are the Key Differences Between IC5 and IC6 Expectations at Google?

At IC5, expectations focus on executing a defined product roadmap with clear metrics and delivering high‑quality launches. At IC6, the expectation shifts to owning the product strategy, influencing org‑level priorities, and delivering impact that scales across multiple products or platforms. An IC5 PM might be responsible for a single feature set with a $2M annual budget; an IC6 PM typically oversees a product line with a $10M‑$20M budget and is accountable for its P&L. The IC6 bar also requires evidence of developing others: at least two formal mentorship relationships where mentees achieved promotion or significant skill growth within six months. Finally, IC6 candidates must show they can navigate ambiguity—leading a project with incomplete data, making a call that later proved correct, and documenting the decision process for future reference.

How Long Does It Typically Take to Prepare an IC5 to IC6 Promotion Packet at Google?

Preparing a competitive packet takes six to eight weeks of part‑time effort, assuming you already have performance data and stakeholder feedback. The first two weeks are spent gathering quantitative results: extracting dashboard data, calculating percent changes, and validating numbers with your manager. Weeks three and four focus on drafting the impact summary and leadership narratives, iterating with a trusted peer or mentor for clarity and conciseness. Week five is dedicated to collecting and shaping peer feedback into three concise themes. Week six involves writing the future‑oriented plan and aligning it with org OKRs, often requiring a brief sync with your director. The final one to two weeks are for polishing the packet, adding an appendix of raw data, and running a mock review with your manager or HRBP to catch any gaps. Packets assembled in less than four weeks tend to lack depth and are frequently sent back for revision.

What Common Mistakes Do Candidates Make in Their IC5 to IC6 Promotion Packets?

Mistake 1 – Overloading with Activities, Not Outcomes

BAD: Listing every meeting you attended, every doc you wrote, and every bug you triaged without tying them to metrics.

GOOD: Selecting three to five high‑leverage initiatives and showing how each moved a key KPI (e.g., “Led the redesign of the checkout flow, which increased conversion by 3.2 % and added $1.8M in quarterly revenue”).

Mistake 2 – Vague Leadership Claims

BAD: Stating “I influenced stakeholders to adopt my vision” without describing the influence tactics or the resistance faced.

GOOD: Describing a specific situation: “When the Ads team resisted adding a new user‑consent layer, I presented A/B test data showing a 0.4 % drop in CTR but a 2.1 % increase in trust score, then facilitated a joint decision‑making workshop that resulted in a shared implementation plan.”

Mistake 3 – Ignoring the Future‑Oriented Plan

BAD: Submitting a packet that only looks backward at past achievements.

GOOD: Including a one‑page plan that outlines two stretch goals for the next 18 months (e.g., “Launch a machine‑learning‑driven recommendation surface expected to lift engagement by 8 % and pilot a cross‑org data‑sharing framework to reduce duplication effort by 15 %”).

Preparation Checklist

• Gather all quantitative results from the last 12 months and validate them with your manager’s dashboard.
• Draft impact summary using the formula: Baseline → Target → Actual → Business Value (in dollars or user impact).
• Write two leadership narratives using the STAR‑plus‑second‑order‑effect format, each under 250 words.
• Collect peer feedback via Googlegeist and distill into three themes with direct quotes.
• Outline a future‑oriented plan that ties to org OKRs and includes two stretch initiatives with rough effort estimates.
• Work through a structured preparation system (the PM Interview Playbook covers promotion packet framing with real debrief examples).
• Run a mock review with your manager or HRBP, incorporate feedback, and finalize the appendix of raw data.

Mistakes to Avoid

(Already covered in the H2 section; this block reinforces the BAD vs GOOD format with concise examples.)

BAD: Submitting a packet that is six pages of dense paragraphs with no visual hierarchy.

GOOD: Using clear headings, bullet points for metrics, and limiting narrative blocks to 150 words each; include a one‑page table of KPI trends.

BAD: Relying solely on self‑assessment without external validation.

GOOD: Including at least three peer quotes that explicitly mention your impact on team outcomes or strategic direction.

BAD: Treating the packet as a formality and completing it the week before the deadline.

GOOD: Starting six weeks out, setting weekly milestones, and treating the packet as a living document that evolves with feedback.

FAQ

How many pages should the IC5 to IC6 promotion packet be?

The packet should be five pages of core content plus an appendix of raw data. Each of the five sections—impact, leadership, scope, feedback, future plan—fits on one page unless a data table requires extra space; keep the total under six pages to respect reviewers’ time.

What salary increase can I expect moving from IC5 to IC6 at Google?

Base salary typically rises from the IC5 band of $170,000‑$210,000 to the IC6 band of $210,000‑$260,000, representing an increase of $30,000‑$50,000 depending on location and performance. Equity refresh grants also increase, often from 0.03 % to 0.05‑0.07 % of shares annually.

Can I reuse my performance review documents in the promotion packet?

You can extract metrics and quotes from your performance review, but you must re‑frame them to meet the promotion bar: show how those results exceed IC5 expectations, demonstrate leadership beyond your immediate team, and connect to org‑level strategy. Simply copying review text without this elevation usually results in a packet that is deemed insufficient.

The 0→1 PM Interview Playbook (2026 Edition) — view on Amazon →