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

SOAR stands for Situation, Obstacle, Action, Result. It structures an answer about something you have actually done, so the interviewer gets the context fast, understands what made the work difficult, and then spends most of the time hearing your decisions.

You'll know a behavioral question by its opening. Listen for "Tell me about a time when…", "Describe a situation where…", "Give me an example of…", "Walk me through how you…", "When have you had to…", and "What's the most difficult … you've dealt with?" Anything in the past tense that asks for one occasion rather than your general approach is a behavioral question, and SOAR fits it.

Use it in competency interviews, panel interviews, and the written application questions some employers ask before any conversation happens. It works just as well in a relaxed chat with a hiring manager — you simply don't announce the labels.

How answers are judged varies. Large employers, and public-sector hiring in many US states and in countries such as the UK, Canada and Australia, often score against a published competency framework. A small business may just be listening for whether the story sounds real.

The action section only earns you credit if the interviewer can tell which hands did the work. Say "I rebuilt the schedule", not "we rebuilt the schedule". Use "we" only when you are naming who else was in the room, then switch straight back to "I". Panels hear team stories all day and cannot score a collective pronoun.

End on something countable. If you have no figures, use a comparison you can defend — "it went from three days to same-day", "we cleared the backlog before the audit", "the checklist is still in use". If the numbers are confidential, give the shape without the specifics: "a mid-six-figure account", "about a fifth of our volume". Never invent a statistic you would struggle to explain in a follow-up question.

"Tell me about a time you had to deliver bad news to a client."

Account manager, mid-size marketing agency, eight retainer clients

Situation: Last March I ran the account for a regional furniture retailer, about a quarter of my book. Six days before their spring campaign went live, our developer told me the landing pages wouldn't be ready — a plugin conflict nobody had caught.

Obstacle: The client had already bought radio spots for the launch weekend that couldn't be moved, and their marketing director had been burned by a previous agency missing a date. Telling her late would cost us the renewal. Telling her with no plan would be worse.

Action: I pulled the developer and the studio lead into a room that morning and had two options costed within four hours: a stripped-back single page we could ship in three days, or a full delay. I called the client that afternoon instead of emailing, opened with the miss and the new date, then walked her through both options and what each would do to her radio spend. I recommended the single page, offered to waive our build fee on phase two, and sent a written recap with owners and dates within the hour.

Result: The page went live two days before the radio flight. The campaign ran on schedule, the client renewed in June at the same value, and I added a build-readiness check at the two-week mark that the agency now runs on every launch.

Notice the shape: two sentences of setup, one short obstacle with real stakes, a long first-person action section full of visible decisions, and a result with dates plus something that outlived the project.

Healthcare: "Tell me about a time you escalated a concern about a patient and got pushback."

Med-surg RN, 32-bed unit, community hospital, night shift

Situation: Last winter I had a patient on day two after a bowel resection, one of six on my assignment.

Obstacle: His vitals were technically in range, but his heart rate had crept up about 20 beats over three hours and he was restless in a way that didn't match his reported pain. The on-call resident had already told me once to keep watching.

Action: I repeated a full set of vitals, did a focused abdominal assessment, and charted the trend rather than the single reading so the numbers sat side by side. I called the resident back with that trend. When he still wanted to wait, I used our chain-of-command policy and brought in the charge nurse, who paged the surgical attending.

Result: The attending was on the unit inside 20 minutes. The patient had a developing anastomotic leak and went back to the OR before dawn, and he went home nine days later. Our educator later used my charting as a teaching example of trend documentation.

Why it works: it tests clinical judgment and willingness to escalate under pushback, and the actions show escalation through policy rather than around a colleague.

Software: "Walk me through a decision you made during a production incident without full information."

> Backend engineer, payments team, B2B software company, about 40 engineers > > Situation: At 6pm on a Thursday our card-charge service started failing on roughly one in five requests. > > Obstacle: The logs pointed at a vendor change, our on-call lead was unreachable, and I'd been on the rotation six weeks. A straight rollback would have killed a fraud rule that shipped that morning. > > Action: I declared the incident in the channel instead of debugging quietly, so support knew before customers called. I posted a timestamped timeline as I worked, reproduced the failure in staging, and found the vendor had started enforcing an idempotency key. Rather than roll back, I shipped a two-line fix behind a feature flag so the fraud rule stayed live, and I asked a senior engineer from another team to review it before deploy. > > Result: Error rates were back to baseline 38 minutes after the first alert. I wrote the postmortem, and "declare early, timeline in channel" went into our on-call runbook. > Why it works: it tests judgment under ambiguity and incident ownership, and the result includes a change to how the team works, not just a fix.

Retail: "Tell me about a time you had to hit a target with less staff than you planned for."

Store manager, 14-person team, mall apparel store

Situation: Two weeks before our busiest trading period, three associates resigned inside a week.

Obstacle: Hiring was frozen until January, my labor hours were fixed, and the holiday floor plan assumed six people on the floor every evening.

Action: I rebuilt the schedule around the two busiest hours of each day instead of spreading shifts evenly. I cross-trained both stockroom staff on register, gave the fitting room to one roaming position so somebody owned it, and asked my district manager to lend me weekend hours from a nearby store rather than approving new headcount. I took the Saturday opens myself for three weeks so my assistant could cover evenings.

Result: We finished the period ahead of the prior year on fewer labor hours, fitting-room shrink dropped because one person was accountable for it, and both cross-trained staff moved up to keyholder in the spring.

Why it works: it tests resource planning and people development under constraint, and every action is a trade-off the candidate chose.

Logistics: "Describe a time a shipment was going to miss its window."

