How to Answer "Why Did You Leave Your Last Job?" (+ Example Answers)

By Alex VanceUpdated Sep 17, 202611 min read

A framework and six worked examples to build a calm, honest answer, plus how to field the follow-up questions that come next.

Table of contents

Why interviewers ask it
Other ways you'll hear it
How to build your answer
Example answers
Mistakes to avoid
Your answer checklist
FAQ

Featured image for "How to Answer "Why Did You Leave Your Last Job?" (+ Example Answers)"

By the end of this guide you'll have a short, calm answer to "Why did you leave your last job?" that states the facts, gives one clear reason, and turns the conversation towards the role you're interviewing for. You'll also know how to handle the follow-up questions that usually arrive straight after it.

Use the framework and the six worked examples to draft your own version, then check it against the list at the end before you rehearse it out loud.

Why interviewers ask it

Three competencies are being tested, and none of them is your loyalty.

The first is judgement. They want to know whether you leave jobs for considered reasons or on impulse, because that predicts how long you'll stay and how you'll behave when this role gets difficult.

The second is self-awareness and accountability. If something went wrong, can you describe it without blaming everyone in the building? Interviewers listen for whether you name your own part in a situation and what you changed afterwards.

The third is professional discretion. How you talk about a former employer is a live sample of how you'll talk about this one. Anyone who trashes a previous manager in an interview is showing what they'd say about their next one.

There's also a practical check: your answer should match your application, your dates and anything a reference would confirm.

Other ways you'll hear it

"Why are you leaving your current role?"
"Walk me through why you left [previous employer]."
"What's prompting you to look right now?"
"I see you were there for two years — what changed?"
"Why the gap between these two jobs?"
"What would have kept you there?"

How to build your answer

Use the FRAME method. It keeps the answer short, honest and pointed forward, and it works whether you resigned, were made redundant or were let go.

Fact — state the move in one neutral sentence. Say what happened and when: you resigned, the contract ended, the site closed, the role was made redundant, you were dismissed. Leading with the plain fact stops the interviewer guessing and stops you rambling. If the fact is unflattering, saying it first actually lowers the temperature.
Reason — give one driver, not four. Pick the single most credible reason: no route to the next level, the work changed shape, a relocation, a restructure, a decision to move into different work. A stack of reasons sounds like a cover story; one specific reason sounds like a decision.
Acknowledge — own your share, if there is one. If performance, fit or a clash played a part, name it in a sentence and say what you'd do differently. This is where accountability is scored. If there's genuinely nothing to own, skip this step rather than manufacturing a flaw.
Momentum — show what you've done since. Mention the handover you finished, the notice you worked, the course, the contract work, the caring responsibility you managed. This answers the unspoken question about gaps and about whether you left responsibly.
Endpoint — land on this role. Finish with what you're looking for next and tie it to something concrete about the job in front of you. The last sentence should be about them, not about your old employer.

Keep the whole thing to roughly 20 to 40 seconds spoken. Say it out loud until the neutral facts sound neutral, then stop rehearsing — over-polished answers on this question sound evasive.

Example answers

New graduate

Priya, graduate data analyst, leaving a fixed-term university placement
My last role was a twelve-month placement in the reporting team at a housing association, and it ended in July because the contract was for a fixed term tied to my degree. I stayed to the last day and handed over the two dashboards I'd built for the repairs team, including the documentation, because the person picking them up was new. Since finishing I've been doing the SQL work I never got to do in the placement, rebuilding one of those reports properly as a practice project. I'm looking for a first permanent analyst job where the reporting is part of the actual operation rather than a side task, which is why this one interested me — you've described a team that sits with the service managers rather than sending files over the wall.

Step up in the same field

Tom, warehouse team leader moving to shift manager

I'm still there, and I'd have stayed if there'd been a route up. I've run the night picking team of eleven for two and a half years, took the team from consistently missing the dispatch cut-off to hitting it most nights, and trained two of the leads who now cover my shifts. The site only has one shift manager and he isn't going anywhere, which is fair enough but it means the next step doesn't exist where I am. I asked my operations manager about it twice and he was straight with me about it, so I started looking rather than sitting on it. Your role covers two shifts and includes the planning side, which is the part I've only ever done informally. I'm working my four weeks' notice properly whatever happens.

Industry switch

Nadia, hotel front-of-house supervisor moving into contact-centre operations

I left hospitality in March after six years, the last two supervising a front desk team of nine at a 140-room hotel. The reason was the pattern of the work rather than the work itself: split shifts and permanent weekends stopped being sustainable once I was the only adult at home in the mornings. I gave a long notice period so they could recruit before the summer season. What I'm bringing across is the bit that actually transfers — I spent six years handling complaints at the point they became complaints, and I ran the shift handover that stopped the same problems reappearing on the next rota. Customer operations is the closest thing to that with a fixed schedule, and your team leads apparently coach on live calls, which is what I did every day on a desk.

Career change

Ben, secondary school teacher moving into learning and development

