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

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

Candidate feedback in recruitment means two different things:

1. feedback from candidates about the recruitment process; and
2. feedback from recruiters or hiring teams to candidates.

Both matter. Candidate-to-employer feedback shows where the process creates clarity, trust or friction. Recruiter-to-candidate feedback helps people understand a decision and improve future applications.

This guide gives you 20 realistic candidate feedback examples, a copy-ready survey template, survey questions, invitation and rejection email templates, and a practical system for turning feedback into process improvements.

Key takeaways

• Ask about a specific stage instead of requesting “general feedback.”
• Include rejected, withdrawn and still-active candidates, not only hires.
• Keep recruiter feedback job-related, evidence-based and consistent.
• Separate the hiring decision from the request for feedback.
• Combine survey responses with behavioral data such as drop-off, response and decline reasons.
• Assign an owner and a next action to recurring feedback themes.

What candidate feedback in recruitment means

The phrase candidate feedback is ambiguous. Before building a survey, template or workflow, decide which direction you mean.

The two directions should support each other. Candidate comments reveal where the process is unclear; structured interviewer notes make it easier to give candidates useful feedback without improvising after the decision.

Feedback is evidence, not a verdict. One comment can reveal a real problem, but it does not automatically prove that the whole process is broken. Look for repeated themes, identify the stage and audience affected, and compare what candidates say with what they actually do.

For a wider view of the hiring journey, read how to improve candidate experience.

20 candidate feedback examples you can adapt

The first ten examples are written from the candidate's perspective. The next ten are recruiter-to-candidate examples.

Adapt the wording to the role, stage and evidence. Do not copy a positive or negative statement when it does not reflect what happened.

Candidate feedback on the recruitment process: 10 sample responses

1. Clear role information

“The role, reporting line and first priorities were explained clearly. I understood what the team expected before the first interview, which made it easier to prepare relevant examples.”

What it reveals: the job page, recruiter message and interview preparation were aligned.

2. Helpful recruiter communication

“The recruiter explained each stage, confirmed who I would meet and followed up when the timeline changed. I never had to guess what was happening next.”

What it reveals: ownership and proactive updates reduced uncertainty.

3. Slow follow-up after an interview

“Everyone I met was respectful, but I waited almost two weeks after the final interview without an update. Even a short message saying the decision was delayed would have improved the experience.”

What it reveals: the issue is not necessarily decision speed; it is the absence of a promised status update.

4. Repetitive interviews

“The interviewers asked thoughtful questions, but three conversations covered almost the same topics. I would have preferred each stage to have a clearer purpose.”

What it reveals: the interview plan may lack distinct competencies, shared notes or stage ownership.

5. Job description and interview mismatch

“The interviews described a role with much more client delivery and travel than the job posting suggested. I appreciated learning this before an offer, but the information should have been clear earlier.”

What it reveals: the role page and interview reality are not fully aligned.

6. Strong salary transparency

“The salary range and bonus structure were shared before I invested time in the process. That made it easier to decide whether the opportunity matched my expectations.”

What it reveals: early compensation information supports informed self-selection.

7. Scheduling friction

“Finding interview times required several email exchanges, and one meeting was moved at short notice. A booking link and clearer time-zone information would have made scheduling easier.”

What it reveals: coordination, not the interview itself, created the main friction.

8. Re-entering résumé information

“The application asked me to upload my résumé and then type the same employment history into separate fields. The duplication made the application feel longer than necessary.”

What it reveals: application design is creating avoidable effort.

9. Accessible interview experience

“The team responded quickly to my request for captions and confirmed the setup before the interview. I could focus on the conversation instead of worrying about access.”

What it reveals: clear accommodation ownership and preparation improved the experience.

10. Clear rejection but limited explanation

“The rejection arrived when the recruiter said it would, and the message was respectful. I would have valued one specific sentence about the main criterion that separated the selected candidate.”

What it reveals: closure worked, but the organization may be able to provide more decision-useful feedback.

Recruiter feedback to candidates: 10 sample responses

Use these examples only when they match documented evidence. Replace placeholders and generic wording with the competency, behavior or work sample that actually influenced the decision.

