Most candidates flunk this question by over-confessing. You get asked “why are you leaving your current job?” and you start explaining the politics, the bad manager, the missed promotion, the way the new VP restructured your team into oblivion. All of it is probably true. None of it helps you. The bar for a strong answer is narrower than people think: sound grateful for what your current role gave you, name an outward-looking reason for moving, and pivot fast to why this job is the logical next step. That’s it. The rest is a trap.

Why interviewers ask this

The interviewer is doing two simultaneous risk assessments. First, maturity: can you talk about a previous employer without venting? People who badmouth their current company on a first interview will badmouth this one too — that pattern is so well-known that recruiters explicitly screen for it. Second, retention risk: if you’re leaving because of something fixable that exists everywhere (long hours, ambiguous priorities, a boss you didn’t click with), you’ll probably leave the new job for the same reason in eighteen months.

There’s a third, quieter thing going on. Layoffs hit 1.2 million people in the US in 2025 — up 58% year-over-year, the highest annual total since 2020, according to MakeMyPaystub’s analysis of Challenger, Gray & Christmas data. Roughly one in five HR professionals now admits their return-to-office mandate was designed to push people to quit. The interviewer knows this. They’re not expecting every candidate to have left voluntarily, on great terms, for a perfect reason. They are expecting you to talk about whatever happened like an adult.

The three-part framework

Every strong answer to this question has the same three beats, in the same order. Skipping any of them is what makes answers feel either bitter or evasive.

Part 1 — Acknowledge the current role (positive frame). One sentence on what the job has given you. Skills, scope, customers, a specific shipped thing. You’re not gushing — you’re showing that you can talk about your employer without bile. This is the maturity test in a single sentence.

Part 2 — The reason, framed outward. Why you’re moving. The key word is “outward.” Inward reasons sound like complaints (“my manager doesn’t get me”, “I’m bored”). Outward reasons are about what you’re moving toward: a domain, a stage of company, a kind of problem, a level of ownership, a market. Even a layoff or RTO mandate can be framed outward — “the role I was hired for no longer exists in the new structure” is outward; “they screwed me” is inward.

Part 3 — Why this role specifically. The bridge. One or two sentences tying the move to something concrete about the job you’re interviewing for. This is what separates a generic answer from one that makes the interviewer lean in. If you can’t make this connection, the answer collapses — it just sounds like you want to leave, not like you want to be here.

Keep the whole thing under 60 seconds. Two to three sentences per beat. The single most common failure mode is letting Part 2 swallow the answer.

15 sample answers

1 · Senior engineer, growth ceiling. “I’ve been at [Current] for almost four years and I led the payments rewrite that’s now serving the whole company. What I’m noticing is that the next logical step for me is a staff-level role, and the org chart doesn’t really have room for one above my current manager. So rather than wait for that to maybe open up, I’m looking for a team where staff-level scope is already on the table — which is why the role you posted caught my eye.”

2 · Marketing manager, post-layoff. “My team at [Current] was eliminated last month when they consolidated growth and brand under a single VP. The work I did there was good — we doubled paid social CAC efficiency in 2025 — but the role no longer exists. What I want next is a B2B SaaS team where paid social is a serious channel rather than a side bet, and that’s exactly the brief you described in the JD.”

3 · Product manager, role pivot. “The last two years at [Current] have been on internal tools — I’ve shipped four products, all used by a few hundred employees. I’ve learned how to build with no marketing budget, which I value, but I want to work on something external customers actually choose to use. Your consumer team is exactly the inflection point I want to be at.”

4 · Designer, RTO mandate. “[Current] moved to a full five-days-in-office policy in January after hiring me as a hybrid role two years ago. I relocated during that time and the commute is no longer workable for me. The work itself I’d happily continue — but I need a role with a sustainable setup, and your hybrid-by-default culture is the right fit.”

5 · Sales rep, comp structure changed. “[Current] restructured the comp plan in Q1 — base went up, commission tiers got compressed. For someone like me who consistently hits 130%+ of quota, the new plan caps upside in a way that doesn’t reflect how I sell. I want a comp structure that rewards over-performance, and from talking to your reps, yours still does.”

