Behavioural questions usually begin with “Tell me about a time when…” or “Give me an example of…”. The interviewer wants evidence of how you actually behaved, not how you think you would behave. The STAR structure helps you tell that evidence as a short, clear story.
What STAR stands for
- Situation — the context, in one or two sentences. Where were you, and what was going on?
- Task — what you were responsible for, or the problem you needed to solve.
- Action — what you did, step by step. This is the heart of the answer.
- Result — what happened because of your actions, and ideally what you learned.
A common mistake is to spend a minute on the situation and ten seconds on the action. Aim for roughly 15% situation, 10% task, 55% action and 20% result.
A worked example for an experienced candidate
Question: Tell me about a time you worked under a tight deadline.
Situation: In my last role as a business analyst, a client moved their product launch forward by two weeks.
Task: I was responsible for delivering the requirements document the developers needed to start, and it was only about half done.
Action: I listed every open requirement and met the product owner to agree which ones were essential for launch and which could follow in a second release. That cut the scope by about a third. I then booked two short daily calls with the client’s operations lead instead of waiting for email replies, and I shared sections with the developers as soon as each one was signed off, so they could start building before the whole document was finished.
Result: The development team started on time and the launch happened on the new date. The second-release items went out three weeks later. I now agree on a “must-have” list at the start of every project, so we know what to protect if timelines change.
Notice how the action is specific (“two short daily calls”, “shared sections as soon as each was signed off”) and uses “I”, not “we”.
A worked example for a fresher
Question: Describe a situation where you disagreed with a team member.
Situation: In my final-year project, our team of four was building a mobile app for booking college sports facilities.
Task: A teammate wanted to add a chat feature two weeks before our submission. I was responsible for testing, and I was worried we would not have time to test it properly.
Action: Instead of arguing in the group chat, I asked him to sit with me for fifteen minutes. I showed him our test checklist and how many items were still open. We agreed to ask our guide which mattered more for the evaluation. She said a stable booking flow was the priority, so we wrote the chat idea up as “future work” in the report.
Result: We submitted a stable app and our guide mentioned the testing in her feedback. My teammate later told me he was glad we had talked it through rather than fighting about it over messages.
College projects, internships, fests, sports teams and part-time jobs are all valid sources of STAR stories.
Build a story bank
You do not need a new story for every possible question. Prepare five or six good stories that show different strengths, then adapt them:
| Story | Can answer questions about |
|---|---|
| A deadline you met under pressure | Prioritisation, stress, time management |
| A disagreement you resolved | Conflict, teamwork, communication |
| A mistake you fixed | Ownership, learning, handling failure |
| Something you improved without being asked | Initiative, problem-solving |
| Something you learned quickly | Adaptability, learning ability |
| A time you led or coordinated others | Leadership, influence |
Write each story as four short bullet points, not a script. Scripts sound memorised; bullet points let you speak naturally.
Keep it to about two minutes
Most STAR answers should take between one and a half and two and a half minutes. Longer than that and the interviewer may lose the thread; much shorter and you probably skipped the action. The only reliable way to know how long your answer takes is to say it out loud and time it.
Practise STAR out loud
- Open the Behavioural (STAR) questions sample set in the practice room or add your own.
- Set a two-minute answer limit, and leave the question visible while you answer.
- After the session, watch each recording and use the review checklist. Under Structure, ask yourself: could someone else identify the situation, task, action and result?
- Flag the answers that ran long or skipped the result, and use Retry selected to practise just those.
Common mistakes
- Saying “we” throughout. The interviewer is hiring you. Describe your part clearly, while giving credit to others where it is due.
- No result. Always say what happened. If the outcome was not good, say what you learned and what you would do differently.
- A hypothetical answer. “I would…” does not answer “Tell me about a time…”. If you genuinely have no example, say so briefly and give the closest real situation you can.
- Inventing numbers. Use real figures if you have them; if you do not, describe the effect plainly rather than guessing.