Post-interview candidate survey template

A post-interview candidate survey is a short set of questions sent right after a candidate's process ends, win or lose, asking how the experience actually was. The template below has three versions — hired, rejected after an interview, and withdrew or ghosted — because the questions that get honest answers are different for each, and a single generic form gets generic answers from all three.

This is a template, not the whole candidate-experience program. For the audit of where a process breaks down before you get to survey results — response times, interview-day basics, access — see how to improve candidate experience, which includes a one-question pulse check for quick use. This page is the dedicated survey: three versions, when to send each, how to keep it anonymous, and how to read the results without overreacting to a small sample.

What this survey is for, and what it is not

The survey answers one question: did our process feel fair and well run, from the candidate's side. It is not a substitute for exit interviews with declined offers (that is a negotiation conversation, not a survey), and it is not a way to find out why a specific rejection decision was made (candidates rarely say that in a form, and you should not ask them to explain your decision back to you). Keep it to the process, not the outcome.

Three moments produce three different candidates. Someone who got the job answers as a new employee with nothing to lose. Someone who was rejected after investing hours in interviews answers carefully, and a badly worded question reads as "explain why we didn't pick you." Someone who withdrew or stopped responding often will not open the survey at all, so that version should be the shortest.

The three templates

Copy the version that matches the outcome. All three fit on one screen.

[VERSION 1 — Hired, sent on day one]
Subject: Two minutes on how your interview process went

Welcome to [Company]. Before the new-hire details take over, we would
like your honest read on the hiring process itself.

1. How clear was the process and timeline, start to finish?      1 2 3 4 5
2. How well were you kept informed between stages?                1 2 3 4 5
3. Did interviewers seem prepared for your conversations?          1 2 3 4 5
4. Was the offer process (timing, details) handled well?          1 2 3 4 5
5. Would you recommend a friend go through our process?    Yes / No / Unsure
6. What is one thing we should keep doing?           [free text]
7. What is one thing we should change?                [free text]

Your manager will not see individual answers.

[VERSION 2 — Interviewed, not selected]
Subject: Two minutes on your interview experience at [Company]

Thank you for the time you put into interviewing for [Role]. We know
that is real effort, and we would like to improve based on it. This
is anonymous and takes about a minute.

1. How clear was the process and timeline?                        1 2 3 4 5
2. How well were you kept informed of where things stood?          1 2 3 4 5
3. Did interviewers seem prepared for your conversation?           1 2 3 4 5
4. Did you have a fair chance to show what you can do?             1 2 3 4 5
5. How was the news of the outcome delivered?                     1 2 3 4 5
6. What is one thing we should change?                [free text]

Your answers do not affect any future application to [Company].

[VERSION 3 — Withdrew or went silent, short form]
Subject: Quick question before you go

You stepped back from the [Role] process, and that's completely your
call. If you have a minute, one question helps us more than any other:

What was the main reason? (pick the closest)
[ ] Timeline was too slow
[ ] Accepted another offer
[ ] Compensation did not match expectations
[ ] A step in the process put you off (which one?) ______
[ ] Personal / timing reasons unrelated to us
[ ] Other: ______

Thank you either way. You are welcome to apply again in the future.

When and how to send each version

Do not send the "not selected" survey in the same message as the rejection. Send the rejection cleanly first (see candidate rejection email templates for wording), then the survey as a short, separate follow-up a few hours or a day later. Bundling them reads as "here's your no, now grade us," and it suppresses honest answers.

Anonymity: what to promise and what to actually do

For the "not selected" and "withdrew" versions, keep responses anonymous by default and say so in the message. That means: no name field, no hidden identifier tying the response to the ATS record, and results reported in aggregate, not read one-by-one back to the hiring manager who interviewed that person. If you need to route a specific serious complaint (harassment, discrimination, an interviewer being unprofessional), add a single optional line: "If you want us to follow up on something specific, leave your email here" — optional, not required, and separate from the rest of the form.

For the "hired" version, a named survey is fine, since the person is now an employee and you may want to follow up on a specific comment. Say plainly at the top who sees the answers.

A worked example: reading the results

An invented month of responses to the "not selected" survey, to show how to read a small sample without overreacting to it:

Two things matter more than the average score: the sample size, and the free-text comments. A 3.9 average from six responses is not a finding, it is six opinions. A pattern that nine of twenty-four people raised unprompted is a finding, whatever the average number says.

Turning answers into changes

What not to survey

• Do not ask candidates to rate individual interviewers by name. It invites retaliation risk and rarely produces usable feedback; ask about "the panel" or "your interviewers" collectively.
• Do not ask "why do you think you weren't selected." Candidates cannot answer accurately (they do not see the comparison), and it pulls the survey into re-litigating a decision that has already been made and communicated.
• Do not ask for compensation expectations in this survey. That is a screening question that belongs in the intake process, not a satisfaction survey sent after the process has ended.
• Do not make the survey mandatory to receive a status update. Gating information behind a survey response reads as pressure, not a request for feedback.

Reporting results without exposing individuals

Report at the level of stage reached (applied, phone screen, interview, final round, offer), not at the level of a single requisition with five candidates, where free-text comments become identifiable. Roll results up monthly or quarterly and share the free-text themes with hiring managers as patterns, not quotes attributed to a specific candidate. If a comment names a specific incident that needs investigation, handle that separately from the aggregate report.

Checklist before you send the first batch

• The right version (hired, not selected, withdrew) matches the outcome
• Anonymity is genuine, not just labeled: no hidden identifier links the response back to the ATS record
• It is sent within the target window (day one, or within a day of the rejection)
• The message states plainly who sees results and whether it affects future applications
• There is exactly one open-text question, not three, so people actually finish it
• You have a plan for reading results monthly, not just collecting them
• Someone owns turning the top pattern into one process change, on a set date