Topic: Job switch

How to answer "Why are you leaving your current job?"

Updated · 5 min read · Job switch

Answer "why are you leaving your current job?" with an honest reason framed around what you're moving towards, not what you're running from: more ownership, a different kind of work, a skill you want to build, or a better fit for your life. Keep it to two or three sentences, avoid criticising your manager or company, and link your reason to something specific in the new role. If you're leaving because of a layoff, health, family or a bad situation, it's fine to say so briefly and neutrally, then move on to why this role fits.

What the interviewer is checking

  • Whether you'll leave this job for the same reason
  • Whether you're likely to speak badly about them later
  • Whether your reason fits what the role offers
  • Whether your story matches your resume

A good answer reassures them on all four.

A simple structure

  1. One honest sentence about your current situation, stated neutrally
  2. What you're looking for next, specific
  3. Why this role offers it

Sample answers for common reasons

Adapt these to your situation. Don't memorise them word for word.

Growth or learning has slowed

"I've learned a lot in my two years supporting the billing application, especially around production debugging. The work is now mostly maintenance, and I want to build new features and work on system design. This role involves building new services, which is exactly the direction I'm aiming for."

Moving from a service company to a product company (or the reverse)

"I've enjoyed working on client projects across three domains, and it's given me a good base. Now I'd like to work on one product for longer, see the long-term effect of my decisions and go deeper on performance. That's why your platform team appeals to me."

Salary below market

Money is a valid reason, but don't make it the only one you mention.

"I'm looking for a role with more responsibility, and with that, compensation in line with the market for my experience. This role offers ownership of a module, which I'm ready for."

Long bench or no project

"My project ended a few months ago and I've been on the bench. I've used the time to complete a cloud certification and build a small project, but I want to get back to hands-on development, which this role offers."

What to do on the bench has ideas for using that time well.

Layoff or company restructuring

"My role was part of a larger restructuring that affected several teams. Before that, I led the migration of our reporting service to the cloud. I'm looking for a stable team where I can apply that experience."

Layoffs are common and most interviewers understand. Be brief, factual and unashamed.

Relocation or family reasons

"I'm relocating to Pune for family reasons, and my current company doesn't have a team here. Your role is a strong match for my backend experience."

Difficult manager or toxic environment

Don't describe the conflict. Focus on what you want instead.

"I'm looking for a team with clearer processes and more collaborative decision-making. From what I've heard about how your team works with code reviews and planning, that seems like a good fit."

Leaving after a short time (under a year)

"The role turned out to be quite different from what was discussed. It was mostly manual testing rather than the automation work I was hired for. I'm looking for a role where automation is the core of the job, and this one clearly is."

Show that you've learned to ask better questions before joining.

What not to say

AvoidWhy
"My manager is terrible."Raises questions about you, not them
"Only for money."Suggests you'll leave again for a better offer
"I'm bored."Sounds like low commitment; say what you want to do instead
"I just want a change."Too vague; they'll keep asking
A different story from the one on your resume or LinkedInInconsistencies hurt trust
Confidential details about your company or clientsA serious red flag

Follow-up questions to expect

  • "Did you discuss this with your manager?" Have an honest answer, such as "Yes, I asked about moving to a development team, but there were no openings in the near future."
  • "What would make you stay?" Be honest without inviting a counter-offer you'd refuse anyway.
  • "How do we know you won't leave for the same reason?" Point to what's different about this role.
  • "What is your notice period?" Be precise; see notice period, buyout and the 90-day notice.

If you've already left

If you're between jobs, say so plainly and explain what you've done since: "I left in March to care for a family member. That's resolved now, and in the last two months I've been refreshing my skills in React and building a small project." Gaps are much less of a problem when you explain them simply.

Check your own reason first

Before the interview, be clear with yourself about why you're leaving. If the real problem is something a new job won't fix, questions to ask before switching jobs can help you think it through. And if you'd like to talk it over with someone anonymous before deciding, that's what NoTitle is for.

Frequently asked questions

Is it okay to say I'm leaving for a higher salary?

Yes, if you pair it with responsibility or growth. Salary alone can make interviewers worry you'll leave again for the next offer.

What if I was fired?

Be brief and honest without going into detail: what happened in one sentence, what you learned, and what you've done since. Don't lie; background checks may reveal it.

Should I mention a bad manager if they ask directly?

Keep it neutral: describe the kind of working style you work best with, rather than criticising a person.

How long should my answer be?

About 30 to 45 seconds. A long explanation can sound defensive.