The SOAR Method: How to Answer Behavioral Questions (+ Examples)

Situation, Obstacle, Action, Result — a four-part script for interview stories, with worked examples from nursing, sales, teaching and construction.

By Junie Castellane · Published · Updated · 18 min read

Featured image for "The SOAR Method: How to Answer Behavioral Questions (+ Examples)"

By the end of this guide you will be able to spot a behavioral question from its first five words, build a short story that answers it, and tell that story in about ninety seconds without rambling. SOAR stands for Situation, Obstacle, Action, Result (University of Oregon, School of Design Career Advising, undated).

You get a worked example, seven more from different industries, a list of questions to prepare stories for, and the five mistakes that cost people good answers.

What it is and when to use it

SOAR stands for Situation, Obstacle, Action, Result, and it is a way of telling a short work story out loud (University of Oregon, School of Design Career Advising, undated). Brock University's Career Zone describes the same technique as a storytelling or narrative approach to answering questions in a job interview (Brock University, Career Zone, undated). Use it when an interviewer asks what you did, not what you would do.

The prompts are easy to spot. Memorial Sloan Kettering Cancer Center Careers says one sign you are facing a behavioral question is an opening like 'tell me about a time when' or 'give me an example'. The Muse lists telltale openings including 'Tell me about a time when…', 'What do you do when…', 'Have you ever…', 'Give me an example of…' and 'Describe a situation…'. Johnson & Johnson Careers adds 'Describe how you responded when…'. Indeed Career Advice names the same two main openings.

Northwestern Career Advancement notes that most employers interview this way because past behavior is taken to predict future performance (Northwestern Career Advancement, Northwestern University, undated). Aston Carter lists SOAR alongside STAR and CAR as named behavioral-interview techniques; SOAR is the one to reach for when the interesting part of your story is the thing that got in the way.

Each part, explained

The shares below follow the split Northwestern Career Advancement gives for the closely related STAR approach — Situation 15%, Task 10%, Action 50%, Result 25%, with action always the longest part of the response (Northwestern Career Advancement, Northwestern University, undated). SOAR swaps Task for Obstacle, so the proportions carry over.

PartWhat goes inRough share of the answer
SituationWhere you were, when, your job title, and the scope: team size, caseload, budget, territory, shift. Include enough detail that someone new to your story can understand what was happening (University of Oregon, School of Design Career Advising, undated). Two or three sentences.About 15%
ObstacleThe thing that made it hard: the conflicting deadline, the missing data, the peer who disagreed, the regulation, the person who outranked you. One or two sentences, stated plainly, with no blame.About 10%
ActionWhat you personally did, in order, and why you chose it over the obvious alternative. This is the part they score. Give the steps, the judgment calls, the people you went to and the thing you decided not to do.About half
ResultWhat changed, measured if you can measure it, plus what stuck afterwards: the process that is still running, the person who stayed, the standard that got written down.About a quarter

Say 'I', not 'we'. Interviewers cannot credit you for a team's work if you never separate yourself from it, and 'we decided' is the most common way good candidates disappear from their own stories. Use 'we' only for context — 'we had four weeks' — and switch to 'I' the moment you start the Action. Then finish on something countable. Memorial Sloan Kettering Cancer Center Careers advises candidates that it is important to include concrete, measurable data when answering questions (Memorial Sloan Kettering Cancer Center Careers, undated). If nothing was counted, use a before-and-after you can defend: three days down to one, two open positions filled, zero repeat findings at the next audit.

One worked example

"Give me an example of a time you had a conflict with a coworker"

This is one of the common behavioral questions The Muse lists (The Muse, undated). The competency is conflict resolution between peers — whether you can disagree with someone you do not manage and still keep the work moving.

Second-shift supervisor, regional distribution center, 40 associates on outbound

Situation: I ran outbound on second shift at a distribution center outside Columbus, with about 40 associates. First shift and second shift shared the same four dock doors and the same forklift fleet.

