Behavioral interviews announce themselves with a formula: "Tell me about a time when..." They do not ask what a candidate would do; they ask what the candidate did, on the premise that past behavior predicts future behavior better than intention does. Anyone who arrives with general opinions about themselves, that they work well on a team or handle pressure, runs out of material in two minutes.
The STAR method is the standard way to answer those questions. This guide covers it from the practical side: what the interviewer is actually scoring, how an answer is structured, how to prepare six to eight stories that cover the competencies in the posting, two complete examples, and the mistakes that cost the most points.
In this guide
What a behavioral interview measures
The interviewer works from a list of competencies defined for the role (teamwork, results orientation, problem solving, communication, adaptability, leadership) and asks for a real past example of each. They take notes and score against behavioral indicators: what the person did, on what reasoning, and what came of it. Hypothetical answers and statements of principle earn nothing because they carry no evidence. Unlike common interview questions, there is no correct answer here; there is an answer with data and an answer without.
The questions are recognizable by shape:
- "Tell me about a time you had to convince someone who disagreed with you."
- "Give me an example of a goal you missed and what you did next."
- "Describe a situation where you had to prioritize among competing urgent tasks."
Follow-up probes are part of the method: "what exactly did you do?", "which part was your decision?", "how did you measure it?" They exist to separate what the person did from what their team did.
The STAR method, step by step
STAR stands for Situation, Task, Action, Result, and it splits the answer into four parts with different jobs and different weights:
- Situation: the context in one or two sentences. Where, when, what was happening.
- Task: what had to be achieved and what the speaker's own responsibility was within it.
- Action: what was done, step by step, in the first person singular. This is the center of the answer and deserves more than half the time.
- Result: what happened, with a number or a verifiable fact, plus one line on what it taught.
A complete STAR answer runs between 90 seconds and two minutes. Longer than that and the interviewer loses the thread; shorter and either the action or the result is missing. A rough proportion: 15% situation, 15% task, 50% action, 20% result.
The most frequent error sits in the Action: describing what "the team" did. The interviewer is scoring one person and needs to hear "I proposed," "I negotiated," "I decided," even when the win was collective.
Preparing six to eight stories
Preparation happens before the interview, in writing, in four steps. First, pull the competencies out of the posting: every soft requirement ("negotiation skills," "works independently," "thrives under pressure") is a probable question. Second, inventory the experiences with real material in them: projects, crises, conflicts, changes, mistakes, and wins, whether at work, in school, or outside both. Third, pick six to eight stories that together cover the competencies in the posting; a good story usually serves two or three. Fourth, write each one in STAR format across eight to ten lines and say it out loud until it comes without reading, either with another person or with an interview simulator that asks the questions for that role.
| Competency | Typical question |
|---|---|
| Teamwork | "Tell me about a disagreement with a coworker and how it got resolved." |
| Results orientation | "Give me an example of a demanding goal you hit." |
| Problem solving | "Describe an unexpected problem and what you did." |
| Adaptability | "Tell me about a change you did not choose and how you handled it." |
| Handling mistakes | "Tell me about a significant mistake you made." |
The set has to include at least one failure story and one conflict story: those get asked most often and improvise worst. With little work experience, academic projects, volunteering, athletics, and informal jobs all count, as long as the story has a task, an action, and a result.
Two complete examples
Example 1: team conflict (marketing analyst)
Question: "Tell me about a time you had a significant disagreement with a coworker."
- Situation. At Brightline Media, a marketing agency in Denver, a designer and I had two weeks to deliver a campaign for a retail client. He wanted a visual concept that, according to the previous campaign's data, had performed poorly with that segment.
- Task. As the analyst, I was responsible for the campaign hitting the conversion target we had agreed with the client, without damaging the working relationship with the designer.
- Action. Instead of arguing about taste, I put together a one-page comparison of the last two campaigns broken down by asset type and proposed we decide from that. I accepted two of his visual elements that did not affect conversion, and held the line on the change to the call to action.
- Result. The campaign shipped on time and beat the previous conversion rate by 22%. Since then we review the data together before every proposal.
Example 2: hitting a goal with fewer resources (logistics coordinator)
Question: "Describe a situation where you had to hit a target with fewer resources than planned."
- Situation. At Cascade Distribution in Portland, two of the six afternoon-shift drivers resigned in the same week, in peak season, with 180 committed daily deliveries.
- Task. I coordinated that shift and had to hold the on-time delivery rate, which was at 96%, with no authorization to hire in the short term.
- Action. I redesigned the routes to group deliveries by zone rather than by account, which cut miles per driver, and negotiated with the morning shift for two drivers to extend their day three times a week. Meanwhile I documented the shortfall with numbers to support the hiring request.
- Result. On-time delivery dropped only to 93% during the three-week transition and returned to 96% once the two new drivers started. Zone-based routing stayed as the shift's standard.
Common mistakes
Mistakes in a behavioral interview are usually structural rather than substantive:
| Avoid | Better |
|---|---|
| Spending a minute on company background before reaching the problem | Situation in two sentences; the time belongs to the action |
| "We did," "the team decided," "it got resolved" | "I proposed," "I decided," "I negotiated" |
| Ending the story without a result ("and it went well") | A number or a verifiable fact: "22% higher conversion" |
| Answering with what you would do ("in that case I'd talk to...") | A real past case, with a place and an approximate date |
| Inventing or inflating the example | Real stories: the follow-up probes expose the invented ones |
One more mistake is reciting a written text from memory: it sounds rehearsed and breaks at the first probe. What gets memorized is the structure and the numbers; the words come in the moment. The rest of the preparation, covering the company, the posting, and the logistics, is in the guide on how to prepare for an interview.
Frequently asked questions
What is the STAR method in an interview?
It is a way of structuring the answer to a behavioral question in four parts: Situation (brief context), Task (what had to be achieved), Action (what the person did, in the first person), and Result (what happened, with data). It keeps the answer evidence-based and under two minutes.
How many stories should be prepared for a behavioral interview?
Six to eight, chosen so that together they cover the competencies in the posting. Each well-built story usually serves two or three different competencies, so that number answers almost any question without repeating.
What if there is no work experience to draw examples from?
Academic projects, internships, volunteering, team sports, and informal jobs all work. What the interviewer scores is the behavior, meaning how it was resolved, which decision was made, and what resulted, not the prestige of the setting.
Can a story with a negative result be used?
Yes, and one should be ready, because "tell me about a mistake" is among the most common questions. The structure stays the same; the result includes what got corrected and what was done differently afterward. What loses points is blaming others or picking a trivial mistake.
How long should a STAR answer take?
Between 90 seconds and two minutes, with roughly half of that on the action. Interviewers who need more detail will probe, and a probe is easier to answer well than a four-minute monologue is to recover from.