Your objective: answer any 'tell me about a time' question with a structured, concrete story that lands a clear result and lesson.
What behavioral questions are really probing
Every behavioral question is testing one or more of these soft skills. Prepare a story that demonstrates each so you are never caught without an example.
- Communication
- Decision making
- Initiative
- Organization
- Time management
- Flexibility
- Leadership
- Problem solving
- Teamwork & comfort with ambiguity
The STAR method
STAR
The structure that makes your answer land. Set the scene briefly, name the task, spend most of your words on the action you took, and finish on a quantified result with a lesson.
| Step | What goes here | Coaching cue |
|---|---|---|
| S — Situation | Briefly set the scene: the context and the challenge. | Two to three sentences. Just enough context. |
| T — Task | The specific goal or responsibility you had. | Make clear what was at stake and why it mattered. |
| A — Action | The specific steps you personally took. | The longest part. Use 'I', not only 'we'. |
| R — Result | The outcome, quantified if possible, plus the lesson. | End strong. A number or a clear takeaway. |
The two habits that fix most weak answers
1. Use 'I', not just 'we'. The interviewer must know what you personally did. 2. Always land a Result. A story with no outcome or lesson falls flat — quantify it where you can.Worked example
Describe two specific goals you set for yourself and how successful you were in meeting them. What factors led to your success?
- State the objectives clearly and up front — what exactly were the goals?
- Explain why you chose those particular goals (your motivation and judgement).
- Describe how you tracked progress or measured success.
- Cover the obstacles you overcame and what you learned along the way.
Answer: Model answer: 'In my pre-final year I set two goals — to get a summer internship, and to grow our coding club from twelve active members to forty. For the internship I gave myself a measurable plan: ten quality applications a week and two mock interviews, tracked in a simple sheet. I landed an internship by April. For the club, I ran weekly beginner workshops and a small hackathon, and we reached thirty-eight members. The factor behind both was the same — turning a vague ambition into a weekly, measurable habit and reviewing it honestly each week.' It works because it gives clear objectives, a stated reason, a tracking method, a quantified result, and a transferable lesson — exactly the four things the question asks for.
Worked example
Tell me about a time when you failed to meet a deadline. What did you fail to do? What did you learn?
- Be honest — do not claim you have never missed a deadline.
- Identify the real root cause, and own it rather than blaming others.
- Describe the concrete change you made afterwards.
- Show the change worked by referencing a later project.
Answer: Model answer: 'In a group project I owned the integration step and underestimated how long testing would take, so we submitted a day late. The root cause was mine: I planned the build but not the testing buffer. Since then I always add a testing buffer to my estimates and track progress daily rather than checking near the deadline. On my next two projects we delivered on time, and I now flag slippage early instead of hoping to catch up.' It works because of honest ownership, no blame, and a concrete change applied later — the question is testing growth, not perfection.
Worked example
Build a story bank (drill): Draft five STAR stories — one each for teamwork, leadership/initiative, a failure, working under pressure/deadline, and navigating ambiguity.
- Write only bullet points for S, T, A, R — not a full script.
- Tell one story aloud and check: was the Action in the first person?
- Check: was there a clear, ideally quantified Result?
- Re-angle each story to see which other questions it could answer.
Answer: One good story usually answers several different questions when re-angled — five well-built stories can cover almost any behavioral round.
⚠ Watch out
- Disappearing into 'we' so the interviewer never learns what you did.
- Telling a story that trails off with no result or lesson.
- Spending too long on Situation and rushing the Action.
- Blaming others or pretending you have never failed.
Takeaways
- Structure beats anecdote. S → T → A → R, with the weight on Action and Result.
- First person. 'I' makes your contribution legible.
- Land the result. A number or a clear lesson every single time.
- Five stories re-angled will cover almost any behavioral question.