Skip to content
SkillCort

October 8, 2026 · 9 min readEvaluation

How to structure an interview: the architecture, not the conversation

Most advice about interviews is about what happens in the room. The decisions that matter more were made before it: how many interviewers, what each one owns, whether they score before they talk to each other, and what order the candidates arrive in. Those choices determine how much the room can tell you.

By Oliver Bennett, MSc in Work and Organizational Psychology

In short

Structuring an interview means fixing the design before any candidate is seen: the competencies each interviewer owns, a common question set, independent scoring recorded before any discussion, and a defined order of stages. Structure increases the consistency of what is observed and makes candidates comparable to each other rather than to the interviewer's memory of the last one. It is a property of the process, not of how formal the conversation feels.

A panel of four meets a candidate for an hour. Everyone asks what interests them. Afterwards they talk, agree quickly, and write "strong communicator, some concerns about pace". The next candidate gets a different hour from the same four people, and the two are compared as though the same thing had been measured twice.

Nothing in that room was badly done. The design was missing before anyone walked in.

Structure is a set of decisions made in advance

The word "structured" is usually taken to mean formal — same questions, no small talk, a scoring sheet. That is part of it and the smaller part. Structure is the architecture of the whole stage: who assesses what, when judgements are recorded, when they are allowed to meet, and where the interview sits relative to everything else.

Those decisions are made once, before the first candidate, and they are what makes the hour comparable across people. Decisions made inside the room are, by definition, made differently each time.

Divide the competencies

The default panel has everyone assess everything. It feels thorough and it is the main source of wasted interview time: four people produce four readings of the same two or three impressions, and the agreement between them is read as confirmation when it is mostly shared exposure.

Assign instead. Each interviewer owns two or three competencies from the blueprint and asks the questions that reach them. Nobody covers everything, and between them the panel covers the role.

Everyone assesses everythingCompetencies divided
What you getseveral readings of the same impressionsevidence on distinct competencies
Agreement meansshared exposuregenuine convergence, where it happens
Gapsinvisible — everyone assumed someone covered itvisible on the coverage map
Interview lengthgrows with panel sizestays bounded

The division also makes the gap honest. If no interviewer owns "handles conflict with a peer", the coverage map shows a blank rather than four people each assuming another had it.

Record before you reveal

This is the single highest-value rule in panel design, and the easiest to drop under time pressure.

Each interviewer scores independently against the rubric and records it — written down, submitted — before any discussion. Then the scores are revealed, and then the panel talks.

The reason is anchoring. Once a confident impression is in the room, the others move toward it. The panel experiences this as reaching consensus; what actually happened is that one judgement was repeated by three people. A debrief that begins "I thought she was excellent, what did everyone else think?" has already collected its answer.

Revealed-after-recording also makes disagreement visible, which is the useful part. Two interviewers two points apart on the same competency is a conversation worth having — about the rubric, or about what each of them saw — and it is a conversation that never starts if the first number spoken is the one everyone settles on.

The order of candidates is part of the measurement

Interviewers calibrate against what they have recently seen. The third candidate of the morning is scored partly against the first two. A strong opener raises the bar for everyone after; a weak one lowers it.

Two cheap mitigations. Randomise the order, so position in the queue is noise rather than a systematic penalty for whoever scheduled late. And if the panel is new to the rubric, re-score the first candidate at the end — the first interview is also the panel's calibration session, and nobody should pay for that.

Where a panel runs across several days, a short re-grounding in the rubric at the start of each day costs five minutes and prevents the standard from quietly resetting overnight.

Sequence the stage, not just the hour

An interview is one stage in a process, and its design depends on what comes before it.

Run the work sample first. Then the interview is not spent establishing whether someone can do the work — that question has an answer already — but on what the work sample cannot show: the reasoning behind the choices, how they would handle the case that escalates, what they would do differently with more time.

This ordering shortens the interview and sharpens it. It also removes the most common failure of the unstructured hour, where a persuasive account of competence is weighed against another candidate's demonstration of it, and the account wins because it was more fluent.

What structure does not buy

Structure makes observations consistent. It does not make them correct.

A structured interview still reports what a person says about their work, filtered through how comfortable they are being interviewed. That is genuinely useful evidence about reasoning, self-awareness and how someone handles a live exchange — and it is not a substitute for seeing the work. Keeping both stages is not belt and braces; they observe different things.

And structure does not remove judgement. It relocates it: from the room, where it is made under time pressure by whoever speaks first, to the design, where it is made deliberately, written down, and applied the same way to everyone. That is the whole of the improvement, and it is enough.

  • structured interview
  • interview panel
  • independent scoring
  • hiring process design
  • evaluation

Key takeaways

  • Divide competencies between interviewers rather than having everyone assess everything — overlap produces agreement, not information.
  • Score independently and record it before the panel talks. A judgement spoken first becomes the panel's judgement.
  • Candidate order is part of the measurement. Randomise it, and rescore the first candidate at the end if the panel is new to the rubric.
  • A structured interview is still an interview: it reports what a person says about their work, which is why the work sample stays in the process.

Frequently asked questions

How many interviewers should a panel have?
Two or three for most roles. One gives you no check on an idiosyncratic read; beyond three the marginal observation is small and the scheduling cost is not, and candidates experience a crowd rather than a conversation. What matters more than the count is that each interviewer owns distinct competencies, so three people are producing three kinds of evidence rather than three readings of the same thing.
Should interviewers see each other's scores before the debrief?
No, and the sequence is the point. Record independently, then reveal, then discuss. Anchoring is well documented: once a number or a confident impression is in the room, the others move toward it, and the panel converges on one person's opinion while believing it reached consensus. Revealing after recording keeps three judgements rather than one repeated three times.
Does structure make the interview feel robotic?
It need not, and the trade-off is usually overstated. Structure fixes which competencies are covered and how responses are scored; it does not forbid follow-up questions, warmth or silence. The thing it removes is the freedom to assess different candidates on different dimensions — which feels like rapport to the interviewer and like inconsistency to the candidate who was asked the harder set.
Where does the work sample fit?
Before the interview, so the interview can be spent on what the work sample cannot show. Someone's written response to an angry customer answers whether they can do it; the interview is where you ask about the decisions behind it, how they would handle the escalation, what they would do differently. Run in that order, the two stages stop duplicating each other and the interview gets shorter.

For hiring teams

Give the panel one rubric and one record

Independent scores captured before the debrief, then compared side by side — so the discussion starts from evidence rather than from the loudest first impression.