My Google Promotion Committee Rejected My IC6 Packet – What I Learned

In the summer of 2023 I submitted an IC6 promotion packet for a Senior Staff role on Google Maps Search. The committee voted 3‑2 against me, and the debrief lasted exactly 45 minutes. Below is the distilled judgment from that loop and three cycles that followed.

Why did my Google promotion committee reject my IC6 packet despite strong technical achievements?

The committee rejected the packet because it showed impact without the required leadership signal. In Q3 2023 the packet listed a 30 % reduction in routing latency for the Maps API, verified by a performance dashboard that I built with Data Studio.

The senior director of Maps Search (who had 12 years at Google) asked, “Where did you influence the roadmap?” during the debrief. The hiring manager, Priya Shah, echoed that question, noting that my peer reviews highlighted “excellent code” but no “cross‑team vision.” The Promotion Rubric assigns 40 % of the score to “Leadership & Influence,” and the committee’s vote reflected a shortfall there. Not a lack of technical depth, but a missing narrative of how I guided other engineers.

In the same debrief, a senior TPM from Google Cloud, Ravi Kumar, pointed out that my packet omitted any mention of the “Impact Matrix” I had authored for the Maps team. The matrix is a Google‑internal framework that maps individual contributions to product OKRs. Because I did not attach that matrix, the committee assumed my impact was isolated. The final vote was recorded as 2 “yes” from the Director of Engineering and 3 “no” from senior directors, a clear majority against.

What signals does Google’s Promotion Rubric prioritize over raw impact?

Google’s Promotion Rubric values breadth of influence more than isolated metrics. The rubric’s four pillars—Impact, Leadership, Judgment, and Execution—are weighted 30 %/40 %/15 %/15 %.

In my case the impact pillar was flawless: I shipped a feature that cut average routing time from 2.4 s to 1.7 s, saving the product $4 M in compute cost per year. However, the leadership pillar was rated “Needs Improvement” because I never led a cross‑functional OKR. Not the depth of the code, but the absence of a documented mentorship plan caused the committee to doubt my readiness for IC6.

During the committee meeting, the senior director from Ads (who sits on the same promotion committee) cited the “Google Leadership Ladder” as a reference. The ladder requires that an IC6 candidate have at least two “leadership narratives” with measurable outcomes. My packet contained only one narrative—improving latency—so the committee cited the missing second narrative as a decisive factor. The final written feedback said, “Your contributions are impressive, but the promotion rubric demands a demonstrated ability to lead at scale.”

> 📖 Related: Google L5 PM TC 2026 vs Meta E5 PM: Which Company Pays More?

How can I restructure my promotion packet to address the committee’s concerns?

The packet must be reframed to foreground leadership before impact. In the revised packet I added a “Leadership Narrative” that described how I organized a fortnightly “Maps Latency Guild” with 12 engineers across three teams, resulting in a 15 % reduction in duplicate work. I also attached the Impact Matrix that linked my latency work to the product’s Q4 2024 OKR of “Sub‑2‑second routing for 95 % of requests.” The matrix is a concrete artifact used by Google’s People Ops to evaluate cross‑team influence.

The committee’s next review, in Q1 2024, showed a 4‑1 vote in my favor after I added those artifacts. Not a change in the technical content, but a shift in presentation convinced the senior director of Ads to cast the decisive “yes.” The debrief note from the hiring manager read, “The added leadership narrative directly addresses the rubric’s missing piece.” The revised packet also listed a mentorship record: 3 junior engineers promoted to L4, each with a salary increase of $12 K‑$15 K, which satisfied the “Judgment & Execution” pillar.

When is the optimal window to raise a promotion appeal after a rejection?

The optimal window is within 30 days of the committee’s decision, when the feedback is still fresh. I filed an appeal on day 22, attaching a one‑page “Leadership Addendum” that referenced the same “Google Leadership Ladder” the committee used. The appeal was reviewed by the same five senior directors, but the process required a fresh vote. The appeal succeeded because the committee’s calendar allowed a re‑vote before the next promotion cycle on October 1.

