The STAR method, with real answers
"Tell me about a time when…" is the most common opening in job interviews, and the one most people answer badly — either with a vague generalisation ("I'm always calm under pressure") or a five-minute story that never gets to the point.
The STAR method fixes both. This guide explains it, shows complete answers to common questions, and gives a way to prepare that means you're never stuck for an example.
Why interviewers ask behavioural questions
Behavioural questions rest on a simple idea: how you handled something in the past is the best predictor of how you'll handle it again. So instead of "Are you good with deadlines?" — to which everyone says yes — interviewers ask "Tell me about a time you had to deliver something under a tight deadline."
They're listening for three things: a real, specific situation, what you personally did, and what happened as a result. STAR is a structure that makes sure all three are there.
STAR in plain terms
- Situation — the context. Where you were, when, what was going on. One or two sentences.
- Task — your responsibility or the problem you had to solve. One sentence.
- Action — what you did, step by step. This is the heart of the answer and should be the longest part.
- Result — what changed because of it. A number if you have one; a concrete outcome if you don't. Optionally, what you learned.
Aim for about two minutes when spoken — roughly 200–250 words. A common mistake is spending a minute on the Situation and ten seconds on the Action. Flip that.
Example 1: "Tell me about a time you found an error others had missed"
Situation: During my internship at a data consultancy last year, the team sent a weekly sales report to a retail client.
Task: I was asked to add a new chart, which meant reading the SQL behind the report for the first time.
Action: While tracing the joins, I noticed that orders with two delivery addresses appeared twice, because the query joined orders to addresses without filtering for the primary one. I didn't want to raise it on a hunch, so I checked it by comparing distinct order counts with the report totals for three weeks — the report was consistently 4–6% too high. I wrote up the issue with the evidence and a one-line fix, and walked my supervisor through it before anything went to the client.
Result: The fix went into the next report and the client's figures were corrected for the quarter. My supervisor added a distinct-count check to the team's report template.
Why it works: the Action shows judgement (checking before raising it) as well as skill, and the Result is concrete.
Likely follow-up: "How did you tell your supervisor?" Have a sentence ready about bringing evidence and a fix, not just the problem.
Example 2: "Describe a conflict with a colleague and how you resolved it"
Situation: At a café where I was shift supervisor, another supervisor and I kept clashing over the closing checklist — she felt my shifts left the kitchen in a worse state.
Task: Our manager asked us to sort it out between ourselves before it affected the team.
Action: I asked her for coffee before a shift rather than discussing it on the floor. I asked her to walk me through what she found when she opened after my closes, and it turned out the real issue was the coffee machine being cleaned but not back-flushed. I hadn't known that step mattered so much for the morning. We rewrote the checklist together, adding photos of what "done" looks like, and I trained my closing staff on it the same week.
Result: The complaints stopped, and our manager rolled the photo checklist out to the other two stores.
Why it works: it doesn't blame anyone, it shows listening, and the fix lasted.
Likely follow-up: "What would you do if she hadn't agreed to meet?" Answer honestly — you'd raise it with the manager, with specifics.
Example 3: "Tell me about a time you failed"
This is the one people dread. Pick a real failure that wasn't catastrophic, and spend most of the answer on what you did about it.
Situation: In my first year as an accounts payable officer, I was handling year-end accruals for the first time alongside normal work.
Task: All accruals were due to the financial controller by 5 July.
Action: I underestimated how many invoices would arrive after 30 June, and two accruals were late. I told the controller as soon as I knew, gave her a revised time, and delivered them the next morning. Afterwards I listed every supplier who'd invoiced late and agreed a cut-off date with project managers for the following year.
Result: The next year every accrual was on time, and the late-invoice list is now part of our EOFY checklist.
Why it works: ownership, no excuses, and a system that prevents a repeat.
Preparing: build a story bank, not a script
You can't predict every question, but you can prepare five or six stories that cover most of them. Each good story usually answers two or three different questions.
- List the requirements in the job ad. Most ads boil down to five or six capabilities: communication, problem-solving, teamwork, working under pressure, attention to detail, initiative.
- Find a story for each. Use the last three to five years. Work, study, volunteering and part-time jobs all count.
- Write each in STAR form, briefly. Bullet points, not a script — you want to sound natural.
- Map stories to questions. Make sure you aren't relying on one project for everything.
- Say them out loud. Time yourself. Cut the Situation if you're over two and a half minutes.
Our STAR interview answers case speeds up steps 1–4: paste the job ad, attach your resume and jot down a few stories, and it returns the six questions you're most likely to be asked, a STAR draft for each built only from your material, the follow-up question to expect, and a table showing which story covers what. Then ask it in the chat to play the interviewer and push back on an answer.
Mistakes that cost points
- "We" instead of "I". Interviewers need to know what you did. Credit the team, then describe your part.
- Hypotheticals. "I would…" isn't an answer to "Tell me about a time when…".
- No result. If the story ends with the Action, the interviewer has to ask "And what happened?" — and you've lost momentum.
- Rehearsed word-for-word. It sounds robotic, and you'll freeze if interrupted. Learn the bullet points, not the sentences.
- A failure that's secretly a strength. "I work too hard" fools nobody.
After the interview
Within 24 hours, send a short thank-you that mentions one specific thing from the conversation — and, if you fumbled an answer, add the point you wish you'd made. The thank-you email case drafts one from your notes in a minute.
And if the interview goes well, the next conversation may be about money. When an offer arrives, the salary negotiation email case helps you ask for more politely, with a specific number and clarity on super.
STAR isn't a trick. It's just a way of making sure the interviewer hears the evidence. Prepare the stories, and the structure takes care of itself.