Situational interview questions

A situational question drops you inside a scenario that has not happened yet: a client escalates two hours before a release, what do you do? The interviewer is not checking whether you have lived through that exact moment. They are watching how you decide when the information is incomplete.

These show up most in rounds that test judgment rather than recall: hiring manager conversations, cross-functional panels, and any role where the daily work is triage. Because nothing in the prompt is real, there is no single correct answer, and trained interviewers score the reasoning path instead of the conclusion.

The two families get mixed up constantly, and the difference changes how you prepare. Behavioral questions open with tell me about a time and ask for a real event from your history. Situational questions open with what would you do and ask you to reason forward from a premise.

• Behavioral: evidence based. You are recalling facts, so preparation means building a story bank.
• Situational: judgment based. You are constructing the answer live, so preparation means rehearsing a decision structure.
• Mixed follow-ups: many interviewers ask a situational prompt, then chase it with have you actually handled something like that? Expect to switch modes mid-answer.

That distinction matters most for career changers. If you lack direct domain experience, situational questions are where you can still score well, because the prompt supplies the context you have not personally accumulated. Role-specific behavioral sets live on the question banks hub.

The prompts below recur across industries. They are grouped by what the interviewer is measuring, which is more useful than grouping them by wording.

Conflict and stakeholder pressure

• What would you do if a teammate repeatedly missed deadlines that blocked your work?
• How would you handle a manager who asked you to ship something you believed was unsafe?
• Two senior stakeholders want opposite things and both outrank you. What do you do?
• How would you respond if a colleague took credit for your work in a meeting?

Priorities and limited time

• You are handed three urgent tasks with the same deadline. How do you sequence them?
• What would you do if you realised on Thursday that a Friday deliverable would slip?
• How would you handle a request that arrives outside your role but nobody else can do it?

Mistakes and recovery

• You discover an error in work that already went to the customer. What are your first three steps?
• What would you do if you did not know the answer to a question a client asked you directly?
• How would you handle finding a mistake made by someone more senior than you?

Customers and difficult people

• A customer is angry about something that is genuinely not your fault. What do you say first?
• How would you handle a request that policy does not allow but that the customer clearly deserves?
• What would you do if a new team member was struggling and had not asked for help?

Ambiguity and new information

• You join a project with no documentation and the previous owner has left. Where do you start?
• What would you do if data mid-project contradicted the assumption the project was built on?
• How would you approach a task you have never done before with no one available to ask?
• Your manager gives you a goal but no method. What do you do in the first week?
• What would you do if you thought the team was solving the wrong problem?

Most candidates freeze on these because there is no story waiting to be retrieved. This section gives you a four-move structure that fits any prompt, whatever the industry. The moves are clarify, decide, name the tradeoff, close the loop.

• Clarify one thing. Ask a single scoping question, then stop. Two or three questions reads as stalling.
• State your first action. Be concrete about what you would do in the first hour, not the first quarter.
• Name the tradeoff out loud. This is the part that separates scores. Say what you are choosing against and why.
• Close the loop. Explain how you would know it worked and what you would change if it did not.

Consider a backend engineer interviewing for a senior role at a cloud vendor. Asked what they would do if a deploy began erroring for a small fraction of users late at night, they clarified whether rollback was still available, chose to roll back before diagnosing, said plainly that they were trading a slower root-cause investigation for a shorter blast radius, and described the alert they would add before redeploying. That answer works whether or not the incident ever happened.

The structure only becomes fast if you say it out loud several times, ideally against follow-up questions you did not write. Practicing that loop is what mock interviews are for. Deciding how much rehearsal actually transfers is covered on the practice hub.