Obstacle: The first-shift supervisor was leaving staged pallets in our lanes so he could finish his counts, so we spent the first 45 minutes of every night clearing them. I had mentioned it twice in passing and nothing changed. He had nine years there; I had eight months.

Action: I pulled the dock scan timestamps for three weeks so we were discussing data rather than memory. Instead of raising it in the supervisors' meeting, I asked him for twenty minutes before handover and opened with his problem — his counts were being pushed late by afternoon trailer arrivals. I proposed splitting the lanes, with two reserved for his staging, plus a fifteen-minute joint dock walk at shift change. I wrote it up as a one-page handover standard and asked the operations manager to approve it rather than enforce it.

Result: Within a month our first outbound trailer left on time nine nights in ten, up from four. The handover walk is still running, and he put the same standard on first shift's board.

Why it works: the obstacle is honest about the power gap, the action is a sequence of choices with reasons, and the result is countable and outlived the argument.

More examples

Seven answers, seven industries. The numbers belong to the people telling them — swap in your own.

"Describe a situation where you escalated a concern about a patient and the physician disagreed"

Competency tested: clinical judgment and willingness to escalate through a hierarchy.

Registered nurse, 32-bed medical-surgical unit, community hospital, night shift

Situation: I had six patients on nights, including a post-op day-two patient whose vitals had been stable all week.

Obstacle: At 2am her respiratory rate crept up and her urine output dropped, but her blood pressure was still within range, so she did not trip the early warning score. The on-call resident told me to recheck in two hours.

Action: I rechecked in thirty minutes instead, documented the trend rather than the single reading, and called back with the numbers side by side. When he held his position, I used the chain of command and paged the rapid response team, then told him I had done it and why, so he was not surprised.

Result: She was septic. She went to the ICU within the hour and came back to us four days later. My manager used the case in our next huddle on trend-based escalation.

Why it works: it shows escalation done by the book, not by temper, and it names the trend she acted on rather than claiming a hunch.

"Tell me about a time something you shipped broke in production"

Competency tested: ownership under incident pressure, and blameless diagnosis.

Backend engineer, payments team, 12-person platform group at a fintech

Situation: I owned the service that retried failed card charges for about 60,000 merchants.

Obstacle: A change I wrote to improve retry timing doubled the retry rate for one card network overnight. Support started getting duplicate-charge complaints at 6am, and I was the only person who understood the retry logic.

Action: I rolled back first and investigated second, which cost me the clean reproduction but stopped the bleeding in eleven minutes. I wrote a script to identify every duplicated charge, handed finance the list before they asked for it, and drafted the customer notice myself rather than leaving support to guess at the wording. In the postmortem I proposed a rate-limit alarm on retries per network, which we had never had.

Result: 412 duplicate charges, all refunded within two days. The alarm has since caught two unrelated bugs before customers saw them.

Why it works: he rolls back before he investigates, hands other teams what they need unprompted, and the result includes the control that stops a repeat.

"Give me an example of a time when you motivated others"

This is one of the sample practice questions published by Virginia Career Works (Virginia Career Works, vawizard.org, undated). Competency tested: motivating people who have no obligation to be motivated.

Seventh-grade math teacher, Title I middle school, 28 students per section

Situation: My fourth-period class had the lowest homework completion rate in the grade — around a third of students turning anything in.

Obstacle: Most of them were not refusing out of defiance; they were behind and did not want to be seen failing in front of each other. Taking points off had already been tried and had made it worse.

Action: I stopped grading homework for accuracy and graded it for attempt, then spent the first eight minutes of class on whatever two problems the most people had missed. I started calling three families a week with something specific that had gone right, not wrong. For the students furthest behind, I set a floor goal of two problems a night and told them privately what it was.

Result: Completion went from about a third to over 80% by the end of the quarter, and eleven of the twelve students on my watch list passed the spring assessment.

Why it works: she diagnoses the reason behind the behavior before changing anything, and the actions are specific enough to copy.

"Tell me about a time you handled a difficult stakeholder"