I resigned at the end of the summer term after seven years teaching science, four of them as head of year. I want to be honest about the reason: I loved the teaching and had stopped coping with the volume of everything around it, and I made the decision over about eighteen months rather than in a bad week. My own part in that was leaving it too long before I asked for help with the pastoral workload, and I've learnt to flag capacity earlier. Since July I've been doing freelance work writing and delivering safeguarding training for two multi-academy trusts, which is where I realised corporate L&D is the job I've effectively been doing with adults. I'm not looking for a gentler version of teaching. I'm looking to design and run training where I can actually measure whether it changed behaviour.

Returning after a gap

Grace, payroll administrator returning after fourteen months out

I left my payroll job in January last year because my father had a stroke and needed full-time care, and I couldn't do both well. It wasn't a career decision — I told my manager the situation and we agreed a leaving date that got me through the year-end run so the team wasn't stranded. He's in a residential placement now and settled, so I'm available full time with no restrictions. During the gap I kept my knowledge current: I did the CIPP update webinars on the legislative changes, and I ran payroll voluntarily for a small charity with about twenty staff, which kept my hands on a real system rather than just reading about it. I'm applying here because it's a bureau role with multiple clients, which is the variety I missed, and because I'd rather rejoin somewhere with a proper checking process than be a one-person function again.

Redundancy

Marcus, retail buyer made redundant in a restructure

My role was made redundant in April when the business merged its two buying teams and cut the layer I sat in — three of us went in the same round, and the category I bought for was absorbed into general merchandise. There was nothing to appeal; it was a structural decision, and the merchandising director has offered to be a reference. I spent my notice handing the supplier relationships over, including the two Far East suppliers I'd onboarded, because a bad handover there would have cost the business a season. Since then I've taken two freelance range-planning projects for a smaller brand, which has been a useful reminder of how much you can do without a big systems team. I'm looking for a buying role in a business where the category has room to grow rather than one being consolidated, and your own-brand plans are the reason I applied.

Mistakes to avoid

Mistake	Fix
Criticising your old manager, team or company culture, even mildly — "the management was a mess"	Describe the structural fact instead of the people: "the role changed after the restructure and the work I was hired for moved elsewhere"
Giving four reasons at once, so it sounds like you're testing which one lands	Choose the single most credible driver and say only that; extra reasons only come out if you're asked
Hiding a dismissal or a gap and hoping references don't come up	State it plainly in your first sentence, keep it to two sentences, and say what you changed afterwards
Talking for two minutes and ending up back inside the old job's politics	Cap the answer at about 40 seconds and finish on a sentence about the role you're interviewing for
Saying "I just needed a new challenge" with nothing behind it	Name the specific thing you'd run out of: no next grade, no budget, the same three products for four years
Making pay the whole answer when you're asked why you left	If pay was a factor, mention it once inside a bigger reason about scope or progression, and save the numbers for the money conversation
Going hot when the interviewer probes — "well, honestly, it was a toxic place"	Decide in advance the one sentence you'll repeat if pushed, and stick to it calmly rather than adding detail under pressure

Your answer checklist

One plain fact first. Resigned, redundant, contract ended, dismissed — stated in a sentence, with a rough date that matches your application.
One reason, specific enough to be believable. Something an interviewer could picture, not a phrase that would fit anyone's CV.
Nothing an ex-colleague could take offence at. Read your draft as if your former manager is in the room, because they may be on the reference call.
Evidence you left responsibly, or used the time well. A handover, a notice period worked, a course, freelance or voluntary work during a gap.
A closing line about this job. What you're looking for next, tied to something concrete you know about the role in front of you.

Frequently asked questions

When in the interview will this come up, and what if it's the first question?

It usually arrives in the first five minutes, right after "tell me about yourself", or at the point where the interviewer walks through your CV dates. Screening calls with a recruiter almost always include it, and a hiring manager will often ask it again later in their own words — so keep your two versions consistent. If it comes first, resist the urge to use it as your whole introduction. Give the short version — fact, reason, forward — and let the interviewer decide whether to dig. You will have other chances to sell yourself, and a brisk answer here signals that leaving wasn't dramatic.

How long should the answer be?

Aim for 20 to 40 seconds, or three to five sentences. That's long enough to be specific and short enough that the interviewer doesn't start reading meaning into the length. The exception is a situation that genuinely needs context: a dismissal, a long gap, or three short jobs in a row. Even then, add one or two sentences, not a paragraph. If you find your draft running past a minute, it's usually because you're justifying rather than explaining. Cut the justification and keep the facts.

What follow-up questions should I expect?

Most commonly: "Did you raise it with your manager before you decided?", "What would have made you stay?", "Would you go back?", and "Can we speak to your last employer?" Prepare a one-line answer to each. "Did you raise it?" is testing whether you deal with problems directly, so a yes with a short description of that conversation is far stronger than a no. "What would have kept you?" is a trap only if you answer with money or a grievance — answer with scope, progression or the work itself. On references, be straightforward about who can be contacted and when, including if it needs to wait until after an offer.

What if I was fired, or asked to leave?

Say it in your own words before they find out another way, keep it factual, and move straight to what you took from it. A workable shape is: what happened, what your part in it was, what you changed, and a sentence on why this role fits better. Avoid re-litigating the decision, even if you think it was unfair. If there was a formal process, a settlement or anything with legal implications, check what you are permitted to say before the interview — an employment adviser or your union can tell you where the line is. Interviewers hire people who have been let go all the time; what they screen out is defensiveness.