Situational Interview Questions: Complete Guide With Sample Answers (2026)
Situational interview questions ask you to describe what you would do in a hypothetical future scenario — not what you have done in the past. They are one of the most common interview formats used by employers worldwide, appearing in interviews at Google, Amazon, McKinsey, the NHS, government departments, financial services firms, and thousands of mid-market companies.
Unlike behavioural questions ("Tell me about a time you..."), situational questions present you with a scenario ("What would you do if...?") and assess your judgment, values, and decision-making process. Both are valuable, but they test different things. Knowing how to approach each type — and how to handle a situational question when you lack direct experience — is a critical interview skill.
Situational vs. Behavioural Questions: The Key Difference
| Behavioural | Situational | |
|---|---|---|
| Focus | Past behaviour | Future hypothetical response |
| Format | "Tell me about a time..." | "What would you do if..." |
| Evidence | Specific past example | Reasoning and judgment |
| Best for | Assessing what you have done | Assessing how you think |
Both are rooted in the same underlying research: structured questions predict job performance better than unstructured conversation. SHRM reports that structured interview formats — including both behavioural and situational variants — have predictive validity coefficients of 0.50–0.55, significantly higher than the 0.38 for unstructured interviews.
Many interviewers use both types in the same interview: behavioural questions to evaluate your track record, and situational questions to assess your judgment in scenarios you may not have faced directly. Understanding both types is essential.
The STAR-L Framework for Situational Answers
For behavioural questions, STAR (Situation, Task, Action, Result) is the standard framework. For situational questions, a modified version works better: STAR-L or the IDEAL framework.
The recommended approach for situational questions:
- Identify the situation clearly — Restate the key elements to show you understand the scenario.
- Diagnose the core challenge — What is actually at stake? Who is affected? What values or priorities are in tension?
- Describe your approach — Walk through what you would do, step by step, and why.
- Reference a relevant experience — If you have faced something similar, briefly anchor your answer in reality: "This is similar to a situation I encountered when..."
- State the outcome you would seek — What does success look like?
This approach demonstrates judgment, process thinking, and real-world grounding — the three things assessors are looking for in situational answers.
How to Answer When You Lack Direct Experience
The most common anxiety with situational questions is "I have never been in that situation." Here is how to handle it:
First, do not say "I have never experienced this." Every candidate has the same answer — it is not differentiating and it signals avoidance.
Second, apply your best judgment to the scenario as described. Situational questions are designed for hypotheticals — the interviewer knows you may not have faced this exact situation.
Third, anchor in transferable experience where possible: "While I have not managed a situation of exactly that scale, I did handle something similar when [brief example]..."
Fourth, be explicit about your reasoning: "I would start by... because... I would then... because..." Demonstrating that you think clearly under uncertainty is often as valuable as having a direct example.
Practice this approach with ClavePrep's AI mock interview tool to build confidence answering hypothetical questions before the real interview.
25+ Situational Questions With Model Answers
Management and Leadership
Q1: If you became the manager of a team and quickly noticed that two team members had a significant, unresolved conflict, what would you do?
I would start by meeting with each person separately before bringing them together. My goal in the individual conversations would be to understand their perspective on the situation, what specifically is driving the tension, and what they need to feel it is resolved — not to assign blame. I would listen far more than I would speak.
After the individual meetings, I would assess whether the conflict is task-based (a disagreement about work approach, priorities, or decisions) or interpersonal (a relationship breakdown). Task-based conflicts are often easier to resolve through clarification of expectations or responsibilities. Interpersonal conflicts may need structured mediation.
I would then bring both parties together for a facilitated conversation — setting ground rules upfront (no interrupting, focus on impact not intent) — and guiding them toward a specific agreement about how they will work together going forward. I would document the agreed behaviours and follow up in two weeks to check whether the agreement was holding.
What I would not do is ignore it, take sides without hearing both perspectives, or assume I know what the conflict is actually about before speaking to both parties. In a previous role, I resolved a similar conflict between two senior engineers by discovering that what appeared to be a personality clash was actually a misalignment about whose responsibility a particular workstream was. Clarifying ownership resolved the tension within a week.
Q2: You are managing a project and it becomes clear that you will miss the deadline. The client has not been informed. What do you do?
The first thing I would do is assess exactly how significant the delay is and what is driving it. Is this a two-day slip or a two-week slip? Is the root cause recoverable with additional resource, or is it a structural problem?
Simultaneously — and before I have the root cause fully understood — I would inform the client. Waiting until I have all the answers before communicating is a mistake. Clients are far more forgiving of delays that are communicated early than of delays they discover at the deadline.
My communication to the client would cover three things: what is happening, what we are doing about it, and when I will next update them. I would not speculate about final timelines until I had more data.
I would then run an accelerated internal review to identify what could be done to recover some of the time: are there tasks that could be parallelised? Could scope be adjusted to deliver the most critical elements on the original date? Could resources be added?
I would return to the client with a revised plan that showed what we were doing to minimise the impact and a new, reliable commitment — not an optimistic hope.
Q3: If you were asked to manage a project with a very limited budget and tight deadline, how would you approach it?
I would start with ruthless scoping. The most common cause of budget and deadline failures is scope creep — taking on more than the resources support. I would convene a project scoping session in the first 48 hours to identify must-have deliverables versus nice-to-have, and document that agreement in writing.
I would then build a critical path — mapping which tasks are sequential dependencies versus which can run in parallel — to identify where the real timeline risk sits. I would build explicit buffer into the critical path (not just overall) because that is where slippage actually originates.
On budget, I would identify the biggest cost drivers early and look for alternatives: open-source tools, internal resources, phased delivery. I would track spend weekly against forecast, not monthly, so I could act on overruns before they compound.
I would also establish a change control process from the start: any request that adds scope or cost goes through a documented review before it is accepted. Without this, small additions accumulate into budget and timeline failures.
Finally, I would communicate proactively throughout. Stakeholders who feel informed are more flexible when issues arise. Stakeholders who feel surprised are not.
Q4: A team member tells you they are struggling with their workload but you cannot reduce it. What do you do?
I would take the conversation seriously and start by understanding the specifics. "Struggling with workload" can mean many things: too many tasks in aggregate, unclear priorities, tasks that are taking longer than expected because of skill gaps, or work that is simply inefficient.
I would sit with them and map out their current work — everything on their plate, with estimated time for each item. Often this exercise itself reveals the problem: either there genuinely is too much for one person, or there are tasks they are over-investing time in relative to their importance.
If genuine overload is confirmed and I cannot reduce it, I would look at every other dimension: Can I help prioritise so the most critical work gets done first? Can I remove administrative burden or low-value tasks that are within my control? Can I pair them with a colleague for the tasks where they are least efficient? Can I make a case to my own manager for temporary resource support?
I would also be honest with the team member: if we are in a constrained period, I would tell them that directly, acknowledge the difficulty, and give them a realistic view of when it would ease. Pretending everything is fine when someone is struggling is not helpful leadership.
Q5: What would you do if your manager asked you to do something you believed was unethical?
I would not simply comply, but I also would not immediately escalate or refuse without attempting to address it directly.
My first step would be a private conversation with my manager. I would describe specifically what my concern was — what aspect of the instruction felt ethically problematic and why — and ask for their reasoning. There may be context I am missing: a legal consideration, a prior agreement with another party, or an interpretation of the instruction that is different from mine.
If my manager's explanation did not resolve my concern, I would be direct: I would tell them that I had a genuine ethical concern and that I was not comfortable proceeding without more discussion or escalation. I would offer to document the concern in writing.
If the manager still expected me to proceed and I remained convinced it was wrong, I would use the appropriate internal channels — HR, a compliance officer, or an ethics hotline if one existed — rather than either complying silently or simply resigning.
The scenario where the ethical concern is severe and immediate (something illegal, something that would harm a person directly) would require faster escalation. I would always prioritise the right outcome over personal comfort in a conflict with a manager.
What I would not do is comply and then complain to colleagues — that damages trust without resolving anything.
Customer Service and Client Situations
Q6: A customer is extremely angry and is being verbally aggressive. What do you do?
I would stay calm and not match their emotional register. Responding to aggression with defensiveness or counter-aggression never helps and often escalates the situation.
I would let them speak without interrupting, which signals that I am listening. Most people who are angry want to feel heard before they want a solution. Once they have said what they needed to say, I would acknowledge the experience: "I can hear how frustrated you are, and I want to understand exactly what has happened so I can help."
I would then shift to specific, solution-focused questions: "Can you tell me what was ordered and when?" I want to move from the emotional to the practical — not because the emotion does not matter, but because practical progress is what actually resolves the situation.
If at any point the customer became verbally abusive — name-calling, threats — I would calmly set a boundary: "I want to help you resolve this, and I can do that best if we keep the conversation focused on the issue. Can we do that?"
I would resolve what I could immediately and be specific about what would happen next if I needed to escalate. Vague promises like "someone will look into it" are worse than "I will raise this with my manager by 3 pm today and they will contact you by 5 pm."
Q7: You notice a long-standing customer is using significantly less of your product than they did six months ago. What do you do?
This is an early warning sign of churn risk, and I would treat it as a priority.
My first step would be to understand the usage data more deeply. Is the drop across the board or in specific features? Did it correlate with any event — a personnel change on their side, a product update on ours, a competitor announcement?
I would then reach out to the customer proactively — not to pitch or retain, but to genuinely understand. I would frame the outreach as a check-in: "We noticed your team's usage has shifted in the last few months and wanted to make sure everything was working well for you." This opens a conversation without being heavy-handed.
In the conversation, I would listen far more than I would talk. If there was a problem with the product, I would want to understand it specifically. If they had shifted to a competitor for certain use cases, I would want to know which ones and why. If there was a business change on their side (team restructure, budget cut), I would want to understand that context.
Based on what I learned, I would develop a specific action plan — not a generic "here is what our product can do" pitch, but a response to their actual situation. In some cases, the right answer is helping them use the product more effectively. In others, it may be negotiating a different contract structure that fits their current reality.
The worst outcome is to notice the usage drop and do nothing.
Q8: A key client asks you to do something that falls outside the scope of your agreement. What do you do?
I would not say yes immediately, and I would not say no either.
My first step would be to understand exactly what they need and why — not just what they are asking for. "Can you build us a custom report?" might be a symptom of a deeper need (they lack visibility into a particular metric) that I might be able to address through a different means that is within scope.
If the request genuinely falls outside our agreement, I would be transparent about that: "This is not included in our current scope, but I want to help you get what you need." I would then explore three options with them: whether it could be added to the existing agreement for additional cost, whether it could be included in the next contract renewal, or whether I could suggest an alternative within the current scope.
What I would avoid is either quietly doing out-of-scope work (which creates precedent and cost without compensation) or rigidly refusing without exploring solutions (which damages the relationship).
Senior stakeholders appreciate directness and flexibility in combination — "this is outside scope but here is how we can handle it" is almost always better received than either a silent yes or an abrupt no.
Ethical Dilemmas
Q9: You find out that a colleague has been falsifying their expense reports. What do you do?
This is a situation where I would not ignore or dismiss what I had seen — that would make me complicit in the ongoing behaviour.
Before doing anything, I would make sure my own information was accurate. Did I genuinely see evidence of falsification, or could there be an alternative explanation? I would want to be confident I was not acting on a misunderstanding.
If I was confident about what I had seen, I would first consider having a direct private conversation with the colleague — particularly if we had a good working relationship. "I noticed something in your expense submission and wanted to talk to you about it before doing anything else." This gives them an opportunity to explain or correct the situation. In some cases, there may be a genuine misunderstanding or administrative error.
If the conversation confirmed the behaviour was intentional, or if having a direct conversation felt inappropriate given the seniority of the colleague or the severity of the issue, I would report it through the appropriate internal channel — whether that is HR, a compliance team, or a confidential ethics line.
I would document what I had seen and when, and I would keep the matter confidential to the appropriate parties. Gossiping about a colleague's potential misconduct before a proper process has occurred causes harm to everyone involved.
What I would not do is look the other way. Integrity in the workplace requires that individuals act on what they know is wrong, even when it is uncomfortable.
Q10: Two team members come to you separately with opposing versions of the same conflict. Both seem credible. What do you do?
The first thing I would do is avoid forming a judgment until I have more than two data points. When two credible people tell me opposing things, the truth is almost always somewhere between the two accounts — not because either is lying, but because human memory and perception are genuinely selective.
I would thank each person for coming to me and make clear that I was not going to share the content of each conversation with the other party. Confidentiality is important for people to speak openly.
I would then look for any objective evidence that could corroborate either account: emails, meeting notes, shared documents, or other people who were present.
If the conflict was about specific behaviour (one person says the other was dismissive, the other denies it), I would focus the resolution on what both parties need going forward — not on adjudicating who was right historically. "Let us agree on how you will work together going forward" is more productive than "let us establish who was wrong."
If the conflict involved a serious allegation — bullying, harassment, discrimination — I would involve HR immediately rather than attempting to resolve it myself. These situations require formal processes with documentation.
Crisis and Resource Constraints
Q11: You are managing a project and a key team member unexpectedly resigns with two weeks notice. What do you do?
I would act on two tracks simultaneously: managing the immediate knowledge transfer and addressing the capacity gap.
On knowledge transfer, I would meet with the departing team member in the first 24 hours to document everything that exists only in their head: in-progress work, key contacts, system access, and any commitments they have made to others. Two weeks is enough time to capture a lot if used intentionally.
On capacity, I would immediately assess the impact: which deliverables are at risk, by how much, and what are the options? Could other team members absorb the work? Could timelines be extended? Could some deliverables be descoped temporarily? Could we bring in a contractor for specific tasks?
I would communicate the situation to the project sponsor or client promptly — not in alarm, but with a clear assessment and a plan for mitigation. Surprises are worse than bad news delivered with a plan.
I would also resist the temptation to pile the departing team member's entire workload onto one remaining person. Overloading individuals is how teams lose a second person shortly after the first.
Q12: You are given a significantly larger team and budget than expected, but also a correspondingly larger project. How do you set up for success?
More resources are not automatically a benefit — larger teams and budgets bring coordination complexity, accountability confusion, and scope inflation risks.
My first 30 days would be focused on structure: establishing clear roles and responsibilities, creating communication norms that scale (regular standups, decision logs, documented ownership), and setting up the budget tracking infrastructure before spending begins.
I would spend significant time in the first two weeks with each team member individually to understand their strengths, experience, and aspirations. Team performance over a large project is heavily shaped by whether people are in roles that suit them. Getting this right at the start saves significant problems later.
I would also set clear scope boundaries early. Large projects attract scope additions. I would establish a formal change control process from day one so that every addition goes through a deliberate cost-benefit assessment rather than accumulating unchallenged.
Finally, I would identify the first meaningful milestone — something deliverable within 60–90 days — and focus the team on delivering it. Early wins build momentum and reveal which teams and individuals are reliable before the high-stakes deliverables arrive.
Q13: Your company's biggest client is threatening to leave unless you give them pricing they cannot get under any standard agreement. What do you do?
I would not agree to anything unilaterally. Pricing exceptions set precedents and must involve the right stakeholders.
My first step would be to understand exactly what is driving the threat: is this a genuine pricing sensitivity, a negotiating tactic, or a symptom of a deeper dissatisfaction with the product or service? The right response depends entirely on which of these it is.
If it is a legitimate pricing concern, I would escalate internally with a clear business case: the value of the account, the risk of losing it, the competitive context, and a proposal for what we could offer that would retain them without setting a damaging precedent for the rest of the client base.
If it is primarily a negotiating tactic, I would engage with what they actually need rather than just the stated demand. Often there are ways to add value — extended payment terms, additional services, a multi-year agreement — that meet the client's underlying need without cutting headline price.
What I would not do is make promises I could not keep or agree to exceptions I was not authorised to make. That erodes trust both with the client (who will eventually discover the limits) and internally.
Team Conflict
Q14: What would you do if you disagreed with a decision made by your manager?
I would first make sure I fully understood the decision and the reasoning behind it. Sometimes what appears to be a disagreement dissolves once I understand the context or constraints the manager was operating under.
If after understanding the reasoning I still disagreed, I would request a private conversation and share my view clearly and directly — but professionally. I would focus on the business rationale for my concern, not on my personal preference. "I am concerned that this approach may result in [specific consequence]. Can we discuss that risk?" is more constructive than "I do not think this is the right call."
I would listen to the response. My manager may have information I do not have. They may also hear my concern and adjust.
If the decision remained unchanged and I still disagreed, I would accept it and execute it professionally. I would raise my objection through legitimate means; I would not undermine the decision by complaining to colleagues or executing it in a deliberately half-hearted way.
If the decision felt genuinely wrong — ethically problematic or likely to cause serious harm — that would warrant further escalation through appropriate channels. But most professional disagreements do not reach that threshold.
Q15: A colleague consistently misses deadlines, which is affecting your work. What would you do?
I would address it directly with them rather than waiting and hoping it would improve or complaining to others.
I would choose a private moment — not in the middle of a deadline crisis — and be specific: "I have noticed that the work I need from you to move forward has been arriving late on the last three projects. It is affecting my ability to deliver on time. I wanted to talk directly with you about it."
My goal in the conversation would be to understand what was getting in the way. Was the colleague overloaded? Did they not realise the downstream impact of their delays? Were there dependencies on their side that were creating the problem? The solution depends on the cause.
If the conversation produced a clear agreement — a new handover process, a change in timelines, a way of flagging risks earlier — I would document that and give it a genuine chance to work.
If the problem continued after the direct conversation, I would escalate to our shared manager with the specific data: dates, what was needed, when it was delivered. I would frame it as a project risk that needed resolution, not a personal complaint.
Sector-Specific Examples
Q16 (Healthcare/NHS): A patient is dissatisfied with the length of their waiting time and becomes confrontational in your clinic. What do you do?
I would acknowledge the frustration genuinely — not with a scripted apology, but with specific recognition: "I understand that waiting this long is stressful, especially when you are unwell." I would not be defensive about the wait time.
I would then find out whether there was anything I could do immediately to improve their situation: could they be moved to a more comfortable area, given an estimated wait time, or updated on their position? Giving someone specific information and an estimated time restores some sense of control.
If they were still confrontational, I would stay calm, lower my own voice slightly (which often prompts the other person to do the same), and remain focused on what I could help with. I would not argue about wait times or make commitments I could not keep.
If the behaviour became unsafe — if there was a risk of physical aggression — I would involve a colleague or security and, if necessary, follow the organisation's lone worker or violence prevention protocols.
After the interaction, I would document it and share with the team so we could learn from it: was the wait time avoidable? Is there a communication failure that contributed to patient frustration?
Q17 (Finance): You discover an error in a financial report that has already been sent to a major stakeholder. What do you do?
I would not delay. As soon as I confirmed the error was material — not a minor formatting issue — I would inform my manager immediately, before taking any other action.
Together, we would assess the nature and materiality of the error: what figure was wrong, by how much, and what decisions might have been made or are about to be made based on the incorrect data.
We would then correct the report and issue a revised version to the stakeholder with a clear cover note explaining what changed and why. Transparency here is essential — attempting to quietly update a report without acknowledgment is worse than the original error if it is discovered later.
Depending on the stakeholder, either I or my manager would make a direct call to explain what had happened and what steps we were taking to prevent recurrence.
Internally, I would conduct a root cause analysis: was this a human error in the spreadsheet, a data quality issue upstream, or a process gap that allowed the report to be released without a secondary check? I would implement whatever control addressed the root cause.
Q18 (Technology/Software): You are halfway through a product sprint and the requirements change significantly. What do you do?
The first thing I would do is call an immediate sprint review with the product owner, development lead, and any affected stakeholders. Mid-sprint requirement changes need to be documented and assessed — not absorbed quietly.
I would quantify the impact on the current sprint: how much of the existing work is still relevant? What can be carried forward and what needs to be discarded? Is the sprint goal still achievable in any form?
If the changes are significant enough to render the current sprint unachievable, I would recommend ending the sprint early — a sprint abort — rather than delivering a partial output that does not reflect the new requirements. Delivering something "nearly done" on the old requirements and "partially started" on the new ones satisfies no one.
I would then work with the product owner to reprioritise the backlog based on the new requirements and kick off a new, clean sprint. I would ensure that the new requirements are documented and agreed before development restarts — mid-sprint ambiguity tends to compound.
Finally, I would run a brief retrospective on what caused the mid-sprint change. If it was avoidable — insufficient discovery, unclear stakeholder alignment — I would raise that as a process improvement for future planning.
Q19 (Consulting/Professional Services): A junior team member has made a significant error in client-facing work. What do you do?
I would handle this in two parallel tracks: the client situation and the team member situation.
On the client side, I would take ownership of the error with the client immediately — not as the junior team member's error but as our firm's output. I would be specific about what happened, what the corrected position is, and what we were doing to ensure it did not recur. Blaming a junior team member to a client is unprofessional and damages the firm's credibility.
On the team member side, I would have a private conversation that was developmental rather than punitive — particularly if this was a first significant error. I would understand what happened: was it a knowledge gap, a process failure, a time pressure issue, or a misunderstanding of the requirement? The response should match the cause.
If the error was due to a process gap (e.g., the work was not peer-reviewed), I would fix the process. If it was due to a knowledge gap, I would address that through coaching or training. If it was a pattern of carelessness, I would be more direct about expectations.
What I would not do is respond to the error with a reaction that makes the team member too afraid to raise future errors. In professional services, early detection of errors is critical. That only happens in a culture where people feel safe to flag problems.
Q20 (Retail/Consumer-Facing): A customer wants to return a product outside the return policy window. How do you handle it?
I would approach the conversation with genuine service intent, not a compliance mentality.
I would listen to the customer's situation without interrupting, and show that I understood their expectation. I would then explain our return policy clearly but not defensively — the policy exists for good reasons, and I would communicate it that way.
I would then assess whether there was discretion available within the system. Many retail environments allow managers to make exceptions in circumstances where the customer has a legitimate reason, the product is in resalable condition, or the customer is high-value and long-standing. I would explore those options genuinely.
If an exception was not available, I would look for an alternative: could I offer store credit? An exchange? A partial refund? A referral to the manufacturer's warranty?
The goal in every customer interaction is to find the best outcome available, not to enforce a minimum. A customer who leaves feeling that we tried to help, even if we could not give them exactly what they asked for, is far more likely to return than one who leaves feeling dismissed.
Q21 (Management): You have a high performer who has been behaving dismissively toward junior colleagues. How do you address it?
I would address it directly and soon — not after a further incident, not after "giving it more time."
I would have a private conversation with the individual and be specific: not "you have been unkind" but "in Tuesday's team meeting, when Sarah asked a clarifying question, you interrupted and said that was not relevant. I want to talk about that." Specificity prevents defensiveness about generalisations.
I would also be honest about why I was raising it: "Your technical work is excellent, and I want you to progress here. But leadership in this organisation means building others up, not just delivering your own results. The way you are interacting with junior colleagues is getting in the way of that, and I think it is important you know it."
I would listen to their response. Some high performers are not aware of the impact of their behaviour; others know and have rationalised it. The response would shape how I proceeded.
I would set a clear expectation going forward, give it a genuine window to change, and follow up with specific examples of improved or continued behaviour. If the behaviour persisted after a clear conversation and a fair period, I would treat it as a formal performance issue.
I would also make a point of spending time with the junior colleagues who had been affected — not to discuss the high performer, but to ensure they felt supported.
How to Prepare for Situational Questions
Build a mental framework for each question type. Before your interview, think through your decision-making approach for common scenarios: ethical dilemmas, resource constraints, conflict, client problems. You do not need a memorised answer, but you should have a clear mental framework.
Practise out loud. Situational answers that sound coherent in your head often stall or ramble when spoken. Use ClavePrep's AI mock interview tool to practise delivering structured answers under realistic interview conditions.
Know the company's values. Situational questions are often designed to assess whether your instincts align with the company's stated values. If a company emphasises "customer obsession," a situational question about a difficult client is partly assessing whether your natural instinct is to serve or to enforce policy.
Ask a clarifying question if needed. It is entirely professional to ask a brief clarifying question about a situational scenario — "Just to clarify, am I the direct manager of this person or a peer?" This shows rigorous thinking, not uncertainty.
Anchor in real experience where possible. Even for hypothetical questions, "I have faced something similar — here is what I learned that I would apply..." strengthens your answer significantly.
Ready to practise? ClavePrep offers unlimited mock interviews with AI feedback on both your content and delivery. Use it to build confidence before the real interview.