Candidate Experience Survey Questions Template: Application, Interview & Offer Stages

This template gives you candidate experience survey questions you can run right after each hiring stage. You’ll spot friction early (before it hits acceptance rates), get clean talking points with hiring managers, and turn “feedback” into actions with owners and deadlines.

Candidate experience survey questions

Use a 1–5 scale for Q1–Q56: Strongly disagree (1) to Strongly agree (5). Keep it short for candidates: aim for ≤6 minutes completion time. If you want to benchmark your recruiting process and responsibilities end-to-end, align this survey with your internal recruiting workflow and SLAs.

2.1 Closed questions (Likert scale)

Application & job ad clarity (Q1–Q8)
Q1. The job ad clearly described the main responsibilities of the role.
Q2. The job ad clearly stated the required skills and experience for the role.
Q3. The job ad matched what was discussed later in the process (scope, seniority, expectations).
Q4. Compensation information (range or approach) was clear enough for informed decisions.
Q5. The application form asked only for information relevant to this role.
Q6. The application process was easy to complete on my device (mobile/desktop).
Q7. I understood the expected hiring steps and timeline when I applied.
Q8. I received a confirmation that my application was received.
Communication & responsiveness (Q9–Q16)
Q9. I knew who my main contact person was during the process.
Q10. Communication felt timely throughout the process.
Q11. Next steps were explained clearly after each stage.
Q12. Scheduling interviews (date, time, format) was straightforward.
Q13. Changes (reschedules, delays) were communicated proactively.
Q14. I received answers to my questions within a reasonable time.
Q15. I felt informed even when decisions took longer than expected.
Q16. Communication tone was respectful and professional.
Interview process & fairness (Q17–Q24)
Q17. The interview steps were relevant to the role (no unnecessary rounds).
Q18. Interview questions were clearly related to job requirements.
Q19. I was assessed consistently across interviewers (no contradictory expectations).
Q20. The interview environment felt respectful (including remote setup and logistics).
Q21. I was given a fair chance to show my skills (not interrupted, enough time).
Q22. The process considered accessibility needs when relevant (e.g., adjustments, formats).
Q23. I felt psychologically safe to ask clarifying questions during interviews.
Q24. Overall, the interview process felt fair and free from bias.
Recruiter & hiring manager interaction (Q25–Q32)
Q25. The recruiter understood the role and could answer role-specific questions.
Q26. The recruiter set clear expectations on steps, timing, and decision criteria.
Q27. The hiring manager was prepared for interviews and used time effectively.
Q28. The hiring manager explained what success looks like in the first 3–6 months.
Q29. Interviewers introduced themselves and their role in the decision clearly.
Q30. I was treated with respect regardless of the outcome.
Q31. Questions about work setup (remote/office), travel, and flexibility were handled clearly.
Q32. I felt that my time was valued throughout the process.
Offer & decision stage (Q33–Q40)
Q33. I received a clear timeline for the final decision when entering the offer stage.
Q34. The offer package (salary, benefits, start date) was explained clearly.
Q35. The offer matched what was discussed earlier (level, scope, compensation approach).
Q36. I had enough time to review the offer and ask questions.
Q37. My questions during the offer stage were answered clearly and promptly.
Q38. Contract and documentation steps were straightforward.
Q39. The company handled personal data and documents in a trust-building way.
Q40. Overall, I felt confident making a decision based on the information provided.
Overall impression & employer brand (Q41–Q48)
Q41. The process reflected the company culture in a credible way.
Q42. I gained a realistic understanding of the role and team.
Q43. The process increased my interest in the company.
Q44. The process was well organized from start to finish.
Q45. The company’s values (e.g., fairness, respect) were visible in how I was treated.
Q46. I would consider applying again in the future.
Q47. I would recommend applying to this company to someone in my network.
Q48. Overall, I am satisfied with my candidate experience.
Rejected-candidate experience (Q49–Q56) — show only if candidate was rejected
Q49. I received the rejection decision within a reasonable time.
Q50. The rejection message was respectful and clear.
Q51. I received helpful feedback (where feasible) on why I was not selected.
Q52. I understand whether I may be considered for future roles.
Q53. I was informed how my data will be stored and for how long (or how to request deletion).
Q54. The company made it easy to ask follow-up questions after the rejection.
Q55. Despite being rejected, I have a positive impression of the company.
Q56. The rejection process felt fair and consistent.

