"Why Are You Leaving Your Job?" Answering the Flight-Risk Question

Answer "why are you leaving your current job?" by naming what you are moving toward, not what you are escaping, and pointing it at something this specific role offers. Keep it to two or three sentences, stay off blame, and never lead with money. The interviewer is not curious about your old team. They are quietly checking whether you will leave them the same way in a year.

Short answer: State a forward reason (growth, scope, a kind of work you want more of) that the role you are interviewing for genuinely supplies. Do not badmouth anyone. If the true reason is negative (a layoff, a bad manager, burnout), tell the truth in one clean line and then pivot to what you want next. Brief, honest, and forward-facing beats a long justification every time.

The real question behind the question

Nobody asks this because they want gossip about your employer. They ask because your reason for leaving your last job is the best available predictor of why you will leave the next one. Three fears sit underneath it, and your answer either quiets them or feeds them.

• Flight risk. If you are leaving after a year because you were "bored", the interviewer hears that you will be bored here in a year too. Hiring is expensive, and a fast repeat departure is the outcome they most want to avoid.
• A hidden problem. A vague or defensive answer reads as something you are not saying: a performance issue, a conflict, a firing dressed up as a resignation. Ambiguity gets filled in with the worst plausible story.
• A chronic blamer. If the reason is entirely someone else's fault, the interviewer wonders whether you will be sitting in another interview next year explaining that they were the problem. People who narrate every past job as a betrayal tend to repeat the pattern.

The interviewer is not asking "what was wrong with them?" They are asking "what will be wrong with us in eighteen months?" Answer the second question, not the first.

Once you see the three fears, the whole answer gets simpler. You are not defending your past. You are giving evidence that you are a low-risk, forward-looking hire who leaves for reasons a good employer can actually satisfy.

Turn the push into a pull, without lying

Almost every departure has a push (what is driving you out) and a pull (what is drawing you toward something new). Both are usually true at the same time. The push is what you feel; the pull is what you say. This is not spin, and it is not dishonest, because you genuinely are moving toward the thing you name. You are simply choosing which true half to lead with.

Compare the same reality framed two ways:

• Push, said out loud: "There is no room to grow, my manager takes credit, and the pay stopped keeping up."
• Pull, said out loud: "I am ready to own a larger surface than my current role can offer, and this position is built around exactly that."

Both describe one person leaving one job. The first invites three follow-up questions you do not want. The second invites the interviewer to picture you succeeding in the role. The trick is that the pull has to be real and it has to land on this role. A generic "I want growth" said to a company that cannot offer growth is worse than useless, because it shows you did not read what you applied for.

Real reasons, honestly reframed

Here is the reframe for the reasons people actually leave. The left column is the true push. The middle is what sinks the answer. The right is an honest, forward version that describes the same reality.

Notice what every good version has in common: it names a forward want, it stays off people, and it can finish with "which is exactly what this role offers". If your reframe cannot end that way honestly, you may be interviewing for the wrong job.

A note for a worldwide audience: the vocabulary differs by region. A "layoff" in the US is a "redundancy" in the UK and much of the Commonwealth, and statutory notice, severance, and consultation rules vary widely. Use whichever term is accurate for your situation and do not assume the interviewer shares your local frame. The reframe holds everywhere: describe the business event plainly, then pivot to what you want next.

A worked answer, built line by line

Take Farah, a backend engineer with four years of experience. Her company lost its largest client, froze the product roadmap, and moved her team into maintenance-only mode: keep the existing service running, ship nothing new. She is leaving because she wants to build again, and privately she thinks leadership mishandled the client relationship.

Her first-draft answer was a push with blame attached: "Honestly, management lost our biggest account and now there is no real work, just keeping the lights on." True, and disqualifying. It blames named people, it describes only what she is escaping, and it says nothing about what she wants next or why this role fits.

Here is the same three-check logic she used to fix it, as a small model you can run. It asks the three questions the interviewer asks silently, and hands back the fixes.

// Stress-test a "why are you leaving?" answer the way an interviewer hears it.
// Three silent checks: is it forward-facing (a pull, not just a push),
// does it stay off blaming people, and does what you want next actually
// exist in the role you are interviewing for?
function reasonForLeavingVerdict(answer) {
  const checks = {
    forwardFramed: Boolean(answer.movingToward),
    noBlame: !answer.blamesPeople,
    landsOnRole: answer.roleOffers.includes(answer.movingToward),
  };
  const passed = Object.values(checks).filter(Boolean).length;
  const fixes = [];
  if (!checks.forwardFramed) fixes.push("say what you are moving toward, not just what you are leaving");
  if (!checks.noBlame) fixes.push("drop the blame: describe the situation, not a person");
  if (!checks.landsOnRole) fixes.push("aim the reason at something this role actually offers");
  const verdict = passed === 3 ? "ready" : passed === 2 ? "tighten" : "rework";
  return { verdict, passed: `${passed}/3`, fixes };
}

// Draft A: the push-with-blame version.
console.log(reasonForLeavingVerdict({
  movingToward: "",
  blamesPeople: true,
  roleOffers: ["ship-to-users", "own-a-service"],
}));
// => {
//   verdict: "rework",
//   passed: "0/3",
//   fixes: [
//     "say what you are moving toward, not just what you are leaving",
//     "drop the blame: describe the situation, not a person",
//     "aim the reason at something this role actually offers"
//   ]
// }

