“Strong technically” is not enough information to make a hiring decision. A useful scorecard captures what the candidate demonstrated, how it relates to the role and where uncertainty remains. It should help a team compare evidence without pretending that hiring can be reduced to a single number.
Start with the outcomes of the role
Choose a small set of capabilities connected to the work. For a senior platform engineer, these might include systems design, operational judgement, implementation quality and ownership. Give each one a definition before interviews start. Otherwise, interviewers can use the same label to mean different things.
Assign a primary interviewer to each area and explain which interview will generate the evidence. Repeating the same broad conversation across four stages adds effort without necessarily resolving uncertainty.
Use a shared, anchored scale
| Assessment | Meaning |
|---|---|
| Not observed | The interview did not provide enough evidence. |
| Below the role requirement | Evidence reveals a material gap against the agreed scope. |
| Meets the role requirement | Evidence supports independent work at the expected level. |
| Exceeds the role requirement | Evidence shows relevant judgement beyond the required scope. |
“Not observed” matters. A missing signal is not automatically a negative signal. Record whether a follow-up question, a different assessment format or clarification of the brief would resolve the gap.
Record the evidence alongside the judgement
Instead of “good at reliability,” write: “Identified the deployment as a possible cause of the incident, proposed checking recent changes, and explained when rollback would be preferable to continued diagnosis.” This tells the hiring team what actually happened.
Separate observed behaviour from interpretation. Do not treat a familiar employer, shared interests or confident delivery as proof of technical capability. Keep questions relevant to the role and give candidates comparable opportunities to demonstrate the required skills.
Write feedback before the debrief
Ask interviewers to record their assessment independently before discussing the candidate. In the debrief, examine disagreements at the evidence level. Did people assess different skills? Was the question ambiguous? Does the role require the level of depth one interviewer expected?
Avoid simply averaging scores. A critical gap can matter more than several strengths, while a teachable gap may be acceptable when onboarding support exists. Document the reason for the final decision and any unresolved risk.
A reusable interview note
Review the scorecard after a search. If an area repeatedly produces vague feedback, improve the question or definition. Treat the scorecard as a tool for clearer judgement, not an objective guarantee of future performance.
For help defining your next technical role, start a hiring brief. If you are recruiting infrastructure engineers, explore our platform and infrastructure specialism.