40 Situational Interview Questions to Ask Candidates (With Scoring Rubric)

The most revealing interview question I have ever asked is: "A customer calls furious because we shipped the wrong order. They are threatening to leave a one-star review online. You do not have authority to issue a refund. What do you do?" The answer to this question has predicted job performance more accurately than any resume bullet point or reference call. Not because the scenario itself matters, but because the candidate's reasoning reveals how they think under pressure, whether they take ownership, and whether their judgment aligns with how you want your business to operate.

Situational interview questions present hypothetical scenarios and ask candidates how they would respond. They are different from behavioral questions ("tell me about a time when...") because they test judgment rather than memory. This makes them especially valuable for entry-level hires, career changers, and anyone who lacks directly comparable experience. At a small business where you cannot afford to wait for the "perfect candidate" with 5 years of identical experience, situational questions reveal whether someone can think clearly in the situations they will actually face. And given that only 12% of employees strongly agree their company does a great job of onboarding (Gallup), hiring the right person is only the first step.

This guide contains 40 situational questions organized by role type, a scoring rubric you can use immediately, the red flags that predict poor performance, and the questions that are illegal under US employment law. Every question is written for hiring managers at small businesses who conduct interviews themselves. FirstHR handles what comes after the interview: offer letters, compliance paperwork, and structured onboarding for the candidate these questions help you identify.

What Are Situational Interview Questions?

A situational interview question presents a hypothetical work scenario and asks the candidate to describe how they would handle it. The scenario is designed to mirror a real challenge they would face in the role, and the answer reveals their judgment, reasoning process, and decision-making style.

Situational questions work because they test the reasoning behind the answer, not just the answer itself. Two candidates might both say "I would apologize to the customer." But the candidate who adds "then I would find out what went wrong, fix it, and follow up the next day to make sure they are satisfied" demonstrates a depth of thinking that the first candidate did not. The scenario is the prompt. The reasoning is the data.

Situational vs Behavioral: When to Use Each

These two question types serve different purposes and work best for different candidates. Using the wrong type for the wrong candidate produces weak data.

For most small business hires, a mix works best: 3-4 situational questions (testing judgment in scenarios specific to your role) plus 2-3 behavioral questions (verifying that they have actually done relevant work before).

10 General Situational Questions for Any Role

These questions apply to every position. They test core competencies that matter regardless of the role: problem-solving, communication, reliability, ownership, and adaptability.

8 Situational Questions for Customer-Facing Roles

Retail, hospitality, support, and service roles require candidates who can handle difficult interactions while representing the business. These questions test de-escalation, empathy, and real-time judgment.

8 Situational Questions for Office and Administrative Roles

Office managers, administrative assistants, bookkeepers, and operations coordinators handle the daily systems that keep a small business running. These questions test organization, accuracy, and independent problem-solving.

7 Situational Questions for Your First Management Hire

Hiring a manager at a small business is one of the highest-stakes decisions a founder makes. These questions test leadership judgment, not just management theory.

7 Situational Questions for Remote and Hybrid Candidates

Remote work adds specific challenges that in-office roles do not have: asynchronous communication, self-management, isolation, and the discipline to stay productive without physical oversight.

For remote roles specifically, question 36 is the most diagnostic. How someone handles a misunderstanding in text reveals everything about their remote communication skills. The candidate who says "I would pick up the phone and talk to them" is demonstrating the medium-switching instinct that remote work requires.

How to Write Situational Questions for Your Own Roles

Forty questions will not cover every role. A question written for your business beats a generic one because the scenario is real, which means the candidate cannot answer it from an interview prep site and you already know what a good answer looks like. The raw material is sitting in your last quarter: open your calendar or your inbox and find the incidents that actually consumed a day.

The pattern behind all four is context, constraint, conflict. The constraint is the part most people leave out and the part that makes the question diagnostic. "A customer is upset, what do you do" invites a script. "A customer is upset and you do not have authority to issue a refund" forces a decision. Every scenario should have at least one closed door.

Four rules keep the questions usable. Keep the scenario under about sixty words, because a long setup tests listening comprehension rather than judgment. Strip out internal jargon and system names an outsider could not know. Avoid scenarios with one obvious right answer, since a question everyone passes gives you no ranking information. And write between five and seven of them per role, each aimed at a different competency, so you are not scoring the same trait four times and calling it a pattern.

All of that lands on one sheet per role, filled in before the first candidate is scheduled and then reused unchanged for everyone who follows. Write the incident down first, draft the question out of it, and record what your two employees actually said while you still have their words.

How to Ask the Question So the Answer Is Usable

The delivery matters as much as the question. Read the scenario once, at normal speed, and then stop talking. Candidates need six to ten seconds of silence to structure an answer, and interviewers almost always fill that gap by rephrasing the question, which changes it and quietly makes the candidate's answer incomparable to the last person's. If they ask a clarifying question, that is a positive signal rather than an interruption. Answer it briefly, note that they asked, and give every subsequent candidate the same clarification if they ask for it.

The first answer is rarely the useful one. Three probes turn a generic response into evidence:

• "What would you do first?" Sequencing separates people who have a plan from people who have a vocabulary. Anyone can list five considerations; ordering them is the skill.
• "What if that does not work?" Second-order thinking is where rehearsed answers run out. This probe is also the most reliable defense against answers prepared with an AI assistant, which tend to be fluent, well-organized and one layer deep.
• "How would you know it worked?" Candidates who define an outcome are the ones who follow up on the job. Candidates who have never thought past the immediate action stop here.

