30 Situational Interview Questions (With Best Answers)

"What would you do if..."

Situational interview questions ask how you'd handle hypothetical scenarios. Unlike behavioral questions (which ask about past experiences), situational questions test your judgment, problem-solving ability, and decision-making process in real time.

These questions are popular because they level the playing field — even candidates without years of experience can demonstrate good thinking.

Situational vs. Behavioral: What's the Difference?

| | Behavioral | Situational | |---|---|---| | Format | "Tell me about a time when..." | "What would you do if..." | | Focus | Past experience | Future judgment | | What it tests | Proven track record | Thinking process | | Best for | Experienced candidates | All candidates |

Many interviewers use both types. The preparation is different: behavioral requires polished stories, while situational requires a clear framework for thinking through problems.

How to Answer Situational Questions

Use the STAR-P framework (an adaptation of STAR for hypothetical scenarios):

Situation: Acknowledge the scenario and any nuances ("If this happened, the first thing I'd consider is...")
Think: Share your reasoning process ("I'd want to understand X before acting...")
Action: Describe what you'd specifically do
Result: State the expected outcome
Principle: Name the underlying principle guiding your decision

The key difference from behavioral answers: show your thinking, not just your conclusion. Interviewers want to see how you reason through problems.

Workplace Conflict Questions

1. "What would you do if a coworker took credit for your work?"

"I'd start by assuming it was unintentional — in my experience, most credit issues come from miscommunication, not malice. I'd have a direct, private conversation: 'Hey, I noticed the presentation attributed the analysis to your work. I want to make sure we're both clear on contributions going forward.' If it continued after that conversation, I'd make my contributions more visible proactively — sending updates, documenting decisions — and involve my manager if the pattern persisted. I'd rather address it directly than let resentment build."

2. "What would you do if you disagreed with your manager's decision?"

"I'd speak up — respectfully, but clearly. I'd frame it as 'here's what I'm seeing and why I think we should consider an alternative,' backed by data if possible. If my manager heard me out and still went a different direction, I'd commit to executing their plan fully. Disagreeing and committing is an important skill. The only exception would be if I believed the decision was unethical or would cause serious harm — in that case, I'd escalate."

3. "What would you do if two teammates were in conflict and it was affecting the project?"

"I'd talk to each person individually first to understand their perspective — separately, so they can be candid. Often conflicts come from misaligned expectations or miscommunication, not personal animosity. Once I understood both sides, I'd bring them together and focus the conversation on the shared goal: 'We both want this project to succeed. What do we each need to make that happen?' If I couldn't resolve it, I'd involve our manager before it got worse."

4. "What would you do if you noticed a teammate was struggling but hadn't asked for help?"

"I'd approach them casually — maybe over coffee or a DM — and ask how things are going. Something like 'I noticed [specific observation], and I wanted to check in.' I wouldn't frame it as 'you seem to be struggling' because that can feel condescending. If they opened up, I'd offer specific help rather than vague 'let me know if you need anything.' If they insisted everything was fine but I still saw issues, I might mention it to our manager as a general observation."

Decision-Making Questions

5. "What would you do if you had two urgent tasks and could only complete one?"

"I'd quickly assess three things: impact (which one affects more people or has higher stakes), deadline (is one truly immovable while the other has flexibility), and whether either can be partially delegated. Then I'd communicate proactively — tell the stakeholder of the deprioritized task that it'll be delayed, explain why, and give a realistic new timeline. The worst thing would be to try both and deliver neither well."

6. "What would you do if you realized midway through a project that the approach was wrong?"

"I'd raise it immediately rather than hoping it works out. I'd document what I've found — why the current approach isn't working, what the alternatives are, and what the cost of switching is — and bring it to my team or manager. The earlier you flag a wrong direction, the cheaper it is to fix. Staying silent because you're afraid of looking bad always makes it worse."

7. "What would you do if a client or stakeholder asked for something you knew was a bad idea?"

"I'd push back constructively. I'd acknowledge their goal — 'I understand you want X' — and then explain my concern: 'My worry is that this approach could lead to Y.' I'd offer an alternative that achieves their underlying goal in a better way. If they still insisted after understanding the trade-offs, I'd document the decision and my recommendation, then execute. Sometimes stakeholders have context I don't."

8. "What would you do if you were assigned a project outside your expertise?"

"I'd be upfront about the gap and proactive about closing it. I'd say 'I haven't done this before, but here's my plan to ramp up quickly' — then I'd identify who on the team has relevant expertise, do focused research, and set shorter check-in intervals at the start to make sure I'm on track. Some of my best growth has come from projects where I started out uncomfortable."

Pressure and Crisis Questions

9. "What would you do if you discovered a critical bug in production right before a major launch?"