This is one of the common prompts collected by IGotAnOffer (IGotAnOffer, undated). Competency tested: influence without authority on a schedule you cannot move.

Project manager, commercial general contractor, 70,000 sq ft tenant fit-out

Situation: I ran a fourteen-week office fit-out with a hard move-in date tied to the client's lease expiry.

Obstacle: The client's facilities director kept issuing finish changes directly to my drywall sub, bypassing the change order process. Three weeks in we were carrying around $40,000 of unapproved work and he was insisting none of it was a change.

Action: I stopped the side channel at the source by telling the subs in writing that only I could authorize work, then met the director in person rather than emailing. I brought a one-page log of each request with its cost and its effect on the move-in date, and asked him to pick which ones he wanted rather than defending the process. I offered a standing Thursday walk so changes had a place to go.

Result: He dropped four requests, approved six, and we turned the space over two days early. The Thursday walk became standard on our next two projects with that client.

Why it works: he fixes the mechanism, not just the mood, and the result includes a repeat client.

"Tell me about a time you made a mistake"

Another of the common behavioral questions The Muse lists (The Muse, undated). Competency tested: accountability and what you do in the first hour after an error.

Store manager, specialty retail, 18 staff, one mall location

Situation: I built the holiday schedule for the first two weeks of December, our heaviest trading period.

Obstacle: I approved two senior associates for the same week off without checking the coverage grid, so we opened Black Friday weekend three people short with four new hires who had never run a register at volume.

Action: I told my district manager before she found out from the numbers. I came in myself on both days and ran the second register instead of the floor, paired each new hire with an experienced associate rather than splitting them across zones, and moved fitting-room staff to the queue at peak. Afterwards I built a coverage check into the schedule template so a sign-off cannot go through under minimum staffing.

Result: We finished the weekend 6% above the prior year. No scheduling conflict has gone out since the template changed.

Why it works: she names the error in one sentence without excuses, and the fix is structural rather than a promise to be more careful.

"Describe a situation in which you used persuasion to convince someone to see things your way"

This is one of the practice questions published by Virginia Career Works (Virginia Career Works, vawizard.org, undated). Competency tested: evidence-based persuasion of someone with the power to say no.

Account executive, B2B software, mid-market territory of about 90 accounts

Situation: I had a logistics company at the end of a six-month evaluation, with the operations VP sponsoring us.

Obstacle: Their CFO blocked it at the last meeting. He had bought a similar tool two years earlier, seen it go unused, and said he would not pay for shelfware twice.

Action: I did not re-pitch features. I asked for twenty minutes to understand what went wrong the first time, and the answer was that nobody owned adoption. So I rebuilt the proposal around that: a 60-day pilot with two named internal owners, adoption thresholds written into the contract, and a clause letting them exit at 60 days. I asked the operations VP to present the adoption plan instead of me.

Result: They signed a 90-seat deal and renewed the following year at 140 seats.

Why it works: the persuasion is listening first and changing the offer, not arguing harder.

"Tell me about a time you had to stop a production line"

Competency tested: regulatory judgment when output pressure points the other way.

Quality assurance technician, food manufacturing plant, two packaging lines

Situation: I ran in-process checks on a line producing about 12,000 units a shift.

Obstacle: A metal detector failed its mid-shift verification test twice. The line lead wanted to keep running until the end of the shift because we were behind on a customer order, and he had been there far longer than me.

Action: I stopped the line under the hold procedure rather than debating it on the floor, then called the quality manager so the decision was not mine alone. I quarantined everything produced since the last passing check — about four hours of product — and logged it. While maintenance worked on the detector, I reran the verification sequence with the lead watching so he could see what had failed.

Result: Two hours of downtime, 9,000 units held and re-screened, nothing shipped unverified. We passed the customer audit six weeks later with no findings on the metal detection program.

Why it works: she follows the procedure instead of winning an argument, and the result ties the decision to an audit outcome.

Build your story bank

