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.

DirectionMain questionTypical outputBest use
Candidate → employer“How did the recruitment process feel and where did it create friction?”Survey answers, open comments, withdrawal or decline reasonsImprove role information, communication, interviews and process design
Employer → candidate“What job-related evidence supported the decision?”Interview feedback, assessment feedback, rejection feedbackGive useful closure and help candidates understand the decision

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.

#SituationCopy-ready candidate feedbackWhat it may reveal
1Clear and well-organized process“The role, interview stages and expected timeline were clear from the start. Each interviewer knew what had already been covered, so the conversations felt coordinated rather than repetitive.”Strong handoffs, useful preparation and consistent interviewer planning
2Slow follow-up“The interviews were positive, but I waited twelve days without 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.”Missed communication SLA, unclear ownership or approval bottlenecks
3Role differed from the job information“The position described during the interview involved substantially more travel and people management than the job page suggested. I would have preferred to understand those expectations before investing in several interviews.”Incomplete role page, late disclosure of constraints or recruiter–manager misalignment
4Relevant interview questions“The questions were closely connected to the work I would actually do. The case exercise gave me a fair opportunity to show how I approach the role rather than testing unrelated trivia.”Job-related assessment and good role-to-interview alignment
5Repetitive or inconsistent interviews“Three interviewers asked almost the same background questions, but I received different explanations of the role’s priorities. A shared interview plan would make the process more coherent.”Missing scorecard, weak briefing or unresolved role definition
6Compensation disclosed too late“The compensation range was only discussed after the final interview and did not match the level presented earlier. Sharing the range sooner would have saved time for both sides.”Late qualification, unclear budget or inconsistent positioning
7Scheduling friction“Rescheduling required several email exchanges because there was no clear owner or booking option. The interviews themselves were good, but arranging them took more effort than expected.”Manual coordination, unclear contact or unnecessary scheduling steps
8Excessive assessment“The take-home task took about six hours, although the invitation estimated two. The expected depth and evaluation criteria were not explained, so it was difficult to judge how much work was appropriate.”Underestimated workload, unclear rubric or disproportionate assessment
9Accessibility handled well“The team responded quickly to my request for an adjustment and confirmed the interview format in advance. I could focus on demonstrating my skills rather than repeatedly explaining what I needed.”Clear adjustment process and respectful preparation
10Poor closure after rejection“I received an automated rejection after four interviews with no indication of what had changed or whether the role had been filled. Even a brief, role-related explanation would have provided better closure.”Weak final communication, no feedback policy or fragmented decision records

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.

If your ATS or survey tool already knows the candidate’s stage and outcome, store those values as metadata rather than asking again. Otherwise, add a short stage question so you can segment the results correctly.

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

#Survey questionSuggested response
1The role and its expectations were clear before I invested time in the process.1 = Strongly disagree; 5 = Strongly agree
2I understood what the next stage of the recruitment process would be.1 = Strongly disagree; 5 = Strongly agree
3I received updates within the timeframes I was given.1 = Strongly disagree; 5 = Strongly agree
4Recruiters and interviewers treated me respectfully.1 = Strongly disagree; 5 = Strongly agree
5The interview questions and assessments were relevant to the role.1 = Strongly disagree; 5 = Strongly agree
6I had a fair opportunity to demonstrate the skills required for the role.1 = Strongly disagree; 5 = Strongly agree
7The recruitment process was easy to complete on the device I used.1 = Strongly disagree; 5 = Strongly agree
8I knew how to request an adjustment if I needed one.1 = Strongly disagree; 5 = Strongly agree / Not applicable
9The practical conditions of the role were communicated early enough for me to make an informed decision.1 = Strongly disagree; 5 = Strongly agree
10The final status or next step was communicated clearly.1 = Strongly disagree; 5 = Strongly agree / Not yet applicable
11How likely are you to recommend applying to this organization?0 = Not at all likely; 10 = Extremely likely
12What is the one change that would most improve this recruitment process?Optional open text

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}} Your responses will not change the hiring decision. 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.

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.

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

Positive interview feedback examples

