You were laid off from your last job. Walk me through what happened.
answer
- state it flatly, one sentence
- scope: how many, which function
- no defensiveness, no over-explaining
- what I finished and handed over
- pivot to what I want next
basics
~20 sScreens for whether the separation was really about performance and how you handle a setback you did not choose. State the scope of the cut in one flat sentence, stay unbothered, show what you completed, then move the conversation forward.
how to answer
5 beats- the fact, stated flatlyOpen with the plain fact in one unhurried sentence. Tone is the whole signal here — the same words delivered anxiously read as concealment. Practise this sentence more than any other part of the answer.
- the scope of the cutGive the shape: how many people, which function, whether the team was thinned or closed. A whole-function or site-wide cut answers the selection question for you, so state it early rather than making the interviewer ask.
- what I was in the middle ofSpend the bulk of the airtime here, on the work itself with one concrete number. This is the part that quietly refutes any performance theory, and it is the part candidates skip because they are still explaining the news.
- how I left itDescribe the handover: documentation, working sessions, whoever picked the work up. Behaviour in the notice period is the closest thing an interviewer has to a live sample of how you act under bad news.
- what I am looking for nowClose by turning the answer toward the role in front of you, ideally connected to what the experience taught you to look for. One sentence, then stop.
your answer
4 story prompts- Write the scope of the cut in one flat sentence: how many people and which function.
- List two things you finished before the decision, at least one with a number.
- Name the person who would confirm the cut was not about your performance.
- Rehearse the opening sentence aloud until it sounds unbothered rather than braced.
draft and rehearse your own answer in a learn session
go deeper
Involuntary exits get screened for two things: whether the separation was performance-related, and how you carry a setback you did not choose. The interviewer is listening for a calm factual account with no score-settling. A strong answer gives the scope of the decision, the work you completed and handed over, and a forward-looking close rather than a defence.
Sure. The company cut about a third of engineering when a funding round came in smaller than planned, and the quality pod went entirely — five of us on the same day. It was not performance related; my review two months earlier was fine and my lead offered to be a reference, which she has been. I had been on the test automation program for a bit over four months. I had converted the account-settings and notification suites, twenty-nine cases between them, and the nightly run for those areas went from eating most of somebody's morning to being green before standup. The piece I was mid-way through was the fixtures for search, so I used my last week to write that up properly, with the gaps listed, so whoever inherited it would not start cold. I will not pretend it was not a jolt — it was my first job and I found out in a fifteen-minute call. But there is nothing complicated behind it, which is why I would rather say it up front than have it come up later. What I want now is somewhere quality is staffed as a function in its own right rather than being the first line trimmed when the numbers move, and that is honestly what made me apply here.
It works because the news takes two sentences and the work takes the rest, with a number attached. Naming the reference and admitting the jolt without dwelling on it reads as settled rather than defensive. Speculating about who was kept, or leaving out the handover, would weaken it considerably.
There was a company-wide reduction after a strategic reset, and quality engineering was one of the functions closed outright rather than thinned — nine people across two sites. I was not blindsided. The automation program I was leading was about three weeks from finished, and the stated plan afterwards was to fold testing into the feature squads, so the function had an end date one way or another. What I did with the notice period matters more to me than the news does. I finished the last two service migrations, ran two working sessions with the squads inheriting the suites, and wrote a triage guide for the failure modes they would hit in their first month. Hands-on checking per release was down to eighteen hours from sixty-two, and I wanted that to hold after I left rather than decay in a quarter. I would put it plainly: the decision was about cost structure, not about my work, and my former director will say the same. Where it leaves me is wanting the opposite of what I just came out of — an organisation where the quality function has a mandate that survives a budget cycle. That is the thing I have been asking about in every conversation, including this one.
The strength is that the handover carries the answer: two working sessions and a triage guide are evidence no adjective can substitute for. Understanding the business logic without endorsing or attacking it reads as maturity. Any hint that the decision was foolish, or a result claimed without the handover, would flatten it.
Say it plainly and do not apologise for it. Your job is to make it boring: the scope of the cut, one piece of work you finished, and someone who would confirm it was not about performance. Nerves show up as over-explaining, so practise the short version aloud.
Show that you understood the business reason, not just the personal outcome. Interviewers at this level expect you to describe what you were mid-way through and how you handed it over, because a clean handover under bad news is the strongest evidence available to you.
You may have seen it coming or been consulted on it. Speak about the economics neutrally, describe what you did to protect continuity for the work and the people around you, and resist any framing where you were the last competent person standing.
Give the strategic context in a sentence — what changed, what the company chose — without relitigating the decision or naming who made it. What distinguishes this level is what you preserved: successor, documentation, commitments honoured. Any trace of score-settling with executives reads as a leadership failure of your own.
saying these in an interview costs you the question
- Over-explaining until the answer sounds like a defence
- Implying the cut was really about a grudge or office politics
- Leaving it out and letting the interviewer discover it later
- Bitterness about leadership, investors or the funding situation
- No account of what you accomplished before the decision
- Delivering it as an apology rather than as a fact
- How many people were affected?Give the number and the shape of the cut — a function closed, a site consolidated, a percentage across engineering. The shape matters more than the number, because a whole-function closure removes the question of individual selection entirely. If you genuinely do not know the total, say the part you do know rather than guessing.
- Do you know why your role was one of the ones cut?Answer with the structural reason if there is one, and be willing to say you were not given a detailed rationale. Do not fill the gap with speculation about colleagues who stayed. If there was any performance element at all, a short honest framing plus what you changed since beats a version that unravels on a reference call.
- Would your former manager give you a reference?Say yes only if it is true, and offer the person's role rather than treating it as a rhetorical flourish. If the relationship is complicated, name a different credible referee — a tech lead, a peer, a stakeholder — and move on without explaining the complication in detail.