What makes an interview structured?
A structured interview asks every candidate for the same role a set of core questions, in the same order where practical, and assesses answers against criteria set in advance. Interviewers may ask clarifying follow-ups, but they are not inventing an entirely new conversation for each person. The aim is to compare evidence about the work rather than compare how much the interviewers enjoyed each conversation.
Consider a team hiring a customer support specialist. In an unstructured interview, one candidate might be asked about resolving a difficult request while another spends most of the time discussing career goals. Both conversations may be useful, but they provide different evidence. A structured interview gives both candidates an opportunity to explain how they would investigate a customer problem, communicate a next step and document the outcome.
Structure does not make an interview perfectly objective. Question choices, scoring rules and interviewer judgments can still reflect assumptions. It does, however, make those choices visible so a hiring team can examine and improve them.
Start with the work, not an idealized personality
Before writing questions, identify a small number of capabilities the role actually requires. Look at the tasks someone will perform, the decisions they will make and the ways they will collaborate. For the support role, useful criteria might include troubleshooting, clear communication and judgment about when to escalate an issue. Broad labels such as “great attitude” are harder to assess consistently unless the team defines what relevant behavior would demonstrate them.
Write one or two questions for each priority. A past-experience question might ask, “Tell us about a time you had to explain a complicated problem to someone unfamiliar with it. What did you do, and what happened?” A scenario question might describe a customer report with incomplete information and ask what the candidate would do first. Either approach should leave room for candidates from different backgrounds to show how they think and work.
Check each question for relevance. If an answer would not help the team assess a stated criterion, the question may not belong in the scored interview. This check also helps keep the interview manageable: too many questions can leave little time for thoughtful answers.
Build a scorecard interviewers can actually use
For each question, define what interviewers should listen for before meeting candidates. A simple rating scale can describe what a limited, adequate and strong answer would show. For a troubleshooting scenario, an adequate answer might identify missing information and propose a sensible first check. A stronger answer might also explain how to prioritize the issue, communicate uncertainty and decide when to involve someone else. These descriptions are more useful than a bare number.
Ask interviewers to record brief, job-related evidence alongside their ratings. “Asked for the error message and checked whether the problem affected other users” is more informative than “seemed sharp.” Interviewers should make an initial assessment independently before discussing candidates together. In the discussion, they can compare the examples they heard, explore differences in interpretation and correct misunderstandings without treating the loudest opinion as the deciding factor.
A scorecard supports a decision; it should not conceal one. If the team gives some criteria more weight, decide that before interviews begin and connect the weighting to the role. Keep notes focused on relevant evidence, limit access to people involved in the decision and follow the organization’s practices for retaining candidate information.
Keep the process accessible and human
Consistency means providing a comparable opportunity to demonstrate relevant skills, not insisting that every candidate participate in precisely the same way. Share the interview format, expected length and general topics ahead of time. Invite candidates to request adjustments to how the interview is conducted, and make it clear that a request will not itself be scored. An adjustment to the format need not change the capability being assessed.
Interviewers can also reduce unnecessary pressure by allowing a moment to think, repeating a question when asked and explaining whether notes are being taken. Use the same approach for all candidates unless an individual adjustment calls for something different. Leave time for candidate questions, but keep that portion separate from the scored criteria unless it assesses a clearly defined, job-related capability.
Review the method after each hiring round
Once the process is complete, ask whether the questions produced useful evidence. Did candidates understand the scenarios? Did interviewers apply the rating descriptions in similar ways? Were any questions so vague that nearly every answer received the same score? Reviewing these points can improve the next round without changing the rules midway through this one.
Structured interviews work best as one part of a coherent hiring process. A relevant work sample, for example, may reveal something an interview answer cannot, provided candidates receive clear instructions and are assessed against shared criteria. The goal is not to turn people into numbers. It is to give each person a fair chance to show how they would do the work, and to give the hiring team a clearer basis for its decision.
