Why Are You Leaving Your Job When the Honest Reason Is Your Manager

Say the honest reason is your manager. When an interviewer asks “why are you leaving your job,” don’t name the manager. Name the facts the manager created. Build the answer in three parts. First, give one or two facts about your current role that anyone could check. A frozen roadmap counts. So does a promotion path that needs scope your team no longer has. Leave out judgments like “my manager doesn’t value engineering.” Second, say what you tried before you started looking. Third, connect the gap to something specific in this role. Interviewers listen for two risks in this answer. One is that your verdict on your old team can’t be trusted. The other is that you leave at the first sign of trouble. Facts handle the first risk. Your attempt to fix things handles the second. This post follows one Android engineer whose real reason was her manager. It ends with her full answer.

Why are you leaving your job gets scored on how you describe the reason

Alison Green writes the Ask a Manager column. In a February 2023 answer, she draws a useful line. The rule against badmouthing an employer is mostly about subjective claims. Her examples include “my boss was a nightmare” and “the culture was toxic.” The interviewer doesn’t know you yet. So they can’t tell whether your verdict is fair or whether you’re the difficult one. A short, objective fact doesn’t carry that risk.

Green also prefers the plain answer when one is true. Several years in a role and readiness for something new is enough, she says. But she adds a limit. After five months in a job, “ready for something new” sounds flighty. In that case she suggests the most neutral true fact you have. One of her examples fits many engineers. You were hired to do one thing. Then the company turned out to need another.

Codecademy published a May 2024 guide to this question by Rebecca Dodd. Codecademy sells courses and career coaching. The page promotes both. The guide quotes Jean du Plessis, a senior engineering manager at Upbound. He says he asks candidates what they did to improve things before leaving. “I would rather not hire somebody who moved on at the first sign of struggle,” he told Dodd. So the reason itself rarely decides this question. How you describe it and what you did about it carry the score.

Nadia’s real reason was a manager who froze her work

Nadia is an Android engineer at a fitness app company. A year ago, her team got a new engineering manager. Within two months, he moved the Android app to maintenance mode. New features went to the iOS team first. Nadia’s proposal to split the app into modules was shelved twice. Her promotion case to senior stalled. The feedback was that she lacked “cross-team scope.” Her team no longer had any cross-team work.

Her first practice answer sounded like this. “My new manager doesn’t really value Android. He shut down every proposal I made. I don’t see a future there.” Each sentence is her honest view. But each one is a verdict on a person. The interviewer hears one side of a conflict with no way to check it. They also start to wonder what Nadia’s manager would say about her.

Swap each judgment for a fact the interviewer could check

Take each sentence of the first draft and ask what a stranger could confirm. “He doesn’t value Android” can’t be checked. “The Android app moved to maintenance mode” can. So can “new features ship on iOS first.” “He shut down every proposal” becomes “a modularization plan I wrote was deferred to next year.” “I don’t see a future” becomes “the senior promotion needs cross-team scope that my team doesn’t have.”

The facts tell the same story. Now the interviewer draws the conclusion from them. Leave the manager out of the sentences entirely. “The team moved to maintenance mode” is true and neutral. “My manager moved us to maintenance mode” invites the question of why you two clashed.

Keep it to two facts. A long list starts to sound like a case you’re building. Our post on the worst manager interview question makes the same move. It describes a practice rather than a person. That question asks about the manager directly. This one doesn’t, so the manager shouldn’t come up at all.

Say what you tried before you started looking

Du Plessis’s grit test comes as a follow-up. He asks what you did to change things. If you did nothing, the interviewer may assume you’ll leave their team the same way.

Nadia did try. She asked her manager for one cross-team project to support the promotion case. He said none were planned for the next two quarters. She also offered to take on the iOS team’s shared networking layer from the Android side. The iOS lead said no. Two attempts, each with a clear answer, show she worked the problem first. They also make her timing make sense. She started looking only after the answers came back.

Name the attempt and the reply in one sentence each. Don’t add how you felt about the reply. If you never raised the issue, say what you did inside your own work instead. Nadia could also mention a small internal tool she shipped during the freeze.

Check your reason against the job you’re applying for

Dodd’s guide gives one trap for engineers. A candidate who complains about an outdated stack may sound unwilling to work on inherited code. That matters if the new team has a large legacy codebase. Your reason for leaving tells the interviewer what you’ll dislike about their job.

So read the posting before you settle on wording. Nadia’s target role is on a team that owns a ten-year-old Android app. If she says “I’m tired of maintenance work,” she disqualifies herself. Her real gap is narrower. She wants a team where Android gets roadmap work and where cross-team scope exists. The posting mentions a shared design system across Android, iOS and web. That is the detail she ties her answer to. Our post on the “why do you want to work here” answer covers how to find that detail.

Nadia’s answer, which runs under a minute

Nadia, her company and her numbers are made up for this post. Keep her order of facts, attempt and fit. Put your own situation in it.

I’ve been on the Android team for three years. I’m proud of the work. We took the crash-free rate from 98.1% to 99.6%. About a year ago, the company moved the Android app to maintenance mode. New features now ship on iOS first. My promotion to senior needs cross-team scope. My team has none planned.

I tried to create some first. I asked for a cross-team project. None were planned for the next two quarters. I offered to help build the shared networking layer with the iOS team. The iOS team kept that work. So I started looking about two months ago.

What drew me here is the shared design system across Android, iOS and web. That’s the kind of cross-team work I’ve been trying to get. I’m also comfortable in an older codebase. Most of my crash-rate work was in code older than my time on the team.

The first paragraph never mentions her manager. The second answers the grit question before it’s asked. The last line heads off the legacy-code worry for this specific team.

Give the recruiter and the hiring manager the same reason

This question can come up twice in one loop. A recruiter may ask it in the first call. The hiring manager may ask it again later. Both may write notes. Those notes can be read side by side. Our post on the Amazon bar raiser interview shows how a debrief compares them. Say you told the recruiter “growth.” Then the hiring manager hears about a frozen roadmap. The gap can look like a hidden reason.

So make the recruiter version a short cut of the full one. Nadia’s is three short sentences. “The Android app moved to maintenance mode. My promotion needs cross-team work my team doesn’t have. This role has that work.” The hiring manager then hears the same reason with the attempt and the detail added. Nothing in the longer version contradicts the shorter one.

1 thought on “Why Are You Leaving Your Job When the Honest Reason Is Your Manager”

Leave a Comment