The short answer: start with six to eight
Six to eight stories are usually enough to cover common behavioural themes while remaining realistic to prepare in depth. This is a starting point, not a universal rule.
A short first-round interview may require fewer. A senior, multi-stage or framework-heavy process may justify eight to twelve. Add examples because they close an evidence gap, not because a larger number feels safer.
Choose range, not repetition
Your portfolio should reveal different parts of your judgement and experience. Six project-success stories do not create useful coverage, even if every result is impressive.
- Success: a meaningful result you helped create.
- Failure: a mistake, setback or target you missed.
- Conflict: disagreement handled constructively.
- Ambiguity: a decision made without complete information.
- Influence: progress achieved without formal authority.
- Leadership: direction, standards or capability you improved.
- Customer or stakeholder: a need you understood and addressed.
- Change: an improvement you initiated or implemented.
Map stories to competencies
Create a simple grid with stories on one axis and likely competencies on the other. Mark one or two primary themes for each example and note any credible secondary uses.
This exposes both gaps and over-reliance. If one story is carrying five competencies, you may be stretching it. If no story shows failure or difficult feedback, the portfolio is incomplete.
Test whether each story has enough depth
A usable story must survive questions beyond the opening STAR answer. Confirm that you can explain the stakes, your responsibility, alternatives considered, decisions made, resistance encountered, metrics and lessons.
Remove examples where your individual contribution is impossible to distinguish or where you cannot discuss the details confidently. A famous project is less useful than a smaller example with clear ownership and judgement.
Reuse carefully without sounding repetitive
One story can answer different questions when the underlying evidence genuinely supports them. A difficult launch might demonstrate planning, stakeholder management or recovery from failure depending on the emphasis.
However, repeated use of the same example within one interview loop narrows the evidence available to interviewers. Treat adaptability as efficiency, not permission to rely on two stories for everything.
When you need more than eight stories
- The process includes several behavioural interviewers.
- The company uses a broad, published competency framework.
- The role is senior and requires evidence across strategy, people and execution.
- Your initial portfolio does not cover a key requirement.
- The recruiter explicitly asks you to prepare for a wide range of themes.
Prepare the smallest portfolio that gives you credible range and enough depth. More stories help only when they add new evidence.
Frequently asked questions
Should every story have a positive result?
No. Failure and setback examples are valuable when you explain your responsibility, correction and later behaviour change honestly.
Can two stories come from the same project?
Yes, if they concern distinct decisions and evidence. Make the boundaries clear so they do not sound like the same example repeated.
How much should I write?
Keep a structured set of prompts: context, responsibility, key decisions, obstacles, result, metric and learning. Full scripts are harder to adapt naturally.
The free STAR Story Builder helps you organise six to eight examples and identify the evidence that still needs work.
Get the free STAR Story Builder