the interview story bank

five stories. twenty-five answers. one page you actually open before the call.

twenty-five questions in here. all of them come back to the same five stories.

build five, answer twenty-five

stop memorising fifty separate answers. write five real stories in bullets, then change which part you emphasise depending on what you are asked.

  • one story per category. five in total, drawn from at least three different projects.
  • bullets only. enough to trigger memory, never enough to recite.
  • reuse a story across several questions by changing the emphasis, not the facts.
  • target 60–90 seconds per answer, then stop and let them ask follow-ups.
the quick test

if anyone else on your team could tell the same story word for word, it is too generic. add the constraint you were under, the call you made, and what it cost you.

the framework

star, plus the two parts most people leave out.

  • situationwhat was happening. two sentences, maximum.
  • taskwhat was specifically yours to own.
  • actionwhat you personally did. roughly half your airtime.
  • resultwhat changed. a number, deadline, stakeholder, or before and after.
  • reflectionwhat you did differently afterwards.

the boxes below are sized to match. action gets the most writing room on purpose.

the two you'll definitely get

these open almost every interview, and neither is a star story. write them once and the rest of the conversation gets easier.

“tell me about yourself”

60 to 90 seconds, three beats.

your current role or programme and what you focus on. one sentence.
the two or three moves that got you here, and why each one made sense at the time.
what you want next, and why it is this role rather than a similar one.

“why this role / why us”

three beats again.

what the job actually does day to day. proof you read past the title.
where you have already done a smaller version of it. point at one of your five stories.
what you are hoping to build or learn here. specific enough to be believable.
the most common mistake

do not narrate your cv from top to bottom. they have it open in front of them. give them the thread that connects it instead.

your five stories

bullets, not paragraphs. tap a story to open it — everything saves as you type.

the question map

map the question to the story before the interview, not during it. most questions are one of these five in disguise.

if a question genuinely fits none of the five, answer it directly and briefly. forcing a story into the wrong question is more obvious than not having one.

your proof points

the number is the part they remember and the part you are most likely to fumble under pressure. write all five down once, then say them out loud.

three rules for numbers
  • give the baseline. a number with nothing to compare it against sounds invented.
  • give the window. “six hours a week” and “six hours, once” are very different claims.
  • only use numbers you can defend if they ask how it was measured. a modest number you own beats a large one you cannot explain.
no numbers? use one of these instead

scale (how many people, accounts, or files), stakeholders (who signed off), constraints (what deadline or budget), or a concrete before and after. “nobody knew who owned it; afterwards, one person did” is a real result.

the quality check

run each of your five stories through this before you practise out loud. most weak answers fail on the same three lines.

the 24-hour prep

in order. two hours, once, beats re-reading your cv six times.

  1. read the job description. highlight the four to six behaviours the role actually rewards.15 min
  2. choose your five stories. check they are not all from the same project.10 min
  3. fill the star boxes in bullets only. do not write paragraphs.45 min
  4. add one proof point per story and test it against the three rules.15 min
  5. say each story out loud once, timed. cut anything past 90 seconds.20 min
  6. write two questions that show you understand the role, not ones you could google.15 min

2 hours, total

no work experience yet? you still have five stories

course projects and capstones, club or society roles, part-time and volunteer work, a side project nobody asked you to build, sport, or a family business all count. interviewers are testing judgment, not job titles. a story about a team project that nearly missed its deadline is worth more than a vague one about an internship.

the last ten minutes before you join
  • have this page open, not the full workbook.
  • say your five proof points out loud once.
  • reread the question map so the mapping is already made.
  • decide your opening line for “tell me about yourself”, then stop rehearsing.
final reminders
  • answer the question that was asked. a forced story is more obvious than a short one.
  • spend more time on what you did than on what was happening around you.
  • say “i” for your part and “we” for the team's, and be clear which is which.
  • if you blank: pause, describe the situation, and the rest usually follows. calm beats fast.
0 of 5 stories written open your one-pager