How many STAR stories should you prepare for an interview?
Trying to prepare a separate answer for every behavioural question leaves you with a pile of scripts. Worse, those rehearsed answers may not fit the questions you are asked.
Prepare a small bank of real experiences instead. Together, they should cover the parts of the role that matter most.
Quick answer: For most professional interviews, prepare six to eight strong STAR stories. Choose examples that collectively cover delivery, problem-solving, collaboration, influence, adaptability, leadership and learning. Senior, specialist or multi-stage interviews may justify eight to ten. There is no universal required number, so adjust your preparation to the role and interview format.
How many STAR stories should you prepare for an interview?
For most professional interviews, six to eight strong stories is a sensible starting point. You get enough range to cover the role without trying to memorise dozens of answers.
The right number still depends on the interview. A short screening call may need fewer examples, while a senior role or multi-stage process may need more. What matters is whether your stories cover the work the employer cares about.
Quick preparation guide
- Prepare six to eight core stories for a typical professional interview.
- Consider eight to ten for a senior, specialist or multi-stage process.
- Cover the role’s main capabilities rather than every possible question.
- Include at least one setback, disagreement or learning example.
- Keep a second example for the two or three most important capabilities.
- Prepare evidence notes, not fully memorised scripts.
- Never invent a number or outcome to fill a gap.
Before choosing your final set, use the scorecard in How to Choose Your Best STAR Interview Examples.
Why six to eight is a useful starting point
There is no official number of STAR stories that every candidate must prepare.
Structured interviews are built around job-related criteria. The US Office of Personnel Management says candidates are asked predetermined questions and assessed against the same standards. CIPD also recommends basing structured interviews on the requirements of the role.
Your story bank needs enough examples to cover several capabilities, with a few alternatives for the most important ones. Six to eight stories usually does the job without creating too much to rehearse. Treat that number as a preparation guide, not a hiring standard.
| Interview situation | Practical starting point |
|---|---|
| Short screening interview | 3 to 4 stories |
| Typical professional interview | 6 to 8 stories |
| Senior or people-leadership role | 8 to 10 stories |
| Technical or specialist process | 6 to 10 stories |
| Multi-stage process | 8 to 12 stories across all stages |
| Early-career interview | 4 to 6 stories |
Six well-supported examples are more useful than twelve vague stories that all demonstrate the same capability.
Build coverage, not a script library
Start with the role description. Identify the five or six capabilities the employer is most likely to assess, then select stories that cover them.
| Story area | Possible question | Evidence to prepare |
|---|---|---|
| Delivery | Tell me about a time you delivered under pressure | Constraints, planning decisions and verified result |
| Problem-solving | Describe a difficult problem you solved | Investigation, options and reasoning |
| Collaboration | Tell me about a time you worked across teams | Different interests, your contribution and shared outcome |
| Influence | Tell me about a time you influenced without authority | Resistance, influence method and observable response |
| Adaptability | Describe a time plans changed | What changed, how you reassessed and what you did next |
| Leadership | Give an example of when you took the lead | The gap, direction you created and how others were enabled |
| Setback | Tell me about a mistake or failure | Accountability, corrective action and learning |
Replace any area that is less relevant with a capability from the actual role, such as customer service, commercial judgement, safety, data analysis or coaching.
For question-specific prompts, read 15 Behavioural Interview Questions and the Evidence You Need for Each.
One story can answer several questions
A good work example often shows more than one capability.
Suppose two teams were working from conflicting assumptions during testing. You spotted the problem, clarified the constraints and helped them agree on one approach.
The same factual experience could support:
- problem-solving, by focusing on how you diagnosed the issue
- influence, by explaining how you gained agreement without authority
- collaboration, by showing how you brought different teams together
- delivery, by describing how resolving the blocker allowed work to continue
You can change the emphasis, but not the history.
| Question focus | Emphasise | Keep unchanged |
|---|---|---|
| Problem-solving | Investigation and reasoning | The actual problem and decision |
| Influence | Resistance and persuasion | Who made the final decision |
| Collaboration | Coordination and shared goal | Your individual contribution |
| Delivery | Timing and recovery action | The verified result |
It is fine to reuse a story when it genuinely fits. Just do not force the same example into every answer.
Prepare two levels of detail
Do not memorise complete paragraphs. Prepare a short recall card and a fuller evidence record.
Recall card
Story title:
Capabilities:
Situation in one sentence:
My main action:
Result:
Evidence:
Evidence record
Situation and why it mattered:
My responsibility:
Constraints or competing interests:
Actions I took and why:
Who else contributed:
Observable result:
Evidence supporting the result:
What I cannot verify:
What I learned:
Your notes are there to preserve the evidence and sequence, not give you a word-for-word script. Ascending Careers lets you save the original work moment and shape it into an interview story later without changing the facts.
For the full structure, read The STAR Interview Method: A Practical Guide With Credible Examples.
Check your story coverage
A simple matrix makes gaps and repeated examples easier to spot.
| Story | Delivery | Problem-solving | Collaboration | Influence | Adaptability | Learning |
|---|---|---|---|---|---|---|
| Resolved conflicting testing assumptions | ✓ | ✓ | ✓ | ✓ | ||
| Replanned after a dependency changed | ✓ | ✓ | ✓ | ✓ | ||
| Improved an approval process | ✓ | ✓ | ✓ | ✓ | ||
| Corrected an inaccurate status report | ✓ | ✓ | ✓ | ✓ | ||
| Managed a customer escalation | ✓ | ✓ | ✓ | ✓ | ✓ | |
| Coached a colleague through a new process | ✓ | ✓ | ✓ | ✓ |
These examples are illustrative. Replace them with your own experiences.
The matrix is the easy part. Finding enough specific work moments to fill it is harder. Capture those moments as they happen and Ascending Careers can help you find the ones that fit a role when an interview comes up.
Look for three issues:
- A blank capability column: add or replace a story.
- Several near-identical stories: choose a different type of experience.
- A story with weak evidence: clarify the result or select a stronger example.
Prepare alternatives for high-priority capabilities
Keep a second example for the two or three capabilities most important to the role.
For a project management role, these might be stakeholder influence, risk management and delivery under constraints. For a people-leadership role, they might be coaching, difficult decisions and strategic alignment.
A backup helps when the interviewer asks, “Can you give me another example?” It also gives you another option when your first story is confidential or too similar to one you have already used.
Include a setback or incomplete result
Do not fill your story bank with smooth successes. Behavioural interviews often include questions about mistakes, difficult feedback, failed assumptions or changing priorities.
Prepare at least one example showing accountability and corrective action. Do not disguise a strength as a failure.
You can also use an example where the final outcome was not yet known:
I identified that two approval paths were creating duplicated work and proposed a simpler process. The operational leads accepted the recommendation, and it was included in the implementation plan. I left before post-launch data became available, so I would not claim a verified reduction in processing time. The supported result was agreement and implementation of the revised design.
Stop the result where the evidence stops.
Signs that you need more stories
Add another example when:
- most questions would force you to use the same project
- an important role capability has no supporting evidence
- all examples involve routine work with little judgement
- you have no setback, conflict or learning story
- your only relevant example is difficult to discuss safely
- you cannot provide a second example for a critical capability
Signs that you have prepared too many
Reduce your story bank when:
- you confuse facts between examples
- several stories demonstrate the same thing
- you are rehearsing scripts instead of understanding the evidence
- you are polishing low-relevance examples
- you feel pressure to invent stronger results
If you have more than ten or twelve possible stories, prepare the strongest examples fully and keep the rest as brief backup notes.
A 30-minute preparation exercise
- Identify the five or six capabilities most likely to be assessed.
- List ten possible situations from work, study, volunteering or community experience.
- Select six to eight based on relevance, personal action, complexity and evidence.
- Place them in a competency matrix and identify gaps.
- Create a recall card for each selected story.
- Practise adapting the emphasis while preserving the facts.
Compare your draft responses with Weak Versus Strong STAR Answers: 10 Before-and-After Examples.
Frequently asked questions
Is six STAR stories enough for every interview?
No. Six is a practical starting point. A short interview may require fewer, while a senior or multi-stage process may require more. Use the role and interview format to decide.
Should I prepare one story for every question?
No. Prepare varied experiences that cover the likely competencies. One story can answer several related questions when you adjust the emphasis without changing the facts.
Can I use the same story twice?
Yes, when it is clearly the strongest evidence. Briefly acknowledge that you are returning to the same situation and focus on a different part of your behaviour.
How many backup stories should I have?
Keep one alternative for the two or three capabilities most important to the role. These can remain brief unless the process is extensive.
Do all stories need a positive result?
No. A setback or incomplete result can be credible when you explain your actions, accountability and learning. Do not present an unknown long-term impact as confirmed.
How long should each STAR answer be?
There is no fixed duration. Give enough context to make the story understandable, spend most of the answer on your actions and finish with the supported result. Leave room for follow-up questions.
Prepare a small bank of strong evidence
You cannot predict an interview word for word. You can walk in with enough real evidence to answer thoughtfully.
For most professional roles, begin with six to eight stories. Choose examples you can support, and keep a backup for the capabilities that matter most to the role.
Start building your career story bank