📝 HR

Candidate Feedback Surveys

Your employer brand depends on candidate experience. Collect feedback from every candidate — hired or not — to continuously improve your recruitment process. Our conversational format helps candidates share honest, constructive feedback.

Overview

Candidate feedback surveys collect honest reflections from people who recently went through your hiring process — those you hired, those you turned down, and those who withdrew partway through. The point is to understand how your funnel actually feels to the person walking through it, which is almost always different from how it looks on a recruiting dashboard. Common topics include clarity of the role description, responsiveness of recruiters, quality of interviewer preparation, length of the process, and overall fit between expectations and reality.

Why this matters: your employer brand is built one candidate at a time, and the people you do not hire often talk about you more than the people you do. Negative experiences end up on Glassdoor and Blind; great experiences turn rejected candidates into future applicants or external referrers. Feedback surveys are also the cheapest way to identify where your process actually breaks down — usually somewhere boring like a slow scheduling step or an unstructured interview that delivers low signal for both sides.

Who uses them: in-house recruiting teams measuring funnel health, talent acquisition leaders building the business case for a process change, hiring managers who want to know whether their interview style is landing, and people-ops teams running quarterly hiring retros. The same survey design works for senior hires, early-career roles, and contractor placements, with light adjustments to the question stems and the granularity you need from each segment.

What You'll Achieve

Understand how candidates perceive your hiring process
Identify bottlenecks and pain points in your recruitment
Improve your employer brand with data-driven changes
Benchmark your process with NPS-style scoring
Close the feedback loop with automated thank-you emails

Why CrispForms for Candidate Feedback

CrispForms makes it easy to send a short, conversational feedback survey to every candidate at every stage of your process — not just the final-round outcome. The Auto-Responder Emails let you trigger surveys automatically when a candidate is moved to "rejected" or "hired" in your tracker, so you stop relying on a recruiter remembering to send a manual follow-up. The Logic Builder routes hired candidates and declined candidates to different question paths, since their feedback is genuinely different and bundling them dilutes both sets.

Scoring & Calculations let you turn the feedback into an NPS-style score you can chart across quarters, which is how you actually spot whether a process change improved things or just shuffled the problems around. Submission Reports let you slice the data by recruiter, hiring manager, or interview stage so improvements land with the right owner instead of a vague company-wide directive.

Unlike sending surveys through your applicant tracking system — where they often look like another transactional HR email candidates ignore — CrispForms surveys can be branded to match your careers site and feel like a natural extension of the candidate experience. The result is response rates closer to 35 percent than 5 percent, which is the difference between an instrument that informs real change and one that quietly gets archived after one cycle.

CrispForms Features Used

This use case leverages the following CrispForms capabilities:

Scoring & Calculations Auto-Responder Emails Analytics Dashboard Submission Reports Logic Builder Google Sheets Integration

Sample Candidate Feedback Questions

Use these proven questions as a starting point. Customize them to fit your brand and goals.

Overall, how would you rate your interview experience with us? (Options: 1 through 10)
How clearly was the role described before you applied? (Options: Very clear, Clear, Somewhat clear, Unclear)
How responsive was our recruiting team throughout the process? (Options: 1, 2, 3, 4, 5)
How long did it take from first interview to a final decision? (Options: Less than 1 week, 1-2 weeks, 3-4 weeks, More than a month)
Did our interviewers seem prepared and informed about your background? (Options: Yes, Somewhat, No)
In your own words, how would you describe our company culture based on what you saw?
Which stage needs the most improvement? (Options: Application, Recruiter screen, Hiring-manager interview, Onsite or panel, Offer)
How likely are you to recommend applying here to a peer? (Options: 0 through 10)
What did we do well that we should keep doing?
Anything we could have done differently to make this a better experience for you?

Best Practices

Send within 48 hours of the decision

Memory fades fast — and candidates rationalize their feelings either up or down within a few days. Send the survey as soon as the candidate hears yes or no, while the experience is still concrete and the answers reflect what actually happened rather than a polished retrospective.

