The SOAR Method: Situation, Obstacle, Action, Result (and SOAR vs STAR)

The short answer: SOAR stands for Situation, Obstacle, Action, Result. It’s a way to structure answers to behavioral interview questions, like the STAR method, but it puts the obstacle where STAR puts the task, so the difficulty you overcame is the center of the story. Use SOAR when the question is about a challenge, a conflict or a setback; use STAR when it’s about a responsibility you carried out. Either way, end with a one-sentence takeaway that connects the story to the job.

What SOAR stands for

Georgetown University’s career center teaches an extended version, SOART, which adds a T: a takeaway or tie-in, what you learned and how it makes you a strong candidate for this role. It’s worth adding every time.

SOAR vs STAR

STAR is older and more widely known: the consulting firm DDI introduced it in 1974, and its own version already merges the first two steps into “Situation/Task”. Interviewers listen for the same things in both: a real situation, your actions and a result. Our full guide to the STAR method has eight more examples and a free worksheet.

When to use SOAR

SOAR fits questions that are about difficulty:

• “Tell me about a time you faced a significant obstacle.”
• “Describe a conflict with a coworker and how you handled it.”
• “Tell me about a project that went wrong.”
• “Describe your most challenging project.”
• “Tell me about a time you had to work with limited resources.”

Naming the obstacle explicitly does two things: it shows you understood what made the situation hard, and it makes your actions easier to judge, because the interviewer knows what you were up against.

Two SOAR examples

These illustrate the structure; they aren’t quotes from real candidates.

“Tell me about a time you faced an obstacle at work.”

• Situation: “I was coordinating the move of our support team to a new ticketing system.”
• Obstacle: “Two weeks before launch, we found that the old system’s customer history couldn’t be exported in a format the new one accepted.”
• Action: “I worked with one engineer to write a conversion script, tested it on a sample of 500 tickets, and when the test surfaced errors in old records, I set up a rule to flag them for manual review instead of delaying the launch.”
• Result: “We launched on time, with 98% of history migrated automatically and the rest cleaned up by the team in the first week.”
• Takeaway: “I learned to test data migrations on real samples early, which I’d bring to your implementation projects.”

“Describe a time you had a conflict with a teammate.”

• Situation: “In a group project for my final-year marketing class, I was one of four students building a campaign for a local business.”
• Obstacle: “One teammate kept missing our meetings, and the others were ready to go to the professor.”
• Action: “I asked to talk with the teammate one-on-one first. They were struggling with a heavy course load, so we agreed they’d take the research section they could do on their own schedule, and I set up a shared tracker so everyone could see progress.”
• Result: “They delivered their section on time, and the business owner adopted two of our recommendations.”
• Takeaway: “It taught me to ask what’s going on before assuming someone doesn’t care.”

Common SOAR mistakes

• Spending too long on the obstacle. Describe it in one or two sentences, then move to what you did. The problem is the setup, not the story.
• Blaming people. Describe the obstacle as a situation, not someone’s character.
• Choosing a trivial obstacle. If it wasn’t really hard, the answer can’t show much.
• No result, or no takeaway. End with what changed and what you’d bring to this job.

For conflict questions specifically, see our guide to collaboration and conflict answers.

Frequently asked questions

Sources

• Georgetown University, Cawley Career Education Center, General Interview Guide (the SOART technique). Read on 29 September 2026.
• DDI, STAR Method for Interviewing and Feedback. Read on 29 September 2026.