How to Answer “Why Are You Leaving Your Current Job?”

Short answer: A good answer to “Why are you leaving your current job?” is short, true and pointed forward. Name the real reason in neutral terms, give your current employer credit for what you learned there, then connect the move to what this role offers. Keep it to three or four sentences, never criticize your boss or company, and if you were laid off or let go, say so plainly once and spend the rest of the answer on what you have done since.

The question sounds like small talk, but it can come up as early as the first recruiter call, and your answer colors how the interviewer hears everything after it.

What the interviewer is really checking

Interviewers are rarely trying to trap you. They are listening for four things:

• Will the same problem happen here? If you are leaving over on-call load, slow promotions or an office policy, they want to know whether their job has the same issue. A mismatch found now saves both sides a bad hire.
• Are you moving toward something or just away? “I want to own a service end to end” is a reason to hire you. “I can't stand it there anymore” is a reason to wonder what you will say about them in a year.
• Judgment and discretion. How you talk about your current employer previews how you will talk about this one. Candidates who vent about a boss come across as hard to work with, even when the boss really was the problem.
• Consistency. Your answer should line up with your résumé dates, your “tell me about yourself” story and whatever a reference might say.

A three-part formula that fits almost any reason

1. The reason, stated neutrally (one sentence). Say what is true, framed as what you want rather than what you dislike: “I'm looking for more ownership of production systems” instead of “they never let me touch anything important.”
2. Credit (one sentence). Name something real you built or learned in the current role. It shows you leave places on good terms.
3. The bridge (one or two sentences). Tie the reason to something specific about this job: the team, product, stack or scope. This part overlaps with your answer to “Why do you want to work here?”, so research the company before you rehearse.

Then stop. A long explanation tends to invite follow-up questions about exactly the part you wanted to keep brief. Thirty to sixty seconds is plenty.

How to reframe the most common real reasons

The reframe has to be true. You are choosing which honest part of the story to lead with, not inventing a nicer one, and you should be able to back it with an example if asked.

Sample answers you can adapt

Written for software engineers, but the structure works for any role. Swap the bracketed details for your own; an answer that sounds memorized loses most of its value.

Growth ceiling

“I've spent [three years] on our [payments] team, and I'm proud that I [led the move of our checkout logic into its own service]. The next step I want is technical ownership of a larger system, and on my current team those roles are filled for the foreseeable future. This role owns [the whole order pipeline], which is exactly the scope I'm looking for.”

Compensation is part of it

“To be direct, compensation is part of it. Over the past year I've taken on [the on-call lead role and mentoring two new hires], and I want a role where the title and pay match that work. Beyond that, what drew me here is [the team's focus on developer tooling], which is where I want to grow.”

Saying pay matters is fine if it is true, but do not make it your only reason and do not name numbers here. Save specifics for the compensation conversation, which usually happens with the recruiter; our salary negotiation guide covers how to handle it.

Burnout or an unsustainable pace

“My team has been understaffed for most of the past year, and I've been carrying on-call for two services. I learned a lot about incident response, but it isn't a pace that produces good work long term. I'm looking for a team with a healthy rotation, and from what the recruiter described, that's how this team runs.”

You do not have to use the word “burnout” or share health details. Describe the conditions, not your state of mind.

A difficult manager or constant reorgs

“My team has been through several reorganizations, and priorities change often. I've kept my projects moving with short written plans and weekly check-ins, but I do my best work with stable goals and regular feedback. Your team's roadmap looked clear, and that's a big part of why I applied.”

No names, no blame: you describe the environment you thrive in and show you tried to make the current one work.

Relocation

“My partner accepted a job in [city], so we're moving in [month]. I've enjoyed my team and would have stayed, but the company doesn't support remote work for my role. I'm focusing my search on [city], and this team is a strong match for my background in [data infrastructure].”

How to explain being laid off

A layoff is usually a company decision about budgets or headcount, not a judgment of one person's work, so present it as a business event. Your job is to say it cleanly and move on.

• Use plain words, once. “I was laid off” or “my role was eliminated in a restructuring.” Vague euphemisms sound evasive.
• Add scope only if you know it. “The company cut its entire mobile team” makes it clear the decision was not about you. Do not guess at numbers.
• Skip the critique. Second-guessing leadership invites a debate you cannot win in an interview.
• Spend most of the answer on results and the present. What you delivered before, and what you have done since: a course, open-source work, contract projects or a focused search. A gap needs a sentence, not an apology.
• Line up a reference. A former manager who can speak to your work is one of the clearest signals that the layoff was not about performance.