Lead with appreciation, not data

Open the survey with a genuine "thank you for your time" and a one-line explanation of how the feedback will be used. Candidates who feel respected give longer, more useful answers; candidates who feel like they are being audited give terse one-word responses.

Survey rejected candidates too

Rejected candidates have more candid, more useful feedback than the ones you hired — they have less to lose and have just experienced the parts of the funnel that need the most work. Use the Logic Builder to route them to a slightly different question set that respects the outcome.

Share findings with interviewers

Once a month, send each hiring manager and interviewer a redacted summary of feedback that mentions their stage. People will not improve interviewing skills they never know are an issue, and named feedback (without naming the candidate) is the fastest path to real behavior change.

Segment by outcome and source

Hired candidates and rejected candidates will rate your process very differently, and an average across both hides the pattern. Use the Submission Reports to compare scores within each group and look for differences by sourcing channel — that is usually where the actionable insights live.

Common Mistakes to Avoid

Mistake: Only surveying hired candidates.

Fix: Send the survey to everyone, regardless of outcome. Rejected and withdrawn candidates often give the most useful feedback because they experienced the parts of the funnel where things actually broke. Use the Logic Builder to tailor the questions to each group.

Mistake: Waiting weeks before asking.

Fix: Send the survey within 48 hours of the final decision while the experience is still fresh. Candidates rationalize their feelings within a week — either too positive or too negative — and the answers stop reflecting what actually happened during the process.

Mistake: Asking only quantitative ratings.

Fix: Pair every rating question with an optional follow-up text field for the "why." Numbers tell you something changed; words tell you what to fix. Without the qualitative layer, you end up with directionally interesting trends and no idea what to do about them.

Mistake: Sending from a no-reply address.

Fix: Use a real recruiter or recruiting-team alias so candidates know responses go somewhere. A no-reply sender signals that feedback is going into a void, which depresses response rates and skews who bothers to fill out the survey toward extreme experiences only.

Mistake: Never sharing results internally.

Fix: Build a monthly cadence of sharing redacted findings with interviewers and hiring managers. The point of collecting feedback is to change something, and that only happens when the people running interviews actually see how candidates experienced their part of the process.

Frequently Asked Questions

How do I get rejected candidates to actually respond?

Three things help most: lead with a genuine thank-you rather than a request, keep the survey under five questions, and send it from a real human inbox rather than a no-reply alias. Most candidates want to give feedback if they believe it will be read; the format and tone signal whether you actually mean it.

What is the best way to measure interview-process NPS?

Ask "On a scale of 0 to 10, how likely are you to recommend applying here to a peer?" and follow up with a free-text "why." Use Scoring & Calculations to track the NPS-style metric across quarters, and segment by hired versus rejected. The trendline matters more than the absolute number in any single quarter.

Can I send different surveys to hired and rejected candidates?

You can either run two separate forms or use the Logic Builder inside one form to branch on a first question that asks about the outcome. The single-form approach is easier to maintain and gives you a clean, unified dataset for analysis. Tailor follow-ups so each group sees only the questions that are relevant to their experience.

Should I make the survey anonymous?

For most teams, semi-anonymous works better than fully anonymous. Ask for the role they applied for and the rough stage they reached, but skip name and personal email. That lets you analyze trends by stage and team without surfacing individual identities, and respondents are typically more honest than they would be in a fully-attributed format.

When in the process should I send this?

Send it within 48 hours of the final decision — yes or no. Memories are sharpest in that window, and candidates have not yet rationalized the outcome. For very long processes, consider a brief mid-process pulse after the onsite as well, separately from the final post-decision survey.

Why are my response rates so low?

The most common causes are sending from a no-reply sender, sending too late, and asking too many questions. Trim the survey to five or six items, send within 48 hours from a recognized internal name, and explain in one sentence how the feedback will be used. Those three changes together typically double response rates.