2.2 Overall / NPS-like question (optional)

Q57. How likely are you to recommend applying to our company to a friend or colleague? (0–10)

2.3 Open-ended questions (open text)

O1. What was the single best part of the process, and why?
O2. What was the single most frustrating part of the process, and why?
O3. If you could change 1 thing about communication or scheduling, what would it be?
O4. If you were rejected: what would have made the rejection experience more respectful or useful?

Question(s) / area	Score / threshold	Recommended action	Responsible (Owner)	Goal / deadline
Application & job ad clarity (Q1–Q8)	Avg <3.5 or ≥20% ratings ≤2	TA Lead + Hiring Manager rewrite job ad; remove non-essential form fields; publish hiring steps & timeline	TA Lead	Updated ad + form within 14 days
Communication & responsiveness (Q9–Q16)	Avg <3.5 or Q10 <3.0	Set response SLAs; add automated status updates; standardize “next-step” message templates	Recruiting Ops	SLA + templates live within 21 days
Interview fairness (Q17–Q24)	Avg <3.5 or Q24 <3.0	Reduce rounds; introduce structured interview guides; train interviewers on consistent scoring	Hiring Manager + TA Lead	New guide + training within 30 days
Recruiter & hiring manager interaction (Q25–Q32)	Q25 or Q27 <3.5	Run a 30-minute role briefing before opening roles; align on decision criteria and “must-have vs nice-to-have”	Hiring Manager	Briefing mandatory for all new roles within 14 days
Offer & decision stage (Q33–Q40)	Avg <3.7 or Q35 <3.5	Implement offer checklist (scope, level, compensation alignment); add pre-close call; tighten approval timelines	TA Lead + Comp/HRBP	Checklist + pre-close step within 21 days
Rejected-candidate experience (Q49–Q56)	Avg <3.5 or Q51 <3.0	Create rejection standards by stage; provide “feedback where feasible” rules; add talent pool consent step	TA Lead	Standards + templates within 30 days
Open text flags (O1–O4)	Any comment alleges discrimination, harassment, or data misuse	Start sensitive-case workflow; document facts; involve DPO/Legal; pause process if required	HRBP + DPO	Acknowledgement within ≤24 h; assessment within 7 days
Overall satisfaction (Q48) + recommendation (Q57)	Q48 <3.7 or Q57 (0–10) avg <7.0	Prioritize top 2 drivers with lowest scores; publish 1-page “what we changed” update to hiring team	Head of TA	Driver plan within 14 days; update within 45 days

Key takeaways

Measure each stage, not just “overall,” to find the real bottleneck.
Use thresholds so feedback triggers actions, not debates.
Assign one owner per fix and set deadlines like any other delivery.
Segment results to spot fairness gaps without exposing individuals.
Close the loop with hiring teams so candidates feel the change indirectly.

Definition & scope

This survey measures how candidates experience your hiring journey from application to decision, including rejection. It’s designed for Talent Acquisition, recruiters, HR/People Partners, and hiring managers in EU/DACH contexts. Use results to improve SLAs, interview structure, fairness, and offer consistency, and to guide coaching and process changes across teams.

Scoring & thresholds for candidate experience survey questions

Use a 1–5 Likert scale: 1 = strongly disagree, 5 = strongly agree. Treat Avg <3.0 as critical, 3.0–3.9 as needs work, and ≥4.0 as strong. For faster reading, track “favorable” as ratings 4–5 and aim for ≥80% favorable per dimension.

If scores drop, decide by pattern: one low item often means a local execution gap; a whole dimension low means a process design problem. If open comments indicate serious misconduct or data concerns, handle it as a sensitive case, not as “survey feedback.”