If you wait beyond 45 days, the committee’s momentum shifts to the next cycle and the original feedback becomes a historical footnote.

In my case, the appeal was decided in a 3‑hour follow‑up meeting, and the final vote changed to 4‑1 in my favor. The senior director of Maps Search explicitly said, “We needed the leadership evidence; now it’s there, so the packet meets IC6 standards.” The appeal added $0 base change but unlocked a $30 000 equity grant and a $5 000 sign‑on bonus that were part of the IC6 compensation package.

> 📖 Related: Product Designer Interview Google vs Meta: How Whiteboard Design Challenges Differ

Who on the promotion committee can influence a reconsideration and how should I engage them?

The most influential members are the senior directors who own the “Leadership” pillar. In my case, Ravi Kumar (Senior Director, Google Cloud) and Maya Lin (Director, Google Ads) each hold veto power. Engaging them requires a concise “Leadership Update” email that references the exact rubric criteria they score. I sent a 200‑word note to Ravi on day 19, titled “Leadership Addendum – Impact Matrix Attached,” and copied the hiring manager. Ravi replied, “I’ll review this before the next vote.”

Not a generic thank‑you, but a data‑driven follow‑up that cites the rubric turns the conversation from polite to decisive. The follow‑up also mentioned my upcoming “Q4 OKR Review” where I will present the guild’s results to the broader organization, demonstrating future leadership. After the appeal, Maya Lin cast the decisive “yes,” and the packet was approved. The final compensation statement listed a base salary of $210 000, 0.04 % equity, and a $15 000 sign‑on, matching the IC6 level for senior staff engineers in 2023.

Preparation Checklist

  • Review the latest Google Promotion Rubric (the 2023 version that splits Leadership 40 %).
  • Extract two concrete leadership narratives from your recent projects; quantify mentorship outcomes.
  • Attach the Impact Matrix that maps your work to the team’s OKRs; include screenshots of the Data Studio dashboard.
  • Seek a pre‑review from a senior director not on your committee; incorporate their feedback on the leadership section.
  • Work through a structured preparation system (the PM Interview Playbook covers “Leadership Narrative Building” with real debrief examples).
  • Draft a one‑page “Leadership Addendum” that cites the Google Leadership Ladder and includes a timeline of cross‑team initiatives.
  • Schedule the appeal email within 30 days of the rejection, targeting the senior directors who own the Leadership pillar.

Mistakes to Avoid

BAD: Submitting a packet that lists only engineering metrics.

GOOD: Pair each metric with a leadership story that shows how you guided other engineers or influenced product direction.

BAD: Waiting six weeks to appeal, letting the committee move on.

GOOD: File the appeal within 30 days and attach a concise addendum that directly references the rubric criteria.

BAD: Sending a generic thank‑you note to the committee after a rejection.

GOOD: Send a data‑driven follow‑up that highlights the missing leadership evidence and requests a re‑vote.

FAQ

What if my promotion packet is rejected for “Leadership” but I have no formal people‑management experience?

The judgment is that leadership at Google is not limited to people‑management; it includes influencing cross‑team initiatives, mentorship, and OKR ownership. Document any guilds, working groups, or mentorship programs you have led, and tie them to measurable outcomes.

Can I appeal a promotion decision more than once in the same cycle?

The judgment is that a single appeal is allowed per cycle; a second appeal is treated as a new packet and must meet the full rubric. Use the first appeal to add the missing leadership evidence; a second attempt without new material will be rejected automatically.

How does the compensation differ between IC5 and IC6 after a successful promotion?

At Google in 2023 the base salary for an IC5 senior staff engineer averages $180 000, while an IC6 senior staff engineer averages $210 000. Equity typically rises from 0.02 % to 0.04 % of the company, and sign‑on bonuses increase from $5 000 to $15 000. The promotion also unlocks a higher stock vesting schedule and a larger annual performance bonus.amazon.com/dp/B0GWWJQ2S3).

Related Reading

Why did my Google promotion committee reject my IC6 packet despite strong technical achievements?