6 · Recent grad, first-job mismatch. “I joined [Current] out of school 18 months ago thinking I’d be in product analytics. The role drifted toward operational reporting — useful work, but not what I trained for. I’ve finished the cohort I committed to, and now I’m looking for a role where SQL and modeling are the core of the job, not a side workflow. Yours is the first JD I’ve seen this quarter that maps cleanly to that.”

7 · Engineering manager, IC return. “I’ve managed a team of seven for three years at [Current]. I’m good at it, and the team has done strong work, but I miss writing code as the primary thing on my calendar. I’m looking to go back to a senior IC role — and your staff engineer track is one of the few I’ve found that doesn’t quietly treat IC as a demotion.”

8 · Customer success, industry pivot. “I’ve been in CS at a healthcare SaaS for four years. I learned the GTM motion deeply, but the regulatory environment in healthcare means sales cycles are 9-12 months and I’d like to work somewhere with a faster feedback loop. Developer tools — what you build — is exactly the kind of bottoms-up motion I want to learn next.”

9 · Finance analyst, company stage change. “I joined [Current] when we were 80 people. We’re now 1,400. The work has gotten further from the operators and closer to corporate FP&A, which isn’t what energized me about the original role. I want to be back at sub-100-person scale, where finance sits next to the founders — and that’s the stage you’re at right now.”

10 · Recruiter, returning from contract. “My last 18 months was a contract role at [Current] that wrapped on schedule in February. It was a great window into hyper-growth recruiting — I closed 34 engineering hires in a year. Now I’m looking to come back full-time and build a function from the ground up rather than execute on someone else’s plan, which is what the talent lead role here would be.”

11 · Junior data scientist, mentorship. “I joined [Current] as the second data scientist. I learned a lot, but I’ve been senior-most on most of my projects, which isn’t great for me at this stage of my career. I want to work somewhere with a more developed ML org where I can be the most junior person in the room again. Your team’s research output is exactly the level I want to be around.”

12 · Operations lead, acquired company. “[Current] was acquired in November. I stayed through the integration, which I think was the right call, but the acquiring company runs ops very differently — much more centralized, much less ownership at the regional level. I want to be back in a structure where the ops lead actually owns the P&L for their region, and that’s the role you’re hiring for.”

13 · Frontend engineer, tech stack. “I’ve been writing the same Angular codebase at [Current] for almost five years. The team has no plans to migrate, which is a reasonable business decision — but I’m at the point where I want to work in a modern React/TypeScript stack so my skills stay current. Your platform is built on exactly that, and your engineering blog suggests you actually care about technical excellence.”

14 · PM, founding team. “I’ve been at [Current] for two years and learned a huge amount about scaling a product past PMF. What I want next is to be earlier — pre-PMF, founding PM, willing to be wrong publicly about what to build. Your seed-stage product role is the cleanest version of that I’ve found.”

15 · Career changer, post-bootcamp. “Before my current role I spent six years in K-12 teaching. I finished a part-time backend bootcamp in 2025 and have been writing internal automation scripts at [Current] for the last year to build a portfolio. I’m now ready to make software engineering my full-time job, and your apprenticeship-track role is the most credible path I’ve seen for someone with my background.”

What NOT to say

Closing move and practice routine

The closing move is what most candidates skip: after Part 3, stop talking. The interviewer asked a binary question — “why are you leaving?” — and you’ve answered it in 45 seconds. Silence is fine. The longer you talk past the answer, the higher the chance you say something inward that you’ll regret.

To practice: write your three-part answer on a single index card. Time yourself reading it out loud. If it goes past 60 seconds, cut Part 2 — that’s almost always the part that bloats. Then do three live runs with a friend or a recorded camera. The first run will sound rehearsed, the second will sound flat, the third will sound like you. That’s the one you take into the interview.

One more thing: align your stated reason with your LinkedIn and your references. If you say “the role was eliminated” but your manager tells the reference checker you quit, the offer dies. Get the story straight across every surface before you start interviewing — that’s the difference between a clean exit and a process that quietly stalls in the background check.