Two failure modes need a specific response. When a candidate says "it depends," do not accept it and do not penalize it, because it is often the correct instinct. Ask what it depends on, then have them pick one branch and answer it. And when an answer is a polished abstraction with no detail in it, convert the hypothetical into a behavioral question on the spot: "has anything like this actually happened to you?" A real story has friction in it, names, a moment where something went wrong. A fabricated one does not. That single pivot recovers most of what situational questions give up relative to behavioral ones.

Budget five to seven minutes per question including probes. That is five to seven questions in a 45-minute interview with about ten minutes left for the candidate's own questions, which you should never cut, since what a candidate asks is itself assessment data. Take notes on verbs, not adjectives: write down the actions they named and the order they named them in, rather than "seemed confident." Adjectives are what you will still remember three days later anyway, and they are exactly the part of the interview you should be least willing to trust.

How to Score Situational Interview Answers

Situational questions without scoring produce the same problem as unstructured interviews: you remember who you liked, not who answered best. A scoring rubric turns subjective impressions into comparable data points.

Score each question on the competency it is designed to assess. Complete the scorecard within 30 minutes of the interview. Compare total scores across candidates. If two candidates are within 2-3 points, look at which one scored higher on the competency most critical for this specific role.

Turning Scores Into a Decision

A rubric only helps if the scores are made independently and the bar is set before you meet anyone. Decide during the job posting stage what a hire looks like in numbers. A workable default: a minimum of 3 on every competency, no 1 anywhere, and a threshold total that a genuinely qualified person should clear. Writing that down in advance is what stops the standard from moving to fit whoever you liked most, which is the specific failure that scoring exists to prevent.

When more than one person interviews, each interviewer scores alone and submits before the debrief. Ten minutes of hallway conversation before scoring collapses three opinions into one, usually the most senior person's, and you have paid for three interviews and received one data point. In the debrief, have the most junior interviewer speak first for the same reason. Then treat disagreement as the useful part. If one interviewer gave a 4 on judgment and another gave a 2, the resolution is to compare the notes and find what one heard that the other did not, not to average to a 3 and move on. Wide spread on the same candidate usually means the question was ambiguous, and that is worth fixing before the next round of interviews.

Two patterns override the total. A candidate who scores 1 on judgment does not get rescued by strong scores elsewhere, because judgment is the competency training does not fix. And a candidate whose scores are strong but who scored low on the one competency that defines the role, de-escalation for a support hire or accuracy for a bookkeeping hire, is a worse fit than a candidate with a lower total and the right shape. Rank on the critical competency first, then use the total to break ties.

Keep the completed scorecards. Federal anti-discrimination recordkeeping rules generally require employers to retain applications and hiring records for at least one year from the date of the record or the personnel action, longer for federal contractors, and if a charge is filed you must preserve everything relating to it until the matter is resolved. Interview notes are part of that record and they are discoverable, which is a good reason to write only job-related observations. "Did not describe how they would verify the fix" is a note. Anything about the person's appearance, family, accent or perceived age is not a note, it is an exhibit.

Red Flags in Situational Interview Answers

Not every weak answer is a red flag. Some candidates are nervous. Some need a moment to think. But certain patterns in situational answers reliably predict problems on the job. Eight patterns to watch for.

One important note: a single red flag is a data point, not a verdict. Two or more red flags across different questions form a pattern. Patterns predict behavior. Single data points might be nerves, a bad day, or a misunderstanding of the question. Ask a follow-up before concluding.

Situational Questions You Legally Cannot Ask

Situational questions that require candidates to reveal protected characteristics are illegal under federal anti-discrimination law (EEOC). The scenario itself may sound neutral, but if the only way to answer it is by disclosing information about a protected class, the question is problematic.

The rule is the same as for any interview question: if the question is not directly related to the candidate's ability to perform the job, do not ask it. Reframe any scenario that could inadvertently reveal protected information into a job-focused version that any candidate can answer regardless of personal circumstances.

Do not assume you are under the federal threshold

Title VII and the ADA generally apply to employers with 15 or more employees, and the ADEA at 20 or more, which leads a lot of small business owners to conclude that interview rules are somebody else's problem. State fair employment laws are where that assumption fails. Coverage thresholds vary considerably from state to state, several states reach employers with only a handful of employees, and a few apply from the first employee. Many states and cities also protect characteristics federal law does not, and separate rules on subjects like salary history and criminal record inquiries commonly apply at low headcounts or from the first hire. Check your own state's threshold once rather than assuming the federal number is the operative one.

If you record interviews or use AI scoring

Recording an interview or running it through an automated scoring tool adds a second layer of rules on top of the question design above. Recording itself is governed by state wiretap and consent laws, and a meaningful number of states require the consent of every party rather than just one, which for a remote interview may mean the state where either person is sitting. Automated tools are regulated separately and the landscape is state and city specific: Illinois requires notice, an explanation and consent before artificial intelligence analyzes a video interview for an Illinois-based role, New York City requires an annual independent bias audit and advance candidate notice for automated employment decision tools, and Maryland requires a signed consent before facial recognition is used during an interview. More jurisdictions are adding requirements. The practical rule for a small business is that any tool which records, transcribes or scores candidates needs a compliance check against your state and your candidate's state before its first interview, not after.

Frequently Asked Questions