Situational Inter­view Questions: Practicing Your Reasoning

Situational interview questions ask how you would handle an imagined scenario, for example "What would you do if..." or "How would you handle...". Answer the hypothetical you are actually asked. Relevant true experience can inform your reasoning, but do not pass it off as the outcome of the imagined scenario. This guide shows how to state your assumptions, work within your authority and policy, and practice explaining your thinking without inventing results.

The practice suggestions here are optional, so adapt them to the question and to any limit or instruction the interviewer gives. Honesty, confidentiality and permission are not optional. All scenarios are fictional, and the outlines are examples of reasoning, not answers to copy.

Tell the question types apart

A question that asks "What would you do if..." is hypothetical, so you reason about it. A question that asks "Tell me about a time..." asks about a real event, so you describe what happened. Our guide to STAR method examples covers real events. Do not answer a hypothetical question with an invented story, and do not describe a hypothetical as if it had happened. If you mention a real experience to support your reasoning, say that it is a real experience and do not present it as what would happen in the scenario.

A reasoning outline

You do not need every step for every question.

1. Check any real ambiguity. Ask a question only if something important is unclear, for example whose responsibility the task is. If the scenario is clear, you can begin. Our clarification guide has wording you can adapt.
2. State your assumptions. For example: "I'm assuming this is my responsibility and that I can't tell yet which task matters most."
3. Say what matters here. For example the people affected, accuracy, fairness, the limits of your role and the employer's policy.
4. Describe what you would do within your authority. Say who you would involve and what you would check.
5. Mention an option you considered and why you would not choose it, if that helps explain your thinking.
6. Say how you would check afterwards, and what might change your answer.

Stay within authority and policy

Do not promise discounts, deadlines or exceptions that you could not authorise, and do not state what a customer or colleague is entitled to unless you know it. Say what you would offer if your role and the employer's policy allow it, and say that you would check the policy if you do not know it. Name who would decide if the decision is not yours.

This guide does not teach responses to emergencies or to clinical, legal, safety-critical or similar scenarios, and it does not give procedures for them. If a question is about one of those areas, answer only from your own training and authority, say plainly what you do not know or are not trained or authorised to do, and do not suggest that following a procedure or telling someone is all that is needed. Do not invent a procedure. If a scenario touches a core competence of the role that you lack, say so instead of hiding it behind a general statement about process.

Fictional practice scenarios

Each outline below is an example of reasoning, not a result and not a script to copy. None of them describes something that happened.

Fictional scenario, a colleague's mistake: "A colleague tells you they have sent a report with a mistake in it."

• Assumptions: "I'm assuming the report has already gone out and the mistake could matter to the reader."
• What matters: accuracy, the reader, who owns the report and the colleague's ability to correct it.
• Approach: "I would ask the colleague who owns the report and how corrections are normally handled. If it isn't something I'm able to correct, I would make sure the right person knows. I wouldn't correct it quietly without telling anyone, because the owner may need to know."
• Afterwards: "I would check the status later, and if it was still unresolved I would tell the right person."

Fictional scenario, competing tasks: "You are given three tasks that are all due at the end of the day."

• Assumptions: "I'm assuming they are all mine, and I can't tell which matters most."
• Check: "That is worth asking, because the answer changes my order of work."
• Approach: "I would ask my manager or the people who need each task which matters most, explain what I can finish and when, and agree an order. I wouldn't promise a deadline I didn't think I could meet."
• Afterwards: "I would tell people if something changed."

Fictional scenario, a request for an exception to an ordinary process: "A customer asks for an exception to an ordinary process, and you are not able to approve exceptions."

• Assumptions: "I'm assuming I can't approve exceptions, and that I don't know the full policy."
• What matters: being honest with the customer, staying within my authority and treating them fairly.
• Approach: "I would listen, check what I'm authorised to offer, explain what I can and can't do and offer any option I'm authorised to give. If it needs a decision I can't make, I would pass it to the person who can decide. I wouldn't promise an outcome I can't authorise, and I wouldn't guess at what the customer is entitled to."
• Afterwards: "I would make sure the customer knew what would happen next and who was deciding."

Rehearse your reasoning

1. Read a scenario. Write down your assumptions and what matters, without writing a full answer.
2. Answer aloud. You can record yourself.
3. Listen back. Did I state my assumptions? Did I stay within my authority and policy? Did I promise anything I could not authorise, or state an entitlement I do not know? Did I describe a result as if it had happened?
4. Choose one change, and answer again.

Optional experiment: try a shorter and a longer version of the same answer, and notice which lets you reason clearly. This guide sets no required length, but in a real interview follow any limit the interviewer sets. If you practice with another person, agree with them before recording. Leave out confidential information.

If you do not know the policy or the context

Say what you would want to find out and who you would ask. Do not invent a policy. Our guide on what to do when you don't know an answer covers this.

In a real interview, do not use any tool to generate answers unless the organiser has explicitly allowed it, and do not record the conversation unless the interviewer has agreed.

This guide is published by Muqabala. You can visit our interview practice page for your next practice session. Use any method that suits you, and check how any tool handles your data first. Do not paste confidential employer, client or personal information into a practice tool.