11. Positive feedback on role understanding

“You showed a strong understanding of the role's priorities. Your example of reducing onboarding time connected the customer problem, the operational constraint and the measurable result.”

Why it works: it identifies the competency and the evidence instead of saying only “great interview.”

12. Positive feedback on stakeholder communication

“Your explanation of the migration project was clear and well structured. You adapted the level of detail for technical and non-technical stakeholders and explained how you handled disagreement.”

Why it works: it describes observable behavior relevant to the job.

13. Positive feedback on problem-solving

“You did not jump straight to a solution. You clarified the objective, tested the assumptions and compared the trade-offs before recommending an approach.”

Why it works: it explains what the candidate did well in the assessment.

14. Positive feedback on technical execution

“Your work sample was easy to follow, covered the main failure cases and explained the decisions you would revisit with more time. That matched the level of judgment we need in this role.”

Why it works: it recognizes both execution and professional judgment.

15. Positive feedback on leadership

“Your example showed how you set direction, involved the team and changed course when the initial plan was not working. The outcome was specific and your own contribution was clear.”

Why it works: it avoids vague labels such as “leadership presence.”

16. Constructive feedback when evidence was too general

“Your answers described the team's achievements, but we needed more detail about the decisions you personally made. In future interviews, separate the context, your action and the result so the interviewer can assess your contribution.”

Why it works: it identifies the missing evidence and gives an actionable next step.

17. Constructive feedback on the required scope

“The role requires ownership of multi-team programs from planning through delivery. Your examples were strongest within a single team, so we did not yet have enough evidence of the cross-functional scope required for this position.”

Why it works: it compares demonstrated experience with a documented requirement.

18. Constructive feedback on a work sample

“The proposed solution covered the main user flow, but it did not address access control or failure recovery, which were two scored criteria for the exercise. Explaining those trade-offs would have strengthened the submission.”

Why it works: it points to predefined assessment criteria.

19. Constructive feedback on prioritization

“You generated several useful ideas, but the recommendation did not identify which action should happen first or what evidence would change the priority. This role requires explicit sequencing under limited time and budget.”

Why it works: it connects the gap to work the candidate would perform.

20. Respectful feedback after selecting another candidate

“You met the core requirements and performed well in the interviews. We selected a candidate who provided deeper evidence of leading enterprise implementations, which is the most immediate need for this hire. The decision was based on that role-specific experience rather than a general concern about your capability.”

Why it works: it explains the comparative criterion without inventing a flaw.

Candidate feedback survey template

A useful candidate survey is short, stage-specific and easy to answer on mobile. It should include rating questions for comparison and optional open-text questions for context.

You can copy the template below into your survey tool.

Survey introduction

Thank you for taking part in the [Company] recruitment process for [Role]. This optional survey asks about your experience so we can improve how we communicate and evaluate candidates. Your answers [are anonymous / are confidential / will be linked to your recruitment record]. They will not change the decision already communicated to you. The survey should take only a few minutes.

Choose one privacy statement and make sure it reflects the way you actually store and use the responses.

Candidate experience survey questions

Use the same labels across reporting periods. For a five-point scale, for example:

• 1 — Very poor
• 2 — Poor
• 3 — Acceptable
• 4 — Good
• 5 — Excellent
• Not applicable

Do not force candidates to rate a stage they did not experience. Record the candidate's stage and outcome so you can compare hired, rejected, withdrawn and active candidates without mixing unlike experiences.

Candidate feedback survey email template

Send the decision first. Then use a separate message for the survey so the request does not obscure the outcome.

Subject: A quick question about your recruitment experience

Hi [First name],

Thank you for the time you invested in the recruitment process for [Role].

We are reviewing how we communicate with and evaluate candidates, and your perspective would be useful. Would you be willing to complete this short, optional survey?

[Survey link]

The survey should take only a few minutes. Your answers [are anonymous / are confidential / will be linked to your recruitment record] and will be used to improve the recruitment process.

Thank you,
[Name]
[Company]

For candidates who withdrew, acknowledge the withdrawal before asking why. Do not make the survey feel like a challenge to their decision.

