Why use a scorecard instead of a gut feeling?

Scorecards force interviewers to rate the same competencies against the same anchors, which reduces bias and makes candidates comparable. A documented rationale also protects you if a hiring decision is ever questioned.

What does each number on the 1-5 scale mean?

1 is well below the bar, 2 is below, 3 meets expectations, 4 exceeds, and 5 is exceptional. Anchoring each level to a behavioral indicator stops different interviewers from interpreting a 3 differently.

Should I average the scores to get a decision?

Averaging is a guide, not a rule. A single 1 on a critical competency can be disqualifying even if the average looks fine. Use the scores to structure the debrief, then make a deliberate hire / no-hire call.

Who fills out the scorecard?

Each interviewer completes their own scorecard independently, ideally before the debrief, so opinions aren't anchored by the loudest voice in the room. Then compare and discuss divergences.

How many competencies should a scorecard have?

Four to six focused competencies works best. Too many dilutes attention and turns the interview into box-ticking; too few misses important dimensions of the role.

What is the Interview Scorecard Builder?

Builds an interview scorecard with competencies, behavioral indicators for each level on a 1-5 scale, and space for interviewer notes and an overall hire recommendation. It runs free in your browser on Gera Tools, with nothing uploaded.

Interview Scorecard Builder

Name: Interview Scorecard Builder
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

A consistent rubric for every candidate

Hiring decisions improve dramatically when every interviewer scores the same competencies against the same anchors. Without a scorecard, interviewers leave the room with general impressions that are hard to compare and easy to bias toward whoever spoke most confidently. This builder turns a role and a list of competencies into a structured scorecard with behavioral anchors for each point on a 1-5 scale, notes space, and an overall recommendation line.

How it works

For each competency you enter, the tool generates a five-level rubric. Behavioral anchors at levels 1, 3, and 5 define what each rating means in observable terms — so a “3 on problem-solving” means the same thing whether Alex or Jordan is filling in the scorecard. The scorecard includes a notes field per competency (critical for capturing evidence) and a final block for an overall rating and a deliberate hire / no-hire / strong-hire recommendation.

Ratings are intentionally not auto-averaged into a verdict. An average can mask a disqualifying gap: a candidate who scores 5 on every competency but 1 on integrity, for example, should not get an automatic hire simply because the mean is still high.

Choosing the right competencies

Four to six competencies is the practical sweet spot. Too few and you miss dimensions that matter; too many and interviewers spread attention across box-ticking rather than probing deeply. A typical set for a senior individual contributor might look like:

Technical depth — mastery of the core skills the role requires
Problem-solving — how they structure and work through ambiguity
Communication — clarity in explaining complex ideas to different audiences
Collaboration — evidence of working effectively with others to achieve shared goals
Drive — self-direction, ownership, and follow-through without supervision

For roles with a specific functional requirement (sales: closing skills; engineering management: people development), replace one of the generic competencies with the role-specific one.

Running the debrief well

The scorecard is most useful if each interviewer completes it independently before the debrief begins. Once someone shares their overall impression in the room, the others tend to anchor on it — a pattern called “anchoring bias” that flattens the variance the scorecard was designed to surface.

Run the debrief by going competency by competency, asking each interviewer to share their rating and the evidence behind it. Divergences — one person gave a 4, another gave a 2 on the same competency — are the most valuable moments: they reveal either that different questions probed different things, or that one piece of evidence changed the assessment. Resolve them with evidence, not volume.

Tips

Treat a 3 as a genuine pass, not a polite minimum. Reserve 4 and 5 for clear, specific evidence. Grade inflation in scorecards is the main reason they stop being useful.
Write verbatim quotes in the notes field when you can. “She described the exact approach she used to reduce API latency by 40%” is far more useful in a debrief than “strong technically”.
Flag any competency at the top of the scorecard where a score below 3 is disqualifying regardless of the overall average, so the panel knows before discussion starts.