Software engineering hiring starts with an interview scorecard template. Write it before the job ad.
Decide what the person must do in year one. Then what evidence proves they can.
Design the question last.
If you cannot write the strong answer in advance, the question is not ready.
On this page
Most hiring problems are decided the moment a team writes a job ad.
Before anyone agreed what a strong candidate looks like. Some teams call it an interview rubric or a hiring scorecard.
What does an interview scorecard template contain?
An interview scorecard template holds three written levels per scored line. Each describes evidence rather than a rating.
Strong describes what the candidate did. Weak describes what they left out.
Now 2 interviewers in the loop have something to disagree about that is not taste.
Take “system design”. Useless as a scorecard line on its own. The useful version:
Strong. Clarified requirements before designing. Estimated scale with numbers. Named a trade-off nobody prompted them about.
Chose a simpler option and said why.
Mixed. Produced a workable design. Needed prompting to consider failure modes. Explained the choice when asked but did not volunteer it.
Weak. Started drawing components without establishing requirements. Could not say what breaks first under load.
The whole scorecard template for a senior backend role fits in 4 lines. Copy it and rewrite the evidence for your role:
| Line | Strong | Mixed | Weak |
|---|---|---|---|
| System design | Clarified requirements first. Estimated scale with numbers. Named a trade-off nobody prompted | Workable design. Considered failure modes only when prompted | Drew components before requirements. Cannot say what breaks first under load |
| Practical coding | Working solution. Wrote a test for the edge case they named themselves. Said what they would change with more time | Working solution. Tested only when asked | Solution does not run. No test. No plan for the edge case |
| Ownership | Ran a system end to end. Says what broke and what they changed after | Ran part of a system. Cannot say what changed after an incident | Describes only tasks that were assigned to them |
| Communication | Says what they do not know. Asks before assuming. Sums up a decision in 2 sentences | Answers when asked. Does not volunteer uncertainty | Talks past the question, or bluffs when unsure |
Why does writing the scorecard template first change the questions?
Writing the scorecard template first exposes bad questions.
You find questions whose strong answer is “has seen this before”. That is a recall test you did not mean to run.
You find questions where you cannot write a strong answer at all. Those get cut.
The order to write the scorecard template
1. What does this person need to do in the first year? 3 to 5 concrete things. “Own the ingestion pipeline.”
2. What evidence would convince you they can? For each item, what would you need to see. This is the scorecard template.
3. Which question produces that evidence? Now design the interview. This is the last step.
4. Now write the job ad. It practically writes itself, and it is accurate, which means fewer mismatched applications.
How do you know your scorecard template is real?
Give the scorecard template to 2 engineers who did not write it. Have them score the same recording independently.
Scores more than one level apart mean the scorecard template is not specific enough. Fix it and repeat.
Scoring the same candidate separately is the calibration exercise you should run anyway. It takes an afternoon.
What does a scorecard template fix in software engineering hiring?
A scorecard template fixes four things: debriefs, candidate feedback, interviewer ramp-up and bias.
Debriefs stop being arguments about taste and become arguments about evidence, which converges.
Feedback to candidates becomes possible, because you wrote down what you were looking for.
New interviewers ramp faster instead of guessing at an unwritten bar.
Bias narrows too, because a written standard is harder to bend unconsciously. A written standard is still a human one.
The number that justifies the afternoon
Unstructured interviews explain about 4% of on-the-job performance.
Structured ones explain about 18% (Sackett and colleagues, 2022).
An afternoon on the scorecard is the difference between those 2 figures.
On every hire you make afterwards.
Where do teams give up?
Teams write the scorecard template for 1 role and never for the next one. Keep them, because most roles are variations.
Each scorecard template after the first takes less time.
Treat the first one as a project and you pay that cost on every role.
Where do you keep scorecard templates?
Keep scorecards in the same place as the job ads.
Date the scorecard and name its author.
A year later you will want to know who agreed to that bar.
A scorecard nobody can find gets rewritten from memory every time. That is how a team stops writing scorecards.
Want this built into the team, calibration included? That is the workshop sprint.
An audit or a workshop sprint. Book a free 30-minute call.
Common questions
How long does an interview scorecard template take to write?
An interview scorecard template takes an afternoon for the first role, less for each after. Most roles are variations on one you have written. The cost people resist is the meeting where the team agrees what the job is. That meeting is the point.
How many lines should a scorecard have?
A scorecard needs 4 to 6 lines. Each maps to one thing the person must do in year one. A 14-field rubric does not get filled in, and engineers are right to refuse it. If a line does not map to something the role requires, cut it. Do not score it out of habit.
Can you reuse a scorecard across levels?
Reuse the lines, rewrite the evidence. Senior and staff are tested on the same dimensions with a different bar under each. Naming an unprompted trade-off is strong at senior and expected at staff. Writing both columns side by side also settles levelling disputes fast.
How do you score an interview rubric?
Score an interview rubric one line at a time: strong, mixed, weak, or no evidence. A rubric is the same thing as a scorecard. Write the candidate’s words beside the score. Submit before the debrief. Never average the lines into one number. A strong design line does not cancel a weak ownership line. The hiring manager needs to see both.
Who should write the interview scorecard template?
The hiring manager drafts it, and the panel argues with the draft. A scorecard template written alone gets ignored by everyone who did not agree to it. An hour with the 4 interviewers brings the disagreements about the bar into the open. That is the meeting doing its job.
The short version
For a scorecard template, decide what the person must do. Decide what evidence proves they can. Then design the question.
If you cannot write the strong answer in advance, the question is not ready.
Excel, 3 sheets
Interview scorecard template
The 4-line senior backend scorecard with strong, mixed and weak evidence written out, a blank 6-line sheet for your role, and the order to write it in.
Leave a work email: the file opens right here, and one hiring stage, taken apart, follows every week. One click to leave.
Read next
Structured Interview Questions, With the Strong Answer Written First
Unstructured interviews explain 4% of later performance. Structured ones explain about 18%. The difference is 3 questions per round and a strong answer written first.
How to Be a Good Interviewer
Robert Walters found 40% of hiring managers never had formal interview training. These 5 habits make an interviewer worth listening to in the debrief.
Want this fixed in your loop?
SmartHiring trains engineering interview panels on their own open roles. Elman Huseynov, a Tech Hiring Expert in Berlin, runs every engagement. One workshop writes the scorecards for your roles, then calibration runs until the panel agrees. It starts with a free 30-minute call.
No pitch if the loop is already fine. See an example audit report.