Structured interviews: why the same questions make hiring fairer
A structured interview asks every candidate the same questions, in the same way, and rates the answers against criteria agreed in advance. Why that predicts performance better than a friendly chat, how bias creeps in without it, and how to run one.
Ask a hiring manager how they interview and most will describe a conversation: a look at the CV, a few questions that come to mind, a feel for whether the person would fit. It is pleasant, it feels insightful, and it is one of the least reliable ways to choose between candidates. A structured interview fixes that with a simple idea: ask every candidate the same questions, in the same way, and rate the answers against criteria you agreed before anyone walked in.
This guide explains what a structured interview is, why it predicts job performance better than an unstructured one, where bias creeps in without it, and how to run one without making the process feel like an exam.
What a structured interview is
A structured interview has four parts. Remove any one of them and the structure quietly collapses.
The same questions for every candidate, written from the job before interviews start, and asked in the same order.
The same conditions. The same amount of time to answer, the same information up front, the same format.
Criteria agreed in advance. For each question, a short description of what a strong answer includes, written before anyone has seen a candidate.
Independent ratings. Each interviewer rates each answer on a fixed scale on their own, before the group discusses.
An unstructured interview has none of these. The questions vary, the follow-ups vary, the time varies, and the "rating" is a gut feeling formed somewhere in the first few minutes and defended afterwards.
Why unstructured interviews feel good and predict badly
Research on selection methods has been remarkably consistent for decades: structured interviews are among the best predictors of how someone will perform in a job, and unstructured interviews are among the weaker ones, not far above the CV alone. The gap is not because interviewers are careless. It is because an unstructured interview gives the interviewer's instincts free rein, and instincts are good at judging likeability and bad at judging future performance.
The feeling of insight is real; it is just measuring the wrong thing. After a lively conversation you know whether you enjoyed talking to someone. You do not know whether they can do the work, because you did not ask every candidate the same hard question and compare the answers.
Where bias creeps in without structure
First impressions. An opinion formed in the first minutes shapes which questions get asked next, and how the answers are heard. A strong start earns easier follow-ups; a nervous one earns harder ones.
Similarity. We rate people who remind us of ourselves more generously: same university, same hobbies, same way of speaking. In an unstructured chat, that similarity is exactly what gets explored.
Order and fatigue. The fifth interview of the afternoon is not judged like the first. Candidates get compared with whoever came just before them rather than with the job.
The loudest voice. When a panel discusses before anyone writes down a rating, the most senior or most confident person sets the verdict and everyone else adjusts.
Memory. Notes written an hour after the call are a story about the candidate, not a record of what they said.
Structure does not make interviewers unbiased. It gives bias fewer places to act: the questions are fixed, the criteria are fixed, the ratings are written before the discussion, and the record is the answer itself.
How to run a structured interview
1. Write the questions from the job, not from habit
List the three to five things the role genuinely needs, then write one or two questions for each. Prefer questions that ask for a specific example ("Tell us about a time you...") or a specific plan ("How would you handle...") over questions about attitudes ("Are you a team player?"), which everyone answers the same way.
2. Write the "strong answer" line before you interview anyone
For each question, one sentence: what does a strong answer include? For "tell us about a time you dealt with an unhappy customer", a strong answer names the situation, what they did, what the customer did next, and what they would change. Writing this down takes ten minutes and does more for fairness than anything else on this list.
3. Give everyone the same conditions
Same questions, same order, same time per answer, same information up front. If one candidate gets a 45-minute chat and another gets 20 minutes squeezed before a meeting, you are no longer comparing like with like.
4. Rate independently, then discuss
Each interviewer scores each answer on a fixed scale, say one to five stars, against the strong-answer line, before seeing anyone else's score. Then compare. Disagreements are where the useful conversation is: two people who rated the same answer two and five have usually heard different things, and the discussion should be about what was said, not about who is more senior.
5. Keep the record
Ratings, notes and ideally the answers themselves, so that when two candidates are close you can go back to what they actually said rather than to what everyone remembers.
Where one-way video interviews make structure the default
Most of the effort in a structured interview goes into keeping it structured: making sure every interviewer asks the same questions, in the same way, with the same time, and writes their score down before the group talks. A one-way video interview removes most of that effort, because the structure is built into the format.
Same questions, same order, same time. You write the questions once and set a time limit for each. Every candidate sees exactly the same interview, with a 5-second countdown before each answer and a timer that stops at zero. No interviewer can drift, run over, or add a friendly follow-up for one person and not another.
Same conditions. Everyone checks their camera and microphone, answers a practice question that is never recorded, and records one take per answer.
Independent ratings. Each reviewer rates every answer from one to five stars, gives an overall recommendation (Strong yes, Yes, Maybe or No) and writes private notes on their own. The team then sees everyone's feedback side by side.
A record you can return to. The answer is the recording. When two candidates are close, watch again rather than argue.
Reusable question sets. Save the questions and the time limits once, then import them into the next interview for the same role, so the structure survives staff changes and busy weeks.
You can see the full list on the features page, and how to review video interviews fairly as a team goes deeper on the rating side.
"Won't it feel robotic?"
This is the objection every team raises, and it deserves a straight answer. A structured round is less chatty than an unstructured one. Candidates, on the whole, do not mind. What they mind is feeling that the process was arbitrary: that someone else got an easier interviewer, a longer slot, or a friendlier start. Tell candidates up front that everyone gets the same questions and the same time, and most read it as what it is, which is fairness.
And structure does not mean the whole process is scripted. Use it for the rounds where you are comparing candidates against each other, which is the early ones. Keep the final conversation live and human, with the people you have already decided are worth it. Async vs live interviews: which rounds suit each? walks through that split.
A checklist before your next round
Three to five questions, each tied to something the job needs.
Every question asks for a specific example or plan.
A one-line "strong answer" written for each question, before anyone is interviewed.
The same questions, order and time for every candidate.
Each reviewer rates on a fixed scale before the group discusses.
Ratings and answers kept, so close calls can be revisited.
If you can tick all six, you are running a structured interview, whatever tool you use. If you are starting from scratch, how to write first-round interview questions has a framework and 20 examples to build from.
