Situational Interview Questions

Situational versus behavioral

A behavioral question asks for evidence. Tell me about a time you missed a deadline wants a thing that happened, with dates and people in it. A situational question asks for judgment instead. What would you do if you realised on Friday that Monday's deadline was gone puts you in a hypothetical and waits to see how you reason.

Candidates treat the second kind as the easy one because nothing can be checked. That is exactly backwards. A story from your life has a floor under it, because it happened and the details hold together on their own. A hypothetical has no floor. Every answer you give invites another condition, and interviewers who like this format will keep adding conditions until something gives.

This is also why the STAR format does not transfer cleanly. There is no Situation to describe and no Result to report, because the whole thing is in the future tense. What survives is the reasoning: what you would find out first, what you would decide, and what you would do when the decision turned out badly.

The questions, with answers

Thirty of the ones that actually get asked, with the shape of a good answer. Keep each to about ninety seconds out loud.

• What would you do if you were assigned a task with no clear instructions? Say what you would try first on your own, then name the point at which you would stop and ask. The bad answer is either ask immediately or never ask.
• What would you do if you disagreed with your manager's approach? Say it once, privately, with your reasoning. Then execute their version properly. Say that out loud.
• What would you do if you missed a deadline and nobody had noticed yet? Tell them the day you know. The question is testing whether you wait.
• What would you do if a colleague took credit for your work? Go to the colleague before you go to anyone else. Describe what you would say.
• What would you do if you were given two urgent tasks by two different managers? Ask them to sequence it between themselves, having first told them what each would cost.
• How would you handle a team member who is not pulling their weight? Find out why before you decide it is a performance problem.
• What would you do if you made a mistake nobody else had spotted? Report it within the hour. Say who you would tell first.
• What would you do if a customer asked for something you could not deliver? Say no clearly, then say what you can do. Name the thing you would never do, which is imply a maybe.
• What would you do if your project's budget was cut in half? Say what you would stop doing, by name, rather than promising to be efficient.
• How would you onboard yourself if your manager left in your first week? Name the three people you would ask for time and what you would ask each one.
• What would you do if you were asked to do something you thought was unethical? Ask the question that clarifies it first. Then escalate, and say to whom.
• What would you do if a client complained about a colleague? Take the complaint seriously and do not adjudicate it in front of the client.
• What would you do if you realised a project was going to fail? Say when you would raise it and what options you would bring with you.
• How would you deal with a coworker who constantly interrupts you in meetings? Deal with it outside the meeting, once, directly.
• What would you do if you inherited a process you thought was wrong? Run it as designed for one cycle, then propose a change with evidence from that cycle.
• What would you do if a teammate asked you to cover a mistake? Decline, and offer to help them report it.
• What would you do if you were the only person who disagreed with a decision? Say your reasoning once and ask what you are missing.
• How would you handle a heavy workload with no extra resource? Name what drops. Every answer without a drop in it is a dodge.
• What would you do if a senior stakeholder ignored your emails? Change channel and shorten the ask. Say what your third attempt would look like.
• What would you do if you found an error in work that had already shipped? Assess blast radius, tell the owner, then fix. In that order.
• How would you handle a direct report who missed targets three quarters running? Say what you would have documented by now and what conversation is overdue.
• What would you do if two of your team members refused to work together? Find out what each of them wants, separately, before proposing anything.
• What would you do if a project scope kept expanding? Say when you would stop absorbing it and what you would ask for instead.
• How would you respond to negative feedback you thought was unfair? Ask for the specific example. Then decide.
• What would you do if you were asked to lead a team of people more experienced than you? Say what you would ask them and what you would decide anyway.
• What would you do if you had to deliver bad news to a client? Early, directly, with a recommendation attached.
• How would you handle a request that would breach policy for a good reason? Name who the policy protects and check with them.
• What would you do if your top performer resigned? Ask why, honestly, and expect the real answer to arrive in the second conversation.
• What would you do if you did not know the answer in front of a customer? Say so and give a time by which you will come back.
• What would you do if you joined a team with no documentation? Write the page you wish had existed, as you learn, and say who you would have check it.

Situational interview questions for managers

Managers get a harder version of the same format, because the hypotheticals involve other people's careers. Expect underperformance, conflict between reports, and resourcing.

The move that separates a manager's answer is naming what you would have already done before the situation arose. Asked about a report who has missed targets for three quarters, a weak answer describes a supportive conversation. A strong answer points out that three quarters of missed targets means the documentation should already exist and the difficult conversation is nine months late.

Situational questions for customer-facing roles

For support, sales and service roles the hypotheticals are about the gap between what a customer wants and what you can give them. The questions sound like: an angry customer demands a refund outside policy, a client asks you to commit to a date you cannot promise, a caller has been transferred four times already.

Answer these by separating the emotion from the request. You can almost always meet the first and often cannot meet the second, and the strongest answers say so in plain language rather than promising to do everything possible. If you have a real example, use it: our page on working under pressure walks through one that gets cross-examined.

Where situational answers break

Here is the mechanism. You give a reasonable hypothetical answer, and the interviewer says: so you would talk to them directly. What if you had already tried that twice, and they had agreed both times, and nothing changed.

Now the answer you prepared is gone, because it was the first move and you are three moves in. This is what hypothetical questions are for. There is no story to retreat into and no set of facts that fixes the position, so what the interviewer is watching is whether you can keep reasoning when your first answer has been removed.

The candidates who handle this well do one thing consistently: they say what they would find out next, rather than what they would do next. Escalating is a decision. Asking the person what changed between agreeing and not doing it is a way of getting information, and it survives another round of conditions in a way that a decision does not.

The other thing that breaks these answers is confidence with no hedge in it. Describing exactly what you would do, in a situation you have never faced, with no acknowledgement that you would want more information, reads as somebody who has not done the job.

Can you use STAR here

Partly, and with modification. There is no Situation to recount and no Result to report, so two of the four letters have nothing to attach to.

What transfers is the Action and the discipline behind it. Say what you would do, in order, with the reason for the order. If you have a genuine past example that resembles the hypothetical, use it and label it clearly as something that happened rather than something you would do. That converts a hypothetical into evidence, which is a strictly stronger position.

For the full format and where it collapses under follow-ups, see the STAR method.