Reason for Job Change: How to Answer (With Sample Answers)

The reliable formula for this question is to turn a push into a pull: state what you are moving toward rather than what you are escaping. Interviewers are checking two things — whether you will leave this job for the same reason, and how you talk about people you no longer work with. That second one is why criticising a current employer costs candidates offers even when the criticism is fair; it reads as a preview. Layoffs, restructures and redundancy need no euphemism at all, and stating them plainly works far better than a vague answer that invites follow-up.

Every interview for an experienced candidate includes some version of it: “What is your reason for job change?” It sounds like small talk. It isn’t. This is a risk-assessment question, and a careless answer here undoes a strong interview.

The trap is that the honest answer is often negative — a bad manager, no increment, a project going nowhere. You can’t lie, and you shouldn’t. But you can choose which true thing to lead with.

On this page

• What the interviewer is checking
• The safe formula
• Sample answers by situation — growth, salary, bad manager, layoff, no projects, relocation, career switch, short tenure, gap
• What never to say
• If you’re pushed for the real reason
• FAQs

What the interviewer is checking

• Will you leave us too, and how soon? They’re hiring to stop a vacancy, not create a new one in nine months.
• Is the problem the job, or is it you? Candidates who blame every previous employer sound like the common factor.
• Are you moving toward something, or just away? People running away tend to take the first offer and keep looking. People moving toward something stay.
• Does your reason match the role? If you say you want ownership and this role has none, an honest interviewer may screen you out for exactly the reason you gave.

The safe formula: push becomes pull

The technique is simple: state the limitation factually, then spend most of your answer on what you’re moving toward.

1. One neutral sentence on what’s missing in the current role. Factual, no adjectives, no names.
2. One sentence on what you want next.
3. One sentence connecting that to this specific role.

Roughly 20% about leaving, 80% about arriving. Most candidates get that ratio backwards, and the interview turns into a discussion of a company they’re no longer going to work at.

Sample answers by situation

1. No growth, or learning has plateaued

The most common real reason, and the easiest to say well.

“I’ve been in the same role for about three years and I’ve learned a lot there, but the work has become fairly repetitive — the systems are stable and the roadmap is mostly maintenance now. I’m looking for a place where I can work on problems at a larger scale, which is why this role interested me: you’re rebuilding your data pipeline, and that’s the kind of work I want to be doing for the next few years.”

2. Salary

Money is a legitimate reason and interviewers know it. The mistake is making it the only reason.

“Honestly, compensation is part of it — my current package hasn’t kept pace with the market or with the responsibility I’ve taken on. But it’s not the only reason. I’ve also been the only backend person on my team for a year, and I want to work somewhere with a proper engineering team I can learn from. This role has both.”

Do not say “only for a hike.” Even where it’s true, it tells the interviewer you’ll leave for the next ₹1 lakh.

3. A manager or team problem

Never name a person. Never use a value-laden word. Convert it into a description of a working style you’re looking for.

“There’s been a fair bit of churn in my team over the last year and priorities have shifted several times, which has made it hard to see anything through. I do my best work with clear ownership over a defined area, and from the job description this role is set up that way.”

This is true, it’s specific, and it doesn’t require the interviewer to take your side against someone they’ve never met.

4. Layoff or company shutdown

No spin required. Be direct and unembarrassed — layoffs are common and interviewers know it.

“My company cut about 30% of the workforce in March and my team was part of that. It wasn’t performance-related — the whole product line was shut down. I’ve used the time since to finish an AWS certification I’d been putting off, and I’m looking for a stable team where I can go deep on infrastructure work.”

Say the number, say the reason, move on. Candidates who sound ashamed of a layoff create doubt that the facts don’t support.

5. On the bench / no real project

Common in Indian service companies and worth answering plainly.

“I’ve been on the bench for about four months. My last project ended and the allocations since have been short-term support work. I’d rather be building than waiting for allocation, and I want to work somewhere with a single long-running product where I can see the consequences of my own decisions.”

6. Relocation or personal reasons

Keep it short. You don’t owe details.

“My family has moved to Pune and I’m relocating to be with them, so I’m looking for a role here. Beyond the location, I chose to apply here specifically because of the work your platform team is doing.”

7. Career or domain switch

“I’ve spent four years in manual and automation testing, and over the last eighteen months the parts I’ve enjoyed most have been the tooling I built for the QA team rather than the testing itself. I’ve been learning backend development in parallel and built two services end to end. I’m looking to move into a developer role properly, and I’m comfortable that means starting a level below where I am now.”

That last clause pre-empts the obvious objection.

8. Leaving within a year

Short tenure needs a reason that isn’t about you giving up.

“I joined expecting to work on the mobile team, and three weeks in I was moved to internal tooling because of a reallocation. I gave it eight months to see if it would change, and it hasn’t. I don’t want to spend another year away from the work I actually want to build a career in — which is what this role is.”

Be ready for a follow-up. Interviewers probe short tenures, and a defensive reaction hurts more than the tenure does.

9. Explaining a gap

“I took eight months off after my last role — partly planned, partly because the market was slow. I used it to complete a cloud certification and to contribute to an open-source project, which is actually where I picked up Kubernetes properly. I’m ready to be back full-time now.”

What never to say

Anything negative about a named person. “My manager was incompetent” tells the interviewer how you’ll describe them in eighteen months. This is the single most damaging answer in the whole category.

“Toxic work culture.” Even when it’s accurate, it’s unverifiable and puts the interviewer in an awkward position. Describe the concrete thing instead — unclear ownership, constant re-prioritisation, no code review.

“I was bored.” True for many people; sounds like you disengage rather than raise problems. Say the work became repetitive and name what you want instead.

“Only for salary.” See above.

“Too much work.” Reads as low capacity. If workload really was the issue, frame it as wanting depth over spread: “I was covering three roles and doing none of them well.”

Badmouthing clients or a specific project. Same problem as badmouthing a manager, with an NDA risk on top.

Over-explaining. A ninety-second answer with three caveats sounds defensive. State it once and stop talking.

If they’re pushing for the real reason

Some interviewers will press — “but what’s the actual reason?” — either to test composure or because your first answer was too smooth.

Don’t panic and don’t reverse yourself. Give one more layer of honest detail without adding blame:

“That is the main reason. If I’m being fully candid, the reorganisation also meant the person who hired me left, and the new direction isn’t work I’m excited about. Nothing dramatic — I just don’t want to spend two more years on it.”

Composure under that follow-up is often what’s actually being tested.

Related questions

This one sits in a cluster with why should we hire you, your self introduction, and strengths and weaknesses. Prepare them together — they need to tell one consistent story. If your introduction says you love ownership and your reason for leaving says you wanted less responsibility, the interviewer notices.

Have a couple of questions ready for the end too. Asking about team structure is a natural, credible follow-through when your stated reason is about ownership or team quality.

Rehearsing the difficult ones

The situational answers — a layoff, a short tenure, being fired — are the ones that go wrong under pressure, because you’re managing your own discomfort while trying to sound composed. Reading a script isn’t enough; you need to have said it out loud a few times.

NostrobeAI runs AI mock interviews covering the full HR round with instant feedback on structure and pacing, plus real-time support during the interview itself. One-time credit packs, no subscription. (See how it compares to other AI interview tools.)