Exit interview questions
Exit interview questions have one job: turn a departure you couldn't prevent into information that prevents the next one. The 13 below ask a departing employee what actually drove the decision. Pick six or seven, promise nothing you won't deliver, and read the answers for patterns across departures, not verdicts from one.
All 13 questions
Core exit interview questions to ask every departing employee
- 01What prompted you to start looking for another role, and when did that start?
- 02What would have had to change for you to stay?
- 03What does the new role offer that this one couldn't?
- 04Would you recommend working here to a friend? What would you warn them about?
- 05What will be hardest about this job for the person who takes it over?
Exit interview questions about AI and tooling
- 06Did our tooling — including how we've handled AI — play any part in your decision to leave?
- 07Which AI tools or workflows did you build for yourself that we should keep after you leave?
- 08Where did our approach to AI make your job harder than it needed to be — and where did it genuinely help?
- 09If you could change one thing about how this team works with AI before your replacement starts, what would it be?
Exit interview questions about management and growth
- 10How would you describe working for your manager to the person who takes your seat?
- 11Did you raise the things that bothered you while you worked here? What happened when you did?
- 12Was the job you actually did the job we hired you for? Where did it drift?
- 13When did you feel most valued here — and when did you feel least valued?
Questions 1–5
Core exit interview questions to ask every departing employee
What prompted you to start looking for another role, and when did that start?
A useful answer names a specific trigger — a reorg, a passed-over promotion, a manager change — and a date. The gap between trigger and resignation is how long the warning light was on unnoticed.
What to look for
- A dateable trigger event, not a fog of 'it was just time'.
- Months between the trigger and the resignation letter — your window to catch the next one earlier.
- Whether the trigger ever surfaced in a one-on-one or survey while there was still time to act.
Example answerRed flags
Example answer
The March reorg, honestly. My role went from owning the roadmap to executing someone else's, and nobody discussed it with me — I found out from the all-hands deck. I started taking recruiter calls in April. If someone had asked me then what I wanted to own, I might have stayed.
Red flags
- 'Just time for a change' with no trigger you can date — either guarded or genuinely nothing to learn.
- The trigger sat in survey results or one-on-one notes for months while nothing moved — the signal existed; nobody owned acting on it.
What would have had to change for you to stay?
The single most actionable exit question. A strong answer names one or two concrete, feasible changes — scope, pay band, manager, flexibility — and tells you whether this departure was preventable at all.
What to look for
- One or two specific changes, sized realistically — not a wish list.
- Whether the change was ever requested through a real channel, and what happened to the request.
- 'Nothing — the new role is simply better' is a legitimate answer; it clears your management chain.
Example answerRed flags
Example answer
A path to senior that didn't depend on headcount opening up. I asked twice; both times the answer was 'next cycle'. I'm not leaving angry — but the new company put promotion criteria in the offer letter. If you'd shown me a real timeline in January, I'd still be here.
Red flags
- They asked for the change properly and the request died without a decision — your escalation path leaks.
- The fix they name is cheap, and you've heard it in three other exit interviews this year.
What does the new role offer that this one couldn't?
This separates pull from push. Candid answers compare specifics — scope, compensation, technology, commute — and tell you whether you lost to a genuinely better offer or drove the search that found it.
What to look for
- A concrete comparison: title, scope, money, or something this role structurally lacked.
- Push versus pull — whether they were recruited away or went shopping.
- Gaps you can close for the people still here; pay-band drift shows up in this answer first.
Example answerRed flags
Example answer
Mostly scope. I'll own pricing end to end; here it was split across three teams and every decision took a committee. The pay bump is real — about 18% — but I'd have taken 8% for the scope alone. Your bands have drifted; two recruiters quoted me the same range.
Red flags
- The differences they name are things you actually offer but never told them about — an internal-mobility failure, not a market loss.
- The same 15–20% compensation gap appearing across several exits — your bands are stale, and this conversation is the cheapest place to learn it.
Would you recommend working here to a friend? What would you warn them about?
An honest yes-with-caveats is the normal answer, and the caveats are the data. The warning a leaver would give a friend is usually the truest sentence in the whole interview.
What to look for
- The caveat itself — sharper and more specific than anything your engagement survey collects.
- Which teams or managers the recommendation depends on.
- Whether the warning matches what you already knew, or is news.
Example answerRed flags
Example answer
Yes, with one warning: come for the product work, and check which team you're joining. My first team was great. After the reorg I landed under a director who cancels one-on-ones for weeks. I'd tell a friend to ask, in the interview, how often their manager actually meets their reports.
Red flags
- A flat no from a strong performer — treat it as an incident to investigate, not an opinion to file.
- The warning names a manager you've heard named before; two exits pointing at the same person is a pattern.
What will be hardest about this job for the person who takes it over?
Part handover, part diagnosis. Strong answers surface the invisible workload — relationships, workarounds, undocumented systems — and tell you whether the role is one job or two stapled together.
What to look for
- Undocumented dependencies: the spreadsheet, the contact, the manual step nobody else knows exists.
- Whether the hard part is the work itself or the politics around it.
- Signs the role has quietly outgrown its title — and its pay band.
Example answerRed flags
Example answer
The vendor renewals. There's no playbook — I carry the history of every negotiation in my head, and our biggest discount exists because of a favor from 2023. I've started writing it down. Also, be honest in the job ad: this role is 30% procurement, whatever the title says.
Red flags
- The role only functions on unpaid overtime or heroics — you're about to hire someone into a burnout seat.
- Nothing can be handed over because nothing was ever documented — a bus-factor problem that outlives this exit.
Questions 6–9
Exit interview questions about AI and tooling
2026 · AIDid our tooling — including how we've handled AI — play any part in your decision to leave?
Tooling rarely tops the stated reasons and often sits just under them. A candid answer says whether working here felt slower than the market, and whether the friction was the tools, the policy, or both.
What to look for
- A named bottleneck: the approval queue, the banned tool, the six-month procurement cycle.
- A market comparison — someone who just interviewed elsewhere has seen other stacks up close.
- Policy friction versus tool friction; one is a budget fix, the other a governance fix.
Example answerRed flags
Example answer
Not the reason, but a tiebreaker. Getting an AI coding assistant approved took five months and two committees; my new team had it in the interview take-home. I stopped asking for tools around March, which in hindsight was the moment I checked out.
Red flags
- 'I stopped asking' — learned helplessness about tooling means the request pipeline broke long before this resignation.
- They routed around policy with personal accounts — you have a shadow-AI problem, and the person who understood it is leaving.
Which AI tools or workflows did you build for yourself that we should keep after you leave?
Departing employees take undocumented automation with them. A useful answer inventories the prompts, scripts, and checks they built, who else quietly depends on them, and which will break the week they leave.
What to look for
- Automation other people already rely on without knowing who maintains it.
- The verification habits attached — what they checked before trusting output.
- Anything running on personal accounts or keys that walk out the door with them.
Example answerRed flags
Example answer
Three things. A prompt set that drafts the weekly client report from our dashboard export — Priya uses it too. A script that flags contract renewals 60 days out. And a checklist for reviewing AI-drafted replies before they reach customers. The renewal script runs on my personal API key, so it dies unless someone moves it.
Red flags
- Business processes running on personal credentials — a continuity risk with a countdown attached.
- Nobody asked what they'd automated until this conversation — the knowledge-transfer gap is systemic, not personal.
Where did our approach to AI make your job harder than it needed to be — and where did it genuinely help?
You want the friction map, not a verdict. Strong answers name one place policy or tooling slowed real work and one place it helped — the balance tells you the account is fair rather than a grievance.
What to look for
- Specific tasks with time costs attached — 'the legal review adds a week to every piece of content'.
- Balance: naming what worked signals a fair witness, not score-settling.
- Frontline workarounds that leadership doesn't know exist.
Example answerRed flags
Example answer
The blanket ban on AI in customer emails made sense for contract questions, but it also covered order-status replies — answers that took thirty seconds elsewhere took ten minutes here. Credit where due: the transcription setup for research calls was actually good. I'd narrow the ban, not lift it.
Red flags
- The whole team apparently shares the complaint but nobody raised it — your feedback channels are dead.
- They can't name a single thing that helped — you're hearing a grievance, not a map; weight it accordingly.
If you could change one thing about how this team works with AI before your replacement starts, what would it be?
Framing the question around the successor unlocks candor — the advice costs the leaver nothing now. Expect the one change they'd make with an owner's authority: adopt this, drop that, write the policy down.
What to look for
- One change chosen over all the others — the prioritization is the insight.
- Whether it's adoption ('start using X for Y') or restraint ('stop trusting X for Y').
- A realistic sense of what the change costs and who would have to approve it.
Example answerRed flags
Example answer
Write the actual policy down. Right now it's folklore — everyone has a different idea of what's allowed, so half the team uses nothing and the other half improvises. One page: approved tools, banned uses, who to ask. My replacement will waste their first month relearning what I learned by trial and error.
Red flags
- The one change is something leadership already announced and never executed — your gap is follow-through, not strategy.
- Advice so cautious it says nothing — if they don't trust this conversation even on the way out, ask why.
Questions 10–13
Exit interview questions about management and growth
How would you describe working for your manager to the person who takes your seat?
Framing it for their successor gets a truer picture of the manager than any upward survey. Listen for how the relationship worked day to day: feedback, availability, and what happened to promises.
What to look for
- Concrete habits: one-on-one cadence, feedback quality, follow-through on commitments.
- Fairness — a balanced account is worth more than a tribute or a takedown.
- Whether problems were raised with the manager directly, and what changed after.
Example answerRed flags
Example answer
Sharp, fair, and permanently overbooked. Our one-on-ones happened maybe twice a month, and feedback came in the moment or not at all. When she had time, she was the best manager I've had. She manages eleven people; nobody gets good management at that ratio. That's a structure problem, not a her problem.
Red flags
- A span-of-control or structural complaint you've heard from this manager's other reports — the org chart is the issue.
- Fear still shapes the answer on their way out the door — psychological safety is worse than your surveys claim.
Did you raise the things that bothered you while you worked here? What happened when you did?
This measures whether your feedback channels work. The expensive pattern is 'I raised it, nothing happened, I stopped raising things' — that silence is how companies get surprised by resignations.
What to look for
- Concrete instances: what was raised, to whom, through which channel.
- What came back — a decision, a fix, or silence.
- When they gave up, if they did; that date marks the start of disengagement.
Example answerRed flags
Example answer
Twice, properly. I flagged the on-call load in a skip-level and in the engagement survey. The survey came back as 'we hear you' with no changes; the skip-level said he'd look into it and never circled back. After that I just did the job. You learn what raising things gets you.
Red flags
- Raised through the right channels and lost to silence — every current employee watching learned the same lesson.
- Never raised anything because 'it wouldn't have mattered' — the belief that feedback is futile has already spread past this one person.
Was the job you actually did the job we hired you for? Where did it drift?
Role drift is a quiet driver of attrition. A specific answer maps where the real job diverged from the posting, and tells you whether your job descriptions are recruiting for roles that no longer exist.
What to look for
- A specific delta: promised strategy, delivered reporting; hired for X, absorbed Y after a departure.
- Whether the drift was ever renegotiated — title, pay, or at least acknowledged out loud.
- Whether they'd have taken the real job if the ad had described it honestly.
Example answerRed flags
Example answer
About sixty percent of it. I was hired as a product analyst; when Dana left, I absorbed all the ad-hoc exec reporting and it never went back. Nobody renegotiated anything — the extra work just became mine. I'd have taken the real job, honestly. I just wanted someone to name it and pay for it.
Red flags
- The replacement will inherit the same drift on day one because the vacancy ad is a copy of the old one.
- Extra scope was absorbed with no title or pay adjustment — the next resignation on that team is already forming.
When did you feel most valued here — and when did you feel least valued?
The pairing forces specifics on both sides. The 'least valued' moment usually marks the beginning of the end, and it is typically a small, fixable act of management rather than a policy.
What to look for
- Two datable moments, not vibes — a launch credited, a thank-you skipped, a raise that didn't come.
- Who created each moment; recognition problems are usually local, not corporate.
- How long ago the 'most valued' moment was — a long gap is its own answer.
Example answerRed flags
Example answer
Most valued: the January outage — I led the fix and the CTO thanked me by name at all-hands. Least: three months later my promotion case was 'deferred for budget' in a two-line email, no meeting. Same company, same quarter. The email is the one I remember.
Red flags
- The 'least valued' moment is compensation news delivered carelessly — cheap to fix, expensive to keep repeating.
- They can't recall feeling valued at all — check whether recognition on that team exists anywhere outside the annual review.
Scoring rubric
| Score | Evidence anchor |
|---|---|
| 1 | Pure diplomacy — 'great experience, just the right time' — every answer could have been written before the meeting. You end the hour with nothing you can act on. |
| 2 | One real reason surfaces under probing, but stays generalized — 'communication', 'culture' — with no names, dates, or events anyone could investigate. |
| 3 | Specific and honest about the main driver — a datable trigger, a named gap, what would have kept them — though guarded on management questions. Real actionable detail, incomplete picture. |
| 4 | Candid across the set: trigger and timeline, the stay counterfactual, a fair account of the manager, and an honest tooling map. You leave with two or three fixes worth pursuing. |
| 5 | Specific, fair, and complete: dated events, systems named instead of grudges settled, the automation they're taking with them, and warnings that match patterns from other exits. The interview reads like a retention audit you didn't have to commission. |
Frequently asked questions
What are the best exit interview questions to ask an employee?
The two highest-yield exit interview questions are the trigger — what started the job search, and when — and the counterfactual — what would have had to change for them to stay. Every other question on this page refines those two.
How many questions should you ask in an exit interview?
Six or seven in 45–60 minutes. A departing employee's candor is a limited resource: open with the trigger and the stay question, and leave room at the end for whatever they volunteer unprompted — it's often the best material.
Is there a sample exit interview questions template I can copy?
Yes — the copy control beside the question list exports all 13 as a reusable exit interview template, and the page prints cleanly to PDF. Treat the full set as a menu to choose from per interview, not a script to read out.
Who should run the employee exit interview — HR or the manager?
HR or a manager one level removed, never the direct manager — who is, statistically, one of the likeliest reasons for the departure. Candor drops sharply when the person across the table is part of the story.
What should you do with exit interview answers?
Aggregate them. One interview is an anecdote; five naming the same manager, pay band, or tooling gap are a finding. Review themes quarterly with whoever owns retention — exit notes that nobody reads are the most common failure.