Interview guide · Interview types
Structured interview questions
In short
Structured interview questions are a fixed set of job-related questions asked in the same order to every candidate for a role, each scored against a pre-written rating scale. This page gives 32 example questions by type (past behavior, situational, job knowledge, work sample, motivation), what strong answers look like, and how to build, score and run a structured interview.
A structured interview has three parts, and the questions are only one of them. Every candidate gets the same questions, every interviewer uses the same rating scale with written examples of poor, acceptable and strong answers, and the scores are recorded before anyone discusses the candidate. Drop any of those three and you are back to a conversation with a list, which is what most companies actually run. Large meta-analyses of selection research have found for decades that structured interviews predict job performance better than unstructured ones, and they are also easier to defend when a hiring decision is challenged.
The example questions below are grouped by question type, because a good guide mixes types rather than asking eight versions of the same thing. Do not copy all 32. Start from a job analysis, pick four to six competencies, and choose one or two questions per competency. Then write your own anchors for what a 1, 3 and 5 sound like for your role, using the good answers and red flags here as a draft. For the formal definition, see our glossary entry on the structured interview.
What these questions assess
- Evidence tied to the competencyA structured question targets one competency. Score only what the answer shows about that competency, not general likability or how the candidate answered earlier questions.
- Concrete detailSpecific names, numbers, dates and steps make an answer scoreable. Vague answers should be probed with the standard follow-ups, then scored as they stand.
- Sound reasoning on hypotheticalsFor situational questions, the best answers identify the real problem, weigh options and say what they would check first, rather than jumping to one action.
- Accurate job knowledgeKnowledge questions have right and wrong answers. Your anchors should list the points a correct answer covers so different interviewers score the same way.
- Consistency across the interviewA candidate's examples should hold together. Contradictions between answers are worth a note, though they should be scored under the relevant competency only.
- Realistic motivationJob-related motivation questions check whether the candidate understands the actual work, shifts and pay, which predicts early turnover in hourly and entry-level roles.
Past-behavior questions
Tell me about the last time you had more work than you could finish by the deadline. What did you do?
- Why ask it
- Measures prioritization and communication under workload pressure, which almost every role needs.
- A strong answer
- Names the specific workload and deadline, how they decided what came first, who they told and when, and what got done or slipped.
- Red flags
- Says this never happens, or describes working all night with no prioritization or communication.
Describe a time you found an error in your own work after you had already handed it in.
- Why ask it
- Tests honesty and ownership. Everyone makes errors, so the question is what they did next.
- A strong answer
- Reports the error promptly, explains the impact, fixes it and changes a habit or check to stop it happening again.
- Red flags
- Hoped nobody would notice, or the error was someone else's fault.
Tell me about a time you had to follow a rule or process you disagreed with.
- Why ask it
- Reveals how candidates handle compliance and disagreement in the same moment.
- A strong answer
- Followed the rule while raising the concern through the right channel, with a reasoned argument, and accepted the outcome.
- Red flags
- Ignored the rule quietly, or followed it while complaining to peers.
Give me an example of a time you helped a coworker who was struggling.
- Why ask it
- Measures teamwork through action rather than claims of being a team player.
- A strong answer
- Describes noticing the problem, what help they offered, how they balanced it with their own work, and the result for the coworker.
- Red flags
- Took over the work completely or helped only when told to.
Tell me about a time you received feedback that was hard to hear.
- Why ask it
- Predicts coachability, which matters most in the first 90 days.
- A strong answer
- Quotes the feedback, admits their first reaction, describes what they changed and gives evidence the change stuck.
- Red flags
- Explains why the feedback was wrong.
Describe the most difficult customer, client or internal stakeholder you have dealt with in the past year.
- Why ask it
- Tests service orientation and composure with a real case rather than a hypothetical.
- A strong answer
- Describes the person's need behind the behavior, what they said and did, where they held a boundary and how it ended.
- Red flags
- Mocks the customer or stakeholder.
Tell me about a time you improved a process that others had accepted for years.
- Why ask it
- Measures initiative and practical problem solving.
- A strong answer
- Explains what was wrong, how they tested the idea, how they got buy-in and a measurable result such as time saved or errors reduced.
- Red flags
- The improvement was imposed without consulting anyone, or no result is known.
Situational questions
You are halfway through a shift and realize you will not finish your assigned tasks. Your supervisor is in a meeting. What do you do?
- Why ask it
- Tests judgment about escalation and self-management when help is not immediately available.
- A strong answer
- Prioritizes the work with the highest impact or deadline, messages the supervisor with a short status and question, and checks whether a coworker can help.
- Red flags
- Waits silently until the shift ends or leaves tasks undone without telling anyone.
A customer asks for something that breaks company policy but would clearly make them happy. How do you respond?
- Why ask it
- Shows how the candidate balances customer service against rules.
- A strong answer
- Explains the policy kindly, offers what they can do, and escalates if there is a legitimate exception route.
- Red flags
- Would break the policy to please the customer, or refuses with no alternative.
You notice a coworker taking a shortcut that could cause a safety or quality problem. What do you do?
- Why ask it
- Tests integrity and willingness to speak up with peers.
- A strong answer
- Mentions it to the coworker directly first if safe, and reports it if the risk is serious or the behavior continues.
- Red flags
- Says it is not their business.
Your manager gives you two urgent tasks from two different stakeholders that cannot both be done today. What do you do?
- Why ask it
- Measures prioritization and upward communication.
- A strong answer
- Clarifies the real deadline and impact of each, asks the manager to choose if it cannot be resolved, and tells both stakeholders the plan.
- Red flags
- Picks one at random or the one from the louder person.
On your first week, you are given a task you were never trained on and everyone around you is busy. What do you do?
- Why ask it
- Tests resourcefulness and judgment about when to ask for help.
- A strong answer
- Checks documentation or past examples, tries a reasonable first step, then asks a targeted question rather than waiting or guessing on something risky.
- Red flags
- Guesses on something high-risk or waits all day for someone to notice.
A teammate takes credit in a meeting for work you did. How do you handle it?
- Why ask it
- Shows maturity in workplace conflict.
- A strong answer
- Speaks to the teammate privately, assumes a misunderstanding first and makes sure their manager knows their contribution through normal channels.
- Red flags
- Confronts them publicly or does nothing and holds a grudge.
You are told to hit a productivity target, and you believe meeting it would mean cutting corners on quality. What do you do?
- Why ask it
- Tests how candidates handle tension between speed and standards.
- A strong answer
- Tracks where time goes, raises the trade-off with evidence and proposes options, while keeping quality where errors have real consequences.
- Red flags
- Would quietly cut corners to hit the number.
Job knowledge and work-sample prompts
Walk me through how you would complete [core task of the role], step by step.
- Why ask it
- The single most adaptable structured question. It checks whether the candidate knows the actual work.
- A strong answer
- Covers the steps in a sensible order, mentions the checks a careful professional would do and names the tools or systems involved.
- Red flags
- Skips steps that cause real errors in your environment.
Here is a short scenario from a real day in this job. What are the first three things you would do?
- Why ask it
- A work sample in interview form. It shows applied judgment rather than recalled facts.
- A strong answer
- Identifies the most urgent issue, gathers the missing information, and takes action in an order that protects customers, safety or money.
- Red flags
- Addresses a minor detail first and misses the main problem.
What would you check before signing off on [a deliverable typical of the role]?
- Why ask it
- Measures quality habits in specific terms.
- A strong answer
- Lists concrete checks that match your own quality checklist, in a reasonable order.
- Red flags
- Says they would just review it.
Which metric would you watch to know you are doing this job well, and why?
- Why ask it
- Shows understanding of how the role creates value.
- A strong answer
- Names a relevant metric (for example first contact resolution, pick accuracy, time to fill) and explains its trade-off with another metric.
- Red flags
- Cannot name a metric or names one unrelated to the role.
Explain [a technical concept from the role] as if I were a new hire on day one.
- Why ask it
- Tests depth of understanding and the ability to explain clearly, both needed for training others.
- A strong answer
- Clear, accurate, uses an example and checks for understanding.
- Red flags
- Hides behind jargon or explains it incorrectly.
What tools or systems have you used for this kind of work, and what did you use them for day to day?
- Why ask it
- Confirms hands-on experience with tool categories you use.
- A strong answer
- Names the tool categories, the tasks they did in each and a limitation or workaround they discovered.
- Red flags
- Lists tools with no detail about actual use.
Motivation and job-fit questions
This role involves [specific conditions: shifts, weekends, standing, call volume, travel]. How does that fit your situation?
- Why ask it
- A realistic job preview in question form. It reduces early turnover by surfacing mismatches.
- A strong answer
- Engages with the specifics and mentions how they have handled similar conditions before.
- Red flags
- Agrees to everything without reflection, then hesitates on follow-up.
What do you expect a typical week in this role to look like?
- Why ask it
- Checks whether the candidate understands the actual job, not the title.
- A strong answer
- Describes the work accurately from the posting and any research, and asks about the parts they are unsure of.
- Red flags
- Expects a very different job than the one offered.
What made you apply for this role now?
- Why ask it
- Reveals push and pull factors without asking about protected circumstances.
- A strong answer
- Gives a specific job-related reason connected to the work, the team or growth.
- Red flags
- Only reason is leaving a current job they dislike.
Tell me about a job or task you did not enjoy. How did you keep your performance up?
- Why ask it
- Tests self-motivation in a way that applies to every role with repetitive parts.
- A strong answer
- Names the task honestly and describes concrete habits that kept quality and attendance steady.
- Red flags
- Admits performance dropped and sees no problem with that.
Where would you like your skills to be in a year, and what would help you get there?
- Why ask it
- Shows growth orientation and what support the candidate will need.
- A strong answer
- Names specific skills relevant to the role and realistic development steps.
- Red flags
- Expects a promotion within months regardless of performance.
What kind of supervision helps you do your best work?
- Why ask it
- Helps match the candidate with the team's management style, scored against what the role actually offers.
- A strong answer
- Describes preferences honestly and how they adapt when the style differs.
- Red flags
- Cannot work with any feedback or needs constant direction in a role with little oversight.
Questions for leadership and senior roles
Tell me about a hiring decision you made that did not work out. What did you learn?
- Why ask it
- Tests self-awareness and how leaders improve their own selection process.
- A strong answer
- Owns the decision, identifies what signals they missed and changed in their interviewing as a result.
- Red flags
- Blames the hire entirely.
Describe a time you had to deliver a decision to your team that you did not make and did not agree with.
- Why ask it
- Measures leadership maturity and loyalty to decisions.
- A strong answer
- Raised concerns upward first, then communicated the decision clearly and supported it without undermining leadership.
- Red flags
- Told the team they disagreed and that it was not their call.
How have you used data to change a decision your team was about to make?
- Why ask it
- Measures analytical leadership and influence.
- A strong answer
- Names the data, how they gathered it, what it showed and the decision that changed.
- Red flags
- Data was used only to confirm a decision already made.
Tell me about a time you had to address an underperforming team member.
- Why ask it
- Tests fairness, documentation and directness.
- A strong answer
- Set clear expectations, gave specific feedback with examples, provided support, documented and followed through to an outcome.
- Red flags
- Waited months or skipped straight to termination with no coaching.
How would you make sure interviewers on your team score candidates consistently?
- Why ask it
- For managers who will run structured interviews themselves, this checks they understand the method.
- A strong answer
- Mentions shared questions, anchored rating scales, interviewer training, independent scoring before discussion and reviewing score patterns.
- Red flags
- Relies on gut feeling or culture fit.
Describe a significant change you led. How did you bring people along?
- Why ask it
- Tests change leadership with evidence.
- A strong answer
- Explains the reason for change, how they involved the people affected, how they handled resistance and the measured outcome.
- Red flags
- Announced the change and expected compliance.
Sample answers
First I would figure out which tasks really have to be done today and which can wait, because usually there are one or two with a hard deadline or a customer waiting on them. I would do those first. Then I would send my supervisor a short message, something like: I have four tasks left, I am finishing A and B now, C and D will not get done by end of shift, do you want me to stay late or hand them off? That way they can decide when they are out of the meeting without having to come find me. If someone on my team was caught up, I would ask if they could take one. At my last job in a fulfillment center this happened often, and the supervisors liked getting a short heads-up rather than finding out at end of shift.
About a year into my job as a scheduling coordinator, my manager told me that people found my emails abrupt and that two department heads had complained. Honestly, my first reaction was to be defensive, because I was trying to be efficient. But I asked her to show me examples, and she was right: I was sending one-line replies to people who were already frustrated about schedule changes. I started adding a sentence of context to every change notice and calling instead of emailing when a change would hurt someone's plans. A few months later, one of the department heads who had complained asked for me to handle their scheduling. I still reread anything I send when the news is bad.
I would start by agreeing on what we are measuring. For a supervisor role we might pick five competencies from the job analysis and write one or two questions for each. For every question, I would write examples of a 1, 3 and 5 answer from real responses we have heard. Then I would run a short calibration: everyone scores the same recorded answer, and we talk about why scores differ. In the actual interviews, each person scores independently and submits before the debrief. Every quarter I would look at score spreads by interviewer. If one person rates everyone a 4 or never gives above a 2, we sit down and recalibrate. It takes some time up front but it saves arguments later.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Problem solving and judgment | 25% | Identifies the real problem quickly, considers options and consequences, and chooses a sensible first action. | Acts on the first idea, misses the main issue, or cannot explain their reasoning. |
| Job knowledge and skills | 25% | Explains core tasks accurately, uses the right terms and covers the checks a careful professional would make. | Gives general or incorrect answers about the core work of the role. |
| Collaboration and communication | 20% | Shows specific examples of helping others, raising concerns constructively and keeping people informed. | Works around others, avoids difficult conversations or communicates only when asked. |
| Ownership and integrity | 15% | Owns mistakes, follows rules while challenging them properly and speaks up about safety or quality issues. | Blames others, hides errors or treats rules as optional. |
| Motivation and role fit | 15% | Understands the real conditions of the job and gives specific, job-related reasons for wanting it. | Has unrealistic expectations of the role or no reason beyond leaving their current job. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
How to build a structured interview guide in six steps
- Start from a job analysis. List the tasks that matter most and the knowledge, skills and behaviors needed to do them. Ask two or three top performers and their supervisor what separates good from average. This is what makes the interview job-related.
- Choose four to six competencies. More than six and interviewers stop scoring carefully. Weight them by importance, as in the scorecard above.
- Write one or two questions per competency, mixing types. Past-behavior questions work best for candidates with experience; situational and work-sample questions work for entry-level candidates who have never been in the situation. Our behavioral interview questions and competency-based interview questions pages are good sources.
- Write anchored rating scales. For each question, describe what a 1, 3 and 5 answer contain. Use real answers from past interviews where you can. This step is where most teams cut corners, and it is the one that does the most for consistency.
- Write standard follow-up probes. Allow every interviewer the same two or three probes (What did you do next? What was the result?). Probing is fine, as long as it is the same for everyone.
- Pilot and calibrate. Run the guide with two or three current employees, check that questions are understood and that anchors separate strong and weak answers, then train interviewers with a calibration session.
A typical structured interview for an hourly or entry-level role runs 20 to 30 minutes with five or six questions. Professional roles usually take 45 to 60 minutes with eight to ten questions. Leave five minutes at the end for the candidate's own questions, and use our list of interview questions to ask candidates to fill gaps in your guide.
Scoring, legal safeguards and common mistakes
Score each answer right after it is given, on the agreed scale, with a one-line note of the evidence. Interviewers who score at the end of the interview drift toward an overall impression. In panels, every interviewer submits scores before the debrief so the most senior person in the room does not set the number for everyone.
Keep every question job-related. In the US, Title VII of the Civil Rights Act, the Age Discrimination in Employment Act and the Americans with Disabilities Act prohibit discrimination in hiring, and the Uniform Guidelines on Employee Selection Procedures (1978) expect selection procedures that cause adverse impact to be shown to be job-related. Avoid questions about age, family plans, religion, national origin, disability or health. Ask about the ability to do essential job functions instead ("This role requires lifting 50 pounds regularly. Can you do that with or without reasonable accommodation?"). Rules vary by state and country, so check local requirements, including pay history bans in many states.
Watch adverse impact. Compare pass rates by group at each stage. A common screening check is the four-fifths rule from the Uniform Guidelines: if one group's selection rate is below 80 percent of the highest group's rate, look closer at the step causing it.
The most frequent mistakes we see:
- Interviewers who go off script because the candidate is interesting. Extra questions can be asked after the structured portion, but they should not be scored.
- Anchors that only say "excellent" or "poor" without describing what the answer contains.
- Discussing the candidate between interviews, which spreads one person's impression to the whole panel.
- Treating the structured interview as the only tool. For many roles a short work sample or skills test adds more information than three more questions.
Running structured interviews at high volume
Structure is what makes volume hiring work. When 40 hiring managers across 15 sites interview for the same role, a shared guide is the only way to compare candidates and to find out which interviewers are rating differently from everyone else.
For contact centers, retail, warehouse and other hourly hiring, keep the structured interview short: five questions, about 20 minutes, with a simple 1 to 5 scale and anchors printed on the guide. Push routine screening (availability, shift fit, work authorization, basic requirements) into an application form or chatbot so interview time goes to the competencies that predict performance.
Asynchronous video and AI-assisted structured interviews can ask the same questions in the same order to every applicant at any time of day, then score or summarize answers against your rubric for a recruiter to review. This removes scheduling delays, which are often the biggest cause of candidate drop-off in hourly hiring. If you use automated scoring, keep a person in the decision, test results for adverse impact regularly, tell candidates how the interview works, and check local rules: New York City's Local Law 144, for example, requires a bias audit and candidate notice for automated employment decision tools used in hiring, and the EU AI Act classes AI used in recruitment as high risk.
Finally, close the loop. Every quarter, compare interview scores with 90-day performance and retention. Questions whose scores do not relate to anything on the job should be rewritten or dropped.
Frequently asked questions
What is a structured interview?
A structured interview is one where every candidate for a role is asked the same job-related questions in the same order, and every answer is scored against the same pre-written rating scale. It is designed to make interviews more consistent, more predictive of performance and fairer than free-form conversations.
What are some structured interview examples?
Common examples are past-behavior questions ("Tell me about the last time you had more work than you could finish"), situational questions ("A customer asks for something that breaks policy. What do you do?"), job knowledge questions and short work-sample prompts. What makes them structured is the fixed order and anchored scoring, not the wording.
How many questions should a structured interview have?
Typically five or six questions for hourly and entry-level roles (20 to 30 minutes) and eight to ten for professional roles (45 to 60 minutes). Aim for one or two questions per competency you are measuring, plus time for standard follow-up probes and the candidate's own questions.
What should a structured interview guide include?
A structured interview guide includes the competencies being measured and their weights, the exact questions in order, allowed follow-up probes, a rating scale with written anchors for each question, space for evidence notes and instructions for scoring before any group discussion.
Can interviewers ask follow-up questions in a structured interview?
Yes, as long as the follow-ups are standard and used with every candidate, such as "What was your specific role?" or "What was the result?". Unplanned follow-ups that steer some candidates toward better answers undermine the consistency that makes the format work.
Are structured interviews better than unstructured interviews?
For predicting job performance, research consistently finds structured interviews outperform unstructured ones, and they are easier to defend legally because every candidate is assessed on the same job-related criteria. Unstructured conversations still have a place for selling the role and answering candidate questions, but they should not drive the score.