Post-interview surveys serve two completely different audiences:
- Candidate-facing surveys — to measure and improve candidate experience (CX)
- Interviewer-facing scorecards — to structure hiring decisions and calibrate evaluators
These are different instruments with different goals. Trying to combine them is the most common mistake. This post walks through both, separately.
Candidate-facing surveys
What you're trying to learn
- How the end-to-end hiring process actually felt
- Whether rejected candidates would still recommend or reapply (employer brand)
- What to fix in your sourcing copy, interview prep, or feedback timeline
Sample questions
Q1. How would you rate our overall hiring process? (1–5)
Q2. How would you rate your interviewers? (1–5)
Q3. Was the role and team described clearly? (1–5)
Q4. Was the time from interview to decision reasonable? (1–5)
Q5. How well do our mission and culture resonate with you? (1–5)
Q6. What stood out positively in our process? (open text, optional)
Q7. What should we improve? (open text, optional)
Q8. Would you recommend a friend or colleague apply here? (NPS 0–10)
Q9. Would you like us to keep in touch?
○ Yes, for a different role
○ Yes, reapply in ~12 months
○ Yes, future newsletter / talent network
○ No
Send timing
- Offers extended: immediately after the offer
- Rejected candidates: the day after the rejection email (never same day)
- Candidates who withdrew: right after they pull out
Why you have to survey rejected candidates
The honest signal lives there.
- Hires are biased to be polite — they got the offer
- Rejected candidates surface the actual friction in your process
- A bad rejection experience burns brand equity in the long tail (Glassdoor, peer recommendations, future re-applications)
If you only survey hires, your CX scores will look great and your funnel will quietly bleed.
Interviewer scorecards
What you're trying to do
- Structure the decision so it's not "I just had a good feeling"
- Calibrate interviewers against each other so a "4" means roughly the same thing across the team
- Build a longitudinal dataset that can eventually be correlated with on-the-job performance
Sample scorecard
[Candidate basics]
- Name
- Role
- Interviewer
- Date / time
[Hard skills — 1–5]
Q1. Technical skill vs. role requirements
Q2. Relevant experience
Q3. Depth and accuracy of domain knowledge
[Working style — 1–5]
Q4. Communication
Q5. Structured / logical thinking
Q6. Ownership and self-direction
Q7. Curiosity and growth orientation
[Culture fit — 1–5]
Q8. Alignment with mission / values
Q9. Collaboration and teamwork
Q10. Accountability
[Overall]
Q11. Hire recommendation
○ Strong hire
○ Hire
○ No verdict
○ No hire
○ Strong no hire
Q12. Reasoning (open text — required)
Q13. Concerns or things to probe in next round (optional)
Q14. If not this role, would they fit elsewhere?
○ Yes, actively pitch them
○ Possibly
○ No
Behavioral anchors are the secret weapon
The 1–5 scale is meaningless without them. Decide ahead of time what each number actually represents.
Example: communication
- 1: Misreads questions; answers go off-topic
- 2: Handles only direct, simple questions
- 3: Handles standard back-and-forth comfortably
- 4: Structures answers clearly even on ambiguous topics
- 5: Drives the conversation, brings new angles
Write these once, share them with every interviewer, and rater drift drops sharply. This is the single highest-ROI intervention you can make on your hiring process.
Operational tips
Tip 1: Submit scorecards within 30 minutes
Memory degrades fast. The longer the gap, the more "vibes" replace specifics.
Tip 2: Submit before reading other interviewers' scores
This kills anchoring bias. Hold each interviewer's score until everyone has submitted.
Tip 3: Decide on the qualitative notes, not the average
A 4.2 average doesn't mean "hire." The concerns in the open-text fields almost always carry more signal than the numbers. Use the rubric to structure the conversation, then debate the substance.
Tip 4: Capture detail on rejections too
You'll want it for: trend analysis, defending decisions later, and considering candidates for future roles.
How to use the data
Candidate-facing data
- NPS over time — your employer brand health metric
- Low scores on "interviewer rating" by team — flag for interviewer training
- Low scores on "role clarity" — fix the JD or recruiter brief
Interviewer scorecards
- Correlate scores with on-the-job performance at 6 and 12 months — learn which dimensions actually predict success
- Per-interviewer score distributions — identify chronically harsh or generous raters and recalibrate
- Question what you're actually selecting for — the data eventually reveals which "requirements" don't predict anything
Summary
- Design candidate-facing surveys and interviewer scorecards as separate instruments — never one combined form
- Always survey rejected candidates, not just hires
- Behavioral anchors on every rated dimension — without them, scores are noise
- Continuously close the loop: correlate hiring scores with retained-employee outcomes
Repoan ships templates for engineering interviews, sales interviews, and new-grad hiring. The candidate-facing survey and the interviewer scorecard run on separate forms — as they should — and access can be scoped to HR through team workspaces. Open-text feedback flows into AI-clustered reports (details) so themes like "interviewer was unprepared" or "role description was misleading" surface automatically across hundreds of responses.