When an interviewer says "Tell me about a time when…", they're asking a behavioral question. They want proof from your past work, not a description of how you'd like to work. The STAR method is the simplest way to give that proof clearly.
Three examples, well prepared, beat ten half-remembered ones.
What STAR stands for
STAR is a way to keep an answer complete, not a script to recite.
- Situation: one sentence of context.
- Task: what you were responsible for.
- Action: what you did, and the judgment behind it.
- Result: what changed, and what you would do differently.
Situation and task should be short. Action and result carry the weight. The University of Washington's career center suggests giving the action about 60% of your answer, with the situation around 20% and the task and result around 10% each.
The part people skip
The judgment behind the action is what separates two candidates who did the same thing. "I called the client" is an action. "I called the client before they saw the error, because a surprise would have cost more trust than the delay" shows how you think.
Start with a story bank, not a single answer
Most people prepare answers for one interview and start again for the next. Build a story bank instead: a set of real situations from your own work that you can match to whatever is asked. Aim for a mix:
- Something you improved
- Something that went wrong and what you did
- A disagreement you handled
- Work delivered under pressure or short notice
- Something you learned quickly because you had to
- Work that involved people outside your team
Only include things that happened. Anything invented will fail the follow-up question, and the follow-up question always comes.
Choose experiences that show scope, judgment and result
Your best story is not always the right story. The right story is the one that proves a requirement this employer cares about. List the role's top requirements, then match your strongest example to each. A requirement with no example is a gap to plan for, not to hide.
Write the result first
Write the result first, then work backwards into the situation and actions. It keeps you from spending a minute on background and running out of time before the part that matters.
Say "we," then say "I"
Saying "we" the whole way through hides you. Saying "I" about a team effort reads as overclaiming. Do both, in order: name the team effort, then your specific part.
The team rebuilt the intake process. I owned the handover steps and wrote the checks the reviewers used, and that part cut returns to us.
Use numbers you can defend
A modest number you can defend beats a large number you can't. Interviewers test numbers by asking where they came from. If you don't have a number, describe the change in plain terms. "Approximately" is an acceptable word; invented precision is not.
Keep it to about 90 seconds
Most answers land well at 60 to 120 seconds. End on the result, not on trailing detail. Expect the follow-up question; it's interest, not attack.
Practice out loud once
Reading an answer makes it familiar. Saying it makes it sayable. Practice each core story out loud, and change the wording each time so it stays yours. Answers rehearsed word for word sound rehearsed.