Prepare six to eight stories, not twenty. Most interviews pull from the same handful of competencies, and one good story can answer three questions if you emphasise a different obstacle each time. Write each one as four bullets — Situation, Obstacle, Action, Result — never as a script.

QuestionSkill it tests
Give me an example of a time you had a conflict with a coworker (The Muse, undated)Resolving disagreement with a peer you do not manage
Tell me about a time you made a mistake (The Muse, undated)Accountability and error recovery
Tell me about a time you handled a difficult stakeholder (IGotAnOffer, undated)Influence without authority
Tell me about a time you showed leadership (IGotAnOffer, undated)Taking responsibility before being given it
Describe a situation in which you used persuasion to convince someone to see things your way (Virginia Career Works, vawizard.org, undated)Building a case and adapting it to the other person
Give me an example of a time when you motivated others (Virginia Career Works, vawizard.org, undated)Moving people who are disengaged or stuck
Tell me about a time you had to deliver bad newsClear communication under discomfort
Describe a time you missed a deadlinePrioritisation, and how early you flag slippage
Tell me about a time you had to decide with incomplete informationJudgment under ambiguity and risk tolerance
Tell me about a time you had to learn something quicklyLearning agility and self-direction

Map your bank against the job posting before the interview. Take the four or five things the posting repeats — stakeholder management, compliance, mentoring, working across sites — and make sure one story in your bank lands on each. Any competency with no story behind it is the one you will fumble.

Common mistakes

  • Spending ninety seconds on the Situation. You set the scene, name three colleagues, explain the reorganisation, and the interviewer is still waiting for something to happen. Fix: cap the Situation at two or three sentences — role, scope, timing — and get to the obstacle.
  • Telling a story with no obstacle in it. 'We had a busy quarter and I worked hard' gives the interviewer nothing to score, because nothing resisted you. Fix: pick stories where something genuinely went wrong, and say in one plain sentence what made it hard.
  • Disappearing into 'we'. Candidates who say 'we rebuilt the process' and 'we got the client back' get credit for neither. Fix: use 'we' for context only, then switch to 'I' for every sentence of the Action.
  • Stopping at the Action. The story ends with what you did and never says whether it worked, so the interviewer has to ask or move on. Fix: end every answer on a result, with a number or a clear before-and-after — concrete, measurable data matters here (Memorial Sloan Kettering Cancer Center Careers, undated).
  • Making the coworker the villain. In conflict stories, describing the other person as lazy, difficult or irrational tells the interviewer how you will describe them later. Fix: state the other person's position fairly, as they would state it, before you say what you did.
  • Reciting a memorised story that does not answer the question asked. You hear 'conflict' and launch the prepared stakeholder story, which was about scheduling. Fix: take two seconds, repeat the key word of the question back, and choose the story that matches it.

Frequently asked questions

How long should a SOAR answer be?

Aim for 90 seconds to two minutes spoken — roughly 150 to 200 words. Within that, the Action should take about half the time. Northwestern Career Advancement's breakdown for the related STAR approach puts Situation at 15%, Task at 10%, Action at 50% and Result at 25%, with action always the longest part (Northwestern Career Advancement, Northwestern University, undated). Time yourself out loud once per story. If you run past two and a half minutes, the Situation is almost always the part to cut, not the Action.

Can I reuse the same story for more than one question?

Yes, and you should — a strong story usually contains a conflict, a decision and a result, so it can answer questions about conflict, judgment and initiative. Change which part you stretch. For a leadership question, lengthen the Action and the people you brought along; for a failure question, lengthen the Obstacle and what you learned. The limit is repetition in front of the same panel: using one story twice in an hour makes it look like you have only one. Keep at least six in the bank so you never have to.

What do I do if I have no example for the question they ask?

Say so and offer the nearest real thing. 'I have not managed a direct report, but I have trained three new hires — can I tell you about that?' is a good answer; a made-up story is not, because the follow-up questions will unpick it. If there is genuinely nothing adjacent, say what you would do and be explicit that it is hypothetical. You can also ask for a moment to think. A five-second pause reads as considered; a thirty-second invented story reads as rehearsed.

