The wording sounds light. Why do you want to leave your current job? They are not chatting. They need proof the move was planned, that you can say it in under a minute, and that bitterness or fog does not leak out while you talk. They listen for a single signal. Can you cover the change without dumping on your last team?
Build the answer around one result you already delivered. Name one specific opening on their side. Then stop talking. Future-facing beats grievance every time. Skip the complaint list.
Use this frame: "I've delivered [a clear result] in my current role. I want this job because [a concrete opportunity on their team], and I can help with [a goal in the posting]." Practice until it lands in 30 to 60 seconds. Past that, you've stopped answering and started justifying.
What this question is really testing
They are not after your life story. They want to know if you walk when work gets ordinary. They also want to know if this company is a target you picked or just the next lifeboat.
Thing is, the same line can land two ways. "I want more challenge" stays empty until it sits next to a result you already produced and a task this team actually needs done. Attach those two pieces and the same words start sounding like growth instead of flight.
A short tenure will not get you rejected on its own. Blame will. Stay factual. Name the decision yourself. Show why this seat is different.
A four-part answer that fits in 45 seconds
One spine, used every time, is what keeps you from rambling on a live call.
- One line on what you accomplished where you are, or were.
- One clean reason the next step is this kind of work. Not a complaint about people.
- One tie to this company: a product, a team, a scope, or a way of working you actually checked.
- One line on how you'll contribute early, so they can picture you staying.
Cut a 15-second version for the phone screen. Keep a 45-second version for the longer interview. If they ask why they should believe you'll stay, don't wait for the silence to get weird. Say you're being more deliberate now, and this role matches the team, the scope, and the stability you need to do strong work.
Sample answers you can rewrite in your own voice
Don't memorize these. Swap in your numbers. Borrow the company's language straight from the posting.
Career growth can sound like this: "On my current team I led the rollout that cut onboarding time by about a quarter. I've taken that work as far as this seat allows. Your manager opening would let me coach a larger group, and I want that same process discipline on your expansion work."
Hours that stopped being sustainable need a different beat. Try: "I still like the work. The schedule, I don't. I redesigned our weekly workflow so the team stopped living in late-night fire drills, and output held. Your hybrid setup interests me because I do better work when the hours are sustainable. Not because I want an easier job."
That last beat matters. You're asking for conditions that protect performance, not a nap.
Industry switches hold up when you ground them in work you already did: "Five years in retail taught me how inventory actually fails at the store level. I added supply-chain coursework, then used it to tighten a replenishment process. Your operations role is the first place those two threads meet, and I want to run them against a bigger catalog than I have now."
A seat that went stale after a reorg can stay factual. "The restructure turned my seat into maintenance work. I still automated two reporting jobs so the analysts got their mornings back. I'm leaving because I want a harder problem set, and the projects in this posting match that." Don't say toxic if the workplace was rough. Try: "Priorities shifted away from the kind of work I do well. I still closed the cross-team launch on the original date. I'm drawn to how your groups share ownership, because that's how I do my best work."
Short stints on the resume get grouped, not confessed one by one: "The last few roles ran shorter than I wanted. One ended in a reorg. One was a contract. Each taught me how to stand up a process fast. I'm done with sprints. I want a team I can stay with and deepen the work." A mid-career shift might run a little longer. "I spent a decade in marketing analytics, including a year where I grew qualified leads on a lean budget. I want to take that measurement habit into a product org that actually ships. Your posting is one of the few that treats analytics as a partner, not a report factory."
Turns out, none of these prosecute a boss. Every one carries a number or a before-and-after: time saved, fewer errors, faster cycle, customers unblocked. No metric on hand? Use the before-and-after anyway. The core claim repeats itself on purpose, that you've already proven you can do this work and the work here is bigger. Fine in a draft. Cut it when you speak.
How to say the real reason without lighting a red flag
People leave for growth, a brutal schedule, pay that lagged, or a job that changed under them, and you can say all of that without turning the interviewer into your therapist. Use the swap table.
| If this is true | Say this instead | Leave this out |
|---|---|---|
| You outgrew the work | I finished the mandate I was hired for and want a larger scope | They never promote anyone |
| The hours crushed you | I want a setup where high output is sustainable | My boss had no life |
| Pay lagged the market | I want scope and compensation to match | I just need more money |
| The company restructured | The role changed after the reorg and no longer uses my strengths | Everything there is chaos |
| You hopped | Short stints taught me what I need in a longer stay | I get bored fast |
| The culture clashed | I do better on a team with shared ownership | It was toxic |
Money can sit in the story. Just not at the front. "A fair package plus a chance to lead" lands. "I am underpaid" does not.
If they worry you will leave again
Frequent moves are more common than they used to be. Some managers still read them as a risk, that you'll bounce before the project pays off.
Don't fight the label. Agree you want this one to last. Then prove the choice was deliberate.
Walk them through the decision, not the drama. A layoff, a contract end, and a reorg are different animals from "I was over it." If two moves were organizational, one sentence covers both. Then stop, because repeating the hardship makes it sound like bad luck you can't steer.
To be honest, the follow-up that actually decides things is why they should believe you'll stay. You learned what kind of team, scope, and stability you need. This role has those three. You're not collecting titles. You're picking a place to do the work well.
I would not narrate every job in order, because that's exactly how people end up justifying January, then the three months that never even made the resume, and four minutes later the interviewer still has no idea why this job is the one that finally sticks. Pick two moves. Name the structural reason. Land on what you want now.
When the last job really was a bad environment
Name the mismatch and the work you still delivered. Then point at how this team operates, not at your old employer's failures.
Prep the answer the way you prep any other interview story
STAR still helps here, even though this isn't a pure behavioral prompt. Situation is the constraint in the old role. Task is what you were on the hook for. Action is what you changed. Result is the number or the outcome. Then comes the bridge, the part people skip: that result is why this new job is the next use of the skill.
Write three stories, not ten: a growth story, a problem you fixed, and one about the kind of team you need.
Research the company on LinkedIn before you lock the third line of the formula. Size, open roles, recent posts, and how long people on the target team tend to stay will tell you whether "stability" or "build from scratch" is the honest hook.
Then rehearse somewhere you can hear yourself ramble. LinkedIn Interview Prep lets you pick common questions, record an answer, and get notes on filler and weak phrasing. CNET's look at LinkedIn's AI interviewer describes a private mock that builds questions from the job description and flags rambling. A kitchen-table take is enough.
Run this checklist before any call:
- [ ] First sentence is an accomplishment, not a complaint
- [ ] You named something specific about this company
- [ ] You can say it in 45 seconds
- [ ] You have a 15-second cut for the phone screen
- [ ] Resume and cover letter use the same primary reason
Keep the resume, cover letter, and interview in one story
If the cover letter says career change and the interview says work-life balance, they'll pick at both. Pick one primary reason. Let the others support it.
Resume bullets should prove whatever you're about to say out loud. If you claim you want to lead, show a lead result. If you claim a new industry, show the transferable work, not a sudden personality swap.
Resume tools and job-board applications make it painless to paste a different summary into every posting. Don't. The ATS may not care. The interviewer will.
FAQ
Why do they ask why you want to leave? Fit, mostly, plus whether your moves look thought through. A calm, specific answer beats a clever one.
How do you explain job hopping? Group the short roles around what you learned, say you want a longer stay, and connect that to this team's scope. Keep it under a minute.
Can you mention salary? Yes, as one factor sitting next to the work. Don't make pay the whole plot.
Should you use STAR here? Yes, for the accomplishment. Then bridge to this job so it doesn't sound like a leftover story from another question.
Write your 45-second version tonight. Record it once in LinkedIn's interview practice tool, cut the filler, and match the final lines to the job description so you cannot drift.