// Draft B: the forward version, aimed at what this role offers.
console.log(reasonForLeavingVerdict({
  movingToward: "ship-to-users",
  blamesPeople: false,
  roleOffers: ["ship-to-users", "own-a-service"],
}));
// => { verdict: "ready", passed: "3/3", fixes: [] }

Draft A fails all three checks. Draft B passes all three because Farah named a forward want ("ship to users"), kept people out of it, and that want is something the target role visibly supplies. Her spoken version became: "The business shifted away from building new product, and I want to be shipping to users again. This role is centred on exactly that, which is why I applied." Same facts, no blame, and it ends on the role. The client mishap never comes up, because it answers a question nobody asked.

When the true reason is genuinely bad

Sometimes the reframe cannot hide a hard fact, and it should not try. Interviewers are experienced; a too-smooth answer over an obvious gap reads as evasion. The rule for the hard cases is: state the fact once, plainly, without drama, then move forward.

• You were laid off or made redundant. This carries no stigma when you name it cleanly: "My role was cut in a company-wide reduction." Do not over-explain, do not apologise, and do not volunteer that you were "one of the ones they chose". If it created a gap on your resume, our guide on explaining employment gaps in interviews covers keeping that clean too.
• You were managed out or fired. Be honest without confessing at length. "It was not the right fit and we agreed to part ways" is acceptable if it is true; what you must not do is lie, because references and background checks catch it. Then pivot fast to what you learned and what you want next.
• The environment was genuinely toxic. You can signal this without a rant: "The culture changed after an acquisition and it stopped being somewhere I could do my best work." One line. The moment you list specific grievances, the interviewer stops hearing your point and starts wondering how you will describe them one day.

The one reason to handle with extra care is leaving purely for money. Pay is a completely legitimate reason to move, and it is one of the most common ones. Surveys of workers who quit put low pay at the very top of the list. But leading with it in this specific question signals that a slightly higher counteroffer could keep you, or that a competitor with a bigger budget could poach you later. Acknowledge compensation as one factor and let a non-money pull carry the answer, then handle the number where it belongs, in the offer stage. Our guide on negotiating tech compensation covers doing that well.

Three ways a good reason still sinks

Even a sound, forward reason can land badly in the delivery. These are the failure modes to rehearse out of.

The fix for all five is the same discipline: two or three sentences, one honest forward reason, no named villains, and a clear tie to this role. If you cannot say it in under thirty seconds, you are explaining rather than answering.

Frequently asked questions

How long should my answer be? Two or three sentences, roughly fifteen to thirty seconds. This is a screening question, not an invitation to tell your career story. If you are past a minute you are almost certainly justifying instead of answering, and every extra sentence is a new opening for a follow-up you did not want.

Is it ever okay to say I left for more money? Yes, pay is a legitimate reason, and it is one of the most common ones people give. Just do not make it the headline of this particular answer. Name a non-money pull first and treat compensation as one factor among several, then negotiate the number properly at the offer stage.

What if I was fired or laid off? Say it plainly and briefly. A layoff or redundancy carries no stigma; name it as a business decision and move on. A firing needs honesty without a full confession: keep it short, do not lie, and pivot to what you want next. References and background checks will surface a false story, so the truth, cleanly told, is the safe choice.

How do I answer without badmouthing my current employer? Describe the situation, not the people. "The roadmap moved away from the work I want to do" is a fact about the business; "my manager was impossible" is a complaint about a person. The first is safe, the second predicts you will complain about the next employer too.

They keep pushing for the real reason. What do I do? Give one more honest layer, not the whole story. If the follow-up presses, you can add a single specific fact ("the team I was hired to build was dissolved in a reorganisation") and then return to what you want next. Repeating the forward pull calmly signals you are not hiding anything, just not dwelling.

Should my answer change between the recruiter screen and the hiring manager? Keep the substance identical so nothing contradicts across the loop, but you can go one degree deeper with the hiring manager, who cares more about fit and motivation. The recruiter mainly wants to rule out red flags; the manager wants to picture you thriving on the team.

What if I am currently employed and my search is confidential? Answer the same way, and keep the details vague enough that nothing traces back. You never need to name the client that was lost or the reorganisation team. If discretion is your bigger concern, our guide on interviewing while currently employed covers running the process without tipping off your employer.

Sources

• Indeed: how to explain your reasons for leaving a job on keeping the answer brief, honest, and framed around growth.
• BetterUp: why are you leaving your current job on staying positive and never badmouthing a current or former employer.
• Resume Genius: how to answer "why are you leaving your current job?" on giving a concise, forward-focused reason.
• Pew Research Center: why workers quit a job for the data that low pay and no advancement top the real reasons people leave.

Where to take this next

• Answering "why do you want this job?" so the forward pull you name here lands on a specific, researched reason.
• Explaining employment gaps in interviews for the layoff and between-roles version of the same honesty.
• Interviewing while currently employed to run a confidential search without tipping off your current team.
• Negotiating tech compensation for handling the pay reason where it actually belongs, at the offer stage.