The Hiring Committee and the Packet Review

You Are Not in the Room When the Decision Is Made

At Google, Meta, and several other top companies, the person who interviews you does not make the hiring decision. This surprises most candidates and has a critical implication for how you should behave during the interview.

How the Process Works:

1. The Interview: You meet with 4–6 interviewers over a day (or across multiple sessions). Each interviewer is assigned specific dimensions to evaluate — one might focus on coding, another on system design, another on behavioral/leadership.

2. The Packet: After the interview, each interviewer writes a detailed written report. This packet includes: a verbatim or near-verbatim transcript of your code, direct quotes from your explanations, specific behavioral examples you gave, and a structured rating (Strong Hire / Hire / Lean No Hire / No Hire / Strong No Hire).

3. The Hiring Committee (HC): A group of senior leaders — none of whom met you — reads all the packets and makes the final decision. At Google, this committee is specifically designed to be independent of the hiring team to prevent bias and maintain consistency.

4. The Implication: You are not trying to convince the interviewer. You are giving the interviewer ammunition — specific, concrete, quotable material — to advocate for you in a room you will never enter.

What This Means in Practice:

• Bad: Explaining your solution verbally while waving at a whiteboard. The committee cannot see the whiteboard. If the interviewer's notes say "candidate drew something on the board," that is worthless.
• Good: Writing clean, commented code that stands on its own. If the committee reads your code without any context, they should be able to understand your intent.
• Bad: Saying "you know what I mean" or trailing off mid-explanation. The interviewer may understand, but they cannot quote "you know what I mean" in a packet.
• Good: Stating your reasoning explicitly. "I'm choosing a hash map here because lookup is O(1) and we don't need ordering." That sentence can be quoted verbatim in the packet.
• Bad: Giving a vague behavioral answer: "We worked together to solve the problem." The committee cannot assess your individual contribution from that.
• Good: Specific, first-person, measurable: "I identified the bottleneck, proposed the fix, wrote the migration script, and coordinated the rollout with three downstream teams. Latency dropped from 800ms to 120ms."