Most people preparing for a competency interview know what STAR stands for. Fewer have a set of stories ready to put into it. The structure is the easy part. The hard part is sitting in front of an interviewer, hearing "Tell me about a time you disagreed with a colleague", and having a real example come to mind straight away.
That is what a story bank is for. This guide covers how to build one from your own experience, which kinds of story most UK interviews ask for, and how to keep it useful from one application to the next. There is a free template you can copy into Google Sheets or print as a one-pager.
A quick definition. The STAR technique is a way of answering questions about something you have done before. You give the Situation, your Task, the Action you took and the Result, spending most of your time on the Action. If you want the method itself in more depth, with worked answers and timings, our STAR method guide covers it.
What a story bank is, and why STAR alone is not enough
A story bank is a short written list of real examples from your working life (and sometimes outside it), each one noted in STAR form and tagged with the kinds of question it can answer. It is not a set of scripts. It is closer to an index: enough on each story to bring the detail back, and enough tagging to find the right one quickly.
STAR on its own is a shape. It tells you how to tell a story once you have chosen it, but it does not choose it for you. Without a bank, most of the effort in an interview goes on recall, searching through years of work for something that fits, and only a little goes on telling it well. With one, the recall has already happened at a desk, without pressure, and the interview is mostly about delivery.
A bank also lasts. Stories written for one application mostly still work for the next, so the effort adds up rather than starting from nothing each round.
How many stories you need
Our STAR guide suggests eight to ten stories as a starting point, and that still holds. It is usually enough to cover a full interview without repeating yourself, with a spare for "Can you give me another example?"
A bank can grow beyond that, though. Think of eight to ten as the number you take into any one interview, chosen from a larger bank that might hold fifteen or twenty over time. The larger pool means you can pick the best fit for each role rather than stretching the same few stories to cover everything.
Short on time? Start with one story per slot (below) and add the rest as you go.
Finding stories in your own experience
The stories need to be yours and they need to be true. Interviewers often ask follow-up questions, and a story you have borrowed or exaggerated tends to come apart at the second or third one. So the job here is remembering, not inventing.
Go through each role you have held, one at a time, and use prompts like these:
- What had a beginning and an end? A launch, a fix, a migration, an event, a difficult month. Projects make better stories than ongoing duties.
- What went wrong? Missed deadlines, complaints, errors, things that had to be redone. These are often the most useful stories you have.
- When did someone disagree with you, or you with them? Including the times you turned out to be wrong.
- What did you change that is still in place? A template, a check, a rota, a way of handling something.
- When were you the person others came to? Covering for a manager, training a new starter, being the one who knew the system.
Look outside paid work as well, particularly early in your career: volunteering, a society role, caring responsibilities, a side project, something you organised. Most interviewers accept these if your part in them is clear.
Evidence helps memory. Old emails, performance reviews, project trackers and your CV will bring back details you have forgotten. Note where each fact came from, for the follow-up questions. If you want a method for working from your CV specifically, our guide to turning CV bullets into interview stories goes through it step by step.
At this stage, just list. A one-line title per story is enough. Sorting comes next.
The six slots most UK interviews cover
Behavioural questions vary between employers, but most come back to a few themes. UK public-sector adverts often name the behaviours they will assess, and private employers signal theirs in the job description, but the themes overlap a great deal. Six slots make it easy to see where you are thin.
| Slot | What it shows | Typical question phrasing |
|---|---|---|
| Conflict or disagreement | How you handle tension without damaging the relationship | "Tell me about a time you disagreed with a colleague or manager." "Describe a difficult working relationship and how you handled it." |
| Failure or mistake | Ownership, honesty, and what you changed afterwards | "Tell me about a mistake you made." "Describe a time something did not go to plan." |
| Delivery under pressure | Prioritising, staying organised, getting it done | "Tell me about a time you had to meet a tight deadline." "Give an example of managing competing priorities." |
| Leadership or influence without authority | Getting people to move when you are not their manager | "Tell me about a time you led a piece of work." "Describe a time you persuaded someone to change their approach." |
| Stakeholder or customer | Understanding what other people need and managing their expectations | "Tell me about a time you dealt with a difficult customer." "Give an example of working with someone senior to get a result." |
| Improvement or change | Spotting a problem and fixing it, not just working around it | "Give me an example of when you improved a process." "Tell me about a time you introduced a new way of working." |
Keep an "other" slot for stories that do not fit neatly, such as learning something quickly, working with data, or a decision you had to make with incomplete information. These often turn out to be the answer to the question you did not expect.
One story can often fill more than one slot. A project where you pushed back on a deadline, agreed a smaller scope with a senior stakeholder and then delivered it could sit under conflict, stakeholder and pressure. Tag it with all three, but give it one primary slot so you notice if every slot is relying on the same story.
Write each story as four lines, not a script
For each story, write one or two lines per part:
- S: What was the problem?
- T: What were you trying to achieve, or what were you responsible for?
- A: What did you do, step by step? Three to five short lines, each starting with "I".
- R: What changed, and how do you know?
Four short lines are much easier to hold on to under pressure than a polished paragraph, and a script is hard to recover if the interviewer interrupts.
Two extra fields make the bank more useful than a list of STAR notes:
- Evidence. Where the result came from: a report, an email, a dashboard, feedback from a named person. If you cannot point to anything, describe the result in plain terms rather than estimating a number.
- Competencies. The words a job description might use for this story, such as "stakeholder management", "attention to detail" or "resilience". This is what lets you search the bank later.
A worked example (illustrative)
This example is fictional. It is here to show the shape of a bank entry, not wording to reuse.
Priya is an exams officer at a secondary school in the Midlands. Going through her current role with the prompts above, one story comes out of "What did you change that is still in place?"
- Slot: Improvement (also fits stakeholder, pressure)
- Working title: Access arrangements tracker
- S: Access arrangements for exam candidates (extra time, readers, separate rooms) were tracked on paper forms held by different staff, and two students were nearly seated without their arrangements in the mock exams.
- T: I wanted one up-to-date record that invigilators and the SENCo could both rely on before the summer series.
- A:
- I listed every arrangement from the paper forms and checked each against the approved records with the SENCo.
- I built a shared spreadsheet with one row per student and a column for each room and session.
- I agreed with the SENCo that only she would approve changes, and I would update the sheet.
- I printed a room-by-room list for invigilators each morning of the series.
- R: Every candidate with an arrangement was seated correctly across the summer series, and the head of centre asked for the same tracker to be used the following year.
- Evidence: Seating plans and the end-of-series review email from the head of centre.
- Competencies: Process improvement, attention to detail, working with others, organisation.
Notice that the result has no invented percentage. "Every candidate seated correctly" is specific and checkable, which is more useful in a follow-up than a figure Priya would have to defend.
How to use the free template
We have put the bank layout into a free template you can use straight away, no sign-up needed. Download the story bank template (CSV) to import into Google Sheets or Excel, or use the printable version if you prefer paper.
The columns follow the four lines above, plus evidence, competencies, the date you last said the story out loud, and notes for follow-up questions you expect.
The template has one filled example row and five blank ones. To use it:
- Fill in the title, slot and role for every story on your list first, without the STAR detail. This shows you which slots are empty before you spend time writing.
- Write the four lines for one story per slot.
- Add evidence and competencies for each.
- Say each story out loud once and fill in the date.
- Add rows as you go. A filter on the Competencies column makes the bank searchable.
Mapping your bank to a job description
Before each interview, take the job description and pull out every skill or behaviour it mentions. Phrases like "builds effective relationships", "manages competing priorities" or "comfortable with ambiguity" are usually close to the questions you will be asked.
Then, for each one:
- Search the Competencies column for a matching word or close equivalent.
- Pick the best story, not the most impressive one. A small project you led usually makes a better answer than a big one where your part was minor.
- Write the story ID next to the competency, so you have a short list like "Stakeholder management: S04. Resilience: S07."
- Check you are not using one story for more than two competencies.
- Note any gaps. A gap is a prompt to go back through your experience, not to stretch a story that does not fit.
If the employer names a specific framework or set of behaviours in the advert, use their wording as the competency tags for this application. It makes the match easier to see.
If you have very little time, work through those steps for the competencies named in the advert only, and fill the rest of the bank afterwards.
Keeping the bank current
A bank is only useful if the stories in it are still easy to recall, and the detail of a project fades quickly once you have moved on. Add a story when a project ends, while the numbers and names are easy to find. After each interview, note which stories you used and which follow-up questions caught you out. Swap older stories for recent ones that cover the same slot, and update a result if something you changed is still in use a year later. Before an interview, check the Last practised date and run through anything you have not said aloud for months.
Common story bank mistakes
Collecting, not choosing. A bank of thirty stories is not more useful than a bank of ten if you cannot remember which is which. Keep the working titles distinct and the tags accurate.
Every slot pointing to the same project. One strong project can cover several competencies, but if every answer comes back to it, the interviewer may wonder what else you have done.
No failure stories. Many people leave this slot empty because it is uncomfortable. It is also one of the most commonly asked themes, and it is much harder to think of a good one on the spot.
Rounding results upwards. If you are not sure of a figure, check it or describe the result without one. The bank is where you catch this, not the interview.
Only writing it down. A story you have never said aloud almost always comes out longer and less clear than you expect. The Last practised column is there for a reason.
Story bank FAQ
Is a story bank the same as a list of STAR examples?
Mostly, with two additions: each story is tagged with the competencies it can cover, and it records where the result came from. Those two fields are what make it reusable across different applications.
How long should each entry be?
Short. One or two lines each for Situation, Task and Result, and three to five short lines for Action. If an entry runs to a full page, it is probably a script.
What if I have no story for one of the six slots?
Go back through the prompts for that slot specifically, including outside work. If there is still nothing, a smaller example is fine. An everyday disagreement handled well is a better answer than a dramatic one you have to stretch.
Keeping your bank in one place
A spreadsheet works, and the free template is a good place to start. It does take some effort to keep up, particularly the competency tags.
That is the part Career Canvas is built for. Send us your CV and we turn every project into a STAR story, laid out on one screen. Pick a competency, such as stakeholder management, and the projects that fit light up, each with a one-line reason why.
We don't invent anything. A result only appears where you can back it up, and you approve every word before it goes live.