Situational video interview questions ("what would you do if...")

Situational video interview questions are hypotheticals. “What would you do if a customer asked for a refund you cannot give?” “How would you handle two projects due the same afternoon?” Instead of asking what you have done, they ask what you would do in a scenario you may not have faced.

The trick is that on a recorded interview there is no one to clarify the scenario, so you answer the question you are given and say your assumptions out loud. These show up constantly in recorded screens, the kind where you get the question one at a time and answer to a camera with no interviewer. They are easy to write, they grade consistently across candidates, and they reveal judgment fast. That is exactly why a one-way interview reaches for them.

This page covers the situational questions recorded interviews actually use, model answers, and the one technique that matters most when no one is there to tell you what they meant.

Why recorded interviews lean on situational questions

A live interviewer can watch you handle a real curveball and follow up. A recorded screen cannot, so it leans on the next best thing: a hypothetical that forces you to show how you think.

There are three reasons hiring teams like them for a first screen. They are fair, because every candidate gets the identical scenario with no interviewer steering one person toward a better answer. They are predictive, because how you would handle an angry customer or a blown deadline says a lot about how you actually will. And they are fast to review, because the reviewer is comparing your judgment against the same prompt every time.

The catch lands on you. In a room, you would ask a clarifying question. “Is this a regular customer or a one-off?” “Do I have authority to issue the refund, or do I escalate?” On a recording, there is no one to answer. You either freeze on the ambiguity or you resolve it yourself. Resolving it yourself, out loud, is the whole skill.

The situational set you should expect

Situational questions cluster around a handful of pressures that nearly every role shares. You will not get all of these, but if you can reason through each one, you are ready.

Conflict and difficult people

• A customer is angry about something that is not your fault. What do you do?
• A coworker is not pulling their weight on a shared project. How do you handle it?
• Your manager asks you to do something you think is a mistake. What do you do?

Pressure and competing priorities

• You have two urgent tasks due at the same time and cannot finish both. How do you decide?
• A project is about to miss its deadline. Walk me through your next move.
• You are halfway through a task when a higher priority lands on your desk. What do you do?

Mistakes and ownership

• You realize you made an error that has already gone out to a customer. What now?
• You disagree with a decision the team has already made. How do you respond?
• You do not know how to do something you have been assigned. What is your first step?

Role-specific scenarios

• A scenario pulled straight from the job. A retail prompt asks about a long line and one register. A support prompt asks about a customer you cannot help. A management prompt asks about an underperformer.

The first three groups are about character and judgment. The last is about whether you understand the actual job. Both reward the same move: resolve the ambiguity, then answer.

The one technique: state your assumption, then answer

This is the part that separates a strong situational answer from a stuck one. When the scenario is vague, do not freeze and do not pretend it is fully specified. Say how you are reading it, then answer that version.

It sounds like this. “I am going to assume this is a repeat customer rather than a first-time buyer, because that changes how much leeway I would extend. With that in mind, here is what I would do.” Or: “If I have the authority to issue the refund myself, I do it on the spot. If I do not, here is how I would escalate without making the customer feel passed around.”

That single sentence does three things. It shows the reviewer you noticed the ambiguity, which is itself a signal of judgment. It lets you answer a concrete question instead of a fuzzy one, so your answer is sharp. And it protects you, because if they meant the other version, you have shown you can handle that too. You have turned a missing follow-up into a strength.

Two assumptions cover most prompts. Authority: do I have the power to fix this myself, or do I escalate? Answer both in a sentence each if it is quick. Context: who is the person and what is the history? Pick the reading that lets you show the most judgment, name it, and go.

Three model answers

The strongest situational answer pairs a principle with a real example. Open with how you would approach it, then ground it in something you actually did. The principle shows judgment, the example proves it is not just talk. This is STAR with a hypothetical front door, and it beats a tidy story with no thinking visible. Treat these as templates to adapt, not lines to recite.

”A customer is angry about something that is not your fault. What do you do?”

First I would assume this is a customer I want to keep, not a one-time interaction, so the goal is to fix the moment, not win the argument. My approach is to let them finish, acknowledge the frustration as real, and move straight to what I can actually do.

When I handled escalations on a support team, a customer came in furious about a shipping delay caused by the carrier, not us. I did not defend the carrier. I said I could see why that was frustrating when they had planned around the date, told them exactly when it would now arrive, and credited their next order without being asked. They went from threatening to cancel to leaving a positive review. The thing that defused it was acknowledging the feeling first and getting to a concrete fix fast, not explaining whose fault it was.

