The STAR method: how to answer behavioral interview questions

The STAR method is a four-part structure for answering behavioral interview questions — the ones that start "Tell me about a time when...". STAR stands for Situation, Task, Action, Result: set the scene briefly, state what you were responsible for, describe what you actually did, and land on what happened because of it. Interviewers at most large companies are trained to listen for exactly this shape, and many score answers against it.

The four parts, weighted correctly

Most STAR answers fail on proportion, not content. The right weighting:

• Situation (10-15%) — two sentences of context: where, when, what was at stake. Not the department history.
• Task (10%) — one sentence: what you specifically were on the hook for, distinct from what the team was doing.
• Action (50-60%) — the core: the decisions you made, in first person singular. "I" carries this section; "we" hides you from the person deciding whether to hire you.
• Result (20-25%) — the outcome, with a number where honest, plus one line on what you learned or would do differently.

A worked example

Question: "Tell me about a time you dealt with a missed deadline."

Situation: "Last year I was running the data migration for our billing system cutover, scheduled for end of quarter, and three weeks out we discovered the legacy exports were missing about 8% of customer records." Task: "I owned the migration timeline and had to decide whether to slip the date or cut scope." Action: "I quantified the gap first — the missing records were all pre-2019 accounts — then proposed migrating active accounts on schedule and running a second pass for legacy data. I got sign-off from finance, wrote the reconciliation checks myself, and moved our standup to daily for the final stretch." Result: "We hit the original cutover date with 100% of active accounts, closed the legacy gap two weeks later, and the reconciliation checks caught two billing errors that would have reached customers. Since then I build a data-quality audit into week one of any migration."

Preparing without sounding scripted

You cannot script every question, and you do not need to. Prepare six to eight stories — a conflict, a failure, a tight deadline, a persuasion, a leadership moment, an ambiguous problem — and know each one at the bullet-point level rather than word for word. Most behavioral questions are one of those stories wearing different clothes. Practicing out loud matters more than writing: an AI interview coach or a patient friend will expose the story that takes three minutes to reach its point.

Where candidates go wrong

• Answering in generalities — "I always make sure to communicate clearly" is a values statement, not a story. The question asked for a specific time.
• Team camouflage — an answer with no "I" in the Action section scores as if you watched the events happen.
• No result — trailing off after the actions. If the outcome was bad, say so and spend the saved time on what changed in how you work.
• Choosing low-stakes stories — the story about mild inconvenience handled competently beats nothing, but barely. Pick the story where something real was on the line.

Frequently asked questions