Story bank
The real examples you tell when they ask “Tell me about a time…”. Most people need six to eight good ones to cover nearly every question.
Pausing onboarding to fix payments
Fits: Changing the roadmap; A payments metric drops
Growing checkout conversion by 17%
Fits: Growing conversion 17%; Measuring a payment flow
Leading a team of five through a reorg
Fits: Competing requests
A launch that missed its date
Fits: A project that failed
Disagreeing with engineering on fraud rules
Fits: Disagreeing with an engineer; Build or buy fraud detection
Moving from design into product
Fits: Design to product
What your stories cover
The kinds of “tell me about a time” question nearly every interview asks.
- A result you’re proud ofGrowing checkout conversion by 17%
- Disagreement or conflictDisagreeing with engineering on fraud rules
- A mistake or setbackA launch that missed its date
- Leading or influencingLeading a team of five through a reorg
- Changing coursePausing onboarding to fix payments; Leading a team of five through a reorg; Moving from design into product
- Build onePressure or a deadlineNo story yet
- Build oneA customer or stakeholderNo story yet
- Build oneLearning something fastNo story yet
Skills the job asks for
In the job spec, but none of your stories shows them yet.
- Build oneBalancing growth and riskHalden
Stories come from your CV and cover letter, and from the ones you build. A story counts as covering a kind of question from its title and what it fits. “Comes up in” is a rough match on your answers, to show which stories you reach for most.