The STAR Method: How to Answer Interview Questions With an Example
"Tell me about a time when..." is not a memory test. The interviewer is checking whether you can describe your own work clearly: what the situation was, what you did about it, and what happened. STAR is just a running order that stops you from rambling.
What the four parts are for
- Situation: the context, in one or two sentences. Where you were and what was going on.
- Task: what you specifically were responsible for. This is the part people skip, and it is what separates your contribution from your team's.
- Action: what you did, step by step, in the first person. This is the longest part by far.
- Result: what changed. A number if you have one, and a plain outcome if you do not.
The proportions matter more than the letters
A common failure is spending ninety seconds setting the scene and ten on what you did. Roughly: a short Situation and Task together, then Action taking most of the answer, then a clear Result. The interviewer is hiring the Action.
Say "I", not "we". Group projects make this feel impolite, but an interviewer cannot assess a "we". Credit the team once, then describe your own part.
Situation: In my final year our group project had four people and a two-week deadline for a data report. Task: I took responsibility for the analysis and for getting everyone's sections into one document. Action: I set up a shared repository so we stopped emailing versions around, wrote the cleaning script myself, and set an internal deadline three days before the real one so we had time to fix problems. When one member fell behind, I split their section into two smaller pieces and took one. Result: We submitted a day early, and the marker specifically noted the consistency of the report. I now start any group work by agreeing where files live.
When you have no impressive numbers
Most students do not have a revenue figure, and inventing one is the fastest way to fall apart under a follow-up question. A result can be a decision that got made, a process that got adopted, time saved, an error caught before it shipped, or something you would now do differently. Scale and context work when a metric does not: "used by about two hundred students on my course" is concrete without being invented.
Prepare stories, not answers
You cannot predict the wording of the question, so do not memorise responses. Prepare five or six real episodes from your studies, jobs, projects or societies, each with the four parts clear in your head. Most behavioural questions can be answered from a small set of good stories: a conflict, a failure, a deadline, a time you led something, a time you learned something fast.
Then listen to the actual question and choose. The same project can answer "tell me about teamwork" and "tell me about a conflict", told with a different emphasis.
The failure question
"Tell me about a failure" is not a trap and it is not an invitation to a fake weakness. Pick something that genuinely went wrong, keep the Situation short, be straightforward about your part in it, and spend the Result on what you changed afterwards. An answer with no real failure in it reads as either dishonest or as someone who has never been stretched.
Read nextHow to Write a Cover Letter That Gets ReadLearn how to write a cover letter recruiters actually read — a simple structure, strong openings, and honest proof, with examples for students.Say it out loud before the day
Written STAR answers sound written. Say each story aloud once and you will find the version that sounds like you, which is the one that survives a follow-up question. That is the whole point: a story you actually lived can be questioned from any angle, and a scripted one cannot.
The questions you'll face for the role, with answers built from what you have actually done.
Practise with your real experience →