Candidate Experience Survey Template: Questions, Timing, and Scoring

What is a candidate experience survey?

Sapia defines a candidate experience survey as a short questionnaire that collects applicant feedback across the recruitment journey, from the job description and application to interviews, communication, decisions, rejection, and onboarding. Its purpose is not to generate a vanity score. The survey should pinpoint friction that recruiters and hiring managers can remove.

Sapia recommends collecting feedback at the end of each key stage instead of asking everything at once. SurveyMonkey groups the relevant touchpoints into application, interviewing, communication, feedback and decisions, and overall experience. That breakdown helps teams investigate whether a weak result belongs to the application form, recruiter handoff, interview panel, or decision process.

Include hired, rejected, and withdrawn candidates. Sapia recommends collecting feedback from both successful and unsuccessful candidates because the groups offer different views of the process. Report each outcome separately instead of burying them in one average.

Measure each hiring stage close to the event, then fix one repeatable failure at a time.

Which candidate experience survey template should you use?

Use this nine-question candidate experience survey template for a compact view of the full process. Questions one through eight use a five-point agreement scale, while question nine adds context. For a shorter stage survey, select only the relevant items and leave the wording and scale labels unchanged.

Use one Likert scale, a fixed agreement scale, throughout: 1 = strongly disagree, 2 = disagree, 3 = neither agree nor disagree, 4 = agree, and 5 = strongly agree. Consistent labels make reporting easier and stop candidates from having to relearn the form midway through.

1. The job description clearly explained the role, responsibilities, and requirements.
2. The application process was easy to complete without unnecessary effort.
3. I received clear and timely communication throughout the recruitment process.
4. I understood the next step and expected timing after each interaction.
5. The interviewers were prepared and knowledgeable about the role.
6. The interview questions were relevant to the work described.
7. The hiring team respected my time and gave me space to ask questions.
8. The recruitment process represented the role accurately.
9. Optional open text: What is the single most useful change we could make to improve this process?

Sapia recommends five to seven items plus one open question for a short survey. Ashby’s 2024 recruiting survey analysis, however, found the same 20.1% average response rate across surveys containing one to ten questions. Nine questions work for a full-journey diagnostic. Use five to seven for a focused stage pulse.

Do not turn this form into an interviewer performance scorecard. Candidate feedback measures the experience your process delivered. A separate interview scorecard should assess evidence about the candidate against agreed role criteria.

When should a candidate experience survey be sent?

Send each survey soon after the event it measures, while the candidate still remembers specific details. Formbricks recommends windows ranging from 24 hours after an application to 90 days after the person starts work. Delay the survey when needed so the recruiter’s decision reaches the candidate before an automated feedback request does.

These windows come from Formbricks’ 2026 stage-based candidate feedback guidance. Treat them as operating rules, not permission to send a survey before a human communicates the decision. Ashby reports that Notion uses a three-day delay specifically to give recruiters time to contact candidates before automation sends the form.

Ashby found that 94% of responses arrived within nine days, so keep the collection window simple. Review late submissions, but do not hold routine reporting open indefinitely. Sequence matters more: make the decision, communicate it respectfully, send the feedback form, and separate the response from the individual hiring decision.

What questions should rejected, withdrawn, and hired candidates receive?

Give each outcome its own short survey because each group can diagnose different parts of the process. Rejected candidates can assess communication and treatment. Withdrawn candidates can explain where the opportunity lost momentum. Hired candidates can compare recruiting promises with the real job after 90 days of experience.

Copy-ready rejection survey

• I received the decision within a reasonable and clearly communicated timeframe.
• The hiring team treated me respectfully throughout the process.
• I understood the recruitment stages and what was expected of me.
• The interviews or assessments were relevant to the role.
• Open text: What should we change for future candidates?

Use the standard five-point scale for the first four items. If rejection can happen after application review, screening, assessment, or interview, tag the response with the applicable stage. Starred provides separate templates for these rejection points, allowing each stage to be measured independently.

Copy-ready withdrawal or offer-decline survey

• Multiple choice: What was the primary reason you withdrew or declined?
• The role and offer terms were explained clearly.
• The recruitment timeline supported my decision-making needs.
• My experience during recruitment influenced my decision.
• Open text: What, if anything, could have changed your decision?

