Structured interviews — where every candidate is asked the same questions, in the same order, evaluated against the same criteria — consistently outperform unstructured interviews in predicting job performance. Despite this, most interviews are still largely unstructured: conversation-driven, impression-based, and highly variable from one interviewer to the next. This guide explains how to build a structured process your team can run consistently.
What Makes an Interview Structured
Structured interviews have four defining characteristics:
- Standardised questions — Every candidate for the same role is asked the same core questions, in the same sequence
- Job-related content — Questions are derived from a job analysis: what skills, behaviours, and knowledge does this role actually require?
- Anchored rating scales — Answers are scored against a defined rubric, not a gut feeling (a 5-point scale with descriptors for each score level)
- Consistent evaluation — Each interviewer scores independently before the panel discusses; debrief is structured to compare scores, not persuade
Question Types to Include
Behavioural questions ask candidates to describe past behaviour: "Tell me about a time when you had to deliver a project under a compressed timeline. What did you do?" These are best for assessing soft skills and work patterns. Look for specificity — a strong answer names a real situation, describes concrete actions, and states measurable outcomes.
Situational questions present a hypothetical: "If you inherited a process that the team had used for years but that you believed was inefficient, how would you approach changing it?" These work well when the role requires judgment in novel situations.
Technical or skills-based questions test specific knowledge relevant to the role. For engineering roles this might be a coding problem; for finance, a modelling exercise; for writing roles, a short editing or drafting task.
A well-structured interview for a mid-level role typically has 6–8 questions with 2–3 follow-ups per question available to the interviewer.
Building Your Scoring Rubric
For each question, define what a 1, 3, and 5 answer looks like before the interviews begin. Example for a question about handling conflict:
- 1 (poor) — Avoids conflict, no resolution, blames others, or no concrete example given
- 3 (acceptable) — Describes a real situation, took some action, partial resolution
- 5 (strong) — Specific situation, proactive approach, described the other person's perspective, clear positive outcome with measurable or observable result
This calibration exercise should happen before the interview cycle starts, with all interviewers aligned on the rubric.
Running the Debrief
After all interviews are complete, run a structured debrief:
- Each interviewer submits scores before the meeting — no discussion beforehand that could anchor others' views
- In the meeting, each person shares scores and key evidence first, then discussion opens
- Disagreements on scores are healthy — require the lower scorer to articulate what the candidate would have needed to say to score higher
- Document the hiring decision and the primary evidence for it — this is your legal record if the decision is ever challenged
Structured interviews take more setup time upfront and save enormous time at the back end: fewer bad hires, fewer do-overs, and a defensible process. TalentLane helps employers build role-specific job requirements that map directly to structured interview criteria — start your next search with the structure already in place.