Is SOAR better than STAR?

They are the same shape with a different middle. Aston Carter lists both as named behavioral-interview techniques, with SOAR standing for Situation, Obstacles, Action and Result, and CAR for Challenge, Action and Result (Aston Carter, undated). STAR uses Task where SOAR uses Obstacle (Aston Carter, undated). SOAR tends to produce a better story, because naming the obstacle forces tension into the answer, whereas 'task' can be answered with a job description. Interviewers score the content, not the acronym, so use whichever one keeps you from rambling.

Can I use examples from school, volunteering or a different industry?

Yes, especially early in a career or when changing fields. What matters is that the scope is real and you can describe it: a capstone project with a client, a shift you ran at a food bank, a unit you led in the military, a side business you invoiced for. State the setting plainly so the interviewer can judge the scale, then make the obstacle and your decisions do the work. If the context is unfamiliar to them, add one sentence of translation — what it is comparable to in the role you are applying for.

What if the story ends badly?

Tell it anyway, and land it on what changed afterwards. Failure questions are asking whether you can see your own part in a bad outcome, so a story where you were blameless defeats the purpose. Give the honest result — the project cancelled, the client left, the deadline missed — then one or two sentences on what you did differently next time and the evidence it stuck. The recovery is the result. What loses points is minimising, blaming the team, or picking a 'failure' that is secretly a success.

Should I say the words 'Situation' and 'Obstacle' out loud?

No. The labels are a drafting tool, not a script. In the room, the structure should show up as a story that has a setting, a problem, a sequence of things you did, and an ending. Writing your bullets under the four labels is what keeps you from skipping the Result, which is the part most people drop under pressure. The one exception is a signposting phrase at the start of the Action — 'so here is what I did' — which tells the interviewer the useful part is coming.

Sources

  1. University of Oregon, School of Design Career Advising — Employment Interviews
  2. Brock University, Career Zone — SOAR Technique for Job Interviews

Written by

Junie Castellane

Junie covers the freelance and gig side of the job world, from invoicing headaches to the strange dignity of being your own boss. She writes with equal parts sympathy and skepticism about hustle culture.

More in Interview Preparation

Featured image for "10 Questions to Ask About Company Culture in an Interview"
Interviews

10 Questions to Ask About Company Culture in an Interview

By the end of this guide you will have ten culture questions ready to go, know which to ask to a hiring manager versus a recruiter or a future teammate, and be able to read the answers for what they tell you about how the place really works.

Olu Adeyemi · 9 min read

Featured image for "How to Answer "Where Do You See Yourself in Five Years?" (+ Example Answers)"
Interviews

How to Answer "Where Do You See Yourself in Five Years?" (+ Example Answers)

By the end of this guide you'll have a 60 to 90 second answer to "Where do you see yourself in five years?" that sounds honest, fits the job you're actually interviewing for, and doesn't box you into a title you may not want. The trick is to talk about scope, skills and contribution rather than a rung on a ladder.

Priya Nathwani · 13 min read

Featured image for "How to Answer "Why Do You Want to Work Here?" (+ Example Answers)"
Interviews

How to Answer "Why Do You Want to Work Here?" (+ Example Answers)

By the end of this guide you'll be able to build an answer to "Why do you want to work here?" that names a real detail about the employer, connects it to work you have actually done, and lands in under 90 seconds. The method is the same whether you're a new graduate, stepping up, switching industries or coming back after time out — only the evidence changes.

Desmond Okafor · 11 min read

Featured image for "In-Person Interview Checklist: What to Bring and Do Before You Go"
Interviews

In-Person Interview Checklist: What to Bring and Do Before You Go

An in-person interview is mostly won in the preparation you do before you leave the house: the route you have timed, the documents in your bag, and the three or four stories you can tell without hunting for them. This guide gives you a checklist for the week before, the morning of, the interview itself, and the hours afterwards.

Ananya Rao · 11 min read