Interview Preparation — 2026 Guide
Situational Interview Questions: Complete Guide & 20 Worked Answers
Everything you need to master "what would you do if..." interview questions — the STAR-S framework, all five question categories, and 20 fully worked example answers for graduates and professionals.
20Worked examples
5Question categories
STAR-SAnswer framework
2026Fully updated
Section 01
Situational vs Behavioural Questions — Key Differences
Before you can answer situational interview questions well, you need to understand precisely what makes them different from behavioural questions — and why interviewers choose one over the other. Many candidates conflate the two formats, which leads to answers that miss the mark entirely.
Situational interview questions are hypothetical. They present a future or imagined scenario and ask what you would do. The classic opener is "What would you do if..." or "Imagine you are in a situation where...". The interviewer is testing your values, judgment, and decision-making process — not your CV. Because there is no "right" experience required, situational questions are particularly common in graduate schemes, public sector roles, and structured interviews where fairness and consistency matter.
Behavioural interview questions, by contrast, look backwards. They ask you to draw on real, lived experience with openers like "Tell me about a time when..." or "Give me an example of...". The underlying premise — popularised by industrial psychologists in the 1980s — is that past behaviour is the single best predictor of future behaviour. Behavioural interviews are covered in depth in our most common interview questions guide.
Competency-based interviews are a third format that often blends both. They are built around a defined set of competencies (e.g., "teamwork", "problem-solving", "communication") and use a mix of situational and behavioural questions to assess each one. Our competency-based interview guide covers this format in detail.
| Feature | Situational Questions | Behavioural Questions | Competency-Based |
|---|---|---|---|
| Time orientation | Future / hypothetical | Past / real experience | Both — blended per competency |
| Typical opener | "What would you do if..." | "Tell me about a time when..." | Either, structured by competency |
| What is being tested | Values, judgment, decision-making | Track record, proven skills | Evidence against defined criteria |
| Best answer framework | STAR-S (hypothetical) | STAR (real example) | STAR or STAR-S per question type |
| Experience required | None — hypothetical | Relevant work/study experience | Varies by competency and seniority |
| Common in | Graduate schemes, public sector, structured panels | Most professional roles, senior hires | Grad schemes, civil service, big employers |
| Psychometric validity | Moderate — tests reasoning | High — past behaviour predicts future | High when properly structured |
Many interviews use both formats in the same session
A structured panel interview for a graduate scheme might include three situational questions ("What would you do if a team member missed a deadline?") and three behavioural questions ("Tell me about a time you worked under pressure"). Preparing only for one format leaves you vulnerable. See our full interview preparation guide for a combined preparation strategy.
One important nuance: interviewers sometimes follow up a situational question with a behavioural one — "That's what you'd do in theory. Can you give me an example from your experience where you did something similar?" This is deliberate. Strong candidates should have real examples ready to support their hypothetical answers wherever possible. For more on strengths-based approaches that complement both formats, see our strengths-based interview guide.
Section 02
The STAR-S Framework — How to Structure Situational Answers
The standard STAR interview technique (Situation, Task, Action, Result) was designed for behavioural questions drawing on real past experience. For situational hypothetical questions, a direct application of STAR falls short — because there is no real Situation or Result to describe. The STAR-S adaptation solves this by adding a Self-reflection component and reframing each element for hypothetical reasoning.
S
Situation
Acknowledge and set the hypothetical context. Show you understand the scenario fully before jumping to solutions.
T
Task
Define your responsibility and role within the scenario. What is expected of you specifically?
A
Action
Describe the specific steps you would take — in order, with reasoning. This is the core of your answer.
R
Result
Explain the outcome you would expect from your actions. Be realistic and outcome-focused.
S
Self-reflection
What would you take away or learn from the experience? This demonstrates self-awareness and growth mindset.
How to Apply STAR-S in Practice
The most common mistake candidates make with situational questions is jumping straight to the Action — describing what they'd do without first establishing context or their role. This makes answers feel generic and disconnected from the specific scenario. The STAR-S structure forces you to slow down, understand the scenario, and respond thoughtfully.
Your Action element should be the longest part of your answer — typically three to five concrete steps, explained in a logical sequence. Avoid vague commitments like "I would communicate effectively" or "I would be proactive." Instead, describe the exact conversation you'd have, the email you'd send, the person you'd escalate to, or the data you'd gather first. Specificity signals competence. Vagueness signals that you haven't thought it through.
The Self-reflection component (the second "S") is often omitted by candidates who haven't been coached on the STAR-S variant — yet it is one of the most powerful differentiators. Interviewers are looking for self-awareness: candidates who can recognise what a situation taught them, what they'd do differently next time, or what skill it would reinforce. This is particularly important in roles that value continuous learning, such as consulting, teaching, healthcare, and financial services.
Treat hypothetical scenarios as real — then reflect as if they happened
The most effective STAR-S answers don't sound tentative. Instead of "I might think about..." say "I would first...". Use confident, present-tense action language for the Action step, then shift to reflective language for Self-reflection: "This experience would reinforce for me that..." Speaking as if the scenario is real conveys conviction and makes your answer far more compelling to interviewers.
Timing Your Answer
A strong situational interview answer should run between 90 seconds and 3 minutes when spoken aloud. Shorter answers often skip the Action detail that makes answers compelling. Longer answers risk losing the interviewer's attention and can signal an inability to be concise under pressure. Practise your answers aloud with a timer — most candidates significantly underestimate how long their answers run when nervous.
Section 03
Category 1: Teamwork & Conflict Situations
Teamwork and conflict situational questions assess your ability to collaborate effectively, navigate disagreement constructively, and maintain professional relationships under pressure. They are nearly universal across graduate schemes and professional roles. For a related set of past-tense examples, see our guides on teamwork interview questions and conflict interview questions.
Q1: What would you do if a team member consistently missed deadlines, putting the project at risk?
I would begin by having a private, one-to-one conversation with the team member rather than raising the issue in front of the group, since public confrontation rarely resolves underlying problems and tends to damage trust. In that conversation, I'd approach it with genuine curiosity rather than accusation — asking whether they were facing any blockers, whether the workload was manageable, or whether there was something outside work affecting their capacity. Often, missed deadlines stem from unclear priorities, technical blockers, or personal circumstances rather than disengagement. Based on what I learned, I'd work with them to identify specific solutions — whether that was redistributing tasks, adjusting interim milestones, or flagging resource constraints to our manager. If the issue continued after we'd agreed on a plan, I'd escalate to the project lead with the evidence I'd gathered and the steps I'd already taken, framing it as a project risk rather than a personal complaint. Looking back, I think this situation would reinforce for me that proactive communication — checking in on progress before deadlines rather than after — is the most effective way to prevent this pattern from developing in the first place.
Q2: What would you do if two members of your team had a serious disagreement that was affecting the whole team's morale?
My first step would be to speak with each person separately to understand their perspective without the other present. People in conflict rarely feel fully heard in joint settings, and individual conversations give me a clearer picture of the root cause — whether it's a professional dispute about approach, a personality clash, or a genuine misunderstanding that has escalated. Once I understood both perspectives, I would look for areas of common ground or shared goals that both parties actually agree on, since most professional disputes coexist alongside significant common purpose. I'd then bring the two individuals together in a neutral, structured conversation — not to adjudicate who is right, but to redirect energy toward the project's shared objectives and agree on working norms going forward. Throughout this process, I'd be transparent with the broader team that I was aware of the tension and actively working to resolve it, without sharing private details, because uncertainty and silence tend to amplify the morale impact. If the conflict persisted and was genuinely affecting delivery, I would involve my manager or HR rather than trying to manage it alone — knowing when to escalate is part of good judgment. Reflecting on this, I think the experience would strengthen my facilitation skills and remind me that managing team dynamics is as important as managing tasks.
Q3: What would you do if you disagreed with a decision made by your manager?
I would first take time to ensure I fully understood the reasoning behind the decision before voicing any disagreement — sometimes what looks like a poor decision makes sense once you understand the constraints or context the manager is working within. If after reflection I still had a genuine concern, I would raise it privately and professionally, framing my view as an alternative perspective rather than a challenge to authority. I'd come prepared with specific reasoning and, where possible, evidence or data to support my position, since a well-reasoned concern is far more persuasive than a general objection. I'd listen carefully to my manager's response and be genuinely open to being persuaded — intellectual honesty means acknowledging when someone else's reasoning is stronger than mine. If the decision stood and I still had reservations, I would commit fully to implementing it while perhaps noting my concerns on record for future review. The one exception would be if the decision involved an ethical breach or compliance issue — in that case, I'd escalate through the appropriate channels. This scenario would teach me the importance of picking battles wisely and influencing through evidence rather than emotion.
Q4: What would you do if a colleague took credit for your work in front of senior leadership?
My immediate instinct would be to avoid reacting emotionally in the moment — publicly correcting a colleague in front of senior leadership can create awkwardness that reflects poorly on everyone, including me. After the meeting, I would speak with the colleague directly and calmly, describing what I observed and asking if it was intentional or an oversight; in many cases it is the latter and can be resolved quickly with a clarifying email to the relevant stakeholders. If the colleague confirmed credit appropriately in a follow-up message — copying in the relevant people — I'd consider the matter resolved. However, if this was a pattern of behaviour or if the colleague dismissed my concern, I would speak with my manager privately and present the factual record of my contributions — emails, document version histories, meeting notes — without dramatising the situation. I'd also reflect on whether my own visibility habits needed adjusting: sharing progress updates proactively, documenting contributions clearly, and volunteering to present my own work in future. This experience would highlight the importance of maintaining a clear contribution record and building relationships directly with senior stakeholders so that my work speaks for itself over time.
Section 04
Category 2: Problem-Solving & Analytical Situations
Problem-solving situational questions assess how you approach ambiguous or complex challenges — whether you gather data before acting, structure your thinking logically, and make sound decisions under uncertainty. These questions are particularly common in consulting, finance, operations, and technology roles. They often link closely to the analytical skills assessed in assessment centre exercises.
Q5: What would you do if you were given a complex project with unclear requirements and a tight deadline?
Before doing anything else, I would invest time upfront to clarify the requirements, because starting work on unclear specifications is the single fastest way to waste effort and miss the real objective. I'd schedule a brief meeting with the key stakeholders to ask three specific questions: what does a successful outcome look like, what are the non-negotiables versus the nice-to-haves, and who are the decision-makers whose sign-off I need along the way. With that foundation, I'd break the project into its core components and identify the critical path — the sequence of tasks where any delay would directly impact the final deadline. I'd then prioritise ruthlessly, focusing effort on the elements with the highest impact on the outcome rather than trying to do everything perfectly. I'd set clear internal milestones and share a brief progress update with stakeholders at each one, so that any misalignment is caught early rather than at the final deadline. This approach reduces rework significantly and keeps everyone aligned. Looking back, I'd take from this experience a reinforced conviction that a few hours of upfront clarification almost always saves far more time than it costs.
Q6: What would you do if you discovered a significant error in a report that had already been distributed to senior stakeholders?
The first thing I would do is verify the error myself — checking the source data, methodology, and any relevant calculations to confirm it's genuine and understand its magnitude. Once I was certain, I would inform my manager immediately, even if it was uncomfortable, because discovering the problem later and not having reported it promptly would be significantly worse than the error itself. Together, we'd agree on the correction and the communication plan. I would then prepare a corrected version of the report along with a brief, factual note to stakeholders acknowledging the error, explaining what it was, what the correct figures are, and confirming any impact on decisions that may have been made using the incorrect data. I'd avoid being defensive or over-explaining — a clean, professional correction with a focus on accuracy is more reassuring to stakeholders than an elaborate explanation. I'd also immediately trace back through my process to identify where the error entered: whether it was a data source issue, a formula error, or a review gap — and put a specific safeguard in place to prevent recurrence. This situation would strengthen my commitment to building systematic review steps into reporting workflows rather than relying solely on individual vigilance.
Q7: What would you do if you were presented with conflicting data from two reliable sources when making an important decision?
Conflicting data from reliable sources is actually a signal worth investigating, not simply a problem to resolve by picking one dataset. My first step would be to understand why the two sources diverge: whether they are measuring different things, using different time periods or definitions, drawing on different sample populations, or applying different methodologies. Often what looks like a contradiction at the headline level resolves once you look at what each source is actually capturing. I would document the discrepancy clearly and flag it to the relevant stakeholders before making the decision, because proceeding as if one source is definitively correct when there's genuine ambiguity could introduce unacknowledged risk. Where possible, I would seek a third reference point — an additional source, an expert view, or primary data we could gather directly — to help triangulate. If time pressure meant I had to proceed with incomplete certainty, I'd state my assumptions explicitly, make the decision transparently, and build in a review point to revisit the conclusion once additional data was available. This situation would reinforce for me that acknowledging uncertainty openly is a sign of analytical rigour, not weakness.
Q8: What would you do if you were asked to complete a task you had never done before, with no guidance available?
I would start by breaking the task down into its component parts and identifying what I do and don't already know — since most genuinely new tasks have significant overlap with things I've encountered before. For the gaps in my knowledge, I'd research methodically: looking at internal documentation, similar completed projects or templates, professional resources, and relevant online content. I would not spend excessive time researching in the abstract — I'd aim to gather enough to make a credible start, then learn iteratively as I progressed. I'd set a short internal checkpoint — perhaps after the first third of the task — to review my approach and ensure I was on the right track before investing further effort. If midway through I encountered something where getting it wrong would have a significant consequence, I'd actively seek out a colleague or professional contact who had relevant experience, even briefly, rather than proceeding with insufficient confidence. When the task was complete, I'd document what I'd learned in a way that would help me or a colleague approach the same task more efficiently next time. This experience would remind me that resourcefulness and structured self-teaching are as important as pre-existing knowledge.
Section 05
Category 3: Leadership & Initiative Situations
Leadership situational questions don't only apply to management roles — they are common for any position where you're expected to take ownership, influence others, or step up in ambiguous situations. They assess whether you default to action or passivity, and how you motivate and direct others without necessarily having formal authority. Our leadership interview questions guide covers the behavioural equivalents of these questions in depth.
Avoid the "I would just take over" trap
A common mistake in leadership situational answers is describing an approach that ignores other people's expertise or autonomy — essentially saying you'd override the team and do everything yourself. Interviewers flag this as a red flag for poor people skills. Strong leadership answers demonstrate influence, enabling others, and building consensus — not unilateral action unless the situation genuinely demands it.
Q9: What would you do if you were asked to lead a project but had no formal authority over the team members?
Leading without formal authority is one of the most common and important leadership challenges in modern organisations, so this is a scenario I think about seriously. My first action would be to invest in the relationships before trying to direct any work — taking time to understand each team member's expertise, what they're working on, and what they care about in this project. Influence in the absence of authority comes from credibility and trust, not position. Once I had established rapport, I would bring the team together to co-create a shared understanding of the project goals and success criteria — people commit more deeply to plans they helped design. I'd be clear about my role as coordinator and facilitator rather than director, and I'd rely on persuasion, transparent communication, and creating genuine accountability rather than top-down instructions. If I encountered resistance or a team member who didn't prioritise the project's work, I would first try to understand their constraints, and if necessary work with the project sponsor to clarify expectations and resolve competing priorities at a higher level. Throughout the project, I'd make sure individuals' contributions were visible and recognised, because recognition is one of the most powerful motivators available to an informal leader. This scenario would strengthen my understanding of influence-based leadership and the importance of building coalitions.
Q10: What would you do if you noticed a process in your team that was significantly inefficient, but no one else seemed concerned?
I would begin by doing my own analysis to quantify the inefficiency — how much time or resource it was consuming, what the downstream impact was, and whether the apparent lack of concern from others reflected genuine acceptance or simply a lack of visibility into the problem's scale. Data makes a much stronger case than instinct. Once I had a clear picture, I'd discuss my findings informally with one or two trusted colleagues to sense-check my thinking and understand whether there were historical reasons for the current approach that I wasn't aware of — sometimes inefficient-looking processes exist for good reasons that aren't immediately obvious to someone new. If I remained confident that improvement was possible, I would bring my analysis and a proposed solution to my manager — framing it not as a criticism of how things have always been done, but as an opportunity to improve the team's output. I'd volunteer to lead the improvement initiative rather than simply flagging the problem, since solutions without accountability rarely get implemented. I'd propose a small pilot before suggesting organisation-wide change, because a tested improvement is much easier to scale than a theoretical one. Looking back, I'd take from this experience that taking initiative to improve processes — even when no one asked you to — is one of the clearest ways to demonstrate ownership and add value beyond your job description.
Q11: What would you do if a project you were leading was significantly behind schedule with the deadline approaching?
My first action would be an honest assessment of exactly where the project stood: which deliverables were complete, which were in progress, which hadn't started, and what the specific blockers were. A clear picture of reality is the prerequisite for any recovery plan. I'd then identify the critical path — the minimum set of deliverables needed to meet the core objective — and distinguish between what was truly essential and what was scope that could be deferred or cut without compromising the outcome. I would communicate transparently with the key stakeholder immediately, not at the last moment. Delivering bad news early gives people options; delivering it late removes them. In that conversation, I'd come with a revised plan, not just a problem — explaining what we would deliver, what we might need to defer, and whether additional resource or a revised scope would allow us to hit the original deadline. I'd work with the team intensively over the remaining time, removing obstacles, re-allocating tasks to match availability, and running daily brief check-ins to maintain momentum. After the deadline, regardless of outcome, I'd conduct a retrospective to understand the root cause of the delay and ensure the same pattern didn't recur. This situation would deepen my commitment to proactive scheduling and early risk identification at the start of every project.
Q12: What would you do if a junior team member was struggling with their confidence and underperforming as a result?
I would prioritise a private, supportive conversation before any formal intervention — because in most cases, confidence issues respond much better to encouragement and practical support than to performance processes. In that conversation, I'd focus on listening first: asking open questions about how they were finding the role, where they felt most and least comfortable, and whether there was anything specific they found difficult. Often people know exactly what's undermining their confidence; they just need to feel safe enough to say it. Based on what I heard, I'd work with them to identify two or three concrete areas to focus on, rather than trying to address everything at once. I'd look for opportunities to assign tasks where they could succeed visibly — building a track record of small wins is one of the most reliable confidence-builders available. I'd also be more intentional about providing specific, timely positive feedback when they did things well, rather than only corrective feedback when things went wrong. I'd check in regularly — not to monitor, but to show genuine investment in their development. If the underperformance had a performance-management dimension that needed formal intervention, I'd involve HR appropriately, but I'd ensure the support was genuine rather than purely procedural. This situation would reinforce for me that strong leaders invest as much energy in developing people's potential as in delivering their own outputs.
Section 06
Category 4: Customer & Stakeholder Situations
Customer and stakeholder situational questions assess how you manage expectations, handle complaints, balance competing interests, and maintain relationships under pressure. They are essential for any client-facing, account management, public-facing, or project management role. These questions reveal your commercial awareness, empathy, and judgment around difficult conversations.
Q13: What would you do if an important client was angry about a service failure that wasn't your fault?
Regardless of who caused the service failure, the client's experience of frustration is real and deserves to be acknowledged fully before anything else. I would open the conversation by listening without interrupting — letting the client articulate exactly what went wrong from their perspective and how it has affected them. Feeling genuinely heard is often the first step in de-escalation. I would then acknowledge the impact clearly and directly, using language like "I completely understand why this is unacceptable" rather than deflecting with explanations about whose fault it was. Clients rarely want a detailed account of internal processes; they want to know that you take their experience seriously and that it will be resolved. Once the client felt heard, I'd move quickly to solutions — what I could do right now, what the timeline for resolution looked like, and who was responsible for each action. I'd give a specific commitment about next steps and follow through on it exactly as promised, since reliability in a crisis is what determines whether a client relationship survives one. Internally, I would also ensure that the root cause was investigated and that the relevant people understood the client impact, so that accountability was clear even if that accountability didn't rest with me. This situation would reinforce that in client relationships, ownership matters more than blame.
Q14: What would you do if two senior stakeholders gave you conflicting instructions on the same project?
My first step would be to make sure I had understood both sets of instructions accurately, since many apparent conflicts dissolve once you clarify the specifics of what each stakeholder is asking for and why. If the conflict was genuine, I would bring both stakeholders together — or facilitate a written exchange — rather than trying to resolve it through a series of separate bilateral conversations, which tends to amplify ambiguity rather than reduce it. In that conversation, I'd present the conflict clearly and objectively, explaining the trade-off between the two directions and the implications of each, and ask the two stakeholders to reach a joint decision. I'd resist the temptation to choose between them unilaterally, because doing so risks losing the confidence of one party and creating a dynamic where I'm seen as taking sides. If the stakeholders were unable to align and the conflict was escalating, I would ask my direct manager to help clarify the priority, since that is exactly the kind of ambiguity that a management layer exists to resolve. Throughout this process, I'd document the different instructions I'd received and the steps I'd taken to resolve the conflict, so there was a clear record of my due diligence. This experience would teach me the value of mapping stakeholders and their priorities explicitly at the start of any project to prevent this kind of conflict from emerging.
Q15: What would you do if a client asked you to do something that was outside your scope of authority?
My first instinct would be to acknowledge the request warmly rather than declining immediately — because how you say no matters as much as the fact of saying no. I'd begin by confirming that I understood exactly what the client needed and why, since sometimes the underlying need can be met in a way that is within my authority even if the specific request isn't. If the request was genuinely outside my scope, I'd be transparent about that — explaining clearly that this particular request required approval or action from someone at a different level, and taking ownership of making that connection happen rather than leaving the client to navigate it themselves. I'd introduce the client to the right person, brief that person on the context, and follow up to confirm the request had been handled. I would not simply redirect the client and disengage, because client relationships depend on the experience of being supported end-to-end. At no point would I attempt to act outside my authority to avoid the awkwardness of saying no — the risk of doing so without the relevant knowledge, authority, or resources is far greater than the short-term inconvenience of the correct process. This scenario would reinforce my understanding that knowing your own boundaries — and navigating them professionally — is a mark of good judgment rather than a limitation.
Q16: What would you do if you realised mid-project that a client's expectations were significantly misaligned with what you could actually deliver?
The moment I identified the misalignment, I would address it — because the longer an expectation gap remains unacknowledged, the harder it becomes to manage and the greater the eventual disappointment. I'd first internally validate my assessment: reviewing the original brief, any emails or meeting notes that captured commitments made, and the current project status to be precise about the nature and scale of the gap. Then I would initiate a proactive conversation with the client, being transparent and direct — framing it not as bad news but as important information that I wanted to surface early so we could solve it together. I'd come to that conversation with options rather than just a problem: what we could deliver in full, what might be achievable with additional time or resource, and what scope could be adjusted or phased across a later stage. Presenting options gives the client agency and demonstrates that I've thought through solutions, not just the problem. I'd be honest about what wasn't feasible without overpromising again, and I'd confirm whatever revised plan we agreed on in writing immediately after the conversation. Looking back, this situation would reinforce the importance of structured discovery and expectation-setting at the very start of every engagement — specifically checking what success looks like from the client's perspective before any work begins.
Section 07
Category 5: Pressure & Deadline Situations
Pressure and deadline situational questions test how you perform under stress, prioritise when everything feels urgent, and maintain quality without burning out or cutting corners. These questions are common across virtually all professional roles, but are particularly weighted in finance, law, consulting, healthcare, and any project-driven environment. For related preparation, see our guide on most common interview questions.
The best answers show a system, not just willpower
Interviewers are not simply looking for "I work hard under pressure." They want to see that you have a structured approach — a method for prioritising, a way of communicating with stakeholders when timelines shift, and a process for maintaining quality when speed is demanded. Answers that rely solely on effort without structure suggest a reactive rather than systematic thinker.
Q17: What would you do if you had three urgent tasks due at the same time and couldn't complete all of them to the expected standard?
The first thing I would do is establish the true priority of each task — not based on who asked most urgently or most recently, but on the actual consequences of missing or delaying each one. I'd ask: which of these directly affects a client, a deadline that cannot move, or a decision someone else is depending on right now? Once I had a clear ranking, I'd communicate proactively with the stakeholders for the lower-priority tasks — not to explain that I was too busy, but to give them an honest, specific update on when they could expect delivery and whether there was anything I could do to partially meet their need in the interim. Most reasonable stakeholders respond well to early, honest communication and poorly to silence followed by a miss. I'd then focus fully on the highest-priority task and deliver it to the standard required before switching attention. For the other tasks, I'd assess whether any elements could be simplified in scope without losing their core value, or whether a colleague could contribute so that quality was maintained across all three. After the pressure had passed, I'd reflect on how the situation arose — whether it reflected a planning gap, unclear prioritisation from above, or an unexpected spike in demand — and discuss with my manager whether there were structural changes that could prevent it recurring. This scenario would strengthen my conviction that managing expectations proactively is as important as managing the work itself.
Q18: What would you do if you were given a task at the last minute that required staying late, when you already had important personal commitments?
I would first understand the full picture of the task: specifically how urgent it was, whether the deadline was genuinely fixed, what the consequences of a short delay would be, and whether there was anyone else who could share the work. In many cases, "urgent" and "genuinely cannot wait" are not the same thing, and a clear-headed conversation can identify flexibility that wasn't immediately visible. If the task was genuinely critical and needed to be done that evening, I would be willing to adjust my plans and communicate with the relevant personal parties as soon as possible — giving them as much notice as I could rather than leaving it to the last moment. However, I would also be transparent with my manager that I had a prior commitment and ask whether we could explore options: partial completion that night with the remainder first thing in the morning, task-sharing with a colleague, or a brief extension if the business case allowed. I would not martyr myself silently, nor would I use personal commitments as an inflexible shield in a genuine business emergency — professional judgment means finding the right balance depending on context. If this kind of last-minute pressure became a recurring pattern rather than an exception, I'd raise it constructively with my manager as a workload planning conversation. This situation would remind me that communicating boundaries professionally and early is essential for long-term sustainable performance.
Q19: What would you do if you made a mistake under pressure that had an impact on a key outcome?
My first priority would be to acknowledge the mistake to myself clearly and without defensiveness — the instinct to minimise or rationalise errors under pressure is understandable but counterproductive. Once I understood what had happened and its impact, I would report it promptly to my manager or the relevant stakeholder, because early disclosure gives more options for mitigation and demonstrates the kind of integrity that builds long-term trust. I would present the facts plainly, take clear ownership without deflecting blame onto time pressure or circumstances, and come with a proposed recovery plan wherever possible. Acting quickly to contain the impact is more valuable than spending time on a perfectly worded explanation. After the immediate situation was managed, I would conduct a rigorous post-mortem for myself: what decision or action specifically led to the mistake, what early warning signs were there that I missed or ignored, and what specific process change would prevent the same error recurring. I'd be specific — "I will add a cross-check step before submitting this report type" rather than "I'll be more careful." Finally, I'd work to rebuild confidence with the affected stakeholder through consistent, reliable delivery over the following weeks. Reflecting on this, I believe that how someone handles a mistake often reveals more about their character than how they handle success.
Q20: What would you do if you were working on a high-stakes project and felt overwhelmed to the point where it was affecting your performance?
I would treat the recognition that I was overwhelmed as early and valuable information rather than a personal failure — because catching the signal early allows for intervention before performance actually deteriorates. My first step would be to step back briefly from the immediate workload and assess the situation objectively: was I overwhelmed because of a genuine volume problem, a skills gap, an unclear objective, insufficient resource, or something more personal? The diagnosis shapes the solution. If it was a volume or resource problem, I'd have a direct conversation with my manager — presenting the current workload clearly, explaining the pressure I was under, and asking for help prioritising or resourcing. Most good managers would rather know about a capacity issue early than manage a missed deadline or a quality problem retrospectively. I'd also look at whether there was scope to delegate, defer, or simplify anything without compromising essential quality. On a personal level, I'd be deliberate about maintaining the basics — adequate sleep, physical activity, and protected recovery time — because sustained pressure without recovery is self-defeating. I'd also have a trusted colleague or mentor I could speak with privately about how I was managing, since sometimes an external perspective is exactly what reframes the situation. This scenario would reinforce for me that self-awareness and asking for help at the right moment are marks of professional maturity, not weakness.
Section 08
Frequently Asked Questions
What is the difference between situational and behavioural interview questions?+
Situational interview questions are hypothetical — they ask "what would you do if..." and test your judgment and decision-making in future scenarios. Behavioural questions are past-focused — they ask "tell me about a time when..." and assess your track record using real examples. Employers use both formats, but situational questions are especially common for graduate roles or when candidates have limited work experience. The key difference is that behavioural questions require genuine past examples, while situational questions test how you think and what values guide your decisions. Both formats can be answered using structured frameworks — STAR-S for situational, STAR for behavioural. See our STAR technique guide for the foundational framework.
How do you answer "what would you do if" interview questions?+
Use the STAR-S framework: describe the hypothetical Situation, clarify your Task or responsibility, explain the Actions you would take step by step, describe the expected Result, and add a Self-reflection on what you'd learn. Be specific and concrete — treat the hypothetical as if it's real rather than giving vague generalities. The most effective answers use confident, present-tense action language ("I would first..." rather than "I might consider..."), describe three to five specific steps in your Action section, and close with a genuine reflection on what the experience would reinforce or teach. Avoid generic statements like "I would communicate well" — describe exactly how, with whom, and in what form.
What is the STAR-S method for situational questions?+
STAR-S is an adaptation of the STAR interview technique specifically for hypothetical situational questions. S = Situation (the hypothetical context you're imagining), T = Task (your role and responsibility in that scenario), A = Action (the specific steps you would take), R = Result (the outcome you'd expect), S = Self-reflection (what you'd take away from the experience). The final S differentiates it from standard STAR and demonstrates self-awareness — one of the most valued qualities in structured interview assessment. Many interviewers specifically probe for self-reflection in situational answers, so including it proactively sets strong candidates apart.
Do employers prefer situational or behavioural interview questions?+
Most employers use both. Behavioural questions are generally considered more predictive of performance because past behaviour is the best indicator of future behaviour — this has been consistently supported by industrial-organisational psychology research. However, situational questions are preferred when candidates are early-career or career-changers with limited directly relevant experience, and when employers need to assess values and ethical judgment rather than technical skill. Many structured interviews blend both formats within the same session, sometimes following a situational question with "and can you give me a real example where you did something similar?" Preparing only for one format leaves you vulnerable. Our competency-based interview guide explains how the formats are typically combined in practice.
How do I prepare for situational interview questions?+
Start by researching the role's core competencies — these are usually listed in the job description or the employer's published values. For each competency, construct one strong STAR-S answer to a relevant hypothetical scenario and practise it aloud until it flows naturally. Study the job description closely for clues about the real situations the role involves — the best situational answers are grounded in the genuine context of the job. Consider your personal values and principles as the foundation of your answers, since situational questions are fundamentally character assessments. For each scenario, think through what you'd do in the worst-case version of the situation, not just the easy version. Finally, practise with a timer — aim for 90 seconds to 3 minutes per answer. Our full interview preparation guide covers the complete preparation process across all formats.
Ready to Master Your Interview?
Practice with our free assessment tools and deepen your technique with our full STAR interview guide — the foundation for every situational and behavioural answer.