How to practise behavioural interviews without memorising scripts
Scripts sound like scripts. Stories do not.
Prepare five or six real stories, not fifty memorised answers. Know two things about each one cold: the result, and the specific thing you did. Then practise answering different questions with the same stories, out loud, until you can bend a story to fit without reciting it.
Stories, not answers
Behavioural questions come in endless wordings. "A time you disagreed with your manager", "a time you pushed back", "a conflict you resolved". You cannot script them all, and a script falls apart the moment the question is worded differently. A story you know well does not.
Picking your six
Choose stories that between them cover the questions that come up most:
| Story type | Answers questions about |
|---|---|
| A hard win | Achievement, impact, ownership, working under pressure |
| A disagreement | Conflict, pushing back, influencing without authority |
| A failure | Mistakes, learning, resilience |
| Leading something | Leadership, delegation, getting a team moving |
| A messy, unclear problem | Ambiguity, prioritisation, judgement |
| Helping someone else | Teamwork, mentoring, collaboration |
The result comes first
For each story, write down one line: what happened in the end, with a number if there is one. Then one line: the thing you personally did that caused it. Everything else is optional detail you can add or drop to fit the time.
Most weak answers are missing one of those two lines. They describe what the team did, and they never say how it turned out.
Bending one story to a different question
Take your hard-win story. Asked about pressure, lead with the deadline. Asked about influence, lead with the person you had to convince. Asked about prioritisation, lead with what you decided to cut. Same story, same result, different door in.
Practising out loud
- Say each story once, out loud, with a timer. Aim for about two minutes.
- Get someone, or a tool, to throw a random behavioural question at you. Pick a story and answer.
- Listen back once. Did it get to the result? Did it say what you did?
- Do it again tomorrow with different questions. Memory of the story, not the words.
Reading your notes silently does not count. Most of the skill is in saying it: where you ramble, where you lose the thread, where you say "we" when the interviewer needs "I".
What HUNT does here
HUNT's interview practice asks you questions for the role you are going for, listens to your answer, and gives you a report: relevance, structure, specificity, concision and delivery (pace, length and filler words), plus what to improve. The point is not a perfect score. It is noticing, before the real interview, that you never said how the story ended. See interview prep.
Related: Your filler words are probably not the real problem, How long should an interview answer be?, Tell me about yourself and STAR method without sounding like you memorized STAR.
Published
Back to field notes