Peer Review Request Template for Google Promotion Committee: Getting Strong Endorsements

Peer Review Request Template for Google Promotion Committee: Getting Strong Endorsements

TL;DR

A strong peer review request is concise, specific, and makes it easy for colleagues to say yes by tying their feedback to the promotion packet’s impact metrics. Choose peers who have directly observed your leadership and impact, and send the request four to six weeks before the packet deadline so they have time to write thoughtful comments. Follow up once, politely, and never ask for generic praise — focus on concrete examples that demonstrate the competencies Google rewards.

Who This Is For

This guide is for Google employees at L4 or L5 who are preparing an L5 or L6 promotion packet and need to gather peer endorsements that will survive committee scrutiny. It assumes you have already drafted your self‑review and impact summary and now need external validation from teammates, cross‑functional partners, or managers you have worked with closely in the last 12 months. If you are early in your career or seeking a lateral move, the tactics here will still apply but you will weight different competencies.

What Should a Peer Review Request Email Include to Get Strong Endorsements for a Google Promotion Packet?

The request must state the promotion level, the deadline, and exactly which competencies you need evidenced, then attach a one‑sentence prompt that guides the peer to a specific story. In a Q3 promotion debrief, a senior L6 manager rejected a packet because three peer reviews said only “great teammate” without linking to impact; the committee could not map those comments to the leadership rubric. The problem isn’t the length of the email — it’s the vagueness of the ask.

Start with a clear subject line: “Peer review request for L5 promotion – feedback due by [date]”. In the body, remind the peer of a project you co‑led (e.g., “Remember the Checkout Flow redesign we shipped in Q2?”) and ask them to describe one instance where you demonstrated the competency you are highlighting (e.g., “How did I drive decision‑making when we faced conflicting data?”).

Attach a shortened version of your impact summary so they can refresh their memory without digging through old docs. End with a low‑friction ask: “If you can spare 15 minutes to jot down a few bullet points, I’ll incorporate them into my packet; otherwise, feel free to reply directly to this email.” This structure turns a favor into a simple, time‑boxed task.

How Do I Choose the Right Peers to Request Reviews From for Google L5/L6 Promotion?

Select peers who have observed you in situations that map to the promotion competencies — ideally a mix of direct reports, peer partners, and a stakeholder who is not your manager. In an HC meeting for an L5→L6 case, the committee noted that four out of six reviews came from the same team, creating an echo chamber that failed to show cross‑functional influence. The problem isn’t quantity — it’s diversity of perspective.

Identify three categories: (1) someone who has seen you lead a team or mentor junior engineers, (2) a partner from another function (e.g., UX, data science) who can speak to your influence without authority, and (3) a senior individual contributor who can comment on your technical depth and judgment.

Aim for at least two reviewers from each category; if you lack a category, consider asking a former manager from a prior rotation who still works at Google. Avoid requesting reviews from close friends who may give overly positive, non‑specific feedback; the committee discounts endorsements that lack concrete detail.

When Is the Best Time to Send Peer Review Requests Relative to the Promotion Cycle?

Send the initial request four to six weeks before the packet submission deadline, giving peers enough window to write, review, and return feedback without feeling rushed. In a promotion cycle walkthrough, a senior HRBP explained that packets arriving less than two weeks before the deadline often contain peer notes that are generic or copied from past reviews because colleagues had to rush. The problem isn’t the deadline itself — it’s the lack of buffer time for quality reflection.

Mark the date on your calendar when the promotion packet is due (usually the first Monday of the review month). Count back six weeks and set that as your “request send” date. If you know a peer is going on vacation or has a known busy period (e.g., quarter‑end), adjust the request earlier or offer to extend the deadline for them specifically. After sending, schedule a single follow‑up reminder three days before your internal deadline; a second nudge is perceived as nagging and reduces the likelihood of a thoughtful response.

How Do I Follow Up on Peer Review Requests Without Annoying Colleagues?

