How do you explain a departure without badmouthing a former employer?

## The mistake this technique exists to fix The single most common way a strong candidate damages themselves is explaining a departure by describing what was wrong with the previous employer. It is a natural answer — the question is literally why you are leaving, and the honest cause often *is* something that was wrong. It is also the answer that costs the most, because it is unverifiable. That asymmetry is the whole thing. A hiring manager can assess your test design or your bug-triage judgment directly. They cannot assess your previous manager. So a critical account gives them exactly one usable data point: the way you talk about people who are not present to answer. Whether the criticism was justified never enters into it. ## The reframe: constraint, not fault Almost every genuine reason for leaving can be stated as a constraint rather than a fault, because they are usually the same fact from two angles. | The fault version | The constraint version | |---|---| | My manager didn't understand testing | The automation work I was hired for kept being deferred | | The developers kept breaking the build | Quality checks ran after the point where fixing them was cheap | | Nobody there cared about quality | Test ownership sat outside the function, so I couldn't change the process | | The company was chaotic | Priorities changed faster than a regression suite could keep up | The right-hand column states what was missing rather than who was at fault. It is not softer, and it is not evasive — it is the same information, expressed in the form the listener can actually use. A hiring manager hearing the constraint version can immediately check whether their role fixes it, which is the conversation you want. ## Three rules that make the reframe hold **Length is the tell.** Even a perfectly neutral explanation goes wrong if it runs long. One clause about the constraint, then move on. If a third of the answer is about the previous role, the listener's summary of you will be 'had a bad time at the last place', whatever words you used. **Never characterise a person.** Situations are safe; people are not. 'Ownership of the suite sat elsewhere' is a fact about an organisation. 'My manager was inexperienced' is a judgment about a human being that the listener cannot check — and softening it does not help. 'He was inexperienced, which is normal in a fast-growing team' is still a character verdict wearing a polite jacket, and experienced interviewers hear it as one. **Land on the forward half.** The reframe is only half the work. After the constraint, say what you are moving toward, specifically enough that the sentence could not be recycled for another employer. Without that, a neutral departure reason just sounds like an absence of enthusiasm. ## A worked rewrite, in a testing role The draft, spoken honestly: 'My last manager had no idea what they were doing. I was hired to automate the regression suite and after a year I was still writing manual cases by hand.' The second sentence is fine — it is a fact about the work. The first is the one that costs. The rewrite keeps everything true and drops the character verdict: 'I was hired to build out the automated regression suite, and the automation work kept getting deferred behind manual sign-off. That is the piece I most want to own, which is why this role interested me.' Nothing has been concealed. The listener now knows the work was deferred, knows what you want, and has not been asked to take your side against a stranger. ## When you are asked directly Sometimes a hiring manager probes: 'Was your manager the problem?' The answer that works is short, non-committal about the person, and specific about the situation: 'We disagreed about the priority of the automation work, and I didn't win that argument. I'd rather join somewhere that has already decided it matters.' You have conceded a disagreement, taken your half of it, and declined to litigate. Repeating the neutral line a second time is fine; interviewers who probe are usually testing whether the composure holds, not fishing for the gossip. ## The failure mode on the other side Over-correcting has its own cost. 'It was a great place, I just fancied a change' is unfalsifiable and empty, and it invites the probe you were trying to avoid. The target is not blandness. It is a real, specific, checkable constraint, stated once, with no person in it.