Exit Interview Questions (and What to Do With the Answers)

Exit interview questions are the prompts you use to learn why someone is leaving and what you could have done differently. Done well, the exit interview is one of your most honest sources of feedback, because a departing employee has little reason to soften the truth. Done as a formality, it is a checkbox that collects polite non-answers and changes nothing. This guide covers the questions worth asking, how to get real answers, and the step that separates the two: doing something with what you hear.

The questions

Aim past the headline reason (the new job, the money) to the real one underneath:

• Why are you leaving, and when did you first start considering it?
• What could we have done to keep you?
• What did you enjoy most about working here? Least?
• How was your relationship with your manager?
• Did you have the tools, information, and support to do your job well?
• Did you feel your work was valued?
• Would you recommend us as a place to work? Why or why not?
• Is there anything we should ask future employees that we are not?

The "when did you start considering it" question is quietly the most useful: the answer is almost always earlier than you would guess, and it tells you when in the lifecycle you lost them, frequently pointing back at onboarding or a specific event.

Getting honest answers

Departing employees are candid if you let them be. Hold the interview near the end of the notice period, when they are relaxed and the relationship is winding down. Use a neutral interviewer, usually HR rather than the direct manager, because manager problems are a top reason people leave and nobody names them to the manager's face. Make clear the feedback is aggregated, not ammunition. And listen without defending; the instinct to explain why their complaint is unfair ends the honesty instantly. The same listening discipline as a stay interview, with even less reason for the person to hold back.

The step everyone skips

Here is where exit interviews mostly fail: the data gets collected and filed, and nothing changes. One exit interview is an anecdote. Ten exit interviews are a diagnosis: the same manager named repeatedly, the same team hemorrhaging people, the same unmet need (no growth, unclear expectations, burnout) recurring. The value is entirely in aggregating across departures and acting on the pattern. A company that has run exit interviews for three years and never changed anything has been wasting its most honest feedback the whole time.

Connect exit to entry

The most underused link: exit interview findings should feed back into onboarding and management. If leavers consistently say they never understood expectations, fix the first 90 days. If they cite a manager, address the manager. If they mention the same knowledge gaps and frustrations, fix those. Exit is the end of one employee's lifecycle and should be the start of an improvement for the next. And operationally, the exit interview pairs with the offboarding checklist and knowledge transfer, the other things that have to happen when someone leaves.

How Sakha helps

Sakha strengthens both ends of the loop the exit interview belongs to. Its surveys and milestone check-ins gather feedback from current employees and new hires, so problems surface long before they show up as resignations, which is the cheaper place to catch them. When patterns from exit interviews point at fixes, Sakha is where those fixes land: a clearer onboarding flow, better-documented expectations, the knowledge gaps closed. And at the point of departure, Sakha supports the knowledge transfer that should accompany the exit interview, capturing what the leaver knows into the knowledge base so it does not walk out with them. The exit interview tells you what to change; Sakha is where you change it.