#Use caseCopy-ready feedback
11Structured problem-solving“Your response to the {{scenario}} question was strong because you clarified the objective, separated assumptions from facts and explained the trade-offs before recommending an approach.”
12Technical or functional depth“In the {{exercise/topic}} discussion, you connected the technical detail to the business outcome and identified the main implementation risk. That matched the level of depth required for this role.”
13Stakeholder communication“Your example of working with {{stakeholder_group}} showed clear expectation-setting, active listening and a practical way of resolving disagreement.”
14Leadership and ownership“The example you gave about {{project}} demonstrated ownership beyond task delivery: you defined the problem, brought the right people together and measured the result.”
15Preparation and role understanding“Your questions about {{team_priority}} showed that you had understood the role’s immediate challenges and were testing whether the environment would support successful delivery.”

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

Constructive and unsuccessful interview feedback examples

#Use caseCopy-ready feedback
16Evidence was too general“For this role, we needed a detailed example of owning {{required_outcome}}. Your answers described the team’s work, but they did not make your own decisions, actions and measurable contribution clear enough for us to assess that criterion.”
17Required depth was not demonstrated“The position requires hands-on experience with {{required_area}} at {{scope_or_scale}}. The examples discussed were adjacent to that requirement, but they did not demonstrate the depth needed to take ownership immediately.”
18Case exercise missed a key constraint“Your proposed solution addressed {{strength}}, but it did not account for {{critical_constraint}} from the brief. We therefore could not confirm the level of risk analysis required for this role.”
19Role level or scope mismatch“Your examples showed strong delivery within a defined area. This position also requires setting direction across {{teams/functions}}, and we did not hear enough evidence of that broader scope during the process.”
20Communication obscured the answer“You had relevant experience, but several answers moved between topics before reaching the decision or result. A more concise situation–action–outcome structure would make your evidence easier to evaluate.”

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. Behavioral data shows where they acted or stopped.

SignalUseful interpretation
Candidate satisfactionOverall perception at a defined stage
Candidate NPS or recommendation scoreWillingness to recommend applying, using one consistent question and stage
Survey response rateWhether the feedback sample is large enough to interpret
Time to first human responseHow long candidates wait for meaningful contact
Time per stageWhere the process slows down
Withdrawal rate by stageWhere candidates choose to leave
Closure coverageWhether candidates receive a clear final decision
Decline reasonsWhy sourced candidates explicitly choose not to continue
Page response rateWhether candidate-page visitors take an explicit Interested or Decline action

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

FAQ

What is candidate feedback in recruitment?

Candidate feedback in recruitment can mean feedback candidates give about the hiring process or feedback recruiters give candidates after an interview or decision. A useful system supports both directions and keeps comments tied to observable, job-related evidence.

How do you ask candidates for feedback?

Ask at a defined stage, explain how the feedback will be used, keep the survey short, make open comments optional and separate the request from the selection decision where possible. Survey rejected, withdrawn and hired candidates rather than only new hires.

What questions should a candidate experience survey include?

Cover role clarity, process transparency, communication, respect, interview relevance, opportunity to demonstrate skills, ease and accessibility, decision communication, overall satisfaction and one open question about what should change.

Should recruiters give rejected candidates feedback?

Where company policy and local law allow it, interviewed candidates can benefit from concise feedback based on documented role criteria and observed evidence. Avoid personality labels, sensitive information, comparisons with other candidates and promises about future selection.

When should candidate feedback be collected?

Useful moments include after application, after interview, after withdrawal, after rejection and shortly after offer acceptance. Do not send a long survey at every stage; choose the touchpoint that matches the question you need to answer.

How should candidate feedback be measured?

Combine survey responses with behavioral measures such as completion, withdrawal, response, time per stage, closure coverage and decline reasons. Segment results by stage, outcome, role and source so one group does not hide another.

How can Role.so support candidate feedback?

Role.so can capture Interested or Decline responses, decline reasons and candidate-page engagement. Use those signals alongside your ATS, interview scorecards and survey tool to understand where candidates continue, disengage or need more information.