Candidate Feedback on the Recruitment Process: 20 Examples + Survey Template

By the Role.so team. Published September 2, 2026.

Candidate feedback is useful only when it leads to a clearer decision or a better recruitment process. The term also causes confusion because it describes two different exchanges:

1. candidate-to-employer feedback about the application, interview and communication experience;
2. employer-to-candidate feedback after an interview, assessment or hiring decision.

This guide covers both. It gives you 20 copy-ready examples, a 12-question candidate survey, an invitation email, a rejection-feedback template and a practical method for turning comments into measurable improvements.

Candidate feedback sample

“The interviews were well structured, but I waited twelve days for an update after being told I would hear back within three. A short message explaining the delay would have made the process feel much more reliable.”

Key takeaways

• Ask candidates about a specific stage, not “the process” in the abstract.
• Survey rejected, withdrawn and hired candidates so the sample is not artificially positive.
• Give feedback using documented role criteria and observable evidence.
• Avoid vague personality labels, protected characteristics and comparisons with another candidate.
• Combine survey responses with behavioral data such as response, withdrawal, time per stage and decline reasons.
• Fix recurring friction first; do not react to every isolated comment.

What candidate feedback means in recruitment

Candidate feedback has two directions, and each solves a different problem.

Keep the two data sets separate. A candidate-experience survey measures the process. An interview scorecard measures evidence against selection criteria. They may inform one another, but they should not be treated as the same thing.

For the wider framework, read How to Improve Candidate Experience.

Candidate feedback on the recruitment process: 10 sample responses

The examples below are written in the candidate’s voice. They are specific enough to be useful without becoming personal attacks. Each one points to an operational question the recruitment team can investigate.

These examples can also be converted into survey response options or coding categories. Do not copy them into a testimonial or public case study without the candidate’s explicit permission.

Candidate feedback survey template

A useful survey is short enough to complete and structured enough to compare over time. Ask questions that the candidate can actually answer at the stage they reached.

Context fields, only when needed

The template contains 12 experience questions, plus up to two context fields when needed. Keep the stage reached separate from the current status or final outcome. Use existing survey metadata only when it is available and consistent with the stated privacy setup; otherwise, ask for the missing field or fields below.

For someone who withdrew after an interview, record interview in C1 and withdrew before an offer in C2. An offer still under consideration is still active, not accepted. Adapt the stage options to your actual sequence. Keep “prefer not to say” separate instead of assigning an outcome. C1 and C2 are context, not scored questions. The CSV’s Stage column describes when a question applies, not the respondent’s answer to C1.

For an anonymous survey, use broad self-reported context rather than attaching an identifiable ATS record. Avoid reporting tiny stage/outcome groups that could reveal a person. Anonymous, confidential and reported in aggregate are not interchangeable descriptions.

The 12 experience questions

Download the candidate feedback survey template as a CSV, or use the questions below.

For questions 1–10, use the same agreement labels in the article and survey tool:

1 = Strongly disagree; 2 = Disagree; 3 = Neither agree nor disagree; 4 = Agree; 5 = Strongly agree.

Allow “Not applicable” whenever the candidate cannot assess an item, and “Not yet applicable” for a next step or decision that has not happened. Exclude these choices and unanswered items from that question’s average and positive-response percentage; never score them as zero. Report the valid response count for each question. C1 and C2 do not enter any score. Keep question 11 on its separate 0–10 scale and question 12 optional.

How to score and interpret the survey

Keep the analysis simple and consistent:

• report each 1–5 question separately and define the scale labels before launch;
• track the share of positive responses, such as ratings of 4 or 5, instead of relying only on a single average;
• report the 0–10 recommendation question separately rather than mixing it into the 1–5 scores; if you call it candidate NPS, calculate the percentage of 9–10 responses minus the percentage of 0–6 responses and always report the sample size;
• code open comments into a small, stable set of themes;
• always show the respondent count and the stage/outcome mix beside the result.

Do not treat a small change in a small sample as proof. Use the first responses to identify patterns, then confirm them with behavioral data such as withdrawal, response time and decline reasons.

Candidate survey invitation email

Subject: A short question about your recruitment experience

Hi {{first_name}},

Thank you for the time you invested in the {{role_title}} process.

We are reviewing the experience candidates receive and would value your perspective. The survey takes about three to five minutes and focuses on the clarity, communication and fairness of the process.

{{survey_link}}

{{privacy_statement}} This survey is optional. {{status_statement}} Please do not include sensitive personal information in the open-text field.

Thank you,
{{recruiter_name}}

