Weighted interview scorecard: how to set the weights and total the score

A weighted interview scorecard multiplies each competency's score by how much that competency matters, then totals the result, so a candidate who is exceptional at the one thing the role needs most outranks a candidate who is merely good at everything. It only works if the weights are set honestly before anyone is interviewed, and the arithmetic is visible enough that a reviewer can check it. Below is the template, the arithmetic worked in full, and the cases where weighting a scorecard adds nothing over a simple average.

The scorecard builder checks that your weights add up to 100 and prints the weighted-score rule on the sheet.

This assumes you already have a scorecard with competencies and a rating scale. If you need those first, start with interview scorecard template; this page is only about the weighting layer on top of it.

What weighting actually buys you

An unweighted scorecard treats every competency as equally important. That is fine when it is true. It breaks down when one competency is genuinely more load-bearing than the others — a security engineer's threat-modeling skill matters more than their presentation polish, even though both are on the scorecard. Weighting lets the total score reflect that difference instead of hiding it inside an average where a 5 on presentation cancels out a 2 on threat modeling.

Weighting does not fix a bad scorecard. If the anchors for each score are vague, weighting a vague number just produces a more confident-looking vague number. Get the scoring itself right first — see interview rating scale for anchored scales — then weight the results.

The weighted scorecard template

Copy this. Fill the weight column before the first interview and lock it.

Role: [title]                          Candidate: [name]

Competency         Weight   Score (1-5)   Weighted score (Weight x Score)
------------------ -------- ------------- --------------------------------
[Competency 1]      [ ]%     [ ]           [ ]
[Competency 2]      [ ]%     [ ]           [ ]
[Competency 3]      [ ]%     [ ]           [ ]
[Competency 4]      [ ]%     [ ]           [ ]
[Competency 5]      [ ]%     [ ]           [ ]
------------------ -------- ------------- --------------------------------
Total weight: 100%                        Weighted total: [sum]
Maximum possible (5 x 100%):              5.00

Must-have gate (pass/fail, not weighted): [competency] must score >= [minimum]
Notes: [anything the weighted total does not capture]

The arithmetic, worked through with an example

An invented candidate for a marketing manager role, scored on a 1–5 scale (see interview rating scale for anchors). The hiring manager set these weights during intake, before any interviews happened.

Out of a maximum possible 5.00, this candidate lands at 3.70. Compare that to what an unweighted average of the same five scores would give: (4 + 3 + 5 + 3 + 2) ÷ 5 = 3.40. The weighted total is higher because the candidate's strongest scores (4 and 5) sit on the two competencies the hiring manager said matter most, and the weak score (2) sits on the competency that matters least. That is the entire value of weighting in one comparison: it is 0.30 points higher than a flat average because the strength lines up with what the role actually needs.

Now compare a second invented candidate, stronger on paper overall but with their weak score in the wrong place:

Unweighted, this candidate's average is (2 + 4 + 4 + 5 + 4) ÷ 5 = 3.80 — higher than the first candidate's 3.40, and their raw scores sum to more overall (19 versus 17). Yet weighted, they land at 3.45, below the first candidate's 3.70. The reversal happens because the second candidate's one weak score (2) fell on campaign strategy, the competency weighted 35%, while the first candidate's weak score (2) fell on budget management, weighted only 5%. This is what weighting is for: making the total sensitive to where the strength and weakness sit, not just how much of each there is.

How to set the weights honestly

1. Do it during intake, before any resumes are reviewed. Ask the hiring manager: if a candidate were only strong at one of these competencies, which one would still make them worth hiring? That is your highest weight.
2. Use a small number of weight tiers, not fine-grained percentages. Three tiers (for example 30%, 20%, 10%) are easier to defend than someone insisting a competency is worth 17% versus 19%. Precision here is usually false precision.
3. Cap how much a single competency can carry. If one competency is weighted so high that it alone decides the outcome, you do not need the other rows on the scorecard, and you should use a must-have gate instead of a weight (see below).
4. Write down why, next to each weight. "35% — this is what breaks if we get it wrong" is a sentence a hiring manager can defend in a debrief three weeks later; a bare number is not.
5. Lock the weights before the first interview and do not touch them until the next requisition. A weight changed after seeing a candidate is not a weight, it is a rationalization.

When weighting adds nothing

Weighting is worth the extra arithmetic only when competencies genuinely trade off — when a candidate can plausibly be strong on one and weak on another, and you need the total to reflect which one mattered more. In several common situations it adds nothing:

• When one competency is a must-have gate, not a trade-off. If a candidate below a minimum bar on any single competency should not be hired regardless of how they score elsewhere, that is a pass/fail gate, not a weight. Weighting it heavily just approximates a gate with extra steps; a real gate is clearer and cannot be out-voted by unrelated strengths.
• When scores are highly correlated in practice. If your interviewers' scores across competencies tend to move together — candidates who do well on one tend to do well on all of them — weighting barely changes the ranking, because there is little variation between competencies to weight differently. Check this by comparing weighted and unweighted totals for your last several hires; if the ranking rarely changes, the weighting is decorative.
• When you have fewer than three competencies. With two competencies, a weight split is really just "which one wins ties," which a decision rule states more plainly than a percentage does.
• When the scores themselves are not yet reliable. If interviewers are not yet calibrated to the same anchors (see interview rating scale), weighting noisy scores just produces a more precise-looking noisy total. Fix calibration before adding weights.
• When the weighting is being used to justify a decision already made. If someone proposes adjusting a weight after seeing how a candidate scored, the honest move is to say the decision was made on gut feel and weighting was added afterward for the paperwork. That is not what weighting is for, and it is worth naming out loud when it happens.

In any of these cases, a must-have gate plus an unweighted average of the rest is simpler, easier to explain to a candidate or a committee, and produces essentially the same ranking. Reach for weighting when the trade-off is real, not as a default.

Combining a weighted score with a must-have gate

The two are not alternatives; most scorecards that hold up over time use both. The gate protects against a catastrophic weakness being averaged away; the weighting ranks everyone who clears the gate.

Step 1 — Gate: [must-have competency] scored >= [minimum]?  Yes / No
  If No: stop. Do not proceed to weighted scoring.
Step 2 — Weighted total (from the table above): [score]
Step 3 — Rank candidates who passed the gate by weighted total.

This is also why the marketing manager example above put budget management at only 5% rather than treating a low score there as disqualifying — the hiring manager had already decided, correctly, that a weak budget-management answer was tolerable if a training plan existed, and a gate would have overstated its importance.

Presenting a weighted total without hiding the parts

A single weighted number invites the question "how did you get there," and a reviewer who cannot see the parts will not trust the total. Always show the table, not just the sum, when the score goes to a hiring manager, a committee, or into a comparison across finalists. The arithmetic in this article is simple on purpose: multiplication and addition that anyone can re-check in under a minute. If your weighting scheme needs more than that to explain, it has become harder to trust, not more sophisticated.

Common mistakes and the fix

A quick way to check if your weights are doing anything

Take your last five or six filled scorecards for a role and compute both the weighted total and the plain average for each. If the two produce the same ranking every time, your current weights are not changing any decisions, and you can drop them for a simpler unweighted scorecard with a must-have gate. If the ranking changes for at least one pair, the weighting is earning its complexity, and it is worth keeping — and worth revisiting whether the weight that caused the swap is the one you actually meant to set highest.