Recruitment Survey Template
Send this recruitment survey to catch friction and confusion before candidates drop out. You will get stage-based CSAT/CES/NPS-style scores plus open-text feedback you can assign and fix weekly. Customize your stages and roles, keep the candidate version to 3-5 minutes, and use separate links or branching for candidates vs hiring managers.
Trusted by 5000+ Brands
When to Send a Recruitment Survey (3 best moments)
1) Right after application completion (ATS/form friction)
Use this to catch ATS and application-form friction before it costs candidates. Starter timing target: send within about 5 minutes of submission (adjust after your baseline by role and channel), and swap in your job families/locations while you keep it short.
Audience: Candidates (all who finish the application).
Length: Aim for 3-5 minutes (starter target; adjust after your baseline) and keep question count lean.
Key goal: Find drop-off drivers like confusing fields, time-to-complete, and upload issues. Do this next: add one CES-style effort item and one open-text prompt for what got in the way.
2) Soon after each interview (scheduling + interview quality)
Use this to capture scheduling pain and interviewer quality while details are fresh. Starter timing target: send within 2-24 hours of the interview (adjust after your baseline), and keep the question set consistent across interview formats (phone, video, onsite).
Audience: Candidates who interviewed; optionally the interview panel (separate link).
Length: Aim for 3-5 minutes for candidates (starter target; adjust after baseline); keep any panel survey short and separate.
Key goal: Measure logistics and interview quality so you can fix what candidates feel immediately. Do this next: branch a follow-up question when a score is low (for example, bottom-box ratings on your CSAT scale).
3) After the decision (clarity + fairness)
Use this to learn what drove outcomes (offer accepted/declined, rejection, or withdrawal). Starter timing target: send within 24-72 hours of the decision (adjust after your baseline), and customize the ending based on outcome (accepted vs declined vs rejected vs withdrew/ghosted).
Audience: Candidates (accepted, declined, rejected, withdrew/ghosted) and hiring managers (identified, separate link).
Length: Aim for 3-5 minutes for candidates (starter target; adjust after baseline); keep the hiring manager version as short as possible even if you add internal process questions.
Key goal: Check clarity and perceived fairness so you can improve communication and decision quality. Watch for: emotional timing after rejection - keep tone neutral and avoid asking for sensitive personal details.
Who to Survey (Candidates vs Hiring Managers) + Stage-Based Deployment Map
Use this to separate candidate experience problems from internal process gaps. Start by sending one short candidate survey per stage, then add an identified hiring manager survey when you are ready to assign fixes. Swap in your stages (screen, loop, assessment) and keep the candidate version short.
Start with clear segments (so your results are actionable)
- Primary candidate segments: hired (offer accepted), rejected, and withdrew/ghosted.
- Secondary internal segments: hiring managers and the interview panel (use separate links so questions stay relevant).
Stage-based deployment map (simple timing you can copy)
- Application complete: send to candidates immediately after submission (audit ATS friction).
- Post-interview: starter timing target is within 2-24 hours (adjust after your baseline; capture scheduling + interviewer quality).
- Post-decision: starter timing target is within 24-72 hours (adjust after your baseline; measure clarity and fairness).
- Post-offer: if you track offer acceptance drivers, add a short module right after accept/decline.
Keep surveys short by using two paths: (1) a candidate link with branching by outcome, and (2) a hiring manager link focused on intake quality, speed, and partnership. If you cannot run separate links, use skip logic so candidates never see internal-only questions and hiring managers never see candidate-only items.
Anonymity rule: default to anonymous for rejected and withdrew/ghosted candidates; add an optional opt-in field if they want follow-up. Use identified responses for hiring managers when you need to assign fixes, and limit access using your privacy and data access controls.
- Invite subject line (candidate): "Quick feedback on your application/interview experience" (starter copy; adjust after baseline).
- Invite body (candidate): "Your feedback helps us improve our recruiting process. This survey takes about 3-5 minutes." (starter target; adjust after baseline).
- Reminder caps: starter rule is 0-1 reminder max to rejected candidates; starter rule is 1-2 reminders to hiring managers if you need coverage (adjust after baseline and your brand policy).
- Length reality check: shorter surveys tend to get more completes; treat 3-5 minutes as a starter target and cut optional modules first (see Effect of questionnaire length, personalisation and reminder type on response rate).
Avoid: one giant survey that asks candidates about everything. You will lose the people who had the worst friction, and your stage diagnostics will blur together.
CSAT vs CES vs NPS-Style: Pick One Primary Metric (and keep scales consistent)
Use this to pick one primary score per section so your recruiting survey stays easy to answer and easy to trend. Default to CSAT for overall stage satisfaction, add one CES item for effort, and only use NPS-style when you are tracking employer brand over time. Keep labels and direction consistent (higher = better), and customize the wording to match your stages.
| Primary metric | What it tells you | Best stage fit | Example item (copy-ready) | Scoring shortcut | Scale notes |
|---|---|---|---|---|---|
| CSAT (satisfaction) | How satisfied candidates were with a stage or the overall process. | Post-application, post-interview, post-decision. | "Overall, how satisfied were you with the [stage] experience?" | % satisfied = % selecting top box(es) (for example, 4-5 on a 1-5 scale). | Works well on 1-5 or 1-7. Use clear endpoints and consistent direction; follow Likert scale best practices. |
| CES (effort) | How hard the process felt (friction). Strong for fixing operational issues fast. | Application form/ATS, scheduling, assessments, interview logistics. | "The [stage] was easy to complete." | Average effort score (or % agreeing, if you prefer a top-box view). | Keep wording unambiguous ("easy" vs "difficult"). Avoid mixing effort and satisfaction in one item. |
| NPS-style (advocacy) | Likelihood to recommend your company as a place to apply/work (brand signal). | Post-decision and post-offer (accept/decline). | "How likely are you to recommend applying to [Company]?" | Promoters - detractors (typically 9-10 minus 0-6, on a 0-10 scale). | Use only if you can run it consistently over time. Add one driver question so you know what to fix. |
| Scale choice (5-point vs 7-point) | How much granularity you want vs speed and clarity. | All stages (choose once and keep it). | 5-point: faster; 7-point: more nuance for mature programs. | Trend the same scoring rule every run (top-box % or mean). | Pick one scale for candidates and stick with it for trending. Switch only at a clean baseline reset. |
Default metric setup (lightweight)
- Candidates (most teams): 1 CSAT + 1 CES + 1 open-ended improvement prompt per stage.
- Employer brand tracking: 1 NPS-style + 1 driver question + 1 open-ended prompt (run post-decision).
Keep your scales clean (do/don't)
- Do: keep scale direction consistent (higher = better) and repeat the same anchor labels every stage.
- Do: use one primary scale per section (for example, all 1-5 agreement items together).
- Don't: use double-barreled items like "The recruiter was friendly and kept me updated." Split it into two questions.
- Don't: mix 1-5, 1-7, and 0-10 scales in the same short candidate survey.
Recruitment Survey Questions (by Stage + Smart Branching)
Use these questions to pinpoint where candidates struggle and why they drop out. Start with the core modules (CSAT, CES, communication), then swap in stage-specific questions for your interview loop and offer flow. Keep optional fields minimal, and use branching so each candidate sees only what matches their outcome.
Overall satisfaction (CSAT-style)
"Overall, how satisfied were you with your experience in our recruitment process?"
Why it matters: This gives you a single headline score you can trend month over month.
When to use: Post-decision for all candidates (accepted, declined, rejected, withdrew).
"How satisfied were you with the [application/interview/offer] stage?"
Why it matters: Stage CSAT tells you where the process breaks, not just that it breaks.
When to use: Add after each major stage survey so you can compare stages side by side.
Effort (CES-style)
"The application process was easy to complete."
Why it matters: High effort at the front door drives abandonment and lower-quality applicant pools.
When to use: Post-application completion. Pair with one open-text question about what slowed them down.
"Scheduling interviews was easy."
Why it matters: Scheduling friction is one of the fastest fixes you can make (and candidates feel it immediately).
When to use: Soon after the interview (starter timing target: within 2-24 hours; adjust after your baseline), especially if you run multi-round loops.
Advocacy (NPS-style)
"How likely are you to recommend applying to [Company] to a friend or colleague?"
Why it matters: This gives you a brand signal that is easy to share internally, but it is not diagnostic on its own.
When to use: Post-decision only. Keep it stable if you want a trend line.
"What is the main reason for your score?"
Why it matters: This turns an advocacy score into a fix list (communication, speed, fairness, role clarity).
When to use: Immediately after the NPS-style item (always show it, not just for low scores).
Communication
"I knew what the next step was after each stage."
Why it matters: Vague next steps create anxiety and drive candidate drop-off.
When to use: Post-application and post-interview. Trend by stage to see where clarity breaks.
"Communication from the recruiter was timely."
Why it matters: Slow updates look like disinterest, even when the team is simply busy.
When to use: Post-interview and post-decision. Use it to justify templates and SLAs.
Scheduling and logistics
"Interview details (time, location/link, agenda) were clear."
Why it matters: Logistics errors are avoidable, and candidates remember them.
When to use: Post-interview. Use as a trigger for calendar and confirmation improvements.
"The time from application to first interview felt reasonable."
Why it matters: Speed affects acceptance rates and candidate confidence.
When to use: Post-interview or post-decision. Compare by role family and source channel.
Role clarity
"Before interviewing, I understood the role responsibilities."
Why it matters: Poor role clarity wastes interview time and increases offer declines.
When to use: Post-interview. Use to tighten job descriptions and recruiter screens.
"The compensation range and level expectations were clear."
Why it matters: Misalignment here often shows up as late-stage declines.
When to use: Post-decision and post-offer. Ask only if you can act on the result.
Fairness and respect
"I was treated with respect throughout the process."
Why it matters: Respect is table stakes, and it directly affects referrals and reviews.
When to use: Post-decision for all candidates. Treat low scores as urgent.
"The interview questions felt relevant to the role."
Why it matters: Irrelevant questions reduce perceived fairness and lower acceptance likelihood.
When to use: Post-interview. Use to improve interviewer training and question banks.
Interview quality
"Interviewers were prepared and had reviewed my background."
Why it matters: Unprepared interviews feel disrespectful and lead to drop-off.
When to use: Soon after the interview (starter timing target: within 2-24 hours; adjust after your baseline), especially in multi-interviewer loops.
"I had enough time to ask questions."
Why it matters: Candidates need space to assess you, not just the other way around.
When to use: Post-interview. Use to adjust agendas and interviewer guidance.
Transparency
"The overall timeline for this role was clear."
Why it matters: Transparency reduces ghosting and cuts inbound status-chasing.
When to use: Post-application and post-interview. Track by role family and seniority.
"I received a clear explanation of the decision outcome."
Why it matters: Clear outcomes protect your employer brand, even when the answer is no.
When to use: Post-decision. Be careful with what you promise; align with your policy.
Drop-off reasons (withdrawn/ghosted branch)
"Which of the following best describes why you withdrew or stopped responding?"
Why it matters: This tells you what to fix to reduce silent drop-off (speed, comp, scheduling, role mismatch).
When to use: Show only if the candidate selects "withdrew" or you mark them as "no longer interested" in your ATS.
"What is one change that would have kept you in the process?"
Why it matters: You get a concrete fix list instead of guessing why people leave.
When to use: Ask after the withdrawal reason question; keep it optional and short-answer friendly on mobile.
Open-ended improvements (low-score follow-up)
"What could we have done differently to improve your experience?"
Why it matters: This explains low CSAT/CES scores in the candidate's words, without forcing them into your categories.
When to use: Trigger when CSAT is low (for example, the bottom 1-2 boxes on a 1-5 scale) or effort is high (starter trigger rule; adjust after your baseline and scale design).
"If you could change one step in our process, what would it be?"
Why it matters: This produces prioritized fixes because candidates tend to name the biggest pain point first.
When to use: Use as your final question to avoid contaminating earlier ratings.
Smart branching rules (keep the survey short)
- Withdrawn/ghosted path: ask 1 reason question + 1 open-text follow-up, then end.
- Low-score follow-up: when CSAT is bottom-box (or CES indicates high effort), ask "What could we have done differently?" and skip the rest (starter branching rule; adjust after baseline).
- Minimal fields: ask only what you will use (role family, stage reached, interview format). Keep demographics optional and separate.
Avoid: leading or loaded wording (for example, "How helpful was our amazing recruiting team?"). Use neutral phrasing and split combined ideas; use how to write better survey questions and the practical checklist in Designing effective survey questions to catch bias before you send.
Scoring, Reporting, and an Action Playbook (Close the Loop)
- Step 1: Score each stage the same way every time
Use this to turn feedback into a stable scorecard you can trend. Start with one overall score plus stage scores, then swap in your stage names and keep your candidate survey short (aim for 3-5 minutes as a starter target; adjust after your baseline).
- CSAT: % satisfied = % selecting top box(es) (for example, 4-5 on a 1-5 scale).
- CES: average effort score (or % agreeing if you standardize on top-box).
- NPS-style: promoters - detractors (typically 9-10 minus 0-6 on a 0-10 scale).
Watch for: scale chaos. If you change scales or label direction, mark a new baseline and do not compare to old scores.
- Step 2: Run the cuts that explain the score (not every cut)
Use this to find where the process breaks for specific groups you can act on. Do this next: build a standard dashboard view with the same segments every week.
- Job context: role family, location, level.
- Source + funnel: source channel, stage reached, outcome (accepted/declined/rejected/withdrew).
- Process design: interview format, number of rounds, assessment used.
- Owner cuts: recruiter and hiring manager (only after you hit your minimum n per person; starter rule, adjust after baseline).
- Step 3: Trend safely and avoid overreacting to tiny cohorts
Use this to make changes based on patterns, not noise. Do this next: set a reporting rule (starter target: minimum n=10 per cut; adjust after your baseline) and follow your sample size guidance before naming an individual recruiter or hiring manager.
Low response rates do not automatically invalidate your results, but they raise the risk of bias. Keep disposition categories consistent and document them using AAPOR Standard Definitions, and align expectations with what low response rates mean for survey interpretation.
Avoid: publishing recruiter-level rankings off a handful of responses. Start with stage and role-family fixes first.
- Step 4: Run a weekly fix cycle (collect -> review -> assign -> fix -> share)
Use this to prevent "survey then ignore." Do this next: book a weekly review (starter target: 30 minutes; adjust after baseline) with recruiting ops and a small internal group.
- Collect: pull stage CSAT/CES plus top themes from open text.
- Review: scan for week-over-week shifts (starter alert threshold: for example, 10+ points in CSAT top-box; adjust after baseline and volume).
- Assign: name an owner and due date for each fix (recruiting ops, coordinator, TA leader, or HM).
- Fix: ship small changes first (templates, scheduling links, clearer timelines).
- Share: report back internally so teams keep responding and improving.
- Step 5: Use a fix-it mapping to choose the first improvements
Use this to move from scores to concrete process changes. Start with the lowest-effort fixes that remove friction, then swap in your own tools (ATS, scheduler, templates).
- Low scheduling CES: add self-serve scheduling, reduce back-and-forth, tighten interview availability windows.
- Low communication scores: standardize next-step templates, set update SLAs, and define who sends what message.
- Low interview quality: train interviewers, use structured question banks, and enforce interview prep expectations.
- Low role clarity: rewrite the job description, align level expectations, and confirm comp range earlier.
Watch for: trying to fix everything at once. Pick 1-3 changes, ship them, then re-measure the same items.
- Step 6: Copy-ready artifacts (internal summary + candidate-facing close-the-loop)
Internal 1-page summary template (paste into email or Slack):
- Headline: Overall CSAT __%; Scheduling CES __; Top theme: __
- Stage flags: Application __; Interview __; Decision __ (call out the lowest stage)
- Top 3 candidate themes: 1) __ 2) __ 3) __
- Actions + owners: Action __ (Owner __, Due __)
- Next check: Re-measure in __ weeks using the same questions
Candidate-facing "You said, we did" message (use only when appropriate): "You told us scheduling was difficult. We added self-serve scheduling and clearer interview details. Thank you for helping us improve."
Avoid: sharing anything sensitive or identifiable in external updates. Keep the message high-level and process-focused.
Frequently Asked Questions
How long should a recruitment (candidate experience) survey be?
A practical starter target is 3-5 minutes for candidates (often around 6-10 questions), then adjust after you establish your baseline completion rates. Use optional modules and skip logic so only the right candidates see the right follow-ups, and keep any deeper detail in a separate hiring manager survey. Shorter surveys tend to improve completion; see evidence summarized in Effect of questionnaire length, personalisation and reminder type on response rate.
When should I send a survey after an interview or rejection?
For post-interview feedback, a common starter window is within 2-24 hours so scheduling and interviewer feedback stays specific; adjust after baseline based on your interview volume and candidate communication patterns. For post-rejection feedback, use a short cooldown (starter window: 24-72 hours; adjust after baseline) so the message lands respectfully, and keep timing consistent so trends are comparable. Cap reminders to one for rejected candidates as a starter rule, and revisit after you see response and complaint rates.
Should recruitment surveys be anonymous or identified?
Default to anonymous for rejected and withdrew/ghosted candidates, with an optional opt-in field if they want follow-up. Use identified responses for hiring managers when you need to assign fixes, and restrict access to a small group with clear retention and access rules aligned to your internal policy. If you offer follow-up, state who may contact them and how their data will be used.
Do I need CSAT, CES, and NPS all at once?
No. Pick one primary metric per section to avoid confusing scale switches, then add one open-ended question for context. A solid default is CSAT + CES + one open-ended prompt for candidates; use an NPS-style item only if you are tracking employer brand consistently over time.
What sample size is enough to report results by recruiter or hiring manager?
Set a minimum-n threshold before you name any individual recruiter or hiring manager (starter target: n=10+ per person; adjust after baseline and risk tolerance). If you are below that, report by stage, role family, and interview format first, and treat small-cohort results as signals to investigate rather than rankings. For consistent definitions and interpretation context, see AAPOR Standard Definitions and what low response rates mean for survey interpretation.
What should we avoid asking candidates for compliance and sensitivity reasons?
Practice data minimization: avoid protected-class questions unless you have a defined, compliant program and a clear use for the data. Be careful with disability and medical inquiries; follow the EEOC guidance on pre-employment inquiries and disability. Make the survey accessible on mobile and with screen readers using WCAG 2.2 accessibility guidelines.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED