Skip to content
CareerCanopy

How to respond to 'why did you leave your last job?' after a layoff

There is exactly one bad way to answer this question, and it is to answer it for ninety seconds. Hiring managers are not asking about the layoff. They are asking whether you can speak about it in two sentences without flinching, without bitterness, and without subtly blaming someone. The answer is a structure, not a paragraph. Fact, scope, what you are looking for next — then back to the role. Practice it once out loud before you ever use it in an interview. The pacing matters as much as the words.

01

The answer

Twenty to thirty seconds. Said calmly. Hands not in front of your face. "I was part of a layoff at [Company] in [month] — they cut the whole [team / division], about [N people / 20% of the org]. It was a budget decision, not performance. What I'm looking for next is a [Senior Product Manager] role at a company that's [past the early-survival stage / shipping to enterprise customers / serious about the data layer] — which is part of why this conversation is interesting to me." Then stop. Do not add a third sentence. Take a sip of water. Wait.

  • Why this works: 'team-wide' or 'about [N]' tells the interviewer this was structural in five words
  • Why this works: 'budget decision, not performance' is the line that closes the question
  • Why this works: pivots back to what you are looking for, which is the actual purpose of the question
  • Why this works: ends with a hook into the role, which most candidates forget to include
  • Why this works: the silence after is on them — most interviewers will move on

02

Variations

If the layoff was a smaller cut and people might ask why you specifically: "I was part of a layoff at [Company] in [month]. It was a smaller cut — about [N] people across [function]. The decision came down to overlap with another team after a reorg, and I was the more recent hire. What I'm looking for now is [role] at a company where [specific thing]." If you have been out of work for a while and they ask why it is taking so long: "I've been being selective. After [Company], I could have taken a few roles, but they would have been roles I'd be searching out of again in a year. I'd rather take an extra month and land somewhere I can build. Which is part of why I asked for this conversation specifically." If the company went under entirely: "The company shut down in [month] — the [funding round didn't close / acquisition fell through / the bridge ran out]. Everyone went home the same day. I'm proud of what we built. Now I'm looking for [role] at a [stage / industry] company." If the cut included your manager and you cannot use them as a reference: "It was a layoff that included most of [function / our level]. My direct manager was part of the same cut, which is why my reference is going to be [grand-skip name / peer / cross-functional partner] — happy to share the context."

03

What not to say

The lines that turn a clean answer into a flag.

  • 'It was complicated' — interviewers hear 'there is more to this story than I want to tell'
  • Anything about your manager, even praise — the question is about you, not them
  • 'I probably should have seen it coming' — sounds like you missed obvious signals
  • 'I'm so grateful for the experience' — too performative for a layoff explanation
  • Long company-strategy narrative — the more sentences, the more it sounds defensive

04

If they push for more

Some interviewers will follow up with 'and what do you think happened there?' That is the test. The answer: "Honestly, the company over-hired in 2022 and corrected in 2024 — same story as a lot of the sector. Inside that, my team's roadmap got consolidated with another team's, and the headcount math didn't work for both. I don't think it was personal, and I don't think it was bad management. It was a budget decision. What I took from it is [one specific lesson]. Which is part of what I'd want to do differently here." The last sentence is the move. It turns the question into a connection back to the role.

Questions

Common questions

How long should my answer to 'why did you leave your last job' be?

Twenty to thirty seconds. Two sentences for the layoff, one sentence pivoting to what you are looking for next. Longer than that and the interviewer starts to read defensiveness into the explanation, even when there is nothing to read.

Should I say I was laid off, or use a softer phrase?

Say 'laid off' or 'part of a layoff.' Soft phrases — 'we parted ways,' 'I transitioned out,' 'my role was eliminated' — sound like you are hiding something. The word 'layoff' is neutral now. Most hiring managers have either lived through one or run one. Clear language is the safer move.

Should I explain why I specifically was cut?

Only if they ask. The first answer should treat the layoff as structural — 'whole team,' 'budget decision.' If they follow up, give one sentence: 'My team's roadmap got consolidated with another team's, and the headcount math didn't work for both.' Then pivot back to the role you are interviewing for.

Read next

$79 · One time

Your plan is built around what you tell us — not a template.

Start with a few questions. The plan follows.

Start your plan

Less than one session with a career coach.