A lot of candidates finish their onsite and then hear a phrase they didn't expect: "Your packet is going to the hiring committee." We've written feedback that went into those packets, and we've been in the rooms where decisions got made. Here's what the committee actually does, and what that means for you.

What is a hiring committee?

A hiring committee is a small group of people who decide whether you get an offer, based on what your interviewers wrote about you. At Google, which made the idea famous, it's usually a handful of senior engineers or managers. Most of them have never met you.

The point is to take the decision away from any one person. If a single interviewer had a bad day or a strong bias, the committee is supposed to catch it. It also keeps the hiring bar the same across teams, so one eager manager can't lower it just to fill a seat.

Which companies use a hiring committee?

Google is the classic example. After your loop, your interviewers' feedback gets bundled into a packet, and a committee reviews it. The order of steps has shifted over the years. For some levels and regions, you do team matching first and the committee reviews your packet with a team already attached. Ask your recruiter which order applies to you. Our Google interview process guide has more on the loop itself.

Meta has its own review after the loop. Candidates describe a meeting where the interviewers' feedback gets discussed, followed by a broader review that mostly confirms the decision and settles your level. Then you move on to team matching. See our Meta interview process guide.

Amazon works differently. There's no separate committee. Instead, everyone who interviewed you meets in a debrief, and that meeting is run by a Bar Raiser. That's a specially trained interviewer from outside the hiring team. Amazon describes the Bar Raiser as someone who drives the discussion and makes the final call together with the hiring manager. See our Amazon interview process guide.

Apple, Microsoft, Netflix, and Nvidia lean more on the hiring team itself. At Apple, for example, candidates report a meeting where the interviewers vote after the loop. The hiring manager usually carries a lot of weight at these companies. You can read more in our Apple, Microsoft, Netflix, and Nvidia guides.

What does the hiring committee actually look at?

They read. They don't watch a recording of you, and they don't rerun your code. They look at a packet that usually includes:

• Each interviewer's written notes on what you did
• Each interviewer's score, on a scale like strong hire, hire, lean hire, and so on
• Your resume
• Sometimes your code or whiteboard work as the interviewer captured it
• Sometimes notes from the recruiter or a hiring manager

This is why what your interviewer can write down matters so much. If you said "I'd use a hash map here because lookups are O(1) and we'll check membership on every step," your interviewer can quote that. If you quietly typed the right answer, the committee just sees "got it" with no detail. Specific notes make a much stronger case than vague ones.

If you want to know what those scores mean, we explain the full scale in what interviewers look for in coding interviews.

How does the committee handle mixed feedback?

Mixed feedback is really common. Plenty of people get an offer with one weaker round in their packet.

The committee looks at the whole picture. A lean hire sitting next to several hires usually still passes. One lean no hire can be outweighed if your other rounds were strong and the notes explain why that round went sideways. Two or more negative rounds are much harder to get past.

They also read the reasons behind a score. Say one interviewer gave a lean no hire because you needed a hint, but wrote that you recovered well and your code was clean. That lands very differently from a lean no hire that says you couldn't explain your own solution. A committee cares about the details, not just the number.

Sometimes the committee can't decide. In that case they may ask for one more interview to get more signal. That's not a rejection. It means they saw enough to want a closer look.

What is leveling, and what does down-leveling mean?

Your level decides your title, your pay band, and what's expected of you. You probably applied for a specific level, like L4 at Google or E5 at Meta. The committee checks whether your interviews actually support that level.

Down-leveling is when they decide to offer you a job, but one level lower than you applied for. It usually comes from the system design or behavioral rounds, since those are where interviewers judge how senior you are. Coding rounds matter less for this. It happens a lot. In an interviewing.io write-up on negotiating with Meta, about 55% of the candidates they surveyed said they'd been down-leveled.

A down-level can feel like a slap, but it's still an offer. You can ask your recruiter what the feedback was, and sometimes you can push back if a competing offer is at the higher level. Just know that the level is harder to change than the salary.

How long does a hiring committee review take?

The review itself often happens within a week or two of your onsite. The wait mostly comes from everything around it. Every interviewer has to finish their write-up first, and the committee may only meet on certain days. At Google, team matching can add weeks on top of that, either before or after the committee.

If you're stuck waiting, our guide on how long it takes to hear back after an interview covers when and how to check in.

What can I still influence after the interview?

Honestly, not much. By the time your packet reaches the committee, your interviews are written up and scored. You can't talk your way into a better review.

There are a few small things that can help, though:

• Tell your recruiter about competing offers. This won't change your scores, but it can speed things up and sometimes affects leveling discussions.
• Send anything they ask for quickly. If the recruiter asks for a transcript, references, or a list of past projects, get it back the same day.
• Mention strong past work. If your resume undersells a big project, a recruiter can sometimes add a note to your packet. It's worth asking.
• If you're in team matching, make a good impression on calls. At Google, a manager who wants you can support your packet. We cover this in what is team matching.

Everything else was decided in the interview room. That's why the best preparation happens before the loop, not after it.