Situational interview questions: how to answer "what would you do"

Situational interview questions describe a hypothetical work scenario and ask what you would do, such as "What would you do if a teammate kept missing deadlines?" Behavioral questions ask what you did in the past. A strong situational answer clarifies the situation, names your priorities, describes the action, says how you'd check the result, and adds a real past example if you have one.

What is a situational interview?

A situational interview is built around hypothetical scenarios. The interviewer describes a realistic problem from the job and asks how you would handle it. Some rounds are entirely situational. More often, a few hypotheticals are mixed into a behavioral or hiring manager round. The scenarios usually come from things that actually happen in the role: missed deadlines, unclear requirements, a production issue, a disagreement.

There is rarely a single right answer. The interviewer is scoring how you reason: what you ask, what you weigh, what you do first, and whether you'd check that it worked.

Situational vs behavioral interview questions

The two are easy to mix up, and the difference changes how you answer.

• Behavioral questions ask about the past: "Tell me about a time you missed a deadline." You answer with a real story.
• Situational questions ask about a hypothetical: "What would you do if you realized you were going to miss a deadline?" You answer with your reasoning and a plan.
• Behavioral questions test what you have done. Situational questions test how you think, including about things you haven't faced yet.
• Both look for the same qualities: judgment, communication, ownership and how you treat people.

A good situational answer often borrows from the behavioral kind. Once you've explained what you would do, a short real example shows you have done it before. For the past-tense side, see behavioral interview questions with answers.

Why do interviewers ask hypothetical questions?

• They can ask every candidate the same scenario and compare the answers directly.
• They work for candidates with little work history, such as new graduates.
• They cover situations specific to the role that you may not have met yet.
• They show your priorities: whether you think about users, teammates, risk and your manager, and in what order.

How do you answer situational interview questions?

A five-step structure works for almost any hypothetical. It stops you from jumping to an action before you understand the problem, and from talking for three minutes without making a decision.

1. Clarify. Ask one or two questions, or state your assumptions out loud. "Is this a customer-facing system?" "I'll assume my manager is reachable." Real situations come with context, and looking for it is part of good judgment.
2. Name your priorities. Say what matters most here and why: user impact, the safety of data, the deadline, the relationship. This is where your judgment shows.
3. Describe the action. What you'd do first, then next. Be concrete about who you would talk to and what you would say.
4. Check the result. How you'd know it worked, and what you'd do if it didn't. This step is easy to skip, and it is what separates a plan from a wish.
5. Add a past example if you have one. One or two sentences: "I did something similar last year when..." It makes the hypothetical believable. If you don't have one, leave it out rather than invent one.

Keep it to about a minute, or ninety seconds at most. Interviewers often change one detail and ask again, so a clear structure matters more than a long answer. Handling those pushes is covered in how to answer follow-up questions.

Worked example: a bug before a release

The prompt: "An hour before a scheduled release, you find a bug in your change. The product manager says a customer is waiting for this feature. What do you do?" Here is an invented example answer that follows the five steps.

First I'd want to know how bad the bug is. Does it corrupt data or affect other features, or is it a cosmetic issue inside the new feature? I'll assume it's in between: the new feature shows wrong totals in one edge case. My priority is not shipping something that gives a customer wrong numbers, because that costs more trust than a short delay. So I'd tell the product manager right away, with the facts: what's wrong, which cases it touches and how long a fix would take. If the fix is small and I can test it within the hour, I'd fix it and ask a teammate to review it. If not, I'd suggest shipping with the feature behind a flag or moving the release by a day, and let the product manager make that call with the customer. After the release I'd watch the error logs and the totals for that edge case. Something close to this happened to me last year with a pricing change, and the one-day delay was a non-event once the customer heard the reason directly.

The answer asks one clarifying question and states an assumption, names a priority with a reason, offers two concrete options, hands the business decision to the person who owns it, describes a check, and closes with one real sentence. It also doesn't pretend the engineer alone decides what the customer gets.

Common situational interview questions with model answers

These come up across many engineering roles. The short answers below are invented examples to show the shape. Say yours in your own words.

What would you do if a teammate kept missing their deadlines?

