"Why are you leaving your current job?" is asked in nearly every interview, and answered poorly in most of them. Candidates either complain (which tells the interviewer how you'll talk about this job in 18 months) or hand-wave (which tells them you don't have a real reason). Both fail the test the question is actually designed to apply.

This post is the structure that gets the answer right without rehearsing it into something that sounds rehearsed.

What the question is actually testing

Three things, in roughly this order:

Do you have a coherent reason? A candidate who can articulate a specific gap their current role can't fill — and why this role addresses it — reads as deliberate. A candidate who says "just looking for new opportunities" reads as either evasive or directionless. Both lose against the candidate with a specific answer.

Do you speak well about your current employer? This is the one most candidates underestimate. The interviewer is implicitly forecasting how you'll talk about them in two years. Negative, aggrieved, or sarcastic descriptions of your current role correlate strongly with negative interviewer assessment, independent of the substance of the answer. The tone of the answer is graded as much as the content.

Are your reasons aligned with what this role offers? If you're leaving because you want platform-scope work and the role you're interviewing for is also team-scope, the interviewer is going to wonder why you're here. Your reason for leaving has to be a reason this role solves.

The answer that does all three lands the candidate in a strong position before the next question is even asked.

The three-move structure

A working answer has three parts:

Frame the move as pull, not push. Lead with what you're moving toward, not what you're escaping. "I'm looking for a role with more end-to-end product ownership" is pull. "My current manager won't let me own anything end-to-end" is push, even though the underlying fact might be the same. The pull framing keeps the conversation forward-looking. The push framing makes the interviewer wonder what you'll say about them eventually.

Name one specific gap your current role can't fill. Generic "I want more growth" is forgettable. "My current role tops out at team-scope work and I'm ready for platform-scope problems" is specific and credible. The specificity does two things: it shows you've thought about this beyond "I'm tired of being here," and it gives the interviewer something concrete to map onto the role they're hiring for. One gap. Named concretely. With evidence in your work history that you've actually maxed out the current scope.

Connect it to this role, not to job-searching in general. Close on why this specific role is the answer. "The platform-scope work you mentioned in the JD is the exact next step." This grounds the answer in the conversation you're actually having, rather than a statement of career direction that would fit any interview.

A worked example

A working answer for an engineer leaving a senior IC role to join a platform team:

"I joined $CURRENTCO three years ago to ship customer-facing product, and that's exactly what I did — I led the migration of our checkout flow, which is what I'm most proud of from this role. Over the last year, the work I've found most interesting has been the platform pieces underneath that — the latency work, the schema migrations, the shared service layer. My current org is structured product-first, so the platform work I'm doing is on the side rather than as the core of the role.

When I read the JD for this role, the description of the work — owning the data-platform layer across product teams — is the exact shape of the work I've been gravitating toward. That's why I'm here."

Roughly 100 seconds out loud. Notice what's not in it: no complaint about the current manager, no criticism of the current company's strategy, no mention of money or promotion. The answer acknowledges what the current role gave them ("led the migration of our checkout flow, which is what I'm most proud of"), names a specific gap (platform work isn't core in a product-first org), and connects it directly to the role being interviewed for.

What to avoid

The common failure modes:

Criticizing your current manager or company. Even when the criticism is accurate. Even when the interviewer asks follow-up questions that seem to invite it. The implicit forecast is that you'd talk about them the same way. Strong candidates find a way to describe their current situation that doesn't require villainizing anyone.

Citing money as the only reason in early-stage interviews. Money is a fine reason to switch jobs. It's not a great answer in an early interview when the interviewer is sorting between candidates. The money conversation belongs with the recruiter or in the negotiation phase, not as your headline reason for leaving in a hiring-manager screen.

Listing grievances. "I was passed over for promotion" or "the team got reorged and I didn't like my new manager" might be true and might be material, but they read as backward-looking. If something material happened (a layoff, a major reorg), name it in one neutral sentence and pivot to what you're moving toward.

Sounding bitter or exhausted. Tone matters more than substance. A factually accurate answer delivered with audible exhaustion lands much worse than a slightly thinner answer delivered with energy. Practice the answer out loud at least once before the interview to hear what you sound like.

Taking three minutes. This isn't an open-ended question. Sixty to ninety seconds. If the interviewer wants more, they'll ask.

Special cases

You were laid off. Lead with one sentence acknowledging it neutrally ("I was part of the $X layoff at $CURRENTCO in March") and pivot immediately to what you're looking for next. Don't editorialize about the company's strategy or whether the cuts were fair. Layoffs are common; interviewers know how to handle the topic. What they're grading is whether you can talk about it without bitterness.

You're being managed out. Don't say so. Frame the search as a deliberate move toward a different scope. Confidentiality protects you and the company; the interviewer doesn't need the internal politics. If pressed, "the team is going in a direction that's not the work I want to be doing" is sufficient.

You're leaving because of compensation. In an early-stage interview, frame it as "the comp ceiling at my current company is structurally below market for my level — that's part of the reason I'm looking, but the bigger reason is X" and then name a non-compensation reason. The recruiter conversation about money happens separately.

For the broader behavioral-interview framework this question sits inside, see behavioral-interview-star-framework. For the related question about how to handle gaps and previous separations on the resume, see how-to-talk-about-getting-fired.

What this isn't

A few clarifications:

• It's not a license to be insincere. The structure works because it forces specificity, not because it papers over the real reason. If you can't name a specific pull, the structure won't save you.
• It's not the same answer for every interview. The "pull" framing should change to reflect the actual role you're interviewing for. A canned answer that doesn't connect to the JD will register as canned.
• It's not the place to negotiate. This question is asked in early-stage interviews. The compensation conversation comes later. Don't use this answer to set up a negotiation point.

The short version: frame as pull not push, name one specific gap, connect to this role, land in 60-90 seconds. The tone of the answer matters as much as the content. The interviewer is forecasting how you'll talk about them next.