Sample: “I was laid off in [June] when the company eliminated its platform team as part of a restructuring. Before that I led our migration to [Kubernetes], which [cut deploy times significantly]. Since then I've [completed a cloud certification and contributed to an open-source CI tool], and I'm looking for a platform role where I can keep building on that work.”

How to explain being fired or let go

This is where honesty matters most. Many employers check references or verify employment, and what a former employer shares varies: some confirm only dates and title, while others will say whether you resigned, were laid off or were let go. A story that does not match can turn a manageable situation into a dealbreaker. If an application asks whether you have been terminated, answer truthfully and keep your interview answer consistent with it.

1. Keep it brief and factual. One or two sentences on what happened. A long defense makes it sound bigger than it was.
2. Own your part. Even if you think the decision was unfair, name what you could have done differently. Interviewers listen for accountability, not self-criticism.
3. Show what changed. The skill you built, the habit you fixed, and evidence since, such as a contract role or a project that went well.
4. Do not hide behind “fit.” If it really was a role that changed under you, say so factually. If it was performance, call it that.

Sample: “I was let go from my last role after about a year. I joined a team that worked mostly in [Go], which I hadn't used in production, and I didn't ramp up fast enough on a project with a hard deadline. Looking back, I should have asked for pairing and help in the first week instead of trying to catch up alone. Since then I've [shipped two Go services as a contractor], and I now raise blockers early, not late.”

What never to say

• Anything negative about a specific person. Even accurate criticism of a named manager or coworker reflects on you.
• “I'm bored,” “I hate my job” or “I'm not really sure.” These suggest low motivation or that you have not thought the move through.
• “The work was too hard.” If the workload was unreasonable, describe the conditions, not your inability to keep up.
• Confidential details. Unannounced layoffs, internal financials, customer names or product plans. Sharing them signals you would share this company's too.
• A reason the new job obviously shares. Complaining about on-call when the role has on-call, or about travel when it requires travel, ends the conversation.
• Different stories to different interviewers, or embellishments. Interviewers at the same company often compare notes, and wrong dates or “I resigned” when you did not can surface in a reference or background check. Pick one honest answer and use it everywhere.

Follow-up questions to prepare for

Rehearsed answers usually fall apart on the follow-ups, so prepare these too:

• “Did you raise this with your manager?” Have one concrete example of trying to fix the issue before deciding to leave, such as asking for a stretch project or proposing a better on-call schedule.
• “What would make you stay?” This probes whether a counteroffer would keep you. If your reason is scope or direction, say plainly that a raise would not change it.
• “Why now?” Name the trigger: a reorg, a project ending, a move, a policy change. “It just felt like time” is weak.
• “Does your employer know you are looking?” It is normal to say no and to ask that they not be contacted until there is an offer.

In a first recruiter call, keep the answer even shorter and use the time to learn about the team; see our questions to ask a recruiter.

How to practice your answer

1. Write the blunt version first, for your eyes only. “My manager micromanages and I'm underpaid.” You cannot reframe a reason you have not named.
2. Rewrite it with the formula: neutral reason, credit, bridge.
3. Read it aloud and time it. Cut until it fits in under a minute.
4. Check it against your other answers. Your résumé, intro and “why this company” answer should tell one story.
5. Say it to someone, then answer their follow-ups. If no one is available, a free AI mock interview in CoPilot Interview works as a stand-in: paste the job description and your résumé, include behavioral questions, answer out loud, and get a score with what worked and what to improve.

FAQ

How long should my answer be?

About three or four sentences, or 30 to 60 seconds. Name the reason, credit your current role, and connect it to this job; longer answers tend to invite follow-up questions.

Is it OK to say I'm leaving for more money?

Yes, if it's true, but don't make it your only reason. Pair it with the scope you want and save specific numbers for the compensation conversation, usually with the recruiter.

How do I explain being laid off?

Say it plainly once: the company cut roles and yours was one of them. Then spend most of the answer on what you delivered before the layoff and what you have been doing since.

Should I tell an interviewer I was fired?

Don't lie, because reference and employment checks can contradict you. Give a brief, factual account, own your part, and focus on what you learned and do differently now.

Can I say I'm leaving because of a bad manager?

Not in those words. Describe the working style you do your best work in, such as clear priorities and regular feedback, and what you did to make the current situation work.

What if I'm leaving after less than a year?

Acknowledge it directly, give the honest reason in neutral terms, and show the next move is deliberate by explaining why this role fits what you want long term.