"Tell me about a time you disagreed with a teammate." "Describe a deadline you almost missed." These are behavioural questions, and almost every interview has a few. Interviewers ask them because past behaviour is a decent guide to future behaviour, and because stories reveal more than claims such as "I am a good communicator".
The challenge is that most people ramble, or answer with what they would do in general. A simple structure fixes both.
What STAR stands for
- Situation: the context, in one or two sentences
- Task: what you were responsible for
- Action: what you personally did, step by step
- Result: what happened, and what you learned
Aim for roughly a minute and a half to two minutes in total. Spend most of the time on Action and Result, because that is where the evidence is.
A worked example
Question: "Tell me about a time you had to learn something quickly."
Situation: "In my final year, my team's project needed a login system, and nobody on the team had built one."
Task: "I volunteered to build it, with two weeks before our first demo."
Action: "I spent the first two days reading the documentation and a few tutorials, then built a small prototype to test the approach. I asked a senior for a review of my security choices, and wrote down what I learned in a short note for the team."
Result: "We demoed on time, the login worked for all thirty users in our test, and my senior's review caught a password-handling mistake before we shipped. I now know how I like to learn: build something small first, then ask for feedback."
Notice the "I". Interviewers want to know what you did, not only what the team did. Notice also the specifics: two weeks, thirty users, a real mistake that got caught.
Build a story bank
You cannot prepare for every question, but you can prepare five or six stories that fit many of them. Look through your projects, internships, college life and part-time jobs for moments like these:
- A project you are proud of
- Something that went wrong, and what you changed
- A disagreement or a hard teammate
- A time you took initiative without being asked
- A time you learned something fast
- A time you handled pressure or a tight deadline
Write each as four short bullet points, one per letter. Then practise telling it aloud, without reading from the page.
Reusing one story for different questions
A good story can answer several questions with a different emphasis. The login story above could answer "a time you learned quickly", "a time you took initiative" or "a time you accepted feedback". Listen to what the question is really asking, then stress the part of the story that fits.
Common mistakes
- Starting with a long background. Spend one or two sentences on Situation. Interviewers get impatient with a ten-minute set-up.
- Talking about "we" throughout. Credit your team, but make your own actions clear.
- Skipping the result. An answer that ends with "and then we finished" is weak. Say what changed, with a number if you can.
- Choosing a story that makes you look bad and ends there. Failure stories are fine, even good, but show what you learned and did differently afterward.
- Making up details. Interviewers ask follow-up questions. A true story survives them, and an invented one usually does not.
- Answering too short. One sentence does not give them enough to judge.
If your mind goes blank
It is fine to pause. Say, "Let me think of a good example," and take a few seconds. If you honestly have no direct experience, use a related one from college, a hobby or volunteering, and say so: "I have not faced this at work yet, but in my college project..." Interviewers hiring freshers expect this.
A practice routine
- Pick six stories and write them in STAR bullets.
- Practise each out loud once a day for three days, timing yourself.
- Ask a friend to throw random behavioural questions at you, and notice which story you reach for.
- Record yourself once, and watch it. Cut filler words and trim anything that runs past two minutes.
Do this for a week and the structure becomes automatic. In the actual interview you will not be reciting a script, you will be telling a true story that happens to have a clear beginning, middle and end.
