Interview Experience Survey Template
Capture fresh, stage-specific candidate feedback (screen, video, onsite, panel) so you can fix scheduling friction, communication gaps, and interviewer consistency. Start with a stable Core block you can trend over time, then add optional modules only when they apply to the interview format or role.
Survey preview loading...
Trusted by 5000+ Brands
When to Send an Interview Experience Survey (3 best moments)
After each major stage completes (screen, hiring manager/technical, onsite/panel)
Goal: pinpoint which stage creates the most drop-off (scheduling, clarity, interviewer experience).
Starter target: send the same day (or within 24 hours) after the stage ends while details are fresh. Adjust based on your completion baseline and candidate time zones.
Do this now: create one SuperSurvey audience list per stage completion, then map the same Core block to every list.
Cadence rule: Core items every stage; add only the module that matches that stage (for example, onsite logistics only after onsite).
Rejected vs advancing: use the same survey for comparability. Change only the thank-you text so it does not imply outcomes or invite debate about decisions.
Candidate experience research consistently finds that communication and process clarity shape perceptions of your organization, even when candidates are not selected. Use stage sends to find the exact break point instead of guessing from end-to-end feedback (see Gallup's The Lasting Impact of Exceptional Candidate Experiences and The Talent Board's CandE Candidate Experience Research).
After a remote/video interview (to check tech + structure consistency)
Goal: catch preventable issues like late starts, poor audio/video, unclear agenda, and rushed Q&A.
Starter target: send within 24 hours, while candidates still remember the setup and flow. If your audience spans time zones, schedule delivery at a consistent local time.
Do this now: add the Video module (tech + pacing) to your Core block only for video-stage lists.
Cadence rule: keep video surveys short (Core + 3-5 video items). Do not stack extra open text prompts on top of tech questions.
Rejected vs advancing: keep the intro identical across outcomes. If you personalize messaging, personalize only the appreciation line (not the questions).
After high-volume interview events (to diagnose logistics fast)
Goal: identify the top operational failures (check-in, directions, wait time, room changes, schedule slips) while you can still fix the next event.
Starter target: send same day, and close collection within a short window (for example, 3-5 days) so you can act before the next cycle. Tune the window based on response patterns.
Do this now: use the Core block + Onsite logistics module, then set a single reminder at 48-72 hours (a common survey follow-up cadence; see Dillman et al.'s Tailored Design Method).
Cadence rule: one event equals one survey. If a candidate went through multiple mini-stages in the event, do not send multiple surveys.
Rejected vs advancing: send to everyone who attended. Keep wording neutral and thank them for their time regardless of the decision timeline.
Next up: pick the Core questions you will trend across every role and stage.
Interview Experience Questions to Ask (Core + Optional Modules)
Goal: collect feedback you can act on by stage without turning the survey into an essay.
Starter target: Core block = 8-10 rated items + 2 open-ended questions. Adjust length based on completion rates and hiring volume (trim open text first).
Do this now: copy the Core block below into your template, then add only the module(s) that match the interview format and role.
Privacy-safe intro (copy/paste options)
- Confidential (default): "Your feedback is confidential. We report results in aggregate and use them to improve our interview process. Please do not include sensitive personal details." (Also review your privacy and confidentiality settings before you send, and avoid collecting unnecessary identifiers; see NIST SP 800-122.)
- Anonymous (only if you can truly support it): "Your feedback is anonymous. Please avoid details that could identify you." If your pipeline is small, do not promise anonymity (re-identification risk is higher when groups are small; see the UK ICO's anonymisation guidance).
- Follow-up permission (optional): "If you want us to follow up, you can opt in at the end." (Keep the opt-in separate from the feedback questions.)
Core block (stable across roles and stages)
"Scheduling and coordination were smooth."
Why it matters: Scheduling is often the first friction point candidates experience. This item tells you if your process breaks before the interview even starts.
When to use: Include in every run. Trend it by stage to see where coordination fails.
"I received clear communication about timing and next steps."
Why it matters: Uncertainty drives negative feedback and repeat follow-ups to recruiters. Clear next steps reduce inbound load and drop-off.
When to use: Include in every stage survey. Use it as a primary driver when you prioritize fixes.
"The interview started on time and followed a clear structure."
Why it matters: Late starts and unclear agendas signal poor coordination. Structure also improves consistency across interviewers.
When to use: Use after any live interview (phone, video, onsite, panel).
"The interviewer(s) treated me with respect and professionalism."
Why it matters: Respect is the baseline. Drops here often point to training gaps or inconsistent interviewer expectations.
When to use: Include in every stage survey. Trend it, but use results to improve the process, not to grade individuals.
"The questions focused on my job-related skills and experience."
Why it matters: This is your fairness signal without asking about protected traits. It helps you spot interviews that drift into irrelevant territory.
When to use: Include in every run, especially for roles with multiple interviewers.
"The role and success expectations were explained clearly."
Why it matters: Poor role clarity creates mismatched expectations and later declines. This item tells you if the team is aligned on what they are hiring for.
When to use: Include in every stage survey. Compare early-stage vs late-stage scores to see if clarity improves over time.
"The assessment(s) I completed felt relevant to the role."
Why it matters: Relevance drives completion and reduces frustration, especially with take-homes and work samples.
When to use: Include whenever you use any assessment, take-home, or work sample.
"The time required for interviews and assessments was reasonable."
Why it matters: Time burden is a controllable driver of drop-off. This question helps you quantify when the process asks too much.
When to use: Include in every run. Use it to justify streamlining steps.
"Overall, I am satisfied with the interview experience."
Why it matters: This is your headline KPI. It is easy to trend and easy to explain.
When to use: Include in every stage survey, or at least at the end of each major stage.
"How likely are you to recommend interviewing with us to a friend or colleague?"
Why it matters: Recommendation intent is a simple employer-brand proxy you can track alongside the overall experience score.
When to use: Use after major stages (onsite/panel) or at process end to avoid repeating it too often.
Open-ended prompts (keep to 2 max)
- Prompt 1 (friction): "What, if anything, made this stage difficult or frustrating?"
- Prompt 2 (fix): "What is one change we could make to improve this stage for future candidates?"
Swap-in modules (add only when relevant)
- Phone screen module (2-3 items): recruiter explained role fit criteria; time for questions; next steps clarity.
- Video module (3-5 items): audio/video quality; joining instructions; pacing and breaks; contingency plan when tech failed.
- Onsite module (3-5 items): directions/check-in; schedule changes; breaks and accessibility; environment (noise, room changes).
- Panel module (3-5 items): panelists introduced roles; handoffs felt coordinated; questions were not repetitive; time was managed fairly.
- Technical role module (4-6 items): coding platform usability; expectations for take-home; fairness of time limit; relevance to day-to-day work.
- Sales role module (3-5 items): role-play mirrored real selling motion; expectations for territory/quota were clear; feedback timeline was clear.
- Leadership role module (3-5 items): stakeholder mix made sense; decision process/timeline was clear; expectations for first 90 days were discussed.
Do not ask about protected-class traits, disability/medical status, or anything that could be interpreted as preemployment medical screening. Keep questions behavior-based (clarity, respect, consistency), and use a separate reporting route for serious concerns (see the EEOC's guidance on disability-related questions and medical exams).
Escalation route (optional, not a promise of anonymity)
- Item (Yes/No): "Do you want someone from our team to follow up about an issue from this interview stage?"
- If Yes: show an opt-in contact field or direct them to your official reporting channel. Do not promise anonymity if you plan to follow up.
Next up: set your send windows, reminders, and fatigue controls so candidates actually finish the survey.
Deployment Checklist in SuperSurvey (Timing, Reminders, and Fatigue Controls)
-
Start with starter deployment targets (then tune): Goal: get comparable feedback by stage. Starter targets: send within 24 hours, Core block only, 1 reminder max. Do this now: duplicate your template into stage versions (or use logic) so each stage gets the same Core + the one relevant module. Review completion and opt-out rates after 2-4 weeks and adjust.
-
Build audience lists by stage completion: Trigger sends from ATS milestones (screen completed, video completed, onsite completed). Keep the list definition simple so you can audit who gets invited.
-
Use a short invitation window: Starter target: send the invite the same day or within 24 hours, then close collection after a short window (for example, 3-5 days). Fresh recall beats late, vague feedback.
-
Cap reminders: Starter target: 1 reminder at 48-72 hours to non-completers (a common follow-up cadence; see Dillman et al.'s Tailored Design Method). If you need higher volume, increase invites (more stages) before you increase reminders.
-
Control fatigue with modules: Keep the Core block stable. Add modules only when a candidate experienced that format (video/onsite/panel) or role step (assessment). Remove modules for early stages.
-
High-volume hiring defaults: Use fewer open text boxes, keep pages short, and test on mobile. If you run hiring events, send one event survey (not one per mini-interview).
-
Small candidate pool guardrail: Avoid collecting identifying details in the survey itself, and report only aggregated results. If a segment has very few responses, roll it up to a higher level (stage, role family) before sharing.
-
Invitation email (copy/paste): Subject: "Quick feedback on your interview". Body: "Thanks for taking the time to interview with us. This short survey (about 3-5 minutes for most people, depending on the stage) helps us improve our process. Your feedback is confidential and reported in aggregate." Keep wording neutral and consistent with AAPOR survey best practices (clear purpose, short length, and transparent use).
-
Thank-you page (copy/paste): "Thank you. We review feedback monthly and use patterns to improve scheduling, communication, and interview structure. This survey does not affect hiring decisions." Use the same version for rejected and advancing candidates, then personalize only the closing line if needed.
-
Boost completion without biasing results: Keep the subject line neutral, keep the survey short, and send at a consistent time. Do not chase response rate alone; nonresponse bias does not track perfectly with response rate (see Groves and Peytcheva's meta-analysis on nonresponse rates and nonresponse bias).
Results Guide: KPIs, Segments, and an Action Plan Workflow
-
Define your KPI set (keep it small)
Goal: turn feedback into a short list of fixes you can ship.
Starter target: track 1 headline score + 4-5 drivers.
Do this now: create a dashboard with these scores: Overall experience, Communication, Interviewer professionalism, Role clarity, Assessment relevance, and (if applicable) Tech experience.
- Overall interview experience score: mean or top-2 box on "Overall, I am satisfied..."
- Driver scores: average the related items (for example, Communication = comms + next steps).
- Stage scores: report the same KPIs by stage so you can see where friction starts.
-
Segment safely (so you get insight without exposing individuals)
Default segments: stage, role family, location, recruitment channel, and panel type.
Do this now: set a minimum reporting threshold and follow your sample size guidance before you publish cuts by interviewer team or niche role.
Small counts rule: if a segment is small, roll it up (for example, from team to department) or delay reporting until you have enough responses. Small-group reporting increases re-identification risk (see the UK ICO's anonymisation guidance).
-
Find the 2-3 biggest drivers (then stop digging)
Default: start with volume + gap.
- Volume: which stage has the most responses (and therefore the most affected candidates)?
- Gap: which driver score is lowest or falling fastest?
Use the pattern to improve the process. Do not use this survey to evaluate individual interviewers.
-
Run a monthly review and pick top fixes
Default cadence: monthly review with TA + HR ops + a hiring manager rep.
Do this now: bring the dashboard and verbatim themes, then choose the top 3 issues by impact (score drop) and volume (responses).
Candidate experience research (including The Talent Board's CandE Candidate Experience Research) reinforces a simple point: candidates notice broken communication and unclear steps. Fix the basics first.
-
Assign owners, due dates, and a concrete change
Default: every issue gets one owner and one due date.
- Issue: "Video interviews start late"
- Fix: update calendar buffers + add a 3-minute tech check script
- Owner: Recruiting ops
- Due date: end of month
Document the change in the same place you track scores so you can explain trend shifts later.
-
Re-measure after rollout (and keep the Core block stable)
Default: re-check next month using the same Core items and the same stage strategy.
Do this now: add a simple "change log" note to your dashboard for each rollout so you can tie improvements to actions.
Next up: lock in a few design choices (anonymity vs confidentiality, scale, and stage strategy) that affect candor.
Design Choices That Change Candor (Anonymous vs Confidential, Scale, and Stage Strategy)
| Decision | Use when | Watch outs | Default recommendation |
|---|---|---|---|
| Anonymous vs confidential collection |
Anonymous: you only need aggregate signals and you can truly avoid collecting identifiers. Confidential: you may need follow-up, or you run small pipelines. |
Anonymous risk: in small pipelines, candidates (and teams) can still guess who said what based on timing, role, or stage. Confidential risk: candor can drop if you do not explain who sees results and how you report them. |
Default: confidential collection + aggregate reporting thresholds. Only promise anonymity if you can support it end-to-end. |
| 5-point vs 7-point rating scale |
5-point: you want speed, mobile completion, and easy reporting. 7-point: you need more sensitivity and you have engaged audiences. |
Scale risk: unlabeled scales create noise. If you change scale length mid-year, you break trending. | Default: a fully labeled 5-point Likert scale (Strongly disagree, Disagree, Neutral, Agree, Strongly agree). |
| Stage micro-surveys vs one end-of-process survey |
Micro-surveys: you want precise diagnosis by stage and faster fixes. End-of-process: you can only send once, or your volume is too low to segment by stage. |
Micro-survey risk: fatigue if you repeat too many items too often. End-of-process risk: blurred recall and no visibility into where problems start. |
Default: stable Core by stage + small, relevant modules; cap reminders to prevent over-surveying. |
Source notes: For practical fieldwork cadence (timing and reminders), see Dillman et al.'s Tailored Design Method. For privacy and re-identification considerations when reporting small groups, see the UK ICO's anonymisation guidance.
Frequently Asked Questions
How soon after an interview should we send the survey?
Use same-day or within-24-hours as a starter target after the stage ends so details are fresh, then tune based on your completion baseline and candidate time zones. If you send reminders, keep it light (often 1 reminder at 48-72 hours) and close collection after a short window (for example, 3-5 days). Keep the Core block every stage and add optional modules only when they apply.
Should the interview experience survey be anonymous?
Use confidential collection as your default because true anonymity is hard to guarantee in small pipelines. If you do offer anonymity, do not collect identifiers and avoid breaking results into tiny segments where people could be inferred. In either case, tell candidates who can see results and report only aggregated scores.
How long should the survey be for good completion rates?
Start with a short, stable core (about 8-10 rated items plus 1-2 open text prompts), then add short modules (2-6 items) only for the interview format or role step the candidate experienced. If you need to shorten, trim open text first and keep your Core ratings stable for trending. Review completion rates after a few weeks and adjust length and modules accordingly.
What should we avoid asking candidates in interview feedback surveys?
Do not ask about protected-class attributes, disability/medical topics, or anything that sounds like screening. Avoid leading or accusatory wording, and do not imply the survey will affect hiring decisions. Ask about observable process behaviors (clarity, respect, time burden) and offer a separate route for serious misconduct reports.
How do we turn interview feedback into actual process improvements?
Run a monthly review of a small dashboard: overall experience plus key drivers like communication, interviewers, role clarity, assessment relevance, and tech. Segment by stage to find where issues start, then pick the top 3 issues by volume and impact, assign an owner and due date, ship the change, and re-measure next month. Use patterns to improve the process, not to manage individual performance.
Can we use this survey for rejected candidates too?
Yes. Send the same Core questions so results stay comparable across outcomes, and keep the message respectful and optional. Adjust only the thank-you text so it does not imply an outcome or invite candidates to argue the decision.
Related Survey Templates
FREE TO START - NO CREDIT CARD REQUIRED