Unstructured interviews predict job performance about as well as a coin flip. Structured interviews — where every candidate gets the same questions in the same order, scored against the same criteria — are 2-3x more predictive of on-the-job success. This guide gives you the question templates to make that switch.
Why structured interviews work
Unstructured interviews measure three things: how likable the candidate is, how similar they are to the interviewer, and how well they perform under social pressure. None of those predict whether they'll be good at the job.
Structured interviews measure what you actually need to know: can they solve problems, do they communicate clearly, have they done this kind of work before, and how do they handle the specific challenges this role throws at them.
The rule of three: Every interview should measure exactly three competencies. More than three and you'll dilute your signal. Less than three and you're not getting a complete picture. Pick your three before writing questions.
Question types: when to use each
| Type | Best for measuring | Example trigger |
| Behavioral | Past performance, problem-solving, work style | "Tell me about a time when…" |
| Situational | Judgment, decision-making, values | "What would you do if…" |
| Competency-based | Specific skills, technical ability | "Walk me through how you would…" |
| Values-alignment | Motivation, culture contribution | "What kind of work environment helps you…" |
For most roles, lead with behavioral questions (they're the most predictive), follow with one situational and one competency question, and close with a values question.
Universal questions that work for any role
These five questions form a solid baseline for almost any position. Customize the specifics per role, but keep the structure:
Question 1 — Problem Solving
Tell me about the hardest problem you solved at work in the last year. What made it hard, what did you try, and what happened?
What to listen for: Specificity. Strong candidates name the problem, their approach, setbacks, and the outcome. Weak candidates give vague answers or describe team efforts where their role is unclear.
Question 2 — Ownership
Describe a time you noticed something was broken — a process, a system, a relationship — and you decided to fix it without being asked. What did you do?
What to listen for: Initiative without permission-seeking. Did they see a problem and act, or did they see a problem and write a memo about it?
Question 3 — Learning
Tell me about a skill you had to learn quickly to get something done. How did you approach it?
What to listen for: Resourcefulness. Do they wait for training, or do they figure it out? The best answer includes a specific learning strategy, not just "I'm a fast learner."
Question 4 — Disagreement
Tell me about a time you disagreed with a decision at work. What did you do?
What to listen for: Can they disagree constructively? Do they raise concerns with data or just with feelings? Do they commit after the decision is made, or do they sulk?
Question 5 — Motivation
Think about the best day you've had at work in the last year. What were you doing, and why did it feel so good?
What to listen for: This reveals what actually motivates them — not what they think you want to hear. Someone who lights up describing a solo deep-work session may struggle in a highly collaborative role, and vice versa.
Role-specific question templates
Customer-facing roles (sales, support, hospitality, retail)
Customer Service
Tell me about a time you dealt with a customer who was angry about something that wasn't your fault. What happened and how did you handle it?
Sales & Persuasion
Walk me through the last time you had to convince someone to change their mind about something important. What was your approach?
Resilience
Tell me about a week where everything seemed to go wrong with customers. How did you get through it?
Skilled trades and field roles (contractors, technicians, installers)
Technical Judgment
Describe a job where the standard approach wasn't going to work. What did you do differently and why?
Client Communication
Tell me about a time you had to explain something technical to a client who didn't understand it. How did you make it make sense to them?
Quality Standards
Walk me through how you decide when something is "done" versus when it's "done right." Give me a specific example.
Administrative and operations roles
Organization Under Pressure
Tell me about a time you had to manage multiple competing deadlines with limited information. How did you prioritize?
Process Improvement
Describe a process you inherited that was inefficient. What did you change and what was the result?
Attention to Detail
Tell me about a mistake you caught that others missed. How did you catch it?
Management and team-lead roles
People Development
Tell me about someone on your team who was struggling. What did you do, and what happened?
Difficult Conversations
Describe the hardest feedback conversation you've had to have. How did you prepare for it and how did it go?
Team Building
Tell me about a time you inherited a team with low morale or trust issues. What did you do in the first 90 days?
How to score structured interview responses
Use the same 1-3 scale for every question. Score immediately after the interview while the details are fresh:
| Score | Label | What it looks like |
| 1 | Below expectations | Vague or hypothetical answers. Can't name a specific situation. Deflects or gives credit to others without describing their own role. |
| 2 | Meets expectations | Names a specific situation with clear personal involvement. Describes what they did and what happened. Answer is relevant to the question asked. |
| 3 | Exceeds expectations | Compelling, specific example with measurable impact. Describes obstacles and how they overcame them. Answer reveals judgment and self-awareness beyond the question. |
Calibration tip: After your first three candidates, compare scores with anyone else reviewing. If you're consistently scoring higher or lower than your co-reviewers, recalibrate. The goal is consistency, not agreement.
Common question-writing mistakes
- Leading questions: "We really value hustle here. Would you say you're a hustler?" — You've just told them the answer you want.
- Hypothetical-only questions: "What would you do if…" questions are fine as a supplement, but past behavior is a much better predictor than imagined future behavior.
- Too many questions: 4-6 questions is the sweet spot. More than 6 and candidates fatigue, answers get shorter, and discrimination between strong and weak candidates blurs.
- Questions that test memory, not ability: "Tell me about a time five years ago when…" — If the candidate has to dig that far back, the answer won't be reliable.
- Culture-fit questions without definition: "Tell me why you'd be a good culture fit" is meaningless unless you've defined what your culture actually values. Replace it with specific values-alignment questions.
Put these questions to work
Create a structured interview set with your chosen questions. Candidates record answers on their own time. You review and score on yours.
Create a free question set →