"First, assess severity: Is it a data loss risk? A security issue? A cosmetic problem? If it's critical, I'd immediately flag it to the team and stakeholders — no heroics, no trying to fix it silently. Then I'd work with the team to decide: can we fix it quickly, or do we need to delay the launch? I'd rather delay a launch by a day than launch with a known critical issue. Either way, I'd communicate the situation, the plan, and the timeline to everyone affected."

10. "What would you do if you were leading a project and a key team member quit unexpectedly?"

"First, triage: what was that person responsible for, and what's at risk? I'd redistribute their critical work immediately — either absorbing some myself or asking the team to cover specific areas. Then I'd reassess the timeline and communicate any impact to stakeholders honestly. I wouldn't pretend everything is fine if it means burning out the remaining team. In parallel, I'd work with my manager to either get a replacement or adjust scope."

11. "What would you do if your manager asked you to do something unethical?"

"I'd push back directly. I'd explain my concern clearly: 'I'm not comfortable with this because [specific reason].' If my manager dismissed my concern, I'd escalate — to their manager, to HR, or to whatever channel the company has for these situations. This isn't something I'd let slide to avoid conflict. My reputation and integrity are more important than any single job."

12. "What would you do if you were given an impossible deadline?"

"I'd be honest immediately rather than agreeing and then missing it. I'd say 'I want to deliver this, but with the current scope and resources, the realistic timeline is [X]. Here are our options: we can cut scope to [reduced version], add resources, or adjust the deadline.' Giving people options is better than saying 'it can't be done.' And if there's truly no flexibility, I'd document the risks and do my best while keeping stakeholders updated on progress."

Leadership and Initiative Questions

13. "What would you do on your first day in this role?"

"I'd focus on listening and learning, not changing things. I'd meet with my direct teammates and manager to understand current priorities, pain points, and the team's working norms. I'd ask what's working well and what's not. I'd review documentation and recent projects to understand the codebase or product. I wouldn't try to prove myself by making changes in week one — I'd earn context first, then earn trust, then drive change."

14. "What would you do if you saw a process that was clearly inefficient but nobody else seemed to care?"

"I'd first make sure I understand why it exists — sometimes processes that look inefficient from the outside exist for reasons that aren't obvious (compliance, historical incidents, etc.). If it's genuinely just debt, I'd document the problem and a proposed improvement, estimate the time investment and expected benefit, and bring it to my manager. I wouldn't just complain about it in Slack — I'd propose a solution."

15. "What would you do if you were hired but the role turned out to be very different from what was described?"

"I'd give it a genuine shot for a few weeks — sometimes the gap between job description and reality is just onboarding confusion. If after a reasonable period it was clearly not what was discussed, I'd have an honest conversation with my manager: 'The role feels quite different from what we discussed. Can we talk about how to align expectations?' It's possible there's a path to the role I was expecting. If not, I'd have to evaluate whether the actual role is still a good fit."

Customer and Stakeholder Questions

16. "What would you do if an important client was unhappy with your team's work?"

"I'd listen first — really listen, not just wait to defend. Understand exactly what they're unhappy about and why. Then I'd own it: 'You're right, this fell short of what you expected.' No deflecting to other teams. I'd present a concrete plan to fix it with a timeline, and I'd follow up proactively so they don't have to chase us. Recovering from a failure well often builds more trust than getting it right the first time."

17. "What would you do if two stakeholders gave you conflicting requirements?"

"I'd get them in the same room — or the same call. Conflicting requirements usually happen because stakeholders are making decisions in isolation. I'd present both requirements, explain the conflict, and facilitate a discussion about priorities. If they can't agree, I'd escalate to whoever has authority over both of them. What I wouldn't do is try to build something that satisfies both conflicting requirements — that usually satisfies neither."

Tips for Situational Questions

Don't rush to the answer. Take a moment to think. Saying "That's a great question, let me think about that for a moment" is perfectly fine.
Think out loud. The process matters more than the conclusion. Walk the interviewer through your reasoning.
Be realistic, not idealistic. "I'd have a calm, rational conversation" sounds nice, but acknowledge that situations are messy.
Draw from real experience when possible. "I'd do X — actually, I faced something similar when..." strengthens your answer.
Ask clarifying questions. "Is this a direct report or a peer?" or "What's the timeline?" shows sophisticated thinking.

Want to practice situational questions? Reherse's AI interview coach throws realistic scenarios at you and gives instant feedback on your reasoning and delivery. Start practicing →

The Bottom Line

Situational questions test how you think, not what you've memorized. The interviewer is watching your reasoning process — how you weigh trade-offs, consider stakeholders, and arrive at a decision.

Show your thinking. Be honest about trade-offs. Name the principle behind your decision. That's what separates a good answer from a great one.