Onsite interviews are scored round by round: each interviewer takes notes, rates you on the skills their round covered, and gives an overall recommendation, commonly on a scale from "strong hire" to "strong no hire". Those write-ups then go to a debrief, and at some larger companies to a hiring committee, where the decision is made from the whole set of feedback rather than any single round.
Exact scales and rules differ by company and are often internal, so this guide describes common practice and cites public sources where they exist. For prep across the whole loop, see our hub on how to prepare for an onsite interview.
How are onsite interviews scored after each round?
When your session ends, the interviewer usually writes feedback before talking to anyone else on the panel. Many companies ask for this so that one loud opinion in the debrief doesn't anchor everyone. A typical write-up contains:
- The questions asked and any hints given.
- Notes on what you said and did, often close to verbatim for key moments.
- Ratings on each competency the round was assigned, such as problem solving or communication.
- Evidence for each rating: specific things you said or did.
- An overall recommendation and sometimes a suggested level.
Google's public re:Work guide to structured interviewing, for example, encourages interviewers to take detailed notes of candidate responses so they can be reviewed later (re:Work structured interviewing guide, as of October 2026). The practical point for you: the decision-makers only see what your interviewer wrote, and your interviewer can only write what you said out loud.
What rating scales do companies use?
There is no universal scale, but many tech companies use some version of a hire or no-hire recommendation alongside per-skill ratings. The table below shows a common pattern, not any specific company's system.
| Recommendation | What it usually means | Typical evidence behind it |
|---|---|---|
| Strong hire | Clearly above the bar; the interviewer would argue for you | Solved fully with clean reasoning, handled follow-ups, raised points unprompted |
| Hire | Meets the bar for the level | Solid solution and communication, minor gaps |
| Lean hire | Probably meets the bar, with some doubt | Got there with hints, or strong in some areas and thin in others |
| Lean no hire | Probably below the bar | Partial solution, needed significant help, unclear reasoning |
| No hire / strong no hire | Clearly below the bar, or a serious concern | Could not make progress, or behavior that raised a red flag |
Some companies drop the middle options to force a clear decision. Others score each competency on a numeric scale. Google's re:Work guide describes rubrics with four levels of answer quality: outstanding, solid, borderline and poor.
How do competency rubrics work?
A rubric tells interviewers what a strong, average or weak answer looks like for each skill, so different interviewers judge you against the same standard. The US Office of Personnel Management describes structured interviews as scored against benchmarks of proficiency, with panel members rating answers individually and then discussing significant differences (OPM structured interview guidance). Our guide to structured vs unstructured interviews explains why employers adopt this approach.
Here is an example rubric we wrote for a coding round, to show the idea:
| Competency | Strong | Borderline | Weak |
|---|---|---|---|
| Problem solving | Clarifies, compares approaches, picks a good one independently | Reaches a workable approach with hints | Cannot find a path forward |
| Coding | Clean, correct, readable code | Mostly correct with small bugs | Incomplete or hard to follow |
| Verification | Tests normal and edge cases unprompted, fixes own bugs | Tests when asked | Does not test |
| Communication | Explains reasoning throughout; easy to follow | Explains when prompted | Long silences; reasoning unclear |
Behavioral rounds work the same way, with competencies such as ownership, collaboration or handling conflict, and evidence drawn from your STAR stories.
How does the debrief work?
After all rounds are written up, the interviewers and usually the hiring manager meet to review the feedback. Commonly, they go through each round, discuss where ratings disagree, look for patterns across rounds, and reach a recommendation on hire, no hire and level. Our full loop interview guide gives an overview of this stage.
Some companies add a role whose job is to keep the bar consistent. Amazon says its Bar Raisers are objective third-party advisers who facilitate debrief conversations and make the final decision together with the hiring manager (About Amazon on the Bar Raiser program, as of October 2026). Our explainer on the bar raiser interview covers what that means for you.
At some larger companies, a hiring committee of people who did not interview you reviews the written packet and makes or confirms the decision. Where that happens, the quality of your interviewers' notes matters even more, because the committee never hears you directly. If you pass, some companies then move you into team matching after the onsite.
Can one weak round sink your onsite?
Not necessarily. Debriefs typically look at the overall pattern, and a single lean no hire surrounded by solid hires is often discussed rather than treated as automatic rejection. Outcomes depend on several factors:
- Which round was weak. A weak round in the area the role depends on most weighs more.
- How strong the evidence is. A detailed, specific concern usually carries more weight than a vague one.
- Whether it was a skill gap or a concern about behavior. Integrity or conduct concerns are hard to outweigh.
- The level. Mixed feedback sometimes leads to an offer at a lower level instead of a rejection.
- Company policy. Some companies require a clear hire from most or all interviewers.
If you think a round went badly, our guide on what to do when you've bombed one round of an onsite covers how to reset for the next session.
How can you make your interviewer's write-up stronger?
You can't control the rubric, but you can control the evidence your interviewer has to work with:
- Think out loud. Reasoning you keep in your head never reaches the feedback form.
- Name the step you are on. "Let me clarify the inputs", "Here's the brute force", "Now I'll test an edge case" are easy to write down as evidence.
- State complexity and trade-offs unprompted. It saves the interviewer from marking that they had to ask.
- Use numbers in stories. "Cut deploy time from 40 to 12 minutes" is quotable; "made deploys faster" is not.
- Make "I" clear. Say exactly what you did, so your interviewer can credit you.
- Summarize at the end. A 20-second recap of your solution or story gives the interviewer a clean line to write.
The round-by-round lists in our software engineer onsite interview questions show what strong answers include. Results often take a week or more after the debrief; see how long it takes to hear back after an interview.
Practice it
The fastest way to see how your answers might read on a feedback form is to have them scored. Rehearse out loud with an AI mock interview built from your résumé and the job description, and get each answer scored out of 10 with what worked, what to fix and a model answer, then a report card at the end. You can do this with an AI interview assistant that scores each answer, free for 15 minutes a day with no account. Treat the score as a practice signal, not a prediction of a real debrief. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
See how your answers score before the onsite
Answer real interview questions out loud and get each one scored out of 10 with what to fix and a model answer. Free for 15 minutes every day.
Try a free AI mock interviewFAQ
How are onsite interviews scored?
Each interviewer usually writes notes, rates you on the competencies their round covered and gives an overall recommendation, often from strong hire to strong no hire. The panel then reviews all feedback in a debrief, and some companies add a hiring committee.
Do interviewers compare notes before writing feedback?
Many companies ask interviewers to submit written feedback before discussing the candidate, so one opinion doesn't influence the others. Practices vary by company.
Can you get an offer if one onsite round went badly?
Often, yes. Debriefs usually look at the pattern across rounds, so one weaker round among strong ones may be discussed rather than treated as a rejection. A weak round in the role's most important skill, or a conduct concern, weighs more.
What is a debrief in an interview process?
A debrief is a meeting where the interviewers and usually the hiring manager review the written feedback from every round, discuss disagreements and reach a recommendation on hiring and level.
What is a hiring committee?
At some larger companies, a group of people who did not interview you reviews the written feedback packet and makes or confirms the hiring decision. It aims to keep standards consistent across teams.
Can I ask for my onsite interview scores?
You can ask for feedback, but most companies do not share scores or written feedback, often for legal or policy reasons. Some recruiters will give general themes if you ask politely.