Replace {{privacy_statement}} with the statement that matches your actual setup, for example: “Your responses are anonymous.”, “Your responses will be treated confidentially.” or “Your responses will be reviewed in aggregate.” Only use a statement that is technically and operationally true.

Replace {{status_statement}} with the paragraph appropriate to the candidate’s situation, and use the same wording in the survey introduction.

Before a final decision: “Your application is still in progress. Your feedback will not be used to evaluate your application.” Use this only when responses are genuinely kept separate from selection decisions; otherwise, wait until the decision has been communicated.

After a final decision: “Your responses will not change the decision already communicated to you.” Send the decision first and the survey invitation separately.

For a withdrawal, acknowledge the candidate’s choice instead of implying that the employer rejected them. Asking why they withdrew remains optional. Keep the privacy statement accurate for both the email and the survey itself.

When to send the survey

Choose the timing according to the problem you want to understand:

• after application: clarity, usability and application effort;
• after interview: preparation, relevance, respect and scheduling;
• after withdrawal: why the candidate chose not to continue;
• after rejection: communication, closure and perceived fairness;
• after offer acceptance: the complete journey, while acknowledging that successful candidates are usually more positive.

A short pulse at one or two decisive stages is usually more useful than sending a long questionnaire after every interaction.

How recruiters should give feedback to candidates

Good recruiter-to-candidate feedback is not a complete transcript of the hiring discussion. It is a concise explanation based on criteria the candidate knew or could reasonably understand.

Use five rules:

1. Start with the decision. Do not make the candidate decode whether they are progressing.
2. Refer to the role criteria. Connect the feedback to a responsibility, skill, level or assessment rubric.
3. Use observed evidence. Describe what was demonstrated or missing in the interview or exercise.
4. Make it proportionate. A screened applicant may receive brief closure; a final-stage candidate deserves more context.
5. Check policy and local requirements. Keep records and feedback aligned with your organization’s legal, privacy and equality guidance.

A four-part feedback framework

Criterion → observed evidence → impact on the decision → practical next step

For example, when communicating a technical decision to a non-technical audience was a documented requirement:

Criterion: explain a technical choice to non-technical stakeholders.
Observed evidence: the answer described the architecture but did not address customer impact or rollout risk.
Impact: the panel did not have enough evidence for that requirement.
Next step: prepare an example that connects the audience, the trade-offs, the decision and the result.

Adapt each part to the interview record. Include a practical suggestion only when the evidence supports it; do not invent a weakness or promise that following the advice guarantees a future offer.

The examples below are templates, not scripts to send blindly. Replace the bracketed details with evidence from the actual process.

Positive interview feedback examples

Positive feedback should still be precise. “You were great” feels pleasant but gives the candidate little information about what worked.

Why example 11 works: it names observable problem-solving steps rather than offering generic praise. Keep only the steps the candidate actually demonstrated.

Constructive and unsuccessful interview feedback examples

Why example 18 works: it ties the missing evidence to a constraint in the brief, rather than to a personality judgment. Check that the constraint was actually part of the assessment criteria before using this wording.

Notice what these examples avoid: “not a culture fit,” “not confident enough,” “too senior,” “too junior,” “not polished,” “not energetic,” or comments about accent, age, health, family situation or another personal characteristic. Those labels are vague, hard to act on and may introduce bias or legal risk.

Candidate rejection feedback email template

Subject: Update on your application for {{role_title}}

Hi {{first_name}},

Thank you for the time and preparation you invested in our process. We have decided not to progress your application for {{role_title}}.

The decision was based on the role’s current need for {{criterion}}. In the interview, we heard useful evidence of {{strength}}, but we did not obtain enough evidence of {{missing_or_less_developed_requirement}} at the level required for this position.

We appreciate the opportunity to learn about your experience and wish you the best with your search.

Kind regards,
{{recruiter_name}}

Do not promise that a candidate will be considered for a future role unless you have a real process and appropriate permission to retain their information.

What not to include in candidate feedback

Before sending or recording feedback, remove content that is not necessary for the recruitment purpose.

Avoid:

• comparisons such as “the successful candidate was younger, more dynamic or more polished”;
• comments about protected or sensitive characteristics;
• medical, family, religious, political or other unrelated personal information;
• speculation about motivation, personality or future behavior;
• statements that contradict the scorecard or documented decision;
• internal debate, blame or confidential information about other candidates;
• absolute promises such as “you will definitely be hired next time.”

In the United States, the EEOC advises employers to ensure tests and selection procedures are job-related and appropriate for their purpose. Privacy, record-retention and feedback rules vary by state and jurisdiction. Apply the rules and policies relevant to your organization; this guide is operational guidance, not legal advice.