A single, polite reminder sent three days before your internal feedback deadline is sufficient; any more than that signals poor planning and damages trust. In a promotion debrief, an L5 manager confessed that after sending three follow‑up messages to the same peer, the peer replied with a one‑line “looks good” just to stop the emails, which the committee later flagged as low‑quality endorsement. The problem isn’t forgetting to follow up — it’s over‑communicating urgency.

Your reminder should restate the deadline, acknowledge their workload, and offer an easy out: “Hi [Name], just checking in — if you’re unable to provide feedback by [date], no worries at all; I understand priorities shift.” This gives them an honorable way to decline without guilt, and most peers will either respond promptly or explicitly say they cannot help, allowing you to seek an alternative reviewer. Never attach a long questionnaire or ask for a meeting; keep the ask as lightweight as possible.

What Common Mistakes Weaken Peer Review Endorsements and How Can I Avoid Them?

The most damaging mistake is asking for generic praise instead of concrete, competency‑linked stories; another is failing to provide context that jogs the peer’s memory; a third is submitting reviews that arrive after the packet deadline, which the committee treats as missing. In an L4→L5 review, the committee rejected a candidate because two peer reviews arrived two days late, and the packet was marked incomplete despite strong self‑review scores. The problem isn’t the quality of the feedback — it’s the timing and relevance.

To avoid vague praise, give each peer a one‑sentence prompt that ties directly to a promotion competency (e.g., “Describe a time you saw me resolve a conflict between engineering and product”). To avoid memory gaps, include a two‑sentence refresher of the project outcome and your role.

To avoid late submissions, set your internal deadline at least five days before the official packet due date and communicate that date clearly in both the initial request and the reminder. Finally, always thank the peer by name in your packet acknowledgments; this reinforces the relationship and encourages future support.

Preparation Checklist

• Draft a list of promotion competencies you need evidenced and map each to a specific project or interaction.
• Identify at least three peers per competency category (leadership, cross‑functional influence, technical judgment) and verify they have worked with you in the last 12 months.
• Write a master email template that includes the promotion level, deadline, project reminder, and a one‑sentence competency prompt.
• Set your internal feedback deadline five days before the official packet due date and calendar reminders for the initial send and the single follow‑up.
• Work through a structured preparation system (the PM Interview Playbook covers peer review request strategies with real debrief examples) to refine your prompts and timing.
• After receiving each review, copy the relevant excerpt into your packet and note the peer’s name and role for the acknowledgments section.
• Run a final packet sanity check with a trusted mentor to ensure every peer comment maps to a competency and no section relies on vague praise.

Mistakes to Avoid

BAD: Sending a peer review request that says, “Please write a short paragraph about my strengths.”

GOOD: Sending a request that says, “In the Checkout Flow redesign, how did I facilitate agreement between the UX and backend teams when we disagreed on the API contract?”

BAD: Asking the same peer for feedback twice in one week because you forgot to set a deadline.

GOOD: Setting a clear date in the first email and sending only one reminder three days before that date, with an explicit “no worries if you can’t” line.

BAD: Submitting peer reviews that arrive two days after the packet deadline, causing the packet to be marked incomplete.

GOOD: Aligning your internal feedback deadline five days before the official cutoff and confirming receipt of each review before the final packet lock‑date.

FAQ

How many peer reviews should I include in my Google promotion packet?

Include a minimum of four distinct peer reviews that each address a different promotion competency; the committee looks for breadth of impact, so aim for five to six if you have strong candidates across leadership, influence, and technical depth.

Can I ask my manager to also serve as a peer reviewer?

No — manager feedback is captured in the separate manager review section; peer reviews must come from individuals who do not have direct authority over your performance rating to avoid conflicts of interest.

What if a peer declines to provide feedback?

Thank them for their honesty, then quickly replace them with another qualified colleague from the same competency category; never pressure a declined peer, as that can harm relationships and yield low‑quality endorsements if they relent.amazon.com/dp/B0GWWJQ2S3).