Interviews
Interview scorecard for a small hiring team
Four criteria, a note, and a recommendation. Use it so two interviewers are scoring the same job, not two private impressions.
An interview scorecard is the page each interviewer fills in before they compare notes. It lists the few things this job actually needs, a short scale, a written example from the conversation, and a recommendation. It is not a personality test. It is how a team of two or three people avoids hiring from the last thing they remember.
Use one scorecard per role. A software engineer and an account manager do not share criteria. If the criteria could sit on any job in the company, they are not criteria yet.
What to put on the page
Start from the job description, not from a generic competency list. Pick four things the person will do in the first year. For an engineer that might be: ships a change in this codebase, writes a test for a bug they did not cause, explains a tradeoff without a slide, and leaves a note the next person can use. For each one, leave a line for the evidence. "Strong" with no sentence under it is a mood, and you will not remember the mood in a month.
Add a scale that a tired person can use. One to four is enough: not demonstrated, mixed, demonstrated, stronger than the bar you set. Define the top of the scale in the job's words. "Stronger than the bar" means they showed the skill on a problem like yours, not that you liked them.
End with a recommendation: hire, no hire, or not sure. "Not sure" should name the missing evidence and the one question that would resolve it. A maybe with no next question becomes a yes by default on a busy Friday.
Leave a blank for the interviewer's name and the date. Two people interviewing the same candidate on the same afternoon should not be able to overwrite each other.
How a small team uses it
Send the scorecard with the interview invite, to the interviewer, not to the candidate. Ask them to fill it in within an hour, before the debrief. In the debrief, read the evidence lines first and the recommendations second. If the two evidence lines describe different jobs, the job description is the thing to fix, not the candidate.
Store the finished scorecard on the candidate's record, next to the job they interviewed for. A file in someone's downloads is not a record. When you reject, the note you send should not contradict the scorecard. When you offer, the offer letter should describe the same job the scorecard scored.
Example
A 15-person studio in Nantes interviewed a designer with a form that asked for "communication, ownership, and craft" on a five-point scale. Both interviewers gave fours. In the debrief they discovered one of them meant the portfolio and the other meant the way the candidate talked about a missed deadline. They had the same numbers and two different hires in mind.
The next round used four lines taken from the job post: a critique of an existing screen, a written response to a client note, a question about how they handle a late asset, and a sentence on what they would not redesign. The scores spread. The hire was the person whose notes matched, not the person with the higher average on the old form.
What to leave off
Do not score accent, age, gaps in a CV, or whether you would socialise with the person. Those lines feel like signal and they are where biased decisions hide. Do not add a criterion you will not ask about. A score against a question you never posed is fiction.
If the role changes, retire the scorecard with it. An old form will keep producing confident numbers for a job you no longer have.
Before the debrief
Each interviewer should be able to point at one sentence of evidence for every score above the bottom of the scale. If the sentence is missing, the score does not enter the comparison. Read those sentences out loud before anyone says hire or no hire. A small team that starts with the recommendation spends the meeting defending a feeling. A team that starts with the evidence usually finds they interviewed for two different jobs, and the job description is what they fix before the next conversation.
Keep the finished scorecard on the candidate record the same day. A month later the only question worth answering is which evidence you trusted. The form is doing its job when that answer is still on the page.
Frequently asked questions
How many criteria should a scorecard have?
Four is enough for a small team. Each one should be something you can point to in the job description. A seventh criterion called culture fit collects a feeling and makes the score look more precise than it is.
Who fills the scorecard in?
Each interviewer fills in their own, before they talk to the other interviewer. A shared form filled in after the debrief is a record of the agreement, not of the interview.
Qonir is ATS software for small teams. The job, the candidate, and the stage stay on one record.
