Unstructured chats feel natural but make candidates hard to compare. A structured interview uses the same questions and a shared scoring guide. Here is how to set one up in an afternoon.
What "structured" actually means
A structured interview is one where every candidate for a role is asked the same core questions, in the same order, and answers are scored against a predefined guide. That is the whole idea.
It sounds rigid, and many interviewers resist it for that reason. They worry it will feel like an interrogation and that they will miss the chance to follow their curiosity. In practice a good structured interview still feels like a conversation. The structure sits underneath, in the preparation and the scoring, rather than in a stiff script.
The reason to bother is simple. Decades of research on selection methods has repeatedly found that structured interviews tend to predict job performance better than unstructured ones, and they leave less room for the biases that creep in when each candidate gets a different conversation. You do not need an exact number to act on that. The direction is well established.
Why unstructured interviews go wrong
Consider a typical informal interview. The interviewer asks about the candidate's background, notices a shared hobby, spends twenty minutes on it, and leaves with a warm feeling. The next candidate is asked harder technical questions and seems stiff. Who is the better hire? You cannot tell, because you ran two different tests.
Common failure patterns:
- Similarity bias. We rate people who resemble us more generously.
- First impressions. The first few minutes color the rest.
- Different questions. Candidates are not compared on the same ground.
- Memory. Notes written hours later reflect the mood of the day, not the answers.
- Loudest voice wins. In the debrief, the most senior or confident person sways the room.
Structure addresses each of these directly.
Step 1: Start from the role's requirements
Good questions come from the job, not from a list of famous interview questions. Take the requirements you set for the role and, for each essential one, ask: "What would we need to hear to be confident this person can do this?"
If you are hiring a customer success manager and one requirement is "handles difficult conversations", that tells you what to probe. If a requirement is "prioritizes under pressure", you need a question that reveals how someone actually does that.
This is why a clear job description matters. The same requirements flow from the post, through the scoring, into the interview.
Step 2: Write behavioral and situational questions
Two types of questions do most of the work.
Behavioral questions ask about past experience: "Tell me about a time you had to deliver bad news to a customer. What happened and what did you do?" The past is the best available predictor of the future, and a specific story is harder to fake than a general opinion.
Situational questions ask what someone would do in a realistic scenario: "A key customer says they will cancel unless a feature ships next week, and it will not. How do you handle the call?" These suit candidates with less directly relevant experience, because they test reasoning.
A few tips for writing them:
- One requirement per question, so scoring stays clean.
- Ask about specific events, not general habits. "Tell me about a time" beats "How do you usually".
- Avoid leading questions that signal the right answer.
- Prepare follow-ups such as "What was your role specifically?" and "What would you do differently?", which you can use for every candidate.
- Use four to six core questions for a one-hour interview. Fewer, deeper questions beat a long list.
Step 3: Build a scoring guide
This is the step most teams skip, and it is the one that makes the interview structured rather than merely repetitive.
For each question, write down in advance what a weak, adequate, and strong answer looks like. Be concrete.
| Level | What it looks like for "Tell me about a difficult customer conversation" |
|---|---|
| Weak | Vague or blames the customer; no clear action; cannot say what they learned |
| Adequate | Describes a real situation and their own action; outcome is acceptable; limited reflection |
| Strong | Clear context, owns specific actions, adapted to the person, measurable or clearly described outcome, and a lesson applied later |
Use a simple scale, such as one to three or one to four, with those anchors. Interviewers now rate against a shared standard rather than a private feeling.
Step 4: Train interviewers and assign focus
Not every interviewer needs to cover everything. In a multi-round process, assign each person a few requirements to explore. This avoids repeated questions and gives you broader coverage.
Spend thirty minutes briefing interviewers on:
- The requirements and why they matter.
- The questions and the scoring guide.
- What not to ask: topics unrelated to the job, and anything touching protected characteristics such as age, family plans, religion, or health. Check the rules where you hire.
- How to take notes: write what the candidate said, not what you concluded.
Step 5: Run the interview
Keep the experience human:
- Open with a few minutes of welcome and an explanation of the format. Candidates relax when they know what to expect.
- Ask your core questions in order. Let the candidate finish. Silence is fine.
- Use your prepared follow-ups, then add natural ones when something interesting comes up.
- Take notes on the answer as it happens.
- Leave time at the end for the candidate's questions, and answer them honestly. Their questions are also informative.
- Explain next steps and timing, and stick to them.
Score each answer right after the interview, before you talk to anyone else, while memory is fresh.
Step 6: Debrief with independent scores
In the debrief, begin with scores already written down, not opinions. Compare them requirement by requirement. Where scores differ, look at the notes and ask what each person heard.
This keeps the discussion on evidence and stops one confident voice from deciding the outcome. The approach is the same one we describe in how to evaluate candidates fairly and consistently.
Common objections
"It will feel robotic." It will only if you read from a script like a bored official. Having prepared questions frees you to listen instead of improvising what to ask next.
"I can read people." Most of us overestimate this. The goal is not to remove judgment but to ground it in comparable evidence.
"We are too small for this." Small teams benefit the most. A bad hire hurts more when there are ten people than when there are a thousand, and a one-page question sheet takes an hour to produce.
"We hire for very different roles." Keep a reusable template and swap the requirement-specific questions. A few questions on collaboration, learning, and ownership will carry across roles.
Connect it to the rest of your process
A structured interview is strongest as part of a consistent pipeline: clear requirements, a fair first review, a focused interview, a comparison on shared criteria. When an earlier evaluation highlights a gap in a candidate's application, it can suggest a question to ask in the interview. That is how Align generates interview questions from the strengths and gaps it finds in each application, so interviewers walk in knowing where to dig.
Whatever tools you use, the practice is within reach today. Write the questions, write the scoring guide, brief your interviewers, and score before you discuss. Your next hiring decision will be easier to explain and, over time, better.