Talk to them first, privately, and ask what's going on before assuming anything. Offer help if the cause is workload or unclear scope. If it continues and affects the team, raise it with your manager, with specifics rather than complaints. A good answer avoids both going straight to the manager and quietly doing their work for them.

What would you do if you disagreed with your manager's technical decision?

Ask about their reasons, then make your case once, with evidence, ideally in writing. If the decision stands, commit to it, help it succeed and say what you'd watch for. The interviewer is checking that you can disagree without stalling the work. More on this in the disagreed with your manager answer.

What would you do if two stakeholders gave you conflicting urgent requests?

Don't pick the louder one. Clarify the impact and deadline of each, then get the two people, or your manager, into one conversation to agree on the order. Tell both what happens to their request once the order is set.

What would you do if you realized you'd miss a deadline?

Say so as soon as you know, not on the due date. Bring options: what can ship on time, what needs more days, what you would cut. Then keep people updated as things change.

What would you do if you made a mistake nobody noticed?

Fix it and tell the people affected. If it reached production or users, say what happened, what you did and what prevents it next time. This question checks honesty, so don't treat it as a close call.

What would you do if the requirements were unclear?

Write down your understanding and the open questions, and take them to whoever owns the requirement. If you have to start before the answers arrive, build the parts that are clear first and keep the uncertain parts easy to change.

What would you do in your first week on a codebase with no documentation?

Run it locally, read the tests and the most-changed files, and ask a teammate for a thirty-minute walkthrough. Write down what you learn as you go, and turn those notes into the first piece of documentation.

What is a situational judgement test?

A situational judgement test is the written form of the same idea. You read short work scenarios and choose, or rank, the most and least effective responses from a list. Some employers use these tests online early in the process, often for graduate and high-volume hiring, alongside or before a first interview.

There is no trick to them. They tend to reward responses that are realistic, honest, respectful of others and focused on solving the problem, over responses that escalate everything or ignore it. Read what the employer says about its values before you start, take each scenario at face value and answer the way you would actually act. Stay consistent, because similar scenarios often appear more than once. If the test is proctored or run under set conditions, follow its rules exactly.

Common mistakes

• Jumping to an action before you understand the situation. One clarifying question shows judgment.
• Giving the textbook answer. "I'd communicate openly with all stakeholders" says nothing. Say who, what and when.
• Escalating everything to your manager, or never escalating anything. Good answers show when each is right.
• Playing the hero. Fixing everything alone overnight is not the judgment interviewers are looking for.
• Refusing the hypothetical. "That would never happen on my team" ends the conversation. Answer it, then mention your experience.
• Never deciding. Listing every option without choosing one reads as avoidance.

A practice loop for hypotheticals

1. Collect scenarios. Take the seven questions above and add three from the job description: the systems, customers or team setup the role mentions.
2. Answer on a ninety-second timer. Out loud. Run the five steps: clarify, priorities, action, check, past example.
3. Change one detail. Answer again with a twist: your manager is on leave, the customer is your largest, the bug is in someone else's code. Notice what changes in your priorities.
4. Check the check. Did you say how you'd know it worked? Add it if not.
5. Pair it with a story. For each scenario, note one real experience you could mention in a sentence. If you have none, that's fine. Leave it out.

Practice situational questions on the Verbal surface

Situational questions are conversational, so they belong to the Verbal surface in HIDEA AI. Verbal is one of four separate surfaces, alongside Live coding, System design and Project, and it works from your resume and the job description, which helps when the scenarios come from the role.

In a mock interview the app asks the questions out loud, listens to your answers and scores the round. Mocks are verbal-only, 20 or 30 minutes, on Pro and Pro+, and the Report tab scores the saved session afterwards. Fifteen session minutes a day is free, with no credit card, on the desktop app for macOS and Windows.

You speak or type every answer. Before using any tool in a live round, check what some employers publish. The FAQ and the interview copilot overview explain how the app works.

Where to go next

• The past-tense version: behavioral interview questions with answers.
• When the interviewer changes the scenario: how to answer follow-up questions.
• Leadership scenarios: leadership interview questions.
• Online tests early in the process: online coding assessment prep.