Job search prompt · Built for Apollo

Build interview stories from my experience

Turns what you actually did into structured answers, and points at the stories that have no result in them yet.

The prompt

Help me build interview answers out of things I have actually done.

The role I am interviewing for: [TITLE AND WHAT THE ADVERT EMPHASISES]
Things I have done that might be worth telling: [LIST THEM ROUGHLY — MESSY IS FINE, ONE LINE EACH]
Pick one to work on in detail, or ask me which: [NAME ONE, OR WRITE "YOU CHOOSE"]

Produce four sections.

1. WHICH STORIES FIT THIS ROLE — map my rough list against what this role emphasises. Say which ones to prepare and which to leave out, and why. If two stories make the same point, say so; interviewers notice.

2. THE STORY, STRUCTURED — situation, what I specifically did as opposed to what the team did, and the outcome. Keep it under 90 seconds spoken. Use my own words. Do not add detail I did not give you: if something is needed and missing, leave a marked gap.

3. WHERE THIS STORY IS WEAK — this is the section I need most. Usually one of: no measurable result, unclear what I personally did, the difficulty is not visible so it sounds easy, or it ends without saying what changed afterwards. Name which, and what to go and find out.

4. THE FOLLOW-UP QUESTIONS a good interviewer would ask about this story, including the uncomfortable one, with what a strong answer would need to contain.

Do not invent numbers. If the story needs a number I have not given you, write [NUMBER NEEDED] and tell me where I might find it.
Try in Rekdan

Replace the outlined parts before running

  • [TITLE AND WHAT THE ADVERT EMPHASISES]
  • [LIST THEM ROUGHLY — MESSY IS FINE, ONE LINE EACH]
  • [NAME ONE, OR WRITE "YOU CHOOSE"]
  • [NUMBER NEEDED]

When to use this

Interview preparation usually means reading a list of common questions and thinking, roughly, about what you would say. That produces answers that are fine and forgettable, because the work was never done: turning something that took nine months into ninety seconds is a real editorial task, and doing it live under pressure is what makes people ramble.

The section that earns this prompt its place is the third one. Most people's stories fail in the same few ways — no result, no visible difficulty, or an unclear boundary between what you did and what your team did — and every one of those is invisible from the inside, because you remember the whole context and the interviewer only hears the ninety seconds. Being told which specific weakness a story has, before you tell it for the first time, is worth more than any amount of rehearsal.

The instruction against inventing numbers matters more here than almost anywhere. A fabricated metric in a rehearsed story is delivered fluently, which is exactly why it gets probed, and there is no recovery from being caught inventing one.

How to use it

  1. List the raw material badly and quickly

    One messy line per thing you did. Section one exists to choose between them, which it cannot do if you pre-select the three you already planned to use.

  2. Go and find the numbers section three asks for

    Old dashboards, closed tickets, a message to a former colleague. A story with a real figure in it is a different story, and this is the highest-value hour in interview preparation.

  3. Say it out loud before you accept it

    Anything you would not say in your own voice will collapse under pressure. Rewrite the phrasing until it sounds like you rather than like a written answer.

  4. Prepare the follow-ups, not just the story

    The prepared answer is rarely where interviews are decided. The second question — what you would do differently, what went wrong — is, and section four is the only part of this that rehearses it.

Variations

The failure question

Help me answer "tell me about a time something went wrong" without either hiding or grovelling.

What actually went wrong: [BE HONEST, INCLUDING YOUR PART IN IT]
What I did about it: [DETAIL]
What I would do differently: [IF YOU KNOW]
The role I am interviewing for: [DETAIL]

Produce:
1. THE ANSWER — owning my part plainly, no more than 90 seconds, ending on what changed rather than on the apology.
2. WHERE I AM STILL DEFLECTING — quote anything in what I wrote that shifts blame to circumstances or other people.
3. WHETHER THIS FAILURE IS SAFE TO TELL for this specific role — some are disqualifying in some jobs, and I would rather know now.
4. WHAT THEY ARE ACTUALLY ASSESSING with this question, so I can aim at it.

Answer 'tell me about yourself' without reciting the CV

Write me an opening answer that is not a walk through my CV.

My background, briefly: [DETAIL]
The role: [TITLE AND WHAT THEY EMPHASISE]
The thread connecting my career, if there is one: [OR WRITE "IT LOOKS RANDOM"]

Produce:
1. THE ANSWER — 60 to 90 seconds, arriving at why I am in this room rather than ending at my current job title.
2. WHAT IT LEAVES OUT and why that is the right call.
3. IF MY PATH LOOKS RANDOM, the honest framing — not a fabricated narrative, but the true reason it went that way.
4. WHERE THEY WILL INTERRUPT, which tells me what they care about.

Where it falls short

  • It only knows what you tell itA thin input produces a thin story with confident structure, which is the worst combination: it feels prepared and contains nothing. If a story comes back full of marked gaps, that is the story telling you it needs research, not rewriting.
  • For structured competency scoringMany large employers and most public sector processes score answers against a published framework. Get the framework and prepare against it — a well-told story can score zero on a rubric it never addresses.
  • Over-rehearsalA story delivered word-perfect sounds recited and stops sounding true. Learn the shape and the numbers, not the sentences.