How many examples should I prepare for an interview?
Three. Plus two backups. No really, that’s the answer.
I know how that sounds (gasp): like being told you can revise for an exam with three Post-it notes and a cup of tea. But the logic holds up, so let’s get into why.
The short version
Most interviews aren’t testing whether you can memorise 17 polished mini-speeches. They’re testing whether you can explain relevant experience clearly while everyone in the room pretends this is a completely normal way to assess a human being (spoiler, it isn’t).
A solid starting point:
- 3 core examples you know inside out.
- 2 backups for when the interviewer veers off-script.
- A few rough notes on other stuff. Not full answers, just enough to not freeze if things get dicey.
Your core three should be your strongest, most flexible stories. Ones that can answer several different questions depending on the angle. Your backups exist purely to stop you panicking when some smartass (the interviewer) asks about the one thing you didn’t prepare for. They don’t really need polish. They just need to be real and clear enough to explain on the spot.
This beats turning up with twenty rehearsed answers. That sounds thorough but usually just means more material to frantically scroll through in your own head while someone across the table asks you to “tell us about a time you influenced a stakeholder.” Lovely.
Why more examples can backfire
Preparing an answer for every possible question feels productive. It scratches the “I’ve definitely revised properly” itch we all remember from school. But past a point, it stops helping.
You end up with a mental prison instead of a set of stories. Lots of effort, not much readiness. Interviews don’t reward whoever shows up with the biggest collection of memorised answers. They reward whoever can recognise what’s actually being asked, pick a relevant example, and explain it calmly enough that the interviewer can follow along.
Prepare too many and you tend to get one of these instead:
- You freeze trying to choose between five similar stories.
- You sound rehearsed because you’re reciting rather than talking.
- Half your examples turn out to be irrelevant to the actual role.
- You spend prep time on quantity instead of sharpening your best three.
- You burn out on prep and end up winging it anyway, a very human outcome, if not an ideal one. And one that is familiar to me personally.
Fewer, sharper stories are easier to remember, easier to bend to different questions, and considerably kinder to your sanity during prep and on the day.
What your three core examples should cover
Aim for variety, so the same three stories can flex across most likely questions.
- A problem-solving or improvement story. Something wasn’t working. Unclear, inefficient, messy, mildly annoying in the way office problems usually are, and you helped fix it. Good for questions on initiative, ownership, attention to detail, or working independently.
- A people or communication story. Working with others, handling disagreement, explaining something clearly, dealing with a customer. “Difficult conversation” doesn’t have to mean a boardroom showdown with someone called Malcolm, it might just mean explaining something to a confused person without making them feel stupid. That counts.
- A pressure or adaptability story. Getting something done despite a deadline, a change of plan, or information arriving late. Useful for prioritising, resilience, and handling pressure.
None of these need to involve saving the company or delivering a TED talk while waving your arms around like you read one too many body language books. They need to show what you did, why it mattered, and what the interviewer should take away. That’s the whole job.
What actually makes an example “good”
A strong example is specific enough to be believable and flexible enough to be reused. It needs:
- A clear situation
- A real problem or challenge
- Something you personally did
- A result, outcome, or lesson
- Some relevance to the job you’re applying for
The weakest link is usually the result. People remember what happened but not what changed afterwards. Understandable, since real life rarely hands you a tidy metric.
A result doesn’t need a number attached. It can be: the customer stopped being confused, the team avoided a delay, a process got clearer, someone knew what to do next, a mistake got fixed. Numbers are great when you genuinely have them. Don’t invent one just because you heard you have to.
One story, several questions
A good example earns its keep by answering more than one question.
Say your story is: you helped organise an event after a last-minute change of plan. That single story can cover:
- “Tell me about a time you worked under pressure” → focus on the deadline and staying composed.
- “Tell me about a time you solved a problem” → focus on what had gone wrong and what you did about it.
- “Tell me about a time you worked with others” → focus on coordination and communication.
- “Tell me about a time you had to adapt” → focus on the change of plan and how you adjusted.
Same story, different angle. That’s the whole deal of preparing flexible evidence instead of trying to predict every question in advance, you can’t, and the attempt will eat your sanity. Just don’t dump the whole story into every answer and hope the interviewer spots the relevant bit themselves. Make the point obvious; remember they are interviewers.
When you might need more than five
Sometimes three-plus-two genuinely isn’t enough:
- Multiple interview rounds
- A role with many distinct competencies
- Senior or management positions
- Explicitly competency-based interviews
- Technical, public sector, graduate scheme, or assessment-centre formats
In those cases, build in layers rather than polishing everything equally:
- Core stories: your 3 strongest, most likely to matter.
- Backups: 2–5 more for common themes.
- Story bank: rough notes on everything else, for if needed.
That gives you range without turning prep into an unpaid second job.
Choosing the right examples for this specific role
Your best examples aren’t necessarily your most impressive ones, they’re the ones that match the job.
Start with the advert. What keeps coming up: communication, problem-solving, organisation, customer service, independence, pressure, attention to detail?
Then check your CV or notes against it:
- Which experiences actually show those skills, rather than just being adjacent to them?
- Which examples show you doing something, not just being present?
- Which have a clear challenge and a clear outcome?
- Which could plausibly answer more than one likely question?
You’re not writing a script. Scripted answers tend to sound stiff, or like you’re reading from an invisible government leaflet. You’re choosing the evidence most likely to make you sound clear, relevant, and like the actual person you are.
Quick checklist before you walk in
- What are your 3 strongest examples for this specific role?
- What does each one prove?
- What actually happened, and what did you personally do?
- What changed afterwards?
- Which likely questions could each one answer?
- Where are your weaker areas, and do you have a backup for them?
If you can answer those, you’re already ahead of most people walking in with a bunch of memorised answers and no idea which one to use.
The actual answer
Prepare 3 strong core examples and 2 backups. That covers most behavioural and competency questions. Build a wider story bank if the process demands it, but more examples isn’t the same as better preparation. At some point you’re not getting readier, you’re just getting tired.
The goal isn’t to prepare an answer for every possible question. It’s to walk in knowing which stories are worth using, what each one proves, how to bend them to different questions, and where your gaps are. Knowing when to stop preparing is part of being prepared.
Need help choosing your interview examples?
If you’re stuck working out which examples to use, Interview Decoded will do a first pass for you. Paste in the job advert and your CV or rough notes, and it builds a focused prep pack: strongest stories to practise, likely questions, possible gaps, and a clear stopping point. All tailored to that specific job ad.