Why are you leaving your current job?
answer
- one honest push reason, no blame
- credit what the role gave me
- what I tried internally first
- pull: what this role offers
- clean forward-looking close
basics
~20 sTests whether the thing pushing you out also exists here, and how you talk about people you are leaving. Give one honest, specific reason without blame, credit what the role gave you, then land on the pull toward this job.
how to answer
5 beats- the reason, in one sentenceOpen with a single specific push reason stated as a fact about the situation rather than a judgement about people. Keep this to about fifteen percent of the airtime; if it needs a however, it is two reasons and you should pick one.
- what the role gave meCredit the current job for something real — a skill, an ownership stretch, a mentor's review habit. This one sentence is what stops the whole answer sounding like a complaint, and it is the clearest evidence you will be fair about this employer later too.
- what I tried before deciding to leaveName the internal ask you made and what the answer was, reported neutrally. This turns a grievance into a decision. If the answer you got was reasonable given the company's stage, say so out loud.
- the pull toward this roleSpend the bulk of the answer here, on a concrete property of this job that resolves the push — a funded team, a system you would own, a specialty that exists as a real workstream. Avoid praising the company's reputation; praise the work.
- the clean closeFinish on how you are leaving: handover in progress, manager informed, no drama. Then stop talking. The most common failure is filling the silence with a second grievance.
your answer
4 story prompts- Write your single push reason in one sentence; if it needs a however, it is two reasons.
- List what your current role genuinely gave you and pick the one you would credit aloud.
- Name one thing you asked for internally and what answer you got.
- Match your push reason to a specific property of this job, not a generic upside.
draft and rehearse your own answer in a learn session
go deeper
This is a motivation and risk probe. The interviewer wants to know whether the condition pushing you out exists here too, and whether you can describe a former employer fairly under mild pressure. A strong answer gives one clear non-blaming reason, evidence you tried to resolve it internally, and a pull toward this role the job can actually satisfy.
I joined a seven-person quality team at a startup that was moving its regression testing off manual scripts onto an automated suite, and I owned two of the checkout flows in that program. Over about thirteen weeks I converted thirty-four of the ninety manual cases in my area, and manual-run hours for those flows went from fourteen a release down to five. It was a good place to start — my lead reviewed every pull request I opened, and most of why I got useful quickly is that habit of hers. What I want next is depth I cannot get where I am. With the migration nearly landed, my area is now mostly maintenance: rerun the pack, triage failures, add the occasional case. I asked to move onto the performance and load side and there simply is not a workstream for it — at that size one person covers it, and it is not going to be me for a while. That is a fair answer for a company at their stage; it is just not the answer I want. That is why this role stood out. You have a reliability testing group as its own team, and the posting talks about building load profiles for new services rather than only guarding existing ones. I would rather grow into that than wait for a slot to open. I am leaving on good terms — I am writing the handover for my two suites now, and my lead knows I am looking.
The push reason is structural rather than a grievance: the work he wants does not exist at that headcount, and he says the company's position is fair. The credit sentence and the handover line do most of the discretion work. Vagueness about what he wants, or any hint that the lead was the obstacle, would downlevel it.
I am the quality engineer embedded with two feature squads at a startup that decided to retire manual regression entirely. I ran the workstream for our payments service — picked the framework, wrote the first fixtures, and then spent most of the program getting four other engineers writing their own checks instead of filing tickets for me to do it. Release-week hands-on verification dropped from fifty-eight hours to twenty-one, and reruns stopped holding up the train. The reason I am looking is the road ahead rather than anything behind me. With that work finished, the plan for the next stretch is feature delivery on a stable base, which is genuinely the right call for them. I proposed a shared test-data platform twice, once in planning and once directly with the CTO, and the honest answer was that it is not a priority at their stage. I do not disagree with the reasoning. What draws me here is that quality tooling is a funded product rather than a side effect of somebody's initiative. I want to spend the next few years on the platform side — data seeding, environment isolation, the parts that make a suite trustworthy at scale rather than just present. And I would leave my current team fine either way: the pattern is documented, and four people can extend it without me in the room.
The signal sits in the internal attempt and in accepting the answer he got without resentment — that is what separates a decision from a complaint. The pull names a property of the work, not the company. Dropping the proposal-and-outcome beat, or claiming the migration alone, would pull this back a rung.
Your reason can be entirely about your own craft: depth, review quality, exposure to a specialty that does not exist where you are. Say what you asked for and what the honest answer was, and keep the tone of someone who learned a lot rather than someone who was held back.
Anchor the reason in the kind of work rather than in conditions. Show that you owned something real, that you raised the gap with your manager before deciding, and that the pull is a concrete property of this team rather than a general upgrade.
The reason should sit at team and production scope: a ceiling on mandate, on the quality bar you can enforce, or on the systems you are allowed to touch. Say what you tried to change at your level, what the outcome was, and why you accept that outcome without resentment.
Frame it as a mismatch between where your leverage is and where the organisation is going, in the company's own economic terms rather than as disappointment. Mention what you set up to survive your departure — the handover, the successor, the mechanism — because at this level a clean exit is itself part of the evidence.
saying these in an interview costs you the question
- Badmouthing a manager, a team or the former employer, even mildly
- A vague non-reason such as wanting a new challenge with nothing behind it
- A push reason with no matching pull toward this specific role
- Listing four grievances instead of naming one clear reason
- Describing a problem that would obviously recur here, with no self-reflection
- Sounding like you are fleeing something rather than choosing something
- What would have to change for you to stay?Answer it literally and narrowly — name the one condition that matches your stated reason. If your answer is a list, you have signalled that the real reason is something you did not say. It is also fine to say the change is not one your current employer can reasonably make at their stage, which reads as fair rather than dismissive.
- Have you raised this with your manager?The expected answer is yes, with a short account of how it went. Describe the ask and the response as facts, not as a verdict on your manager. If you never raised it, say so plainly and give the reason; inventing a conversation collapses the moment they ask what your manager said.
- If we made you an offer and your employer counteroffered, what would you do?They are testing whether your reason is really about money. Restate the reason in one sentence and note that a counteroffer does not change it. Avoid theatrical loyalty pledges and avoid leaving the door visibly open, since both invite doubt about whether you will actually accept.
## One question, one prepared answer This prompt arrives in several wordings that all want the same thing: - **Why are you leaving?**, - **What made you start looking?**, - **Why now?**, and, - for a role already ended, **Why did you leave?**. Treat them as one question with one prepared answer. **Why now?** deserves a small addition — a trigger, something that changed recently — because a reason that has been true for three years without action sounds like an excuse rather than a decision. ## Two axes, weighted unequally The underlying evaluation has two axes and they are weighted unequally. - The **smaller axis is fit**: does the reason you are leaving describe a condition that also exists here? If you are leaving because releases are chaotic and this team ships on the same cadence with the same headcount, a thoughtful interviewer will say so, and you would rather they said it in the interview than discover it yourself six months in. - The **larger axis is discretion**. You are being watched talking about people who are not in the room and cannot answer. Whatever you say about them is a preview of what you will one day say about the people interviewing you. This is why mild badmouthing does more damage than candidates expect: it is not that the complaint is unfair, it is that airing it to a stranger during a first meeting is the actual data point. ## Push and pull Every complete answer contains both. - **Push** is what makes staying unattractive; push alone reads as escape and invites the interviewer to wonder what you left out. - **Pull** is what makes this role attractive; pull alone reads as evasion — nobody leaves a job purely because a different one exists — and it usually produces the flattery register, which is worse. The proportion that works is roughly one sentence of push, then the majority of the airtime on pull, so the answer's centre of gravity is forward. ## Weak versus strong on the push half - **Weak**: *there was no growth and management did not really invest in engineering.* It is a judgement, it names no fact, and it puts the blame outside. - **Strong**: *the specialty I want to move into is one person wide at that headcount, and it is not going to be me for a couple of years.* Same underlying situation, stated as a structural fact about a small company rather than as a failing of the people in it. The strong version is also unfalsifiable in a good way — nobody can argue with it, because it is not an accusation. ## Evidence that makes the reason credible 1. One: **a specific internal attempt** — an ask you made, a proposal you wrote, a conversation with your lead — with its outcome stated neutrally. This converts you from a complainer into someone who tried the cheap fix first. 2. Two: **something you would credit the current role for**. A candidate who can name what a place gave them is a candidate who will be fair about this place later. 3. Three: **one concrete property of the target role that matches the push**. Not the company's reputation — a property of the work. ## How the bar moves - **Early career**, the reason is allowed to be about you: learning, mentorship, a specialty. - **Mid-career** it should be about the work you want to own. - At **senior level**, the interviewer is listening for whether you tried to change the thing before leaving it, because a senior engineer who quietly leaves rather than pushes is a signal about how they handle friction. - At **principal level**, the reason should be legible in business terms, and the manner of leaving — handover, successor, nothing left burning — carries as much weight as the reason itself. ## One last mechanic Rehearse the stop. The commonest failure is not the first sentence but the fourth, when silence pulls a second grievance out of you. Land on the pull, close your mouth, and let the interviewer take the next turn.