How to Run a Structured Interview (and Why Unstructured Ones Keep Failing You)

The short version: a structured interview asks every candidate for a role the same core, job-related questions, evaluated against the same pre-defined rubric. That consistency is the entire point — it is what makes candidates comparable and what makes the interview actually predict on-the-job performance. Unstructured "let's just have a conversation" interviews feel more insightful but are among the weakest predictors in hiring, because they mostly measure rapport and confidence. Structure does not mean robotic; it means fair, consistent, and decision-useful.

Why unstructured interviews keep failing

The unstructured interview is the default almost everywhere, and it is seductive: you talk, you connect, you leave with a strong gut feeling. The problem is that the gut feeling is mostly measuring how much the candidate resembles you, how confidently they speak, and how well the conversation flowed — none of which predict whether they will do the job well. Because every candidate gets different questions, you cannot compare them fairly, and the "insight" is largely your own bias, dressed up as intuition.

Decades of hiring research point the same direction: structured interviews predict job performance substantially better than unstructured ones. The mechanism is simple — consistency removes the noise, so what is left is more signal about the actual work.

The four ingredients of a structured interview

• Job-related questions. Every question ties to a real requirement of the role, not to trivia or "culture fit" proxies.
• The same core questions for every candidate. A consistent spine makes candidates comparable. You can still follow up individually.
• A pre-defined rubric. Decide what a strong, adequate, and weak answer looks like before the interviews, not after.
• Independent scoring. Interviewers score against the rubric before discussing, so the loudest voice in the debrief does not anchor everyone.

Step 1: Define what the role actually requires

Structure starts before any interview. List the four to six competencies that genuinely predict success in this role — the same short list you should have screened resumes against. Everything in the interview maps back to these. If a question does not test one of them, cut it.

Step 2: Write the core questions (and anchor them in evidence)

For each competency, write one or two core questions every candidate will get. The strongest questions are grounded in real experience — "walk me through a system you owned end to end" — because they resist rehearsal. Where you have a candidate's resume, tailor the follow-ups to their specific claims while keeping the core question the same across everyone. That gives you both comparability (same spine) and depth (personalized probes).

Step 3: Build the rubric before you interview

This is the step that separates structured from theater. For each question, define the levels of answer in advance.

With the rubric written down, five interviewers can score the same answer and land in the same place. Without it, "I liked them" competes with "I didn't," and the decision goes to whoever is most senior or most insistent.

Step 4: Score independently, then discuss

Have each interviewer record their scores against the rubric before the group talks. Independent scores prevent anchoring — the tendency for the first strong opinion to pull everyone toward it. Then discuss the divergences: where two interviewers scored the same answer very differently is exactly where the useful conversation is.

Structure without rigidity

A common objection: "Won't a script make the interview cold and stop me from following interesting threads?" No — structure is the spine, not a cage. You ask the same core questions and score on the same rubric, but you follow up freely, dig into what is interesting, and keep it human. The consistency is in the questions and the scoring, not in banning conversation. Candidates actually tend to experience structured interviews as fairer, because everyone gets the same real questions rather than a chat whose outcome depends on chemistry.

Divide the competencies across the panel

If several people interview a candidate, do not have each one cover everything shallowly. Assign competencies: one interviewer goes deep on system design, another on collaboration, another on the specific gap screening flagged. Each comes with their core questions and rubric for their area. You get depth and coverage instead of four overlapping, unfocused conversations — and far fewer wasted rounds.

A structured-interview checklist

• Listed the 4–6 competencies the role actually requires.
• Wrote core questions mapped to each, grounded in real experience.
• Defined strong/adequate/weak answers for every question in advance.
• Assigned competencies across the panel so nobody overlaps.
• Tailored follow-ups to each candidate's resume claims and gaps.
• Scored independently before the debrief.

How TopRec sets up structured interviews

The hardest part of structure is the prep — writing tailored, job-related questions with clear signal definitions for every candidate. TopRec does that from the resume and job description: for each candidate it generates interview questions with strong-signal / weak-signal rubrics and points to the specific gaps worth probing. You get the consistent spine plus the personalized follow-ups, ready before the call — so running a fair, comparable, structured interview takes minutes to prepare instead of an afternoon.