INTERVIEW QUESTION
Why did you leave your last job? What to say in every situation
Explain why you left honestly, even when the reason is awkward, and move quickly to what you want next.
This question feels like a trap because the honest answer is often messy: a reorganization, a manager you clashed with, a layoff, a job that wasn't what the description promised. So people either over-explain or invent a tidy story about “growth.”
You don't need either. The interviewer mostly wants two things: a reason that makes sense, and some reassurance that whatever happened won't follow you into their team.
How much to say about the past
Give the real reason in a sentence or two, plainly and without blame. Then say what you want to do next and why this role offers it.
As a rough guide, if the part about the past takes more than about 15 seconds, it starts to sound like the main story.
A video on answering common product management interview questions describes the same balance. Present the move as a deliberate step toward something, acknowledge what happened without drama, and take ownership instead of blaming anyone.
If the interviewer raises a specific concern, such as a gap or a short stay, answer it directly. Acknowledge it, say what you've done since, and move on to why you're ready for this role. Getting defensive or apologizing at length makes an ordinary situation sound worse.
What to say in each situation
The wording below is made up, to show the tone. Adapt it to what actually happened, and never say anything a reference check would contradict.
Laid off. Say so directly. Layoffs are common, and interviewers rarely hold them against anyone.
“My role was one of about forty cut when the company closed its European office. I'm proud of the work I did there, and I'm looking for...”
Let go or fired. Keep it short and honest, own your part, and show what's different now.
“It wasn't the right fit. The role needed someone who had already run enterprise sales cycles, and I was learning them on the job. Since then I've...”
A short stay. Explain what changed after you joined, without blaming anyone.
“The project I was hired for was paused after a funding change, so the job became mostly support work. I decided to look for a role closer to what I was hired to do.”
Several short stays. Raise the pattern yourself, before they have to. End with something that counters it, such as how long you've been in your current role or a project you saw through.
“Two of those were startups that ran out of money. This time I'm looking for a team where I can stay and build for several years, which is part of why this role appeals to me.”
Changing careers. Present it as a deliberate decision, and name what carries over.
“I spent five years teaching and kept redesigning course materials after watching students struggle. I've trained in UX research and design since then, and this role lets me do that work full time.”
Coming back after a break. One sentence, then the present.
“I took a year out to care for a family member. I've kept my skills current with a part-time project, and I'm ready to come back full time.”
A difficult manager or culture. Describe the environment you work best in, not the people.
“I work best where decisions are made in the open and stick for a while. Our direction changed often enough that it was hard to finish things. From what you've described, your team plans with steadier priorities.”
Still employed, leaving for growth. Name the specific work you want, not just “growth.”
“I've enjoyed my current team, but the service I look after is stable now, and I want to own something earlier in its life.”
Example answers
These made-up examples show a different situation for each role. In every pair the facts are the same, and only the framing changes.
Software engineer
After a layoff
Weaker
“There were layoffs and I was let go. To be honest, it was badly handled. Leadership kept saying our jobs were safe, and then they cut half the team with no warning.”
The frustration is understandable, but the interviewer hears the complaint rather than anything about you.
Stronger
“I was part of a layoff that cut about half of our platform team in March. I'm proud of what I built there, especially the deployment pipeline the whole company now uses.
Since then I've been looking for a team that runs its own infrastructure at a larger scale, which is a big part of why this role appeals to me.”
One factual sentence about the layoff, one about the work, and the rest about this role.
Product manager
After a reorganization
Weaker
“Honestly, my manager made it really hard. Decisions kept getting reversed, nobody listened to product, and leadership didn't have a clear strategy. I just couldn't grow there anymore.”
The frustration may be completely fair, but all the interviewer hears is the complaint. They can't check your side of it, and they may wonder how you'd describe them one day.
Stronger
“After a reorganization, my team moved from building new features to maintaining a platform other teams build on. It's important work, but I've realized I do my best work close to customers, running discovery and deciding what to build.
This role owns a customer-facing product from research to launch, which is what I want to be doing for the next few years.”
Most of the answer is about the future and about this role. The past gets one fair sentence.
Product designer
After a short stay
Weaker
“I've only been there six months, but it wasn't what I was promised. They said it was a senior design role, but I've mostly been making marketing banners.”
The disappointment is fair, but it comes across as a complaint, and it doesn't say what the candidate wants.
Stronger
“I joined to lead design on a new product, but the product was paused soon after I started, and the role became mostly marketing design. I've done that work properly, but it isn't where I want to grow.
I'm looking for a role designing a product with real users, which is what this team does.”
It explains what changed without blaming anyone, and turns quickly to what the candidate wants.
Data analyst
Still employed, looking for different work
Weaker
“I'm bored in my current role. It's the same reports every week, and my manager doesn't give me anything interesting to work on.”
This blames the manager and makes the candidate sound disengaged.
Stronger
“My current role is mostly weekly reporting, which I've automated as much as I can. I've enjoyed the few times I've worked on experiments, and I want that to be most of my job.
This role is on the experimentation team, so it's a direct step toward that.”
The same reason, framed as moving toward something. Mentioning the automation shows the candidate did more than wait.
Program manager
After being let go
Weaker
“I was let go, but honestly it wasn't my fault. The program was badly set up before I joined, and my manager needed someone to blame.”
Even if parts of this are true, blaming others is the biggest risk with this question.
Stronger
“I was let go after a program I was running missed two major dates. Part of that was on me: I didn't raise the risks early enough or clearly enough.
Since then I've changed how I report status. I flag risks the week I see them, with a clear request for help. I'd like to bring that to a team like yours, where programs are large enough that early warnings really matter.”
It owns what went wrong without over-apologizing, and shows what changed. That's what interviewers listen for when someone has been let go.
Consultant
Changing careers into consulting
Weaker
“I'm leaving engineering because I'm tired of just writing code all day and I don't feel valued. I want a job where people listen to my ideas.”
It's about what the candidate dislikes, and “people don't listen to me” raises questions about how they work with others.
Stronger
“I've spent four years as an engineer, and the part I've enjoyed most is working with business teams to decide what to build. I've been doing more of that, and I want it to be my whole job.
Consulting lets me work on those decisions across different companies, and your technology strategy practice would use my engineering background directly.”
A deliberate move toward something, with a clear link between the old career and the new one.
What makes it go badly
In a discussion about a 30-minute HR screen, the red flags listed include criticizing a former employer, unclear reasons for moving and unrealistic salary expectations. Most problems with this answer come from the same few places:
- Complaining. Even a justified complaint turns the answer into a story about blame.
- A made-up reason. An invented growth story can fall apart under one follow-up or a reference call.
- Over-explaining. Two minutes on a layoff makes an ordinary event sound like a problem.
- Wanting something this job can't give. Saying you want to manage people, for a role with no reports, raises a new concern.
- Money as the only reason. Pay is a legitimate reason. As the only one, it suggests you'll leave again for a better offer.
One test before the interview: read your reason as if you were your former manager. If they'd wince, rewrite it until it's accurate and fair. This question often follows tell me about yourself and leads into why do you want this job?, so it helps to practice the three together.