When to ask candidates for feedback

Ask close enough to the experience that the details are still clear, but do not interrupt a sensitive decision or create uncertainty about the candidate's status.

Do not survey only the people you hired. That creates an overly positive sample and hides the experiences of candidates who were rejected, withdrew or stopped responding.

How to ask for honest candidate feedback

Make the question specific

“Do you have any feedback?” puts all the work on the candidate. Ask about a stage or decision instead:

• What was unclear before your first interview?
• Which part of the application required the most unnecessary effort?
• Did each interview have a distinct purpose?
• Was the salary and working arrangement information available early enough?
• What update would have improved the waiting period?
• What made you decide to continue, decline or withdraw?

Explain the privacy model

Use the right word:

• Anonymous: the response cannot reasonably be linked back to the person.
• Confidential: identified responses are restricted to defined people or teams.
• Linked: the response becomes part of the recruitment record.

Do not call a survey anonymous if the URL, email field or analytics identify the respondent.

Keep open-text questions optional

Free-text feedback is valuable but requires effort. Use one question about what worked and one about what should change. Let candidates skip both.

Close the loop internally

Candidates do not need a personal response to every survey answer, but the organization should review recurring themes, assign owners and document changes. A survey without an operating rhythm becomes a collection exercise rather than an improvement system.

How recruiters should give feedback to candidates

Useful recruiter feedback follows a simple sequence:

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

For example:

Criterion: communicating a technical decision to non-technical stakeholders.
Evidence: the answer explained the architecture but did not address customer impact, cost or rollout risk.
Impact: the panel did not have enough evidence for a core requirement of the role.
Next step: prepare an example that explains the audience, trade-offs, decision and measurable result.

Base feedback on documented criteria

The feedback should come from the same criteria used to evaluate the candidate. Structured interviews make this easier because candidates receive consistent questions and responses are assessed against defined, job-related standards. The U.S. Office of Personnel Management's structured interview guidance describes this standardized approach.

Describe evidence, not personality

Prefer:

• “The example did not show ownership beyond one team.”
• “The work sample did not cover two required failure cases.”
• “The answer did not quantify the result.”

Avoid:

• “You were not confident enough.”
• “You did not feel senior.”
• “You were not a culture fit.”
• “The panel did not connect with your personality.”

The second group is vague, difficult to act on and more exposed to inconsistent interpretation.

Keep U.S. hiring feedback job-related

Hiring decisions and feedback should not rely on protected characteristics, stereotypes or disability-related assumptions. The EEOC's overview of prohibited employment practices explains the federal protections that apply to application and hiring, while its small-business guidance on hiring questions covers limits on pre-offer disability-related questions.

This article is an operational guide, not legal advice. Align detailed candidate feedback with your documented selection process, internal policy and legal guidance applicable to the role and location.

Do not promise feedback you cannot deliver consistently

A recruiter may be able to provide detailed feedback after a final interview but not after every high-volume application. Set expectations early:

• which stages receive individual feedback;
• who approves it;
• how quickly it is sent;
• which assessment information can be shared;
• how candidates can ask for clarification.

Consistency matters more than an ambitious promise that the team cannot keep.

Candidate rejection feedback email template

Use this after the decision has been approved. Replace the example criterion with the real, documented reason.

Subject: Update on your application for [Role]

Hi [First name],

Thank you for the time and preparation you invested in the process for [Role].

We have decided not to move forward with your application. The team valued [specific strength or evidence]. For this hire, the deciding criterion was [job-related requirement]. We selected a candidate who demonstrated [specific evidence or scope] more directly during the process.

One practical suggestion for future interviews would be to [specific, actionable next step].

Thank you again for your interest in [Company]. We appreciate the opportunity to learn about your experience.

Best,
[Name]
[Company]

Do not add a positive sentence merely to soften the message. Use a strength only when the interview notes support it.

What candidate feedback should you track?

Survey scores become more useful when you segment them by stage, outcome and role.

Track at least:

• recruitment stage reached;
• hired, rejected, withdrawn or still active;
• role or job family;
• location or market where relevant;
• source or outreach campaign;
• rating for role clarity;
• rating for process clarity;
• recruiter communication rating;
• interview relevance and fairness rating;
• application or scheduling friction;
• likelihood to recommend;
• recurring open-text themes;
• decline and withdrawal reasons.

Define the denominator before reporting a percentage. A response rate based on survey invitations is different from a response rate based on candidate-page visitors. Keep event names, time windows and filters consistent before comparing teams or periods.

Combine feedback with behavioral data

Candidates may say that a process is clear while still abandoning a particular step. Others may decline without completing a survey. Use perception and behavior together.

Examples:

With small samples, treat changes as directional. Read the comments, inspect the affected cases and avoid declaring a trend from one unusually positive or negative response.

How Role.so supports the feedback loop

Role.so helps recruiters collect lightweight feedback before a full survey is necessary.

A personalised candidate page can:

• explain the role, team, terms, process and next step;
• let a candidate respond Interested or Decline;
• collect decline reasons;
• show page views, engagement and response signals;
• preserve the source of personalised links for campaign analysis.

That makes a decline useful rather than invisible. For example, repeated salary, working-arrangement or location objections can reveal that the opportunity, audience or message needs adjustment.

Use Role.so forms and responses to collect explicit candidate actions, review candidate-page analytics, and inspect decline reasons for an individual candidate pack.

A candidate page does not replace a full candidate experience survey or thoughtful recruiter feedback. It adds an earlier signal: whether people understood the opportunity and why they chose to continue or decline.

Candidate feedback process checklist

• Define whether you need candidate-to-employer feedback, recruiter-to-candidate feedback or both.
• Map each survey question to a stage and an owner.
• Keep the survey optional, short and mobile-friendly.
• State whether responses are anonymous, confidential or linked.
• Include hired, rejected and withdrawn candidates.
• Use the same rating labels over time.
• Base recruiter feedback on documented, job-related criteria.
• Avoid personality labels, stereotypes and protected-characteristic references.
• Give one actionable next step when the evidence supports it.
• Group recurring comments into a defined theme taxonomy.
• Compare feedback with funnel, timing and decline data.
• Assign and review improvement actions on a regular schedule.

Common candidate feedback mistakes

Asking only successful candidates

Hired candidates have a different outcome and often a different perception of the process. Their feedback matters, but it cannot represent everyone.

Treating Candidate NPS as the whole system

A single recommendation score is easy to track but does not explain which stage caused the result. Pair it with stage-specific questions and open text. The broader candidate experience measurement guide explains how to combine perception and behavioral metrics.

Giving feedback from memory

Feedback written days later without structured notes becomes vague and inconsistent. Capture evidence against the assessment criteria during the process.

Using “culture fit” as an explanation

“Culture fit” rarely tells the candidate what evidence was missing. Explain the job-related behavior, scope or criterion instead.

Collecting feedback without changing anything

Create a recurring review with a named owner. Decide which themes require a content update, process change, interviewer calibration or tooling improvement.

Creating a survey for every related keyword

One strong page can cover survey questions, invitation templates and examples. Expand this resource when related intent overlaps instead of creating several thin pages that compete with one another.

Conclusion

Candidate feedback works when it is specific enough to act on and structured enough to compare.

Start with one recruitment journey. Ask candidates about role clarity, communication, interviews, speed and accessibility. Give candidates feedback using documented criteria and observable evidence. Then connect what people say with where they respond, decline, withdraw or stop progressing.

A clearer feedback loop improves more than the survey score. It helps recruiters refine the role information, focus interviews, communicate decisions and understand which parts of the candidate journey need attention.

See how Role.so captures candidate responses and decline reasons or create your first candidate page.

Sources

• U.S. Equal Employment Opportunity Commission. Prohibited Employment Policies/Practices.
• U.S. Equal Employment Opportunity Commission. What Can't I Ask When Hiring?.
• U.S. Office of Personnel Management. Structured Interviews.
• Role.so. How to Improve Candidate Experience, Forms & Responses, Analytics & Insights, and Individual Candidate Pack Analytics.