The question is about the joins, not the boxes
The interviewer has your CV. They know where you worked and for how long, and if the sequence were
all they wanted they would have read it in ninety seconds without booking an hour. What the document
cannot tell them is why each move happened, and that is what is being assessed: whether you make
deliberate choices or accept whatever arrives, and whether your choices point anywhere.
So the unit of the answer is not the job, it is the transition. Four jobs means three transitions
plus the decision to be in this room, and those four decisions are where the judgement lives. A
candidate who narrates employers in order is answering a question about their CV. A candidate who
says "I moved from consultancy to product because I kept handing over systems I never saw operated,
and I wanted to be on-call for something I had built" has said what they optimise for, which is more
useful and considerably harder to fake.
Weight by relevance, not by time
The instinct is to start at university and move forward at a constant rate, which spends your
strongest minutes on your weakest material. Invert it. For a ten-year history in about four minutes:
thirty seconds for everything before the last two roles, ninety for the previous role, two minutes
for the current one, and a closing sentence about why this conversation is happening. Early jobs earn
a mention only where they explain something durable — the domain you learned, the reason you moved
into infrastructure. Nobody is hiring the graduate you were, and if you are two minutes in and still
in 2016 you have lost the part of the answer that would have got you the job.
Reasons that read as rational, and reasons that do not
Every transition needs a reason, and the reasons are scored more than the roles. Some carry well
because a manager recognises them as the reasoning of someone who thinks about their own development:
you wanted ownership of a system rather than a slice of one; you wanted somewhere the technical
decisions were still open; you had learned what that company could teach you; you wanted to find out
whether you could lead and the opportunity did not exist where you were.
Others read badly, and it is worth being precise about why. "The money was better" is fine as a
component and thin as the whole reason, because it says nothing about what you will do once you are
paid. "My manager was impossible" invites the question of what you did about it, and if the answer is
"left", that is a data point about your tolerance for friction. "The company was a mess", with no
account of any attempt to improve it, reads as passivity. And three moves in four years with a
different external explanation each time reads as a pattern however good each explanation is — the
interviewer is silently asking whether they are about to become explanation number four.
Two practical rules. Never make the reason a person, make it the work: "the interesting architecture
problems had been settled and I wanted to be somewhere they were still open" is true in most cases
where "my lead blocked everything" is also true, and it avoids criticising someone the interviewer
cannot cross-examine. And if a move was genuinely a mistake, saying so is a strength, provided you can
say what you misread at the time. Candidates who own one bad move are trusted more on the rest of the
account, not less.
The parts you would rather not narrate
Gaps, short stints, redundancies, a demotion, contract stretches, a year that went nowhere. The
mechanics are identical for all of them: state it in one clause, give the reason in one sentence, say
what you did with the time, and move on at the speed you moved through everything else. The cost is
not in the fact, it is in the handling — slowing down, over-explaining or reaching for a euphemism
converts a neutral fact into a flagged one, because the interviewer's attention follows your
discomfort.
"I was in that role eight months. It was a bad fit — I joined to build out their data platform and the
funding went a month after I started, so I was maintaining a reporting stack instead. I left when it
was clear that was the job." Fourteen seconds, finished. The same fact delivered in ninety apologetic
seconds teaches the interviewer that there is something here to dig into.
Redundancy needs no defence beyond the fact. Do not explain that it was not performance-related;
volunteering that raises the question.
Landing the ending, which is the part most people drop
The narrative has to arrive somewhere, and the destination is this role. Ending with "...and that's
where I am now" hands the interviewer nothing and quietly suggests you are available rather than
interested. The last twenty seconds should connect the pattern you have just described to what this
team specifically does, and should be specific enough that it could not be said to another company. If
you cannot make that sentence specific, better to discover it now than to have the panel discover it.
A pattern to adapt rather than recite
Delivered verbatim this will sound borrowed. Read it for the ratio of reasoning to chronology, then
load in your own moves.
"Nine years, three companies, and the thread through them is that I have kept moving towards owning systems in production rather than handing them over. I started in a consultancy doing integration work for insurers. Two useful years — it is where I learned to read someone else's domain quickly — but I was building things I never operated, and I would hear six months later that something I wrote had been failing all along. So I moved to a product company specifically to be on-call for my own code.
That was five years, and it split in two. The first half I was a backend engineer on the payments team. The second half I ended up owning the reconciliation side of it, which came about because I picked up a batch job nobody wanted and concluded it needed replacing rather than patching. That is the piece of work I would point to if you only had time for one. I left because the platform had stabilised and the remaining work was maintenance.
That was my decision and it took me a while to make it, because it was a good team. I moved to my current role for a rebuild, and I have had eighteen months of exactly the work I wanted — although honestly it has also taught me that I do not enjoy greenfield as much as I assumed, which is part of why I am talking to you.
What I am after now is a system with real users and real operational weight where I can own a domain end to end. Your reconciliation and ledger problems are the thing I have spent five years on, and it is not common to find a team where that is the centre of the product rather than a back office."
Count the sentences that are dates and companies — there are very few. The rest is reasons.
Preparation
Write your transitions on one line each, with the real reason next to the sayable reason, and
check that the sayable one is true. Then read the list as a stranger would and ask what it says
you optimise for. If it says nothing, choose the emphasis that is most defensible and reshape the
telling around it — not by inventing motives, but by promoting the ones that were genuinely
there. Then time yourself once. Four minutes, out loud, no notes.
Interviewers are not testing whether your career looks planned; they are testing whether you
can explain your own decisions, and an honestly examined zigzag beats a smooth line with no
reasoning attached to it.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).