Build the stories
before you see
the questions.

A proven interview preparation method — one that works from individual contributor through director and senior leadership — built into an iOS app that tells you exactly what is wrong with every answer.

iOS · Not out yet · One email when it is


01

The method

Most people don't miss out because they haven't done the work. They miss out because they can't articulate it under pressure. The fix is to build the stories first — around ten of them, the real highlights of your career — and then mould them to whatever you get asked.

1

Build out stories

Written from your career, before you have seen a single question.

2

Add the job description

The job you actually want.

3

Perfect the answer

Structure, “I” rather than “we”, a real number attached.

4

Practice rephrasing

The same story, restructured to answer whatever gets asked.

The key is not just writing the stories. It is writing them before you know the question — and then having practised restructuring one so it answers almost anything you get asked.


02

What it actually checks

Every answer is put against a real rubric and told what is wrong with it. This is the whole list, not a sample.

On every story

The situation is written, and establishes stakesdoesn't say why it was hard
The task names what you ownedno task
The action has enough substance60–120 words
The action is written in first personnot your doing
The result is written, and landstoo thin to land
The result is an outcome, not an activityvague result
The result has a number in itno metric
The result actually follows from the actioncause and effect
The story is tagged to a competencyso it matches a job

On your “tell me about yourself”

You said what you actually doyou never said what you do
You said “I”, not “we”mostly ‘we’
There is something measurable in itnothing measurable
It has an arc — present, past, then nextno sense of where you're going
You said why this roledidn't connect to this job
You used the time you pickeddidn't use the time
Your pace is followabletoo fast to follow
Filler wordscounted

After a practice round

Every answer sorted by what the follow-up did to itheld up · needed pushing · didn't recover
Each weak answer names the specific defect, and shows the stronger versionnot just a hint
Patterns across answers, not one at a time“you keep describing what the team did”

03

Why not just use ChatGPT

An actual grading rubric

We built a real rubric, and every answer is put up against it — so the same answer does not get a different score just because you asked on a different day.

It has context

  • The jobs you are looking for
  • The job you are interviewing for
  • What you are getting better at, and what you need to focus on
  • How your mock interviews match the stories you have already built

It gives you the answer, not just the hint

It doesn't only point at what you could change. It shows the stronger version, so you can hear the answer built out properly.


One email when it's out.

No launch countdown, no newsletter, nothing else.