Structured interviews: questions and scorecards

Unstructured interviews, the kind where a manager chats with a candidate for 45 minutes and forms an impression, predict job performance poorly and are the main way bias enters hiring. Structured interviews, where every candidate for a role gets the same questions scored against the same rubric, predict better and are easier to defend. They are also not much more work once the rubric exists. Here is how to set one up for a small company.

Build the scorecard from the job

Take the job description and extract four to six competencies that the role actually needs. For a payroll specialist that might be accuracy under deadline, statutory knowledge, stakeholder communication and ownership. For a backend engineer, system design, code quality, debugging and collaboration. Resist generic lists; "culture fit" is not a competency, it is an invitation to hire people who resemble the interviewer.

For each competency, write a three-level definition: what a weak, adequate and strong answer looks like. "Can describe a PF reconciliation they personally did, including what went wrong and how they found it" is a strong-level definition. "Knows PF" is not. These definitions are the scorecard; writing them takes an hour per role and is the step most companies skip.

Assign questions to rounds

Each interview round covers two or three competencies, and each competency has two or three fixed questions. Everyone interviewing for the role uses the same questions in the same round, so candidates are compared on the same evidence.

The most useful question type is behavioural: "Tell me about a time when…" followed by probing for specifics. What was the situation, what did you personally do, what happened, what would you do differently. A candidate who answers in the plural ("we decided…") is describing a team's work; keep asking until you find their part. The second useful type is a work sample: a small, realistic task from the role, done live or as a short take-home. A one-hour take-home with a paid or clearly bounded scope is fair; a weekend project is not, and good candidates decline it.

Hypothetical questions ("what would you do if…") test imagination more than track record. Brain teasers test nothing. Both can go.

During the interview

The interviewer's job is to collect evidence, not to form an opinion. Practically: ask the fixed questions, take notes in the candidate's words, and save judgement for the scorecard afterwards. Allow a few minutes of rapport at the start and ten minutes for the candidate's questions at the end, and tell them the structure so the formality does not read as coldness.

Each interviewer should fill in the scorecard within an hour of the interview, before talking to anyone else on the panel. Score each competency against the three-level definition, cite the evidence in one line per score, and give an overall recommendation: strong hire, hire, no hire, strong no hire. "Maybe" is not a recommendation.

The debrief

Hold a 20-minute debrief with everyone who interviewed, after all scorecards are submitted. The hiring manager runs it and speaks last. Go competency by competency, not interviewer by interviewer, and look for disagreements: one interviewer scored communication strong, another weak. Those disagreements are where the useful discussion is. Agreements need no time.

The reason scorecards are submitted first is to stop the most senior or most confident voice in the room from setting the verdict. Once that person has spoken, every subsequent opinion shifts toward theirs. Written-first, discussed-second removes most of that effect.

Decide in the room. A hiring process that ends in "let's think about it" loses candidates to companies that decided.

Questions you should not ask

Some questions are unlawful, discriminatory or simply irrelevant to the job, and small companies ask them without thinking because the interview feels like a conversation. Do not ask about marital status, plans to have children, religion, caste, age, health conditions or disability unless directly related to a genuine occupational requirement, or family background. "Are you planning to get married soon" is asked of women in Indian interviews with depressing regularity; it is both unfair and a signal to the candidate about what working for you will be like.

Current salary is a separate case. Asking it anchors your offer to the candidate's previous employer's pay decisions rather than to your pay bands, and it perpetuates whatever gap they already carry. Ask for their expectation instead, and compare it to your range.

Keeping the process honest over time

Record scores and outcomes in the same place for every role, whether that is a spreadsheet or the recruitment pipeline in your HR system. Every six months, look at two things: whether scorecard results predicted who passed probation, and whether candidates from any group were disproportionately rejected at a particular round. If strong scorecards keep producing weak hires, the competency definitions are wrong, not the interviewers. If one round rejects a particular group far more than the others, something in that round's questions or interviewers needs a look.

A structured process will occasionally reject a candidate someone's gut liked. That is the point. The gut was never as good as it felt.