25 structured interview questions for employers, and the rubric to score them
A structured interview means the same questions, same order, and the same rubric for every candidate. That discipline is what makes the scores comparable, not how formal the room feels. Here are 25 questions organized by competency, plus the rubric to score them.
AI summary
- A structured interview asks every candidate the same questions in the same order against the same rubric. The structure is in the consistency, not in the formality of the room. Most teams that say they run structured interviews don't. They run standardized openings followed by improvised everything else.
- 25 questions here organized by the five competencies most professional roles need to evaluate: ownership, communication, judgment, learning, and execution. Plus a behavioral-anchored 1-5 rubric per question.
- The fastest way to make any interview loop more structured is to pick 5-7 questions from this list per role, write the rubric anchors before you start interviewing, and have every panelist submit scores to the scorecard before any group debrief. The discipline of pre-debrief scoring is what makes the structure actually pay off.
A structured interview is just a normal interview with two disciplines added: the questions are the same across candidates, and the answers are scored against an anchored rubric before the debrief. The discipline isn’t formality. It’s not a script the interviewer reads stiffly off a sheet. It’s not a robotic conversation that puts the candidate off. It’s the version of the interview where the variance in scores across candidates reflects variance in candidates, not variance in which questions they happened to get asked.
Most teams that say they run structured interviews don’t. They’ve standardized the opening line and improvised everything else. Even teams that try often stop at “a few consistent questions” and call it done. Talent Board’s candidate experience research found only 56% of organizations ran a fully structured interview process in 2022, down from 61% the year before.
The predictive-validity research behind structured interviews doesn’t apply to those partial versions, because the structure isn’t real. A 2022 meta-analysis in the Journal of Applied Psychology put the corrected validity coefficient for structured interviews at .42, more than double the .19 for unstructured ones.
This post is 25 structured interview questions, organized by the five competencies most professional roles need to evaluate, with a 1-5 behavioral-anchored rubric for each one. Pick 5-7 per role. Write the anchors before you interview. Score independently before debrief. That’s the whole methodology, and it works.
How to pick which questions to use
Five competencies cover most professional roles:
- Ownership. Does the candidate take responsibility for outcomes, including outcomes outside their immediate control?
- Communication. Can they explain complex things to people who don’t share their context?
- Judgment. Do they make calls with reasoning when the answer isn’t obvious?
- Learning. Do they update their thinking when new evidence arrives?
- Execution. Do they ship, and do they ship well?
Most roles need to evaluate 3-5 of these. Pick the ones that matter for your role, and weight them in the final scorecard. Five questions across a 45-minute interview, with roughly five minutes per answer, is about the right load.
If you’re hiring a front-desk coordinator for a 15-person clinic and nobody is sorting the pile for you, three competencies are usually enough. Ownership, communication, and execution probably cover what the role actually needs. You don’t need all five for every hire, and picking fewer, sharper questions beats asking all 25.
The 25 questions below are organized 5 per competency. Pick the questions that match the role’s seniority and the specific skills you’re evaluating. If you’re splitting the questions across more than one interviewer instead of asking all of them yourself, see 20 panel interview questions that actually triangulate for how to assign competencies by panelist so the extra people in the room are actually adding signal.
Behavioral vs. situational: the two structured question formats
Every question in this list is behavioral. It asks about something the candidate actually did. There’s a second format worth knowing before you write your own questions: situational, which asks what the candidate would do in a scenario, whether or not they’ve lived through it yet. The Office of Personnel Management’s guide to structured interviewing treats both as legitimate formats. Most strong loops mix the two.
Behavioral questions work best once a candidate has enough work history to draw a real example from. Situational questions work better for early-career candidates with thinner work history, or for testing judgment on a scenario your team hits often that this particular candidate may not have faced yet.
If you’re writing behavioral questions, the STAR shape (situation, task, action, result) is a useful checklist for what a strong answer contains. Don’t make candidates recite it back to you. Just listen for whether their answer actually has all four parts. An answer that’s all situation and no result is the one to probe.
Structured interviews, consistency, and legal risk
The rigor here pays off past better hires. OPM’s structured interview guidance links higher interview structure to higher rater agreement and less adverse impact, because the format limits how much any one interviewer’s discretion can swing from candidate to candidate. That’s not the same as removing bias. It means every candidate gets measured against the same standard instead of whatever a given interviewer happened to notice that day.
Two things matter most if a hiring decision ever gets challenged. Every candidate answered the same core questions. And every candidate got scored against the same rubric, not five interviewers’ worth of different notes in five different formats. A folder of scorecards that all reference the same anchors is a far easier record to stand behind than a stack of impressions written after the fact.
Consistency is the thread running through this whole piece. Write the anchors before you interview. Ask the same questions in the same order. Score independently before the debrief. Each discipline is small on its own. Together, they make an interview both more predictive of performance and easier to defend.
If you’re running this async first, Truffle’s one-way interviews analyze every candidate’s answer against the same rubric the moment it’s submitted, so no interviewer’s memory of an earlier candidate colors how the next one gets read.
Does structure make the interview feel robotic?
This is the objection you probably have before you try it. Reading from a script feels stiff, and candidates notice.
The instinct is right. The fix people reach for is wrong. What kills a conversation isn’t fixed questions, it’s fixed everything. A structured loop only fixes two things: the core questions and the rubric you score them against. Follow-up questions, tone, and small talk all stay yours to run naturally.
Before you’ve run a structured loop, it’s easy to picture reading off a form. Once you’ve run a few, the opposite tends to happen. The core questions are already picked, so you can actually listen to the answer instead of scrambling to think up the next one. The conversation gets more natural, not less, once you’re not improvising the whole thing live.
The planning cost is real, and it’s worth naming honestly. Writing 5-7 questions and their anchors takes 30-45 minutes per role. That’s the entire cost. It’s a one-time setup per role, not a tax on every interview you run afterward.
Competency 1: Ownership
1. Tell me about a project where you owned the outcome end-to-end. What did you do when things went off track?
2. Describe a decision you made that affected your team beyond what your role formally covered. How did you decide to make it?
3. What’s the most uncomfortable conversation you’ve initiated at work? What made you initiate it?
4. Walk me through a time when an outcome you owned wasn’t going to land on time. What did you do, and how did you communicate it?
5. Tell me about a problem you noticed that wasn’t strictly yours to solve. What did you do about it?
Scoring anchors for ownership
| Score | What this looks like |
|---|---|
| 5 | Names a specific outcome they owned end-to-end. Took responsibility for setbacks without externalizing. Initiated the hard conversations or escalations themselves. Bonus for examples where they owned something outside their formal role. |
| 4 | Solid ownership on examples within their formal role. Acknowledges setbacks; took responsibility without much prompting. May have hesitated before initiating hard conversations. |
| 3 | Ownership at the role’s level. Doesn’t externalize but doesn’t show outsized ownership either. Hard conversations happened, but late or only when prompted. |
| 2 | Soft ownership. Externalizes setbacks (“the team didn’t deliver,” “the data wasn’t there”). Hard conversations avoided or deferred. |
| 1 | Negative ownership signal. Blames others for outcomes they were responsible for. Hard conversations never happened. |
Competency 2: Communication
6. Explain a complex concept from your work to me as if I have no background in your field.
7. Tell me about a time you had to explain a setback to a senior stakeholder. How did you frame it?
8. Walk me through a recent decision you made. Tell me what you’d say if you were briefing your manager on it in 90 seconds.
9. Describe a time you wrote something at work that you’re proud of. What made it work?
10. Tell me about a time you got the message wrong with someone. What was the gap, and what did you do about it?
Scoring anchors for communication
| Score | What this looks like |
|---|---|
| 5 | Adapts the explanation to the listener; checks for understanding; uses analogies that map cleanly. Can structure long answers concisely on demand. Owns communication failures and articulates the gap clearly. |
| 4 | Strong verbal clarity. Adapts language to the audience. May not always check for understanding mid-flow but adjusts when prompted. |
| 3 | Adequate. Clear when the topic is familiar; loses structure on unfamiliar reframes. Uses some jargon without translation. |
| 2 | Smooth but doesn’t engage with specifics. Generic answers. Doesn’t adjust register for the audience. |
| 1 | Confused under pressure. Blames the listener for not getting it. No self-awareness about communication failures. |
Competency 3: Judgment
11. Tell me about a decision you made with incomplete information that turned out to be wrong. What did you do next?
12. What’s a hill you’d die on at your current or most recent job? Why?
13. Walk me through a time you reversed a decision after new information came in.
14. Describe a time you disagreed with a manager. How did you handle it?
15. When you don’t have enough data to decide cleanly, how do you decide anyway?
Scoring anchors for judgment
| Score | What this looks like |
|---|---|
| 5 | Real decisions, real stakes. Owns wrong calls. Names specific reversals and what flipped them. Engages thoughtfully with disagreements without making the other party the villain. Has a working principle for deciding under uncertainty. |
| 4 | Solid examples of decisions made with reasoning. Owns mistakes. Some specificity on reversals. May have a less developed framework for uncertainty but engages with the question. |
| 3 | Decisions at the role’s level. Doesn’t externalize but doesn’t show outsized judgment. Disagreement examples are mild. |
| 2 | Generic decisions. Hedges into “it depends” without committing. No clear examples of reversing themselves. |
| 1 | Refuses to acknowledge wrong decisions or makes them sound trivial. Disagreements externalized to “bad managers.” |
Competency 4: Learning
16. Tell me about something you’ve learned in the last 6 months and what made you go learn it.
17. What’s a piece of feedback you got in the last year that changed how you work?
18. Describe a time you held a view strongly, then updated it. What flipped you?
19. What’s something you’re better at now than a year ago? What made the difference?
20. What’s a piece of feedback you wish you’d gotten earlier in your career?
Scoring anchors for learning
| Score | What this looks like |
|---|---|
| 5 | Specific learnings tied to specific triggers (a project, a person, a failure). Updates visible across multiple examples. Self-aware about gaps and what they’re doing about them. |
| 4 | Solid learning examples. Updates visible. Acknowledges specific feedback that landed. |
| 3 | Some learning examples but generic. Hard to see how their thinking actually changed. |
| 2 | ”I’m always learning” with no specifics. No specific feedback that mattered. |
| 1 | Defensive about feedback. No examples of updating. Treats their current views as static. |
Competency 5: Execution
21. Walk me through a project you shipped on time. What did you have to cut?
22. Tell me about a project that slipped. What was the root cause and what did you do?
23. Describe how you’d structure your first 30 days in this role. What would you prioritize?
24. What’s something you’ve built or shipped that you’re embarrassed about now? What changed?
25. Tell me about a time you had to choose between getting it right and getting it done.
Scoring anchors for execution
| Score | What this looks like |
|---|---|
| 5 | Real shipped work. Cuts made visible. Slip examples with clear root cause and specific learnings. Embarrassment examples show high current bar and update. Trade-off between right and done engaged thoughtfully. |
| 4 | Shipped work with some specifics. Some clarity on root causes for slippage. May lean toward one side of the right/done trade-off without acknowledging the other. |
| 3 | Solid execution at the role’s level. Shipped work but examples less differentiated. |
| 2 | Vague execution stories. Doesn’t engage with what was cut or what slipped. No embarrassment about past work, which often signals static bar. |
| 1 | Execution stories don’t add up, slips blamed externally, no shipped artifacts described concretely, no awareness of trade-offs. |
How to actually run a structured interview
Three disciplines turn the question list above into a working structured loop:
Pick the 5-7 questions before the interview, and write the anchors. Don’t decide which questions to ask in the room. Pick them at intake when you write the JD, and write the anchors in the same document. Starting from a blank page, see how to build an interview scorecard. The anchor work takes 30-45 minutes per role and pays off on every hire.
Ask the same questions in the same order to every candidate. Follow-up questions are fine and encouraged. The constraint is on the core question set, not on the conversation around it. Each interviewer asks the same core questions to every candidate, so the variance you see in candidate scores reflects variance in candidates, not in which questions they got asked. For the fuller research case behind this, see our breakdown of structured versus unstructured interviews.
Score independently before debrief. Each interviewer fills in the scorecard with 1-5 scores per question before the team meets. The debrief reads from the scorecard. The conversation discusses score deltas, where panelists disagreed, instead of trading impressions. This is the single discipline most teams skip, and it’s the one that makes the structure actually produce the validity gain. It only works, though, if the rubric is actually open during the interview instead of buried in a doc nobody looks at once the conversation starts.
Where async screening fits
Most of these questions work well in a Truffle async one-way interview. The candidate records answers to the same questions in the same order. AI analyzes each response against the anchors above. You inherit a ranked shortlist with every candidate already scored on the same 1-5 scale.
Running the structured questions async first has three benefits:
- Every candidate answers every question. Phone screens drop questions when the conversation drifts. Async doesn’t.
- The scoring is independent by default. No live interviewer is reading body language and adjusting the next question because of it.
- The shortlist is pre-scored. Reviewing Candidate Shorts means you see the score against each anchor before you decide who to bring into a live round.
The live round then probes deeper on 2-3 competencies the async round didn’t fully resolve, usually judgment and execution, where back-and-forth matters most. Total interview load drops. Signal density goes up. If that live round loosens into more of a conversation on those last few competencies, that’s fine (see what a semi-structured interview is and when you need one) as long as the core scored questions upstream stayed fixed. The validity gap from the research at the top of this post finally shows up in how your hires perform.
Turn this into a shortlist you can act on
Writing the questions and the rubric is the hard part, and it’s done once you finish this post. Running it the same way for every candidate, every time, on top of everything else on your plate, is where it usually falls apart.
Truffle’s one-way interview software lets you set these questions once and send them to every candidate. Each answer gets scored against the rubric you built here, the moment it’s submitted, so nothing depends on which interviewer is running low on attention by candidate twelve. You still make every hiring call. You’re just making it from a ranked shortlist with the evidence behind every score, instead of a stack of half-remembered impressions.
Start a 7-day free trial, 30 credits, no credit card required.
Frequently asked questions about structured interview questions
What is a structured interview question?
A structured interview question is one that gets asked of every candidate for the same role in the same order, with the same evaluation rubric applied to the answers. The question itself doesn’t have to be unusual, what makes it “structured” is the consistency of how it’s used and scored across candidates. The same conversational question, asked with the same rubric to every candidate, is structured. The most clever question, asked differently of each candidate or scored differently by each interviewer, isn’t.
How many structured interview questions should an interview have?
5-7 core questions per 45-60 minute interview. The questions should cover 3-5 competencies, each tested by 1-2 questions. Going past 7 cuts response time and produces shallow answers. Going below 5 leaves competencies un-evaluated. If you’re running a multi-round loop, distribute the competencies across rounds, one round on ownership and execution, another on judgment and learning, rather than asking all 25 questions to one candidate.
How do you score structured interview questions?
Use a 1-5 behavioral-anchored rubric per question, where each score level has a specific anchor describing what an answer at that level looks like. Each interviewer scores independently before any group debrief. Scores get submitted to a shared scorecard, and the debrief discusses deltas between scores, where panelists scored the same answer differently and why, rather than trading impressions. The pre-debrief scoring discipline is what makes the structure actually pay off in predictive validity.
What’s the difference between structured and behavioral interview questions?
Structured refers to the consistency of how questions are asked and scored across candidates. Behavioral refers to the question format: asking about real past behavior (“tell me about a time when…”) versus a hypothetical. The two often overlap, especially in the highest-validity loops, but they aren’t the same. A behavioral question asked differently of each candidate isn’t structured. A hypothetical question asked the same way of every candidate with the same rubric is structured. Most strong loops use behavioral (and situational) questions inside a structured methodology.
Should you ask behavioral or situational questions?
Use behavioral questions when a candidate likely has enough real work history to draw a specific example from. Use situational questions for early-career candidates with thinner history, or when you want to test judgment on a scenario your team hits often that this particular candidate might not have faced yet. Most loops end up mixing both, with behavioral carrying more weight once a candidate has a real track record to point to.
Do structured interviews reduce legal risk?
They reduce it. They don’t eliminate it. Structured formats are linked to higher rater agreement and less adverse impact because they limit how much any one interviewer’s discretion can vary from candidate to candidate. The real protection comes from the record: every candidate answered the same questions and got scored against the same rubric, so you have something concrete to point to if a decision ever gets challenged.
Can structured interviews include follow-up questions?
Yes. Structure constrains the core questions and the evaluation, not the conversational flow. Interviewers can probe deeper on any answer with follow-up questions, the constraint is that the follow-ups don’t change the rubric the answer is scored against. The improvised follow-ups can show up in the debrief as qualitative color and can break ties between candidates with similar rubric scores, but they don’t drive the primary score. That separation is what lets a structured interview feel conversational while remaining methodologically sound.
Does running a structured interview make the conversation feel robotic?
No, and this is the objection that stops most teams before they start. Structure only fixes the core questions and the rubric they’re scored against. Follow-up questions, tone, and the actual conversation stay natural. Interviewers who’ve run a structured loop a few times often find it easier to stay present in the conversation, not harder, because they’re not scrambling to invent the next question on the spot.
