A situational question gives you a scenario and asks what you would do. "A customer is angry about a late delivery. How do you handle it?" or "Two deadlines clash and you cannot meet both. What do you do?" They are popular because they show how you think when there is no right answer on a page.
How they differ from behavioural questions
A behavioural question asks about the past: "Tell me about a time when". A situational question asks about the future: "What would you do if". With the first you tell a story. With the second you explain your reasoning. (See behavioural vs technical interviews for more.)
What the interviewer is looking for
- Judgement. Do you notice the important things and make sensible choices?
- Priorities. Do you know what matters most?
- Understanding of the job. Does your answer show you know how the work really goes?
- Honesty and ethics. Do you act with integrity when it is hard?
- Communication. Can you explain your thinking clearly?
A method: clarify, plan, act, review
- Clarify. Ask a quick question if the scenario is unclear. "Is this a regular customer?" or "How soon is the deadline?" shows careful thinking, and it is fine to say what you would want to find out first.
- Plan. State what matters most: safety, fairness, the customer, the deadline.
- Act. Describe the steps you would take, in order.
- Review. Say how you would check the outcome and what you would do to prevent it happening again.
A worked example
Question: "You discover a colleague has made an error in a report that is due to be sent to a client today. What do you do?"
"First I would check I have understood the error correctly, so I do not raise a false alarm. Then I would speak to my colleague privately and calmly, because they may know something I do not, and they should have the chance to correct it. If it is clear that it is an error and there is time, I would help fix it. If there is not time, or my colleague cannot be reached, I would tell my manager, because the client should not receive wrong information. Afterwards I would suggest a quick check step before reports are sent, so it is less likely to happen again."
Notice the structure: check, speak, act, escalate if needed, and prevent. It does not claim to know everything, and it shows respect for the colleague.
Draw on real experience where you can
Even though the question is hypothetical, you can add, "I have faced something like this when..." and give a short example. It makes your answer more credible.
Common mistakes
- Jumping to an answer without thinking. A pause is fine.
- Giving a textbook answer. Explain what you would actually do.
- Ignoring the people involved. Good answers consider the colleague, the customer and the team.
- Pretending there is no difficulty. If there is a trade-off, say so.
- Going on too long. One to two minutes is enough.
Practise with scenarios from your field
Each field has its own typical scenarios. The interview question pages list common questions for every field, with what the interviewer is looking for in each. Practise a few aloud, and then start a practice interview: the interviewer builds questions from your resume and the job description, and follows up on thin answers, which is exactly what a situational question needs.



