Get started free

The STAR Method: How to Answer Behavioral Interview Questions

Use the STAR method (Situation, Task, Action, Result) to answer “tell me about a time…” questions clearly. Includes timing, a full example, a story bank template and common mistakes.

GotOffered editorial teamUpdated October 1, 2026 8 min read
On this page

On this page

  1. What STAR is
  2. Getting the balance right
  3. A full example
  4. Build a story bank
  5. Common mistakes
  6. FAQ

“Tell me about a time you disagreed with your manager.” “Describe a project that failed.” Behavioral questions assume that how you handled real situations in the past predicts how you’ll handle them in the job. The STAR method is the simplest way to answer them clearly, without rambling.

What STAR is

StepWhat to sayShare of answer
SituationThe context: where, when, what was going on~15%
TaskYour responsibility or the goal~10%
ActionWhat you did, step by step, and why~55%
ResultWhat changed (ideally with a number) and what you learned~20%

Getting the balance right

The most common mistake is spending a minute on context and ten seconds on what you did. Interviewers are evaluating your actions: your judgment, your skills, how you work with people. Keep the situation to a sentence or two and spend most of your time there.

A full example

Question: “Tell me about a time you had to deliver under a tight deadline.”

STAR answer

Situation. Two weeks before a major retail client’s launch, our payment provider announced it was deprecating the API we’d built on.

Task. As the lead engineer on the integration, I had to get us onto the new API without moving the launch date.

Action. I mapped every call we made to the old API in a day and found that 80% had direct equivalents. I split the work so two teammates handled those while I took the three tricky flows: refunds, partial captures and webhooks. I told the client’s PM on day two exactly what was at risk and agreed a fallback: launch with manual refunds if we had to. We tested daily against the provider’s sandbox.

Result. We launched on schedule with every flow automated, and the client processed about $2M in the first month with no payment incidents. I also turned the mapping into a checklist the team used for two later migrations.

Build a story bank

You can’t predict every question, but you can prepare 6–8 stories that cover most of them. Write a few bullet points (not a script) for each:

  • A success you’re proud of
  • A failure or mistake, and what you changed afterwards
  • A conflict or disagreement
  • A tight deadline or pressure
  • Leading or influencing without authority
  • Learning something quickly
  • Going beyond your role for a customer or teammate

Then map them to the questions you expect. Our interview question generator turns a job post into likely questions, and the interview questions by role pages cover the common ones in depth.

Common mistakes

  • Choosing a story with no real stakes. Pick situations where something could have gone wrong.
  • A “failure” that’s secretly a strength (“I work too hard”). Interviewers see through it. Pick a real one and focus on what you learned.
  • No result. Even if the outcome was mixed, say what happened and what you’d do differently.
  • Memorised scripts. Know your bullet points, not every word. Practise out loud until it sounds natural.

For the opening question of almost every interview, read how to answer “Tell me about yourself”.

Frequently asked questions

How long should a STAR answer be?

Roughly 1.5 to 2 minutes. Long enough for specifics, short enough that the interviewer can ask follow-ups.

Can I use the same story for several questions?

Yes. A good story often shows several things (leadership, conflict, learning). Emphasise the part that answers the question being asked.

See how your résumé measures up

Free score and the exact fixes in about 30 seconds — no account needed.

Score my résumé

Keep reading