Interview Sarthi
STAR method: behavioural interview answers with examples
“Tell me about a time when…” is the core of interviews in the US, UK, Canada, Australia and at most global companies. STAR turns a rambling memory into a two-minute answer.
Short answer: STAR stands for Situation, Task, Action and Result. Spend about 10% of your answer on the situation and task, 70% on what you did and why, and 20% on the result, with a number if you have one and what you learned. Keep each answer to about two minutes, and prepare six to eight real stories that you can adapt to most behavioural questions.
Use live help only where the interview's rules allow AI assistance.
What goes in each part
| Part | Share of the answer | What to say |
|---|---|---|
| Situation | About 10% (with Task) | One or two sentences of context: where, when, what was at stake. |
| Task | Your responsibility in it. Not the team's goal: yours. | |
| Action | About 70% | The steps you took and why you chose them. Say “I”. This is what the interviewer scores. |
| Result | About 20% | What changed, with a number if possible, and what you learned or would do differently. |
Three full examples
“Tell me about a time you had a conflict with a colleague.”
“Situation: in my last role at an IT services company, a developer on our team kept merging changes without tests a day before releases. Task: I was the QA lead for that release, so the risk was mine to manage. Action: instead of raising it in the stand-up, I asked him for a coffee, showed him the three production bugs from his last two merges, and asked what was getting in the way. It turned out he was given tickets late. I proposed we flag late tickets to the manager together and agreed a rule: anything merged in the last 48 hours gets a paired review. Result: the next two releases had no production bugs from late merges, and he started bringing late tickets to me himself. I learned to ask what is causing a behaviour before I correct it.”
“Tell me about a time you failed.”
“Situation: I estimated a data migration for a client at two weeks. Task: I owned the estimate and the delivery. Action: by day six I could see the legacy data was far messier than the sample I'd checked. I told my manager and the client that day rather than at the deadline, split the work into the clean 70% we could move on time and the rest, and wrote validation scripts for the messy records. Result: we moved most of the data on time and the rest a week later, and the client renewed the contract. Since then I sample at least 5% of real data before I give any estimate.”
“Tell me about a time you worked to a very tight deadline.”
“Situation: a regulator moved a reporting deadline forward by ten days. Task: I had to deliver the finance dashboard the report depended on. Action: I listed every feature, agreed with the finance head which four were essential, and moved the rest to a second phase. I automated the one manual data pull that took a day each time. Result: the report went in two days early, and the second phase shipped the following month.”
Examples to show the shape. Use your own situations and numbers; an interviewer will ask follow-ups about every detail.
Build a story bank
Most behavioural questions are variations on a few themes. Prepare one real story for each and you can answer almost anything:
| Theme | Questions it answers |
|---|---|
| Conflict | Disagreed with a manager, difficult colleague, pushed back |
| Failure or mistake | Failed, missed a deadline, got negative feedback |
| Pressure | Tight deadline, competing priorities, sudden change |
| Leadership without authority | Influenced others, led a project, mentored someone |
| Customer or user | Went above and beyond, handled a complaint |
| Learning fast | New technology, new domain, ambiguous problem |
| Data-driven decision | Decision with incomplete information, solved a complex problem |
| Initiative | Improved a process, did something nobody asked you to |
The follow-ups to expect
- “What exactly was your part?” If you said “we”, expect this immediately.
- “How did you measure that?” Know where your number came from.
- “What would you do differently?” Always have an honest answer ready.
- “What did the other person say?” For conflict stories, show you understood their side.
Common mistakes
- Too much situation. Three minutes of background and thirty seconds of action loses the interviewer.
- “We” all the way through. Politeness at home; a missing answer abroad.
- No result. End with what changed. “And it went well” is not a result.
- A hypothetical answer. “I would…” when they asked “Tell me about a time…”. Use a real event.
For how these questions are used in each country, see the US, UK, Canada and Australia guides, and the Amazon Leadership Principles guide.
Two ways Interview Sarthi helps
Practise before the interview, or get suggested answers during the call. Both start free.
Before the interview
Prep Sarthi
- A spoken AI mock interview from your CV and the job you want
- Follow-up questions, then feedback with a stronger answer
- Phone or computer, nothing to install
- Free 7-minute demo, then ₹99 for 30 days
During the interview
Live Sarthi
- Suggested answers from your CV on your screen during Teams, Zoom or Google Meet calls
- Hidden from supported Windows screen sharing; no bot joins your meeting
- Windows 10 (2004 or later) or Windows 11, with your own free Gemini key
- 30 minutes free, then ₹99 for 2 days
Use live help only where the interview's rules allow AI assistance. Looking for roles abroad? Apply Sarthi lists jobs worldwide, free. See how to practise from your resume.