Exit Interview Questions: 15 Useful Questions, Follow-Ups, and Sample Answers

Start with the employee’s reason for leaving, then work through the conditions surrounding that decision. The 15 questions below are suggested prompts: choose the ones that fit the employee’s role rather than treating the list as a script to finish.

UC Berkeley’s exit interview guidance describes gathering reasons for leaving, experiences of the job and supervision, specific suggestions, and patterns across employee feedback. Use that scope to keep the conversation focused.

The best exit interview questions separate what happened from what might improve it. Ask the main question first, listen to the answer, and use the follow-up only when it would clarify something. If the employee has already explained an issue, acknowledge it instead of asking them to repeat it under another heading.

Example: Maya is leaving a project coordinator role. Sam, the interviewer, uses a few questions in depth and checks the summary before closing.

Sam: I’m collecting feedback about the role and possible improvements. I’d like to take notes for the HR summary and discuss process changes with the department manager. Is there anything you want to clarify about the notes or who will see them before we begin?

Maya: I’m comfortable discussing the workflow. I’d like to check the wording of the summary before it goes further.

Sam: Let’s review it together at the end. What most influenced your decision to leave?

Maya: I wanted more responsibility. I was coordinating launches, but I couldn’t make decisions about changing deadlines.

Sam: Can you walk me through a launch where that caused a problem?

Maya: On the September launch, two teams changed their delivery dates. I asked who could approve a revised schedule. I didn’t get a decision before the customer update, so I sent an update with a date I couldn’t confirm.

Sam: What happened as a result?

Maya: I had to correct the update the next day. It also meant doing the same reporting twice.

Sam: What would have helped?

Maya: A named person who could approve schedule changes, plus a backup when that person was away.

Sam: Was this limited to that launch, or did you see it elsewhere?

Maya: It happened on two others. I can describe those, but I don’t know whether other coordinators had the same experience.

Sam: Understood. What should we preserve?

Maya: The weekly cross-team check-in. It helped us spot changes early, even when approval was slow.

Sam: My summary is that you wanted greater decision responsibility, approval ownership was unclear on three launches you worked on, and the weekly check-in was useful. Your suggested change is a named approver and backup. Does that capture it?

Maya: Yes. Please make clear that I’m describing my projects, not the whole department.

Sam: I’ll include that scope. I’ll propose reviewing the approval process with the department manager; that is a next step, not a commitment that your suggested structure will be adopted. Is there anything else you want added?

This exchange turns “I lacked responsibility” into a specific decision problem. It also preserves a working practice and separates Maya’s observations from assumptions about other employees.

Follow the employee’s wording before introducing your own explanation. Good exit interview questions leave room for an answer the interviewer did not anticipate. “Was your manager the problem?” narrows the answer too early; “What made that part of the job difficult?” allows several explanations.

Use the smallest follow-up that resolves the uncertainty. If you already understand the event, ask about its effect. If you understand the effect, ask what would have helped. The active listening practice guide offers exercises for reflecting a speaker’s point before responding.

Prepare one event, its effect on your work, and a request or suggestion. The SBI feedback model can help you organize the situation, behavior, and impact. Add the change you would recommend, without suggesting that you know another person’s intentions.

These four example rewrites preserve the concern while making it easier to understand. Adapt them to what you actually experienced; a polished answer should still sound like you.

Internship exit interview questions should explore what the intern could learn, how guidance worked, and what remains to be handed over. A short placement may offer little basis for judging progression, but it can reveal whether assignments and support made learning possible.

Use these additional prompts in place of questions that do not fit the placement:

• What did you learn to do that you could not do at the start? Follow-up: Which assignment gave you the most useful practice?
• How clear were the instructions and expected outcomes? Follow-up: Where did you have to guess what a successful result looked like?
• When you got stuck, how did you find help? Follow-up: Was there a named person or a clear way to ask?
• Which feedback changed how you approached your work? Follow-up: What made it usable?
• What work or documentation needs handing over? Follow-up: Who needs the context to continue it?
• What would you change for the next intern? Follow-up: What should they receive in their first week?

Example answer: “The research task helped me compare customer needs, but I didn’t know how the findings would be used. Seeing one completed brief before I started would have helped me choose the right detail.”

Separate the learning review from project closeout. Record an unfinished task with an owner and a handover location; record an unclear assignment as feedback about guidance. For a mixed placement, ask what differed between teams instead of assigning one overall rating that hides the contrast.

Before collecting sensitive detail, explain the intended use of the notes, who is expected to receive them, and what you still need to confirm. Ask what scope the employee is comfortable discussing. Do not promise anonymity or confidentiality that you cannot provide.

Keep three things distinct in the record: the employee’s account, your summary, and any proposed action. A summary such as “employee described three delayed approval decisions on their projects” is more precise than “management caused departures.” The second statement adds a conclusion the conversation has not established.

Use a short opening checklist:

• State why you are collecting feedback and the intended audience.
• Explain how you plan to record it, and ask about the scope of notes.
• Invite questions about information sharing before requesting detail.
• Identify anything you need to check rather than guessing an answer.
• Offer to read back the main points for accuracy.

If an employee asks to limit a detail after sharing it, pause and clarify what they mean before continuing. Explain what you can do and what remains uncertain. If a concern needs another process or contact, explain that next step within your role rather than trying to settle it through more questions. Employees can also ask, “Will this be recorded as my wording or your summary?”

Use SayNow AI to rehearse saying one difficult piece of workplace feedback aloud. Choose a relevant scenario, such as performance review, or a framework for organizing your response. Start with an event you can describe clearly, explain its effect, and finish with a practical request. This is general communication practice for the conversation you are preparing.

In SayNow AI’s practice flow, you speak, the AI replies by voice, and you answer the follow-up. When the conversation ends, you receive a score and written suggestions across fluency, content structure, scenario fit, and goal achievement.

Use that feedback to choose one change for your next attempt: shorten the background, make the request explicit, or pause before answering a challenging follow-up. Repeat the conversation with that single change in mind. An interviewer can use the same approach to practice a neutral clarification. Start with the performance review scenario and rehearse the feedback exchange you need to handle.

Finish by checking the summary, then decide what needs review, action, or further information. One person’s account can identify a concrete issue; it does not tell you how widespread that issue is. Keep its scope visible when discussing it with others.

Use this worksheet after the conversation. Keep observed details separate from suggestions so that an attractive solution does not become confused with an agreed decision.

Theme:
Employee’s example:
Effect on the work:
What worked and should be preserved:
Suggested improvement:
Information still needed:
Proposed action or review:
Person responsible for the next step:
Date to check progress:
Summary accuracy checked with:

Example: the theme is approval ownership; the employee described delayed schedule decisions; the proposed next step is to review how approvers and backups are assigned. Name a person to arrange that review. A possible outcome is a clearer approval route, but record it as a proposal until the relevant decision is made.

Before closing your notes, remove unsupported generalizations, retain useful positive feedback, and distinguish an action owner from someone merely mentioned in the discussion. If several conversations describe a similar obstacle, compare the actual examples before treating them as the same problem.

Choose a small set of exit interview questions, prepare neutral follow-ups, and leave space for the employee’s own priorities. Your next step is a clear summary and a named person responsible for reviewing the most actionable issue.