You have changed jobs three times in four years. Why would this one be different?

The cost that sits behind the question

A manager who hires you spends roughly the first quarter getting nothing out of the arrangement, then a stretch of you being useful but supervised, before you are contributing at the level they hired for. Somebody who leaves at eighteen months has consumed most of that investment and returned a fraction of it, and the manager also has to reopen the requisition and rerun the loop. That is the whole of the concern, and it is a resourcing concern rather than a moral one.

This matters for tone, because candidates hear the question as an accusation of disloyalty and answer defensively. Nobody is questioning your character. They are asking whether the money and the ramp-up will be recovered, so the answer that lands is one that makes the next two or three years look likely, not one that argues the past was justified.

Norms also vary by market and by segment, and interviewers know it. Two years is unremarkable in some ecosystems and short in others; a start-up that folded is read differently from a resignation. None of that gets you out of the question, but it means you do not need to be apologetic about the raw count.

Answer the pattern once, in one pass

The instinct is to take each role in turn and defend it, which produces four minutes of explanation and confirms the very impression you are trying to remove. Compress instead. Give the three moves in one breath with a single reason each, in a way that shows a direction.

"Three moves, and two of them were the same decision. First one, eighteen months, the start-up ran out of funding and the team was let go. Second, I moved for a platform role that turned out to be integration work — that one was on me, I did not ask enough about what the team was actually shipping. Third was the right kind of move: I went from a small team to owning a service at scale, and I have been there two years. What I want next is the same direction, one level up."

That is about thirty-five seconds. It contains a redundancy you did not control, a misjudgement you own, and a deliberate step that worked, and it ends by pointing forward. The direction is what turns three data points into a line.

If there is no direction — if the moves genuinely were opportunistic — say the plainer version rather than manufacturing a narrative: "The first two were reactions rather than choices. I got better at this by the third." An interviewer can work with that. What they cannot work with is a story where every move was somebody else's fault and every role was beneath you.

What has changed is a filter, not a promise

"I am looking for somewhere to settle" is worth nothing, because every candidate says it and no candidate can guarantee it. The answer that carries weight is a specific thing you now check before accepting, ideally one you have used in this very process.

Move that went wrong	The filter it produced
Role was not what the description said	Ask to see the team's last two quarters of shipped work
Manager left within three months	Ask how long the hiring manager has been in post and whether reporting lines are settled
Funding vanished	Ask about runway, revenue and which business line the role sits in
Promised scope never arrived	Ask what the first six months are expected to produce, and who decides
Team was reorganised out	Ask why the role is open and what happened to the last person in it

Pick the row that is true for you and then use it, out loud, in the interview: "which is why I asked your manager how long she has been running the team." That single sentence does more than any assurance, because it demonstrates the change instead of promising it.

Do not over-correct into a pledge

Two failure modes sit either side of the answer. One is the pledge — "I am absolutely committed to being here five years" — which is not believed, cannot be verified, and slightly insults the interviewer by assuming they wanted a vow rather than a reason. The other is defiance: pointing out that tenure norms have changed, that loyalty is not rewarded, that everybody moves now. All of that may be true and none of it addresses the manager's ramp-up problem, and arguing with the premise reads as arguing with the interviewer.

There is a third, quieter mistake worth naming, which is agreeing too readily that the record is bad. Candidates say "I know it looks like job hopping" and hand over a verdict nobody had reached. Describe the moves as decisions and let the interviewer decide what they add up to.

Turn it into a question

Once you have answered, the strongest available move is to put the concern back on the table as a genuine enquiry: "What keeps people on this team? The two who have been here longest — what has their path looked like?" This works for three reasons. It shows you are selecting rather than merely being selected, it gets you information that actually predicts whether you will still be there in three years, and the answer is often revealing. A hiring manager who cannot name anyone with tenure, or who describes progression vaguely, has just told you something about the fourth move.

Your record is fixed. What you can still change in the room is whether it reads as a habit or as a sequence of decisions that got better — and that turns entirely on whether you own one of them.