Why it works: it names the assumption, leads with a principle, then proves it with a real result. It never argues that the anger is unjustified.

”You have two urgent tasks due at the same time and cannot finish both. How do you decide?”

I am assuming I cannot just ask for more time on either, so I have to choose. I triage by what is hardest to undo and who is affected, not by which one is louder or landed first.

The week a client report and an internal dashboard were both due Friday, I looked at the stakes. The client report going late risked a renewal conversation. The dashboard was internal and could slip a day with a heads-up. So I flagged the dashboard owner early, finished the client report first, and delivered the dashboard Monday morning with no real cost. Sequencing by what is most expensive to get wrong, and communicating the slip before anyone has to chase me, is how I keep a double deadline from turning into two failures.

Why it works: it states the constraint it is assuming, gives a clear decision principle, and shows the candidate communicates proactively rather than going quiet.

”You realize you made an error that has already reached a customer. What now?”

My first assumption is that speed matters more than my ego here, so I am not going to sit on it. The move is to own it fast, contain the impact, then fix the root cause so it does not repeat.

I once sent a batch of onboarding emails with a broken link. I caught it about twenty minutes later. I told my manager immediately rather than hoping no one clicked, sent a short corrected follow-up that owned the mistake plainly, and then added a link check to our send checklist so it could not happen again. A few people replied that the quick correction made them trust us more, not less. The instinct I lead with is that a mistake you surface and fix beats one you hide and hope about.

Why it works: it resolves the “do I tell anyone” tension up front, shows ownership without drama, and ends on a fix that prevents a repeat. That is the judgment a reviewer is screening for.

Role-specific traps

Situational questions have their own ways of tripping people up, beyond ordinary nerves.

Answering the abstract instead of the concrete. “I would assess the situation and respond appropriately” answers nothing. It is the most common situational failure. Pick a specific reading of the scenario and answer that. A concrete answer to one version beats a vague answer to all of them.

Freezing on the ambiguity. Candidates lose the most time waiting for a clarification that is never coming. The prep window can be tight. One candidate described having “30 seconds to prepare for a two minute answer,” which leaves no room to stall. State your assumption in the first sentence and the freeze never happens.

Skipping the real example. A pure hypothetical answer sounds like theory. “I would stay calm and find a solution” is easy to say and proves nothing. The moment you add “here is a time I actually did this,” your answer gains weight. Treat the hypothetical as a door into a real behavioral example.

Making yourself the hero who never escalates. Some scenarios are tests of whether you know your limits. If a prompt describes something genuinely above your authority, the right answer often includes escalating well, not solving it solo. Knowing when to pull in a manager is judgment, not weakness.

Reading a script off the screen. Situational answers tempt people to over-prepare and recite. Reviewers notice. As one interviewer put it, “you can literally tell if someone is reading an answer to you.” Keep three or four bullets off to the side, glance, and look at the lens. The full mechanics are in how to answer video interview questions.

The AI-scoring reality, stated plainly

If your recorded interview is scored with AI, the situational answer is a good place to understand what that actually means. The honest version is reassuring.

Most tools transcribe what you say and check it against the role’s criteria, then surface that to a human who makes the call. They are reading your words, not judging whether your hypothetical is the “correct” one. The major vendors stepped back from analyzing faces and expressions years ago. HireVue, the most cited example, discontinued facial analysis in 2021. So there is no secret right answer to a situational prompt that an algorithm is checking you against. There is a clear, specific, well-reasoned answer that reads cleanly as text.

The practical takeaway is simple. Speak clearly so the transcript is clean. Name your assumption and your reasoning in words, because the words are what gets read. Do not perform for a camera you imagine is grading your delivery. Answer the scenario on its merits, the way you would explain your thinking to a colleague.

Before you answer

Situational questions are not asking for the one right move. They are asking how you think when the path is not obvious. So when the scenario is vague, resolve it out loud. Name your assumption in the first sentence, state your approach as a principle, ground it in one real example, and stop. If the interview is recorded, read the first screen for the timer and whether retakes are on before you start.

For the broader set of prompts you might face, common video interview questions covers more ground, and the companion behavioral video interview questions page handles the “tell me about a time” half. If you want the structure that carries every answer, the STAR method on a one-way video interview breaks it down line by line.