Behavioural interview questions ask for examples: a difficult customer, a missed deadline, a disagreement or a time you learned quickly. STAR gives your answer a structure: Situation, Task, Action and Result. It is a way to organise evidence, not a requirement to speak in four labelled sections or a formula that guarantees an offer.
Start with a story bank, not a script
Choose a few real experiences that cover different skills. Paid work is not the only source: study, volunteering and personal projects can be relevant when you explain the context honestly. Record a short outline for each story and the competency it demonstrates. Avoid using one impressive example for every question, especially when it does not answer what was asked.
- Collaboration: how you agreed responsibilities or resolved a misunderstanding.
- Judgement: how you compared options with limited time or information.
- Learning: how you sought feedback and changed your approach.
- Accountability: what you did when your own decision did not work.
Story card 1 — Situation and Task
Give only enough background to make the challenge understandable. Explain what needed to happen, what made it difficult and what you personally owned. Long company histories and unexplained internal acronyms make the interviewer work harder without adding evidence.
Illustrative scenario: “During a student group project, two research sections overlapped and we were close to the submission date. I was responsible for combining the draft, so I needed to help the group agree a clear division of work.” This establishes the constraint and the candidate's responsibility without pretending it was a management role.
Story card 2 — Action
Spend most of the answer on decisions and actions. Explain why you chose that approach, who you involved and how you handled obstacles. Use “I” for your contribution and “we” for collective work. Both can belong in the same honest answer.
Continuing the illustrative scenario: “I compared the overlapping sections against the marking criteria and proposed separate questions for each contributor. I asked the group to challenge the split, then wrote down the agreed owners and set a check-in before final editing.” This gives the interviewer concrete behaviour to explore. Only use details like these if they reflect your own experience.
Story card 3 — Result and reflection
Describe what happened, then explain what you learned. Results can include an accepted deliverable, clearer responsibilities or feedback from a customer. Use figures only when you know their basis. If the outcome was mixed, say so; a thoughtful account of a mistake can show accountability better than a perfect story with no credible detail.
In the example, the result might be that the group submitted a coherent report on time, but the last review was rushed. The reflection could be to agree ownership earlier and schedule a midpoint review. Do not invent a grade or claim that one person's action caused the entire outcome.
Rehearsal: three rounds, three different goals
- Round one — clarity: tell the story aloud and ask a listener to identify the challenge and your action. Remove details that do not help.
- Round two — evidence: let the listener ask “Why?”, “What did you do personally?” and “How do you know it worked?” Identify anything you cannot support.
- Round three — flexibility: answer a differently worded question with the same experience only if it genuinely fits. Practise a shorter version and leave space for follow-up.
Record yourself only if you are comfortable doing so, and delete recordings you no longer need. Notes should contain prompts, not a paragraph you intend to recite. A natural answer can pause, clarify or correct a detail.
When the question catches you off guard
Ask for a moment to think or clarify the skill the interviewer wants to explore. If you lack direct experience, say that and offer a related example, or ask whether a hypothetical approach would be useful. Keep a hypothetical answer clearly separate from something you actually did.
Before the interview, choose one success story and one learning story. Check that both protect colleagues' and customers' privacy. Your aim is not to sound flawless; it is to make your reasoning and contribution easy to understand.