Shift supervisor, third-party distribution center, about 60 pickers per shift

Situation: On a Tuesday night our largest grocery customer's trailer was due to leave at 11pm for a 6am delivery slot.

Obstacle: A conveyor failed at 7pm with 40% of the order unpicked, and the maintenance tech estimated two hours. Missing the slot meant the trailer waited until the following night and the customer charged back.

Action: I called the customer's night planner straight away to tell him we were at risk and what time I'd confirm either way — I didn't wait until I had good news. I split the shift: eight pickers onto manual carts for the downed aisles, the rest consolidating pallets that were already staged. I pulled two people off inbound, which I cleared with the inbound supervisor, and I loaded in reverse drop order so the driver could leave part-loaded if we ran out of time.

Result: The trailer left at 11:40pm and made the slot with the driver's legal hours intact. No chargeback. We now keep a manual-pick plan posted for each of the four main aisles.

Why it works: it tests prioritization under time pressure and proactive customer communication, and the obstacle makes the stakes concrete.

Finance: "Tell me about a time you found an error in work that had already been signed off."

Staff accountant, mid-size manufacturer, three-person close team

Situation: During Q3 close I was reconciling the inventory account for a plant that had changed its costing method.

Obstacle: A standard-cost update had been applied twice, overstating inventory by a material amount. My controller had already signed the reconciliation, and the pack went to the board in four days.

Action: Before raising it, I rebuilt the balance from the raw extract so I could show the duplicate entry rather than just assert it. I took it to my controller in person with the two journals side by side, and I said plainly what I thought the restatement was worth. We agreed I'd post the correcting entry, and I wrote a short note for the audit file explaining the cause and the fix. I then added a monthly check comparing standard-cost update counts against the change log.

Result: The pack went to the board with corrected numbers and no late surprise. External audit tested the new check in the year-end and had no finding on inventory.

Why it works: it tests technical accuracy and the courage to challenge upward, and the candidate brings evidence before an opinion.

Education: "Tell me about a time you changed your approach for students who weren't making progress."

Fourth-grade teacher, public elementary school, class of 27

Situation: By November, six of my students were still reading well below grade level and guided reading groups weren't shifting them.

Obstacle: I had no aide in the room, I couldn't add minutes to the literacy block, and three of the six were also pulled out for services, so they missed part of whatever I scheduled.

Action: I ran a quick diagnostic and found that five of the six had a decoding gap, not a comprehension gap, which changed what I'd been doing. I replaced one of my three weekly guided groups with a 15-minute daily phonics routine before the pull-out window, trained two parent volunteers to run fluency repeats on Tuesdays and Thursdays, and started a one-page progress sheet that went home every two weeks so families could see the trend.

Result: Five of the six moved up at least one reading level by March, and four were reading on grade level by the end of the year. Two other teachers on my grade team adopted the pre-pull-out phonics slot.

Why it works: it tests data-informed instruction and adaptability, and the result separates what changed from what didn't.

Construction: "Tell me about a time you stopped work for a safety concern."

Site foreman, commercial fit-out, crew of 18 plus subcontractors

Situation: We were three weeks from handover on an office refit and the mechanical sub was installing ductwork above a live ceiling grid.

Obstacle: Two of their crew were working off a scaffold that had been altered overnight — a guardrail removed to get the duct through, and no tag updated. The sub's lead said they'd be finished in an hour, and the general contractor was already pressing me on the handover date.

Action: I stopped that work area, not the whole floor, so the electrical crew kept moving. I photographed the scaffold, called the sub's supervisor rather than arguing with his crew, and got a competent person to re-inspect and re-tag before anyone went back up. I logged it as a near miss, then raised altered-scaffold tagging in the next morning's toolbox talk for all trades.

Result: The area was back in use within two hours, we handed over on the original date, and the GC adopted the re-tag rule across the site.

Why it works: it tests safety leadership and the ability to hold a line under schedule pressure, and the action is proportionate rather than theatrical.

Most interviews draw from the same small set of competencies. Prepare stories, not answers — then match a story to whatever wording the question arrives in.

Six to eight strong stories will cover this whole table, because most of them stretch across two or three competencies. Keep them on one page: role and scale, one line of obstacle, four or five action bullets, and the result with its number. Review the page the morning of the interview rather than rehearsing sentences, so you sound like you're remembering rather than reciting.

If the employer publishes a competency framework or lists "key selection criteria" in the posting — common in government and large-organization hiring, and standard in some countries — build your bank against those headings instead of generic ones.

• Spending a minute and a half on the setup. You explain the org chart, the product history and who reported to whom, and the interviewer's pen never moves. Fix: give the situation in two sentences — your role, the scale, roughly when — and get to the obstacle.
• Saying "we" all the way through the action. A panel cannot score a group. If every verb is collective, they assume you watched. Fix: write the action out and change each sentence to start with "I", keeping "we" only where you name who else was involved.
• Skipping the obstacle, so the story sounds easy. Without the constraint, a complex rescue sounds like an ordinary Tuesday and nothing stands out. Fix: add one sentence that begins "The hard part was…" and name what would have gone wrong if you'd done nothing.
• Trailing off with "and it all went fine in the end". The ending is where the evidence lives, and vagueness there makes the rest sound inflated. Fix: finish with a number, a date or a before-and-after, plus one line on anything that stayed in place afterwards.
• Making the obstacle a person you blame. "My manager was useless" tells the interviewer how you'll describe them in six months. Fix: state the obstacle as a condition — unclear ownership, a late handover, conflicting instructions — and spend your words on what you did about it.