Why rehearse each story-bank experience from a short cue outline instead of a full written script?
answer
- Fix the beats, leave the words free
- Roughly five to seven cues per experience
- Rehearse aloud, never silently on paper
- The interruption test breaks memorised prose
- Only the framing line is memorised
basics
~20 sA five-to-seven cue outline fixes the beats of an experience while leaving the wording free, so the answer adapts to the prompt actually asked and survives interruption. A fully written script recites, cannot be trimmed on the fly, and derails at the first question.
solid answer
~50 sRehearse each row of the story bank as a cue outline of roughly five to seven beats — the setting, the constraint, the decision point, what you specifically did, the outcome, and what you took from it — and say it aloud rather than writing it out. The beats are what you actually need under pressure; the sentences are what you can generate live and should, because they are the part that must bend to the prompt in front of you. The common failure is writing six experiences out word for word and memorising them: the delivery comes out too even, the answer answers the question you rehearsed rather than the one asked, and one clarifying interruption loses the thread. Rehearsing with a mock-interview partner who deliberately interrupts is the cheapest way to find out which of your rows are secretly scripts.
go deeper
Practise out loud, not in your head, and keep your notes to a handful of cue words per experience. Reading a written-out answer to yourself does not prepare you to say it.
Be able to explain what an outline preserves that a script does not: recoverable beats, variable length, and wording generated in response to the prompt actually asked.
Demonstrate that you can resize and re-angle the same experience live — ninety seconds or five minutes, pressure framing or tradeoff framing — and recover cleanly when an interviewer cuts in at the second beat.
Own the judgment about how much rehearsal is enough. Under-rehearsed material wanders and buries the point; over-rehearsed material reads as performance and costs you the candour that senior conversations are actually assessing.
## The two ways people rehearse Once a story bank exists, every row has to be rehearsed, and there are two ways to do it. One is to **write the answer out as prose** and learn it. The other is to reduce the experience to a **short cue outline** — about five to seven beats — and practise speaking from those cues, differently each time. The second is what works, and the first is the single most common way careful preparation makes a candidate sound worse than no preparation at all. ## What the cues are A workable outline for one row is five to seven fragments, each a few words, in order. For a mobile engineer's row about a crash spike after a release, the cues might be: 1. release cut, crash reports climbing overnight 2. constraint: the fix window before the store rollout widened 3. decision: roll back the release or ship a targeted patch 4. what I did: reproduced on the affected device class, patched, staged the rollout 5. how I got agreement: showed the affected slice to the release owner 6. outcome: crash rate back under the pre-release level, rollout resumed 7. lesson: the staged rollout percentage became part of the release checklist That is enough to reconstruct several minutes of speech. Notice what the cues are *not*: they are not sentences, so there is no phrasing to forget, and no phrasing to fall out of when you are nervous. ## Why scripting fails, concretely **It sounds recited.** Spoken language written in advance has a different rhythm from spoken language generated live: fewer false starts, more subordinate clauses, an even cadence that does not track the interviewer's reactions. Experienced interviewers hear it immediately, and what they conclude is not that you are polished but that they are not learning what you are actually like. **It answers the rehearsed prompt, not the asked one.** A script encodes one framing. Asked a variant — about the tradeoff rather than the pressure — the scripted answer still comes out in its original shape, and the interviewer has to work to extract the part they wanted. **It breaks on interruption.** Interviewers interrupt constantly: to ask what a term means, to redirect, to check who else was involved. A script has one entry point and one order, so an interruption at the second sentence means restarting or losing the thread. An outline can be resumed anywhere, because you only need to know which beat you were on. **It cannot be resized.** Sometimes you have ninety seconds; sometimes the interviewer wants five minutes on the same experience. A cue outline is compressed by giving each beat one sentence and expanded by dwelling on the decision and what you did. A script has exactly one length. ## How to actually rehearse - **Say it out loud.** Reading an outline silently gives no evidence about what the sentences will be like. The whole point is practising sentence generation. - **Vary the wording deliberately.** Tell the same row three times with different opening sentences. If you cannot, it has hardened into a script. - **Practise the compressed and the expanded version** of a few rows. - **Use a mock-interview partner.** Ask them to interrupt at unpredictable points, to ask what you mean by a term, and to redirect mid-answer. Then ask them the diagnostic question: did any part sound memorised? - **Rehearse the transition, not just the body.** The riskiest few seconds are the opening — choosing the row and framing it in one sentence — and the close, where an unrehearsed answer trails off. Beats one and the last beat deserve the most repetitions. ## Where memorisation is legitimate A very small amount of fixed phrasing is fine and useful: a one-line framing sentence that names the experience and the theme, and a crisp closing sentence for the outcome. That is two sentences per row, not two pages. Anything beyond that is where the recited quality creeps in. ## The tell you are aiming for A well-rehearsed answer from an outline sounds like someone who knows the material thinking about it now: slight variation, natural emphasis, easy handling of a mid-answer question, and a willingness to say more or less depending on the interviewer's interest. That is achievable in an afternoon of speaking practice, and it is not achievable at all from a page of memorised prose.
- What should the five to seven cues actually contain?The setting in one fragment, the constraint that made it hard, the decision point, what you specifically did, how you got agreement if others were involved, the outcome, and the lesson you carried forward. Each cue is a few words, not a sentence — enough to trigger recall of the beat, not enough to be recited.
- How can you tell whether one of your rehearsed experiences has hardened into a script?Try to tell it twice with different opening sentences. If the same phrasing keeps reappearing, or you lose your place when a mock-interview partner interrupts at the third beat, it is a script. The other tell is being unable to give a ninety-second version of an answer you normally take four minutes over.
- Is it ever worth memorising a sentence word for word?Two per experience, at most: the framing line that names the situation and the theme, and the closing line that states the outcome. Those are the moments with the least thinking time and the highest cost of fumbling. Everything between them is better generated live from the cues.
saying these in an interview costs you the question
- Writing six experiences out word for word and memorising the prose
- Rehearsing only silently, so no sentence is ever spoken before the interview
- Losing the thread entirely when interrupted mid-answer
- Delivering the rehearsed framing even when the prompt asks something adjacent
- Having exactly one length for every answer, whatever the time available