Lumo360  /  Structured interview guide

Hiring guide

How to build a structured interview, from job description to rubric.

Structured interviews are the best single predictor of job performance in the most recent large review of selection research. Every candidate answers the same job-related questions and is scored against the same rubric. This guide shows how to build one, step by step.

Why structure beats a conversation that wanders

In 2022, Sackett and colleagues re-ran the best-known estimates of how well hiring methods predict job performance. Structured interviews came out on top, with a mean validity of .42, ahead of job knowledge tests (.40), work samples (.33) and cognitive ability tests (.31)1.

Unstructured interviews, where each interviewer asks whatever comes to mind, came out at about .19, less than half the structured figure2. They feel informative, but much of what they measure is the interviewer's impression rather than the candidate's ability.

Structure helps candidates too. Google reports that candidates rated structured interviews as fairer, that rejected candidates who had one were 35% happier than those who didn't, and that ready-made questions and rubrics saved interviewers an average of 40 minutes per interview3.

What makes an interview structured

Remove any one of these and the interview drifts back towards gut feel.

01

Competencies from the job

Decide what the role needs before meeting anyone, and assess only that. Everything else in the interview hangs off this list.

02

The same core questions

Every candidate gets the same questions, each tied to a competency. Google's guidance adds planned follow-ups that probe how the candidate reached their answer3.

03

An anchored rubric

Each competency has a scale with examples of what a poor, borderline, solid and outstanding answer looks like, so two interviewers mean the same thing by a 33.

04

Evidence, then a decision

Record what the candidate actually said, score each competency on its own, and only then make an overall call. Notes let someone else check the score later3.

Build one from a job description

The four-to-six range and the 1–4 scale are our recommendations; adjust them to the role.

Step 01

Pick four to six competencies

Read the job description and pull out the skills and behaviours that separate good performers from average ones. Fewer, sharper competencies beat a long list nobody can assess in 30 minutes.

Step 02

Define each one in observable terms

"Good communicator" is a label. "Explains a complex issue so a non-specialist can act on it" is something you can hear in an answer.

Step 03

Write the questions and follow-ups

One or two questions per competency: behavioural ("Tell me about a time...") or situational ("Imagine that..."). Add follow-ups that ask what the candidate did, why, and what happened.

Step 04

Write the rubric before you interview

For each competency, describe what a 1, 2, 3 and 4 answer contains. Writing anchors after the interview lets the strongest impression set the bar.

Step 05

Review it with the hiring manager

Agree the competencies and the rubric before the role goes live. Disagreements about what the job needs surface here, not after the third interview.

Step 06

Score competencies separately, then decide

Score each competency against its anchors with the evidence in front of you. Then make the overall decision, and write down why.

One competency, from definition to score

Role: customer success manager. Competency: handling a difficult stakeholder. Definition: keeps a strained relationship productive while protecting the outcome the customer needs.

Question: "Tell me about a time a customer was unhappy with something you couldn't change. What did you do?" Follow-ups: "What did you say first?" "What did you offer instead?" "What happened to the account afterwards?"

Weak answer (1–2)Strong answer (3–4)
The situationVague or generic: "customers are often difficult"A specific customer, a specific problem, and why it mattered to them
What they didTalks about what "we" did, or what the policy wasDescribes their own actions and the reasoning behind them
The outcomeNo result, or one they can't connect to their actionsA concrete result, such as a renewal, a recovered relationship or a changed process
ReflectionNone, or blames the customerWhat they would do differently, or what they took into the next account

An anchored rubric like this lets two interviewers reach the same score from the same answer.

Where structured interviews go wrong

Design

Mistakes before the interview

  • Too many competencies, so none is assessed properly
  • Competencies copied from a generic framework, not this role
  • Questions that test interview polish rather than the competency
  • No rubric, or one written after meeting the candidates

Delivery

Mistakes during and after

  • Skipping questions for candidates who "obviously" have it
  • Scoring from memory at the end of the day
  • Letting one strong answer lift every other score
  • Deciding first, then filling in the scores to match

Running structured first rounds at volume

The hard part of structure is doing it every time, for every applicant, when there are hundreds of them. That is the gap Lumo360 is built for.

Lumo360 turns your job description into a competency framework, which your team reviews and adjusts before the role goes live. Every candidate then has a spoken first-round conversation built on the same framework and rubric. Follow-up questions adapt to each answer, but stay within the competency being assessed. Each score links to the transcript moments behind it, and a recruiter reviews every result before anyone moves forward.

See what this looks like for automating the first phone screen, or how it compares with one-way video interviews.

Common questions

What is a structured interview?

An interview where every candidate for a role is asked the same job-related questions and scored against the same rubric, with the competencies and scoring decided before any interview takes place.

Are structured interviews better than unstructured ones?

Yes. A 2022 review of selection research by Sackett and colleagues put the mean validity of structured interviews at .42, the highest of the methods reviewed. Unstructured interviews came out at about .19.

What is a competency-based interview?

A structured interview built around the competencies the role needs, usually using behavioural questions that ask candidates to describe what they actually did in past situations.

How many competencies should an interview assess?

We recommend four to six for a first-round interview. More than that and there isn't time to gather real evidence on each one.

Can you follow up on answers in a structured interview?

Yes. Good structured interviews include follow-up questions that probe the candidate's reasoning. What stays fixed is the competencies, the core questions and the rubric.

Give candidates a conversation.
Give your team the evidence.

See a Lumo360 interview and the report it produces, using one of your own job descriptions.

Book a demo

Sources

  1. SIOP, "Is cognitive ability the best predictor of job performance?", summarising Sackett, P. R., Zhang, C., Berry, C. M., & Lievens, F. (2022), Journal of Applied Psychology, 107, 2040–2068.
  2. KiTalent, "Evidence, not impressions", reporting the Sackett et al. (2022) estimate for unstructured interviews.
  3. Google re:Work, "A guide to structured interviewing for better hiring practices".