You have had three roles in four years — why should I expect this one to last?
answer
- own the pattern before they list it
- sort moves: theirs versus yours
- one deep result inside a short stint
- what you now screen for
- conditions that keep you, said aloud
basics
~10 sScreens for attrition risk against months of ramp-up cost. Separate the moves the business made from the ones you chose, prove depth inside a short stint, then name the conditions under which you stay.
how to answer
5 beats- name the pattern before they enumerate itOpen by acknowledging the shape of the resume in your own words, calmly and without apology. Taking the premise seriously buys you the rest of the answer; arguing with it spends the whole thing.
- sort the moves into theirs and yoursGive a short ledger: which departures the business decided and which you decided. Keep each to a clause. Do not stretch acquisitions and wind-downs to cover a resignation — one stretched claim makes the rest sound rehearsed.
- prove depth inside one short stintThis is the bulk of your airtime. Tell one thing you owned end to end inside a short role, with a before and an after, so the ramp-up objection is answered by evidence rather than by assurance.
- say what you changed in how you chooseName the misread that caused the move you would make differently, and the question you now ask in interviews to catch it. One sentence of self-correction is worth more than three of reassurance.
- name the conditions that would keep you, and check themClose with two or three concrete things that keep you in a role, then ask how those look on this team. Vows are unverifiable; criteria turn the last twenty percent of the answer into mutual diligence.
your answer
5 story prompts- List every role under two years with one line on who ended it, you or them.
- Pick your shortest stint and find one owned result you can state with a before and after.
- Write one sentence on the move you would make differently, and stop after that sentence.
- Name two concrete conditions under which you would genuinely stay three years.
- This can share material with your career-goals answer, angled at staying rather than growing.
draft and rehearse your own answer in a learn session
go deeper
Short tenures read as attrition risk against a hiring cost the interviewer pays in months of ramp-up. The probe tests self-awareness, ownership of your own choices, and whether you can separate circumstance from a pattern you drive. A strong answer prices that risk honestly, shows depth delivered inside a short role, and names the conditions under which you stay.
Fair question, and I would rather lay the three out than have you guess at them. The first was fourteen months at a small agency that got absorbed; my team was rebadged onto client-site work I had not signed up for, and I left once the transition was done. The second ran sixteen months and I would still be there if the practice had not been wound down when both anchor accounts ended within a quarter of each other. The third is eighteen months, and it is the only one I am leaving for something rather than away from something. So of the three moves, two were the business deciding and one is mine. What I would point at instead of the dates is what happened inside them. At the second, a client checkout service went down for fifty-one minutes on a Saturday because cold starts stacked up behind an autoscale event. I owned the incident, built the warm-pool change, and ran the review with their engineers in the room. Cold start on that service went from about 1.9 seconds to 320 milliseconds, and that work took seven months start to finish — longer than the stints people usually worry about. What I want now is to still be there when the second-year problems show up. That means a system I own past launch, which is the thing I would want to check with you.
The ledger comes first and stays unemotional, then a single owned incident with a clean before and after answers the ramp-up objection directly. Closing on a checkable condition rather than a promise is what keeps it from sounding defensive. Vague blame for any of the three exits would sink it.
I will give you the ledger first, then the through-line. Five employers in seven years reads as churn. Three of those moves were agency consolidation — the practice I led was sold twice and closed once — and each time I stayed through the wind-down rather than leaving early, which cost me the better end of the market on the way out. The one move that was purely mine was leaving a wider advisory scope to take a smaller team where I could own reliability instead of recommending it. The through-line is that I have been doing one job under different logos: running backend platform for teams shipping against client deadlines. At the last of them I inherited eleven services where every release re-cold-started the fleet, and a client-visible outage on a Tuesday morning ran twenty-six minutes because a release landed during a scale-up. I set a warm-path standard for new services, put cold-start time on the monthly account health review so it stopped being invisible between incidents, and over a quarter the worst service came down from 4.2 seconds to under 600 milliseconds. Two engineers I hired there followed me to the next role, which is the reference I would offer on whether people want to keep working with me. What I need in order not to repeat the pattern is an owner who is not planning to sell the practice, and scope I can still grow into in three years. That is what I am testing here, and you should test it too.
Senior weight comes from a mechanism rather than a fix — a standard plus a recurring review — and from evidence other people chose to follow him. Staying through wind-downs and naming what it cost him reads as ownership. Dropping the mechanism and keeping only the incident would pull this back a level.
Two short stints early on barely register once you can say who ended each one. Spend the airtime on what you shipped inside them rather than defending the calendar.
This is where the pattern starts costing you, because interviewers price your ramp-up in months. One deep, finished result delivered inside a short role is the proof that you got past onboarding and stayed useful.
A senior hire is expected to outlast a reorg. Sort the moves into business decisions and your own without flinching at the ones you chose, and name the specific scope or ownership condition you now check before signing.
At principal level the question is about the org you attach yourself to. Talk about the diligence you now run on mandate, funding and ownership, and about what you leave standing when you do eventually move on.
saying these in an interview costs you the question
- A separate grievance attached to each departure
- Calling every move a step up when the titles say otherwise
- Promising five years with nothing concrete behind the promise
- Getting defensive or arguing that the premise is unfair
- Leaving a short stint off the resume and letting them find the hole
- No shipped result from inside any of the short roles
- Which of those moves would you make differently?Pick one and own it in a sentence, without a second apology. Say what you misread going in — scope, ownership, the health of the account — and what you now ask in interviews to catch it. Claiming every move was right is the answer that loses trust here; claiming they were all mistakes is worse.
- The shortest of those — what happened there?Give the mechanics plainly: who ended it, what changed after you accepted, what you did with the time you had. Do not relitigate fault. If you left, say what you had tried first, so it reads as a decision rather than a flinch.
- What would make you leave us in eighteen months?Answer honestly — a candidate who says nothing would is not believable. Name the conditions that would genuinely break the fit, ideally ones this team can speak to, then ask how those look here. Framed that way it becomes mutual diligence rather than a threat.
## The prompt family You will hear this as: - *Why so many moves?* - *You seem to change roles every eighteen months* - *What makes you think you will stay here?* - *How long do you see yourself in this role?* Some interviewers never ask it out loud and simply mark it in the debrief, which is the real reason to **raise the pattern yourself** early in the conversation rather than hoping it goes unmentioned. ## What is being priced This is an economics question, not a loyalty test. A mid-level backend hire typically costs a team a quarter or more before the output is worth the salary, and a manager who has been burned once will not absorb that risk twice without evidence. So the interviewer is asking: 1. what fraction of your moves were yours, 2. what did you actually deliver before leaving, 3. and what will make this time different in a way I can verify rather than trust. ## Sorting the moves The single most useful move in this answer is **the ledger**: state, without drama, which departures the business decided and which you decided. - Acquisitions, wind-downs, cancelled products, agency accounts that ended, funding that stopped — these are common and they are not held against you, provided you do not stretch the category to cover a resignation. - Then own the ones that were yours, and own them as decisions with reasons rather than as escapes. A candidate who says two of four were mine and here is what I was chasing sounds far safer than one who has a villain for every exit. ## Depth beats duration The strongest counter-evidence to a hopping pattern is a piece of work that could not have been done by someone who was checked out. Something you owned end to end, with a before and an after, inside one of the short stints. It answers the ramp-up objection directly: you got productive fast and you finished something. Pick the result with the cleanest number and tell it in three sentences, not thirty. ## Naming the conditions Vows are worthless here. What is not worthless is **criteria**: the two or three concrete things that would keep you, stated in terms this interviewer can confirm or deny: - a scope you can grow into for a couple of years, - ownership of a system past launch, - an org that is not about to be reorganised out from under the team. Then ask about them. Turning the tail of the answer into diligence flips the frame from you convincing them to both parties checking a fit, and it is the difference between sounding defensive and sounding like someone who has learned to choose. ## How the bar shifts - **Early career**, short stints are almost free — the market expects churn and the ramp-up cost is low. - In the **middle** it is a live concern and the depth evidence carries the answer. - At **senior level** the interviewer is also thinking about the team you would be leading and how a departure lands on them, so the handover you left behind at your last exit is fair game. - At the **top**, the question stops being about tenure at all and becomes about judgement in choosing organisations: what you now diligence before you sign, and what you leave standing when you go.