How to turn candidate feedback into process improvements

A folder full of survey responses is not a feedback system. Use a repeatable review cycle.

1. Code feedback into a small taxonomy

Start with six to eight themes:

• role clarity;
• process transparency;
• communication and waiting time;
• interview relevance and fairness;
• scheduling and application friction;
• accessibility and adjustments;
• compensation and working arrangements;
• decision and closure.

Allow an “other” category, but review it regularly. If a new theme appears repeatedly, add it to the taxonomy rather than forcing it into the wrong category.

2. Segment before averaging

At minimum, separate:

• applied, sourced or referred candidates;
• screened, interviewed and final-stage candidates;
• hired, rejected and withdrawn candidates;
• role family, recruiter or hiring team;
• source or campaign;
• period before and after a process change.

A single average can hide the experience of rejected or withdrawn candidates. Report the respondent mix alongside every score.

3. Combine perception with behavior

Survey answers explain how candidates experienced the process. Recruiting analytics connects those perceptions with the behavioral data that shows where candidates acted or stopped.

Use the signals together to choose what to investigate, not to claim that a cause has already been proven:

Compare equivalent stages, audiences and time periods, using aggregates when responses are anonymous. Define the denominator: survey responses divided by survey invitations is not the same measure as candidate-page responses divided by visitors.

Treat small samples as directional. A change from two positive responses to four is not proof that the process improved.

4. Assign an owner and a threshold

For each recurring issue, define:

• the evidence required to act;
• the owner;
• the change to test;
• the date of review;
• the primary metric;
• the guardrail metric.

Example: if “timeline was unclear” appears in at least 20% of interview-stage comments for two consecutive months, the recruiting operations owner updates invitation templates and interviewer handoffs, then reviews clarity ratings and candidate withdrawals.

5. Close the internal loop

Share a concise monthly review with recruiters and hiring managers:

• what candidates praised;
• the three recurring friction points;
• which stage and roles are affected;
• actions already taken;
• changes that require a decision;
• whether the previous action improved the target signal.

Do not circulate raw candidate comments more widely than necessary. Use anonymized themes or carefully selected excerpts where possible.

How Role.so fits into the feedback loop

Role.so helps recruiters present a role through a branded candidate page and capture explicit Interested or Decline responses. Decline reasons and page analytics can show where an outreach audience engages, leaves or rejects the opportunity.

Use those signals alongside:

• your ATS for stage and outcome data;
• interview scorecards for selection evidence;
• a survey tool for candidate-experience questions;
• your communication system for response-time and closure tracking.

Use forms and responses to capture explicit Interested or Decline choices, and use the Role.so analytics suite to connect those responses with page engagement and decline reasons. These signals are particularly useful before a formal application, where traditional ATS data often starts too late. A candidate information pack can reduce avoidable feedback about missing role context, while the passive-candidate outreach guide shows where this feedback loop fits in practice.

Candidate feedback implementation checklist

• Define whether you are collecting candidate-to-employer feedback, giving employer-to-candidate feedback, or both.
• Choose one or two stages rather than surveying every interaction.
• Keep the survey within three to five minutes unless candidates opt into a deeper interview.
• State whether responses are anonymous, confidential or identifiable.
• Remove unnecessary personal data from open-text prompts.
• Use a documented scorecard for recruiter-to-candidate feedback.
• Train recruiters and hiring managers on the approved feedback standard.
• Segment results by stage and outcome.
• Review recurring themes on a fixed cadence.
• Assign each improvement action an owner and success measure.
• Link perception data to response, withdrawal, closure and decline-reason data.
• Review privacy, equality and employment-law requirements for each market.

Conclusion

Candidate feedback works when it is specific, safe to use and connected to a decision. Ask candidates about the touchpoint they actually experienced. Give candidates feedback about documented, job-related evidence. Then combine perception and behavior to decide what to improve.

Start with the 12-question survey, select the stage that matters most and review the first responses as a team. For passive-candidate outreach, create a candidate page with Role.so and use Interested, Decline and decline-reason signals to understand the response before the formal application begins.

Sources

• LinkedIn. Candidate Experience: How to Get It Right.
• LinkedIn. Improve the Candidate Experience With This One Simple Tactic.
• LinkedIn. The Best Way to Reject Candidates.
• LinkedIn Hiring. How to Measure Candidate Experience.
• U.S. Equal Employment Opportunity Commission. Employment Tests and Selection Procedures.
• Role.so. Candidate experience guide, analytics and candidate information packs.