For the multiple-choice item, use practical categories such as role scope, compensation, timing, work arrangement, another opportunity, recruitment experience, personal circumstances, and other. Keep the open-text field optional so candidates can add context without being required to explain a private decision.

Copy-ready 90-day post-hire survey

• The job description accurately reflected my current responsibilities.
• The interview process represented the role and working environment accurately.
• The recruitment team set clear expectations before I accepted.
• The transition from signed offer to onboarding was well coordinated.
• Open text: Which recruiting promise proved most or least accurate?

Send this survey after 90 days, as Formbricks recommends, and connect the findings to your onboarding workflow. Compare post-hire alignment with interview ratings to test whether the recruitment process represented the role accurately.

How should anonymity, survey length, and response scales be chosen?

Set anonymity, length, and scale as one measurement policy, then apply it consistently. Sapia recommends five to seven items and anonymous responses by default, while Ashby’s analysis found its highest average response rate among identified-only surveys. Choose the format that fits your privacy and reporting needs, then avoid changing it between periods if you want comparable results.

Read Ashby’s response-rate data carefully. Surveys that let candidates choose between identified and anonymous submission averaged 17.7%, while identified-only surveys averaged 20.6%. That does not prove identification causes more responses, but it shows why anonymity should be chosen as a privacy policy rather than assumed to increase response rates.

When collecting identities, state who can read the response and how the team will use it. If responses are anonymous, avoid report slices that could reveal someone through a tiny cohort. Under either policy, obtain separate consent before contacting a candidate about their comments.

How do you score candidate experience results and act on them?

Calculate response rate, top-two-box candidate satisfaction, and average scores for application, interview, communication, and decision stages. Compare like-for-like cohorts over time, then read comments beside the weakest stage scores. Assign one specific correction per stage. The score locates friction; repeated comments help the recruiting team decide what to change.

1. Validate the sample. Record delivered forms, completed forms, candidate outcome, hiring stage, and role. Do not compare a large application-stage cohort directly with a small final-interview cohort.
2. Find the weakest stage. Compare averages using the same questions, scale, population rules, and reporting window. Treat response rate as context, not as a candidate experience score.
3. Code the comments. Group repeated feedback into practical themes such as unclear next steps, irrelevant questions, technical trouble, scheduling delays, or inaccurate role descriptions.
4. Choose one correction per stage. Name an owner, change the relevant process, and remeasure with the same question wording. Make changes in a way that lets the team evaluate each intervention.

Place these results beside operational recruiting metrics such as funnel movement and hiring speed. Experience and efficiency answer different questions, so review both when deciding where the process needs attention.

How should a candidate feedback form be implemented safely?

Make the form work on mobile devices, automate delivery from the completed hiring stage, explain the privacy terms, and request separate permission for follow-up. Above all, keep survey responses outside individual hiring decisions. Feedback should improve the system after a disposition, not become fresh evidence for or against the candidate.

Build these rules into an HR standard operating procedure. Define the trigger, delay, candidate population, owner, access permissions, reporting fields, and correction process. The survey is only the collection layer. Operating discipline determines whether the feedback changes anything.

Review and remeasure on a fixed cadence that fits your hiring volume. Low-volume teams should wait for a usable cohort before drawing conclusions from individual cases; higher-volume teams can inspect stage movement more often. Keep the cadence stable, preserve the wording, and record every process change made between measurement periods.

How Cogniver helps turn candidate feedback into a better hiring process

Cogniver runs the hiring journey from job post to signed offer and day-one onboarding inside one portal. HR gets a controlled process to pair with this candidate experience survey template, with connected touchpoints across applications, interviews, offers, negotiation, and onboarding.

The branded job portal includes candidate accounts, AI CV screening, and a fairness-configured text AI interviewer that applies the same questions and scoring dimensions to every candidate. Role pages can include photos and PDF attachments. The AI reads those PDFs, so screening and the HR copilot work from what the role page actually promises.

Offer letters remain human-editable throughout negotiation and can require an assigned signatory from the org chart. That person reviews the full recruitment history, then signs or declines before anything reaches the candidate. The signature stays locked to the exact letter text. After signing, the offer reserves a placement seat on the org chart, connecting selection directly to onboarding.