Simple decision flow: If a dimension Avg <3.5 then pick 1–2 fixes, assign an owner, and confirm completion. If Avg stays <3.5 after 2 cycles then change the process design (rounds, rubrics, SLAs), not just templates.

Recruiting Ops defines a dashboard (dimensions + favorable %) within 14 days.
TA Lead sets “red” thresholds (Avg <3.0 or ≥25% ≤2) within 14 days.
Hiring Managers review their role’s results in ≤30 minutes after each hiring sprint.
HRBP validates sensitive-signal handling rules (e.g., discrimination allegations) within 30 days.
Head of TA reviews trend lines quarterly and retires 1 low-impact metric each quarter.

Follow-up & responsibilities

Candidate feedback only helps if you route it like operational work. Define who owns which signals, and set response times. In DACH settings, keep governance clear and privacy-first; if a Betriebsrat is in place, align the survey purpose, reporting levels, and data access early (high-level, non-binding guidance).

Practical routing: If it’s a process issue (timing, scheduling, templates) then Recruiting Ops owns it. If it’s interview behavior or role clarity then the Hiring Manager owns it with TA support. If it’s a sensitive claim then HRBP + Data Protection Officer (DPO) own it.

Recruiter sends the survey within ≤24 h after each stage outcome (application update, interview, offer, rejection).
Recruiting Ops reviews red flags weekly and assigns owners within 7 days.
Hiring Manager implements agreed interview changes (guides, panel, rounds) within 30 days.
HRBP + DPO acknowledge sensitive comments within ≤24 h and document next steps within 7 days.
Head of TA publishes a monthly internal “top 3 fixes shipped” note within 5 business days.

If you use automation, keep it boring and reliable: a talent platform like Sprad Growth can help automate survey sends, reminders and follow-up tasks while keeping owners and deadlines visible.

Fairness & bias checks

Look at results by group to spot unequal experiences—without creating new privacy risks. Good default cuts are location, role family, seniority band, and process type (remote vs onsite). Use Datenminimierung: only collect what you will use, and avoid reporting on small groups.

Set a reporting threshold like n ≥5 per segment (or higher if needed). If a segment is smaller, roll it up. This supports psychological safety: people share more when they trust you won’t expose them indirectly.

Common patterns and what to do:

Pattern: One location has Q10 (timeliness) Avg <3.0. Response: audit scheduling capacity; add backup scheduler; set SLA reminders within 14 days.
Pattern: Remote candidates rate Q20 (interview environment) <3.5 while onsite is ≥4.0. Response: standardize video setup, punctuality, and interviewer “camera-on” norms within 21 days.
Pattern: Rejected candidates rate Q50 (respectful rejection) high, but Q51 (helpful feedback) <3.0. Response: define stage-based feedback rules and train recruiters on safe, factual feedback within 30 days.

If you suspect bias, don’t jump to conclusions from one metric. Triangulate: compare fairness items (Q19, Q24, Q56) with process consistency (Q17, Q18) and open comments, then decide what to fix first.

Examples / use cases

Use case 1: “Candidates drop off after application.” Scores show Q7 (understood steps) at 3.1 and Q10 (timely communication) at 2.9. The TA lead sets a 48-hour update rule and adds an automated status email after screening. Within the next cycle, favorable ratings for Q10 move above 70%, and fewer candidates ask “any update?” by email.

Use case 2: “Interview felt unfair across panelists.” Q19 (consistent assessment) is 3.0 and Q24 (fair and bias-free) is 3.2, while recruiter items are fine. The hiring manager switches to structured questions, adds a shared scorecard, and reduces one redundant round. Candidates report clearer expectations and fewer contradictory signals between interviewers.

Use case 3: “Offer confidence is low.” Q35 (offer matched earlier discussions) is 3.3 and Q40 (confidence to decide) is 3.4. HRBP and TA introduce an offer checklist and require a pre-close call that confirms level, scope, and decision timeline. Result: fewer last-minute renegotiations and clearer internal approvals.

TA Lead documents each fix as “hypothesis → change → metric” within 7 days of results.
Recruiting Ops runs a 30-minute retro with recruiters monthly and picks 1 experiment.
Hiring Manager reviews 3 anonymized candidate comments in the next hiring sync.

Implementation & updates

Roll this out in a way that builds trust first, then scale. In EU/DACH, align early on privacy, retention, and access. If a works council exists, involve them before launch so you don’t rebuild later (high-level, non-binding guidance). If you track employer brand drivers too, keep your measures consistent with how you manage employer branding messages and role storytelling.

Implementation in 5 steps: (1) pilot in 1 function for 4–6 weeks, (2) review anonymity and comment themes, (3) roll out company-wide, (4) train hiring managers on reading dashboards and taking action, (5) update items once per year.

Recruiting Ops pilots the survey with 1 department and ≥30 responses within 45 days.
DPO confirms data minimization fields and retention period within 30 days.
Head of TA runs a 60-minute manager training on interpreting scores within 21 days of rollout.
TA Ops reviews question performance (completion time, item variance) and updates annually.
HRBP sets a quarterly governance check (access rights, segment thresholds) within 90 days.

Track 3–5 metrics so you can see progress without drowning in dashboards: response rate, median completion time, dimension averages (Q1–Q56 grouped), Q57 recommendation score, and action completion rate. If you already run people dashboards, an HR analytics view that joins stage timing with survey results can help you see where delays drive dissatisfaction—without over-collecting personal data.

Conclusion

A good candidate experience survey does three things: it spots issues early (before they hit your funnel), it makes follow-up conversations with hiring managers concrete, and it forces prioritization through clear thresholds. If you run it by stage—not once at the end—you’ll see whether the real pain is the job ad, responsiveness, interview fairness, or offer clarity.

To get moving, pick 1 pilot area and implement Q1–Q57 in your survey tool today, then decide your thresholds (Avg <3.0 critical; 3.0–3.9 needs work; ≥4.0 strong). Name owners for each dimension and set response times, especially for sensitive comments (≤24 h acknowledgement). After the pilot, scale only what you can follow through on—consistency beats complexity.

FAQ

How often should you run a candidate experience survey?

Run it continuously, triggered after each stage outcome (application update, interview, offer, rejection). That keeps feedback fresh and tied to a specific step you can fix. Review results weekly for red flags and monthly for trends. If volume is low, aggregate quarterly. Keep the survey stable for at least 2–3 months before changing items, so you can see real movement.

What should you do when scores are very low (e.g., Avg <3.0)?

Treat Avg <3.0 as an operational incident. First, identify whether it’s one role/team or a broader pattern by checking segments with n ≥5. Second, pick 1–2 fixes only (for example: reduce interview rounds, set a 48-hour response SLA). Third, assign one owner and a deadline (≤30 days). Re-measure in the next cycle and escalate if there’s no change.

How do you handle critical open-text comments safely?

Separate “process complaints” from “sensitive allegations.” If a comment suggests discrimination, harassment, or misuse of personal data, route it into a documented sensitive-case workflow and limit access to HRBP/DPO. Acknowledge within ≤24 h and set next steps within 7 days. Don’t debate the claim in a hiring sync. For privacy basics and rights, use the European Commission guidance as a starting point.

How do you involve hiring managers without turning this into blame?

Make it about behaviors and process design, not personalities. Share dimension-level results (e.g., Q17–Q24) and 2–3 anonymized comments, then agree on one change the manager controls (interview structure, preparation, clarity of success criteria). Set a deadline and re-check in the next hiring sprint. If you already run manager routines like structured 1:1 meetings, add candidate feedback review as a fixed agenda item.

How do you update the question bank over time without breaking trend data?

Freeze core items (Q1–Q48) for at least 2 cycles so you keep trend comparability. Then rotate a small set (up to 20%) based on what you’ve fixed or what changed in your process. Keep the same dimension structure and question intent, even if you reword for clarity. Document every change with the date and reason. If you add new stages (e.g., assessment centers), add new items rather than replacing core ones.

Jürgen Ulbrich

CEO & Co-Founder of Sprad

Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.