skip to content

What keeps tailored versions of your stories consistent when several interviewers compare notes?

level: seniorimportance: should knowfreq 47%

answer

  1. Fixed spine, free presentation layer
  2. Facts, role, outcome never move
  3. Role inflation is the usual drift
  4. Repair with depth, never with scope
  5. Editing a spine line means stop

basics

~20 s

A fixed spine. The facts, the numbers, your own role and the decision you owned stay identical in every version; only order, airtime and framing move. People who compare notes should hear one career told from different angles.

solid answer

~40 s

Write the spine down once and never tailor it: what happened, when, what your part actually was, what changed as a result. Everything above that line — which story you lead with, which beat you expand, how much context you set — is free to move per company. The drift that costs people offers is almost never a contradiction of fact; it is role inflation. You say you led the frontend redesign to one person and helped with it to another, because one conversation felt like it wanted a leader. Since it is common for the people you meet in a loop to compare impressions afterwards, and the recruiter usually hears the earliest version, the safest habit is to fix your role language across all variants before you tailor anything else.

go deeper

for a junior

Keep the facts of each experience identical no matter who is asking. Decide once what your role in it was, and use that same word every time you tell it.

for a middle

Explain the split between a fixed spine — events, your role, outcome — and a free presentation layer of order and emphasis. Know that role inflation, not date errors, is the common drift.

for a senior

Demonstrate the repair discipline: when an answer lands flat, expand the decision rather than your ownership. Show that you plan tailoring on top of written spine facts rather than improvising per listener.

for a principal

Own consistency as a deliberate signal. Decide in advance which threads of your record you will emphasise across an entire process, and treat any tailoring that requires editing a fact as a reason to change the story, not the facts.

## Tailoring has a counter-force Every move that makes a story fit better also makes it different from the version someone else heard. Since it is common practice for the people who meet a candidate to exchange impressions afterwards, and the earliest conversation is often the one that gets relayed, the discipline of tailoring is inseparable from the discipline of staying consistent. The resolution is a **spine**: a small set of facts that never moves, under a presentation layer that moves freely. ## What belongs in the spine For each story in your bank, fix these before you tailor anything: - **What happened, and roughly when.** The sequence of events. - **What your part actually was.** Led, contributed, reviewed, pushed for, executed someone else's call. - **Who else was involved.** Team size and who owned the decision you did not own. - **What changed as a result.** The outcome, stated the same way every time. - **What you would do differently.** Fixed, because a changing regret is a tell. A useful format is one line per bullet, written down. Not a script — a fact sheet you can reread the morning of a conversation. ## What is free to move Everything about presentation: which of your stories you lead with, which beat you expand and which you compress to a clause, how much context you set before the action, and which of several true threads you pull. A frontend redesign story that opens on how the work was sliced for one company and on the migration safety for another is the same story told from two angles. Both angles are in the events. ## The drift that actually happens Almost nobody contradicts a date. Four patterns cause real damage: **Role inflation.** *I led it* in one conversation, *I helped with it* in another. This is the common one, and it usually comes from reading the room rather than from intent: a conversation that seems to want a leader gets a leader. It is also the easiest for a panel to catch, because scope of ownership is exactly what people compare notes on. **Outcome creep.** The result grows across the day as you get more comfortable telling it. Fix the outcome sentence word-for-word and say it the same way every time. **Motive drift.** Why you left a previous role, or why you took a decision, gets re-explained to suit each listener. Have one true version. **Cast changes.** A colleague who was central in the morning is absent by the afternoon because the shorter version needed the space. Compressing is fine; erasing someone whose existence changes what you owned is not. ## How to hold the line under pressure The risk peaks when a listener pushes back or seems unimpressed. The instinctive repair is to enlarge your role slightly, and it is exactly the wrong move — the enlargement is the thing that gets flagged, not the original modest claim. The correct repair is to add **depth**, not scope. If a story lands flat, do not become the person who ran it; instead expand the decision you did make, the option you rejected, and why. Depth is unlimited and true. Scope is fixed and checkable. ## Consistency is a positive signal, not just risk avoidance When several people hear the same events with different emphasis, the impression is of someone who understands their own work well enough to explain it from any angle. When they hear different events, or the same events with a growing protagonist, the impression is of someone assembling a performance. The first impression is worth building deliberately: it is the reason to tailor *emphasis* aggressively and *facts* not at all. ## A practical routine Before a loop, take your promoted stories and read only the spine lines out loud. Then plan the tailoring on top: for this company, this story opens here, that beat gets expanded, this one gets a clause. If tailoring ever requires you to edit a spine line, that is the signal that you have crossed from emphasis into rewriting, and the honest move is to pick a different story rather than a different set of facts.

  • A story lands flat and the listener seems unimpressed. What do you do next?
    Add depth rather than scope. Expand the decision you actually made, the option you rejected and why, the part that went badly. Enlarging your role to rescue the moment is the change that gets noticed and compared later, and it converts a merely unremarkable answer into a credibility problem.
  • How do you handle a story where your part was genuinely small?
    Say what you owned, precisely, and spend the airtime there. A well-told small contribution with a real decision inside it is stronger than a vague large one, because it is specific and it holds up. If the small part cannot carry the question, that is a ranking problem — promote a different story rather than inflating this one.

saying these in an interview costs you the question

  • Escalating your role because a listener seemed unimpressed
  • Letting the outcome grow across successive conversations
  • Giving different reasons for the same past decision
  • Dropping a colleague whose role changes what you owned
  • Treating tailoring as licence to edit the facts per audience

context