STAR, CAR or SOAR, and how to structure a behavioral interview answer

Tell me about a time you disagreed with your manager.

Questions like this are called behavioral, or past-behavior, questions, and they are everywhere because they work. A structure such as STAR, CAR or SOAR makes sure your answer gives the interviewer what they are scoring.

Why interviewers ask about the past

Research on hiring interviews has one finding that has held for decades. Structured interviews, in which every candidate gets the same job-related questions and answers are rated against the same scale, are far more reliable and valid than unstructured conversations. A 2014 review in Personnel Psychology counts twelve meta-analyses that found the same thing (Levashina and colleagues).

Most structured interviews use two kinds of question. Past-behavior questions ask what you did in a real situation, and situational questions ask what you would do in a hypothetical one. Both predict job performance. In the meta-analyses the review summarizes, past-behavior questions did slightly better, with average uncorrected validities of about .31 against .25 for situational questions, and the gap was larger for complex jobs. The two types also seem to measure different things. Situational questions mostly reflect job knowledge and past-behavior questions mostly reflect experience, which is why many interviewers use both.

Behind a behavioral question there is usually a competency, such as handling conflict, prioritizing or influencing without authority, and a rating scale. Your answer is the evidence the interviewer writes down, and a structure makes sure that evidence is complete.

STAR (situation, task, action, result)

STAR comes from DDI, a leadership consultancy, which says it introduced the method in 1974 with its Targeted Selection interviewing system. DDI’s own definition groups the first two letters together. The situation or task gives the context, the action is what you did, and the result is what it achieved and why it worked (DDI).

Spend your time where the evidence is. A sentence or two of situation and task, most of the answer on your actions and a clear result at the end make a practical split.

Situation and task. Two weeks before a product launch, our biggest customer asked for a data export we had not planned, and my manager asked me to scope it. Action. I listed what they actually needed from the export with their analyst in a 30-minute call, found that a scheduled CSV covered 90% of it, and proposed shipping that for launch and the full API a month later. I wrote the trade-off down for my manager and the customer in one page. Result. The customer agreed the same day, we launched on time, and the API shipped three weeks after launch. The one-page format became our template for scope requests.

CAR (challenge, action, result)

CAR merges the situation and the task into the challenge, the problem itself. The University of Wisconsin-Superior’s career office describes it in three prompts. Set up the story and the challenge, explain what you did, and say what happened, with metrics where possible (UW-Superior).

CAR is the better choice when time is short, as in phone screens, panel interviews with many questions or the bullet points on a resume. It makes you open with the problem, usually the part interviewers find most interesting.

Challenge. Our support queue had a three-day backlog after a pricing change. Action. I sorted the tickets by cause, found that 60% asked the same two questions, and wrote two help articles and a saved reply for them. Result. The backlog was gone in four days, and those two questions dropped by half the following month.

SOAR (situation, obstacle, action, result)

SOAR replaces the task with the obstacle, whatever stood in the way. It shows up mostly in coaching material, and we found no research comparing it with STAR. Its value is that it makes you name the difficulty, which is often the most convincing part of a story about persistence, influence or change.

Situation. I was moving our team from weekly to daily releases. Obstacle. The QA lead was against it, because the last attempt had caused two outages. Action. I asked what would make daily releases safe from the QA side, and we agreed on automated checks for the two failure types behind those outages before changing anything. Result. We moved to daily releases two months later with no release-related outage in the following quarter, and the QA lead presented the setup at our engineering all-hands.

Which one to use

The letters matter less than the habit behind them, which is context in a sentence, your own actions in detail and a result someone could check.

When the question is about the future

Situational questions test judgment and job knowledge.

What would you do if a teammate missed a deadline that affects you?

Answering with a story is fine if you have one. The interviewer is scoring how you reason, so a good answer names the goal, meaning what a good outcome looks like here. It lays out two or three options, says which one you would choose and what you would give up for it, and ends with how you would know it worked.

The mistakes interviewers see most

The most common one is saying we all the way through. Teams do the work, and the interviewer is still assessing you, so say what you did. A hypothetical answer to a past question carries no evidence, and DDI points out that STAR keeps candidates on what they actually did. A long situation with a thin action wastes the answer, so if the setup takes half of it, cut it. A missing result, or one with no number, leaves the story unfinished. If you cannot measure it, say what changed and who noticed. And if the project succeeded for reasons you did not drive, say what you contributed.

Build a story bank once

Write six to eight stories, a few lines each. Cover a success, a failure and what you changed afterwards, a conflict, a time you led without authority, a time you changed your mind, pressure on a deadline, and one or two that show the main skill of the role. Tag each story with the competencies it shows. Most behavioral questions are one of a dozen competencies in different words, and a tagged list lets you pick the right story in the second before you start speaking.

Practice each story at two lengths, a 30-second CAR version and a two-minute STAR version. Interviewers who want more will ask, and a follow-up question is a better sign than a long answer.

Prepped’s question bank is one place to keep that story bank. Behavioral questions open in the STAR parts, and it points out the two mistakes that are easiest to miss when you read your own draft. One is a result without a number, and the other is an action part that says we more often than I.