← Back to Blog
October 6, 2026 · 5 min read · By Rezumz Team

Interview Rating Scale: What Each Score From 1 to 5 Should Mean

A five-point interview scale works when each number has a written meaning tied to evidence. As a starting point: 1 means no relevant evidence, 2 means limited or weak evidence, 3 means meets the requirement with a solid example, 4 means exceeds it with strong examples, and 5 means outstanding, with clear results and a depth beyond what the role needs.

Why does a scale need definitions?

Without definitions, one interviewer's 4 is another's 3, and the average of the two scores means nothing. Defined levels give everyone the same ruler. They also make feedback easier to defend, because each score points at something the candidate said.

What could each level mean?

Here is an example set you can adapt. 1: could not give an example, or the example showed the opposite of what the role needs. 2: gave a vague or partial example, with unclear personal contribution. 3: gave a clear example with their own role and a result. 4: gave several clear examples with measurable results and good judgement. 5: showed expert-level judgement, taught or led others, and handled the hardest version of the problem. Adjust the wording to the competency.

How do I write anchors for a specific competency?

Take one competency, for example communication, and write what a 1, 3 and 5 would sound like in an interview for this job. For a role that explains technical ideas to customers, a 3 might be "explained a technical issue clearly to a non-specialist", and a 5 might be "changed a customer's decision through clear explanation, and adapted when they were confused". Writing the middle and the ends is usually enough; the others sit between.

What scoring mistakes should I avoid?

Do not average away a clear concern, because a 1 in a critical competency matters more than a 5 in a nice-to-have. Do not give everyone a 3 to avoid deciding. Do not let one strong answer colour every other score, which is sometimes called the halo effect. And do not score what was not asked: write "not covered" instead of guessing.

How can I speed this up?

Anchors are the most time-consuming part of a scorecard. The Rezumz Interview Scorecard Builder suggests anchors for common competencies and roles in your browser with no account. Use them as drafts, and edit them until they match what good looks like for your team.

Frequently asked questions

Should I use a 1 to 4 scale to avoid middle scores?

An even scale forces a lean one way, which some teams prefer. The more important factor is that every level is defined and used consistently.

What if interviewers disagree on a score?

Compare the evidence each one wrote. Differences often come from different questions being asked, so decide whether another round should cover the gap.

Should candidates see their scores?

That is a policy decision. If you share feedback, base it on the evidence and the criteria, and avoid sharing raw numbers without context.

See it on a real hire

Open a private demo with fictional candidates and walk a hire from job description to offer. No sign-up needed.

Try the live demo →