Updated October 20, 2026
TL;DR: Write internal feedback immediately after the call while the evidence is fresh, and map every rating to scorecard competencies with specific examples, not impressions. Candidate-facing feedback must be job-related, compliant, and sent within 24 to 72 hours of the interview. Capturing interview evidence during the call reduces recall bias, so your debrief runs on shared evidence rather than competing memories.
When interviewers submit scorecards three hours after the call, the feedback driving your debrief reflects what they remembered, not what the candidate actually said. Vague interview feedback stalls debriefs, frustrates recruiters, and exposes the company to legal risk.
Interview feedback splits into two kinds that require different handling: internal interviewer feedback for the hiring team and candidate-facing feedback. For each, you’ll find good and bad written examples, a simple template, and guidance on what to share, what to avoid legally, and when to send it.
Why high-quality feedback drives better hiring
Poor feedback creates two immediate problems: the debrief has nothing concrete to work from, and your sourcing team gets no signal to recalibrate. A gut-reaction scorecard gives you no evidence to push back on a hiring manager’s changing requirements or to explain why a candidate stalled.
Keep feedback fair and defensible
Subjective feedback creates legal exposure, whether it sits in an internal scorecard or goes out to the candidate. Federal law protects applicants from discrimination based on race, color, religion, sex (including pregnancy, sexual orientation, and transgender status), national origin, age (40 or older), disability, and genetic information, according to the EEOC. Separate federal laws also bar hiring discrimination based on citizenship status and military service.
Documentation that references protected characteristics, even accidentally, becomes discoverable evidence. Structured feedback tied to job-related competencies, with documented evidence behind every rating, keeps your process defensible.
How to write interview feedback for your hiring team
Internal feedback is a documentation discipline, not an essay. The goal is to give the debrief a shared evidence base so the team can compare candidates against the same criteria.
Record feedback while the call is warm
Write your feedback as soon as the interview ends, while the candidate’s exact phrasing is still fresh and before other interviewers’ opinions can influence you. Scorecards filled in two days later turn into memory tests, and recall drifts back toward gut feel. BrightHire takes most of the time pressure off: when the call ends, it pushes an AI-generated scorecard into your ATS, drafted from what the candidate actually said. Your job is to review it, check the evidence against your own read of the conversation, and submit.
If you’re working without it and can’t complete the full scorecard right away, jot down one sentence of evidence for each competency, such as a specific example or quote from the candidate. Then come back within the hour and use those notes to write the full scorecard.
Map feedback to scorecard competencies
Every rating must tie to a predefined competency from your interview scorecard template, and every score needs evidence behind it. The rule is simple: no evidence, no score. This keeps vague feedback out of the debrief.
Use specific evidence, not impressions
Name the behavior and the skill it shows: “Walked through three ways to cut query latency and chose one based on read-heavy traffic.” Specific evidence also tells the next interviewer where to dig. When you write “hasn’t run Kafka in production, but described debugging a consumer lag issue in detail,” the next interviewer knows exactly what to probe.
Write fair and neutral notes
Describe what the candidate said and did, not how you felt about them. Evidence notes should capture observable actions, such as “Described how they resolved a launch-date conflict between product and engineering,” in place of “easy to work with.” Neutral language keeps the focus on job-related qualifications and reduces bias risk.
See the difference: strong vs. weak evaluations
Each row below shows the same interview written up two ways.
| Criterion | Weak | Strong |
|---|---|---|
| Specificity | “Seemed smart” | “Solved the system design problem using a distributed caching approach” |
| Evidence | “Good culture fit” | “Referenced three examples of cross-team collaboration aligned with our transparency value” |
| Rating | “Thumbs up” | “Technical: 4/5, Communication: 3/5, Problem-solving: 5/5” |
How to provide verifiable interview notes
A complete note records the question, the candidate’s answer, the competency, and the score with its evidence: “Asked to design a rate-limiting system for our API. Candidate proposed a token bucket algorithm, explained why a sliding window approach would be more accurate but more complex, and coded a working solution. Mapped to System Design competency: 4/5. Evidence: clear explanation of tradeoffs, working code, asked clarifying questions about scale requirements.”
How to write behavioral evaluations
Use the STAR method (Situation, Task, Action, Result) to structure behavioral evidence. “When asked about handling conflict, candidate described a specific situation where two engineers disagreed on architecture (Situation), her role as tech lead mediating (Task), how she facilitated a decision meeting with written criteria (Action), and the project shipped on time with both engineers satisfied (Result).” This gives the debrief concrete evidence to evaluate against the Leadership competency.
Interview feedback template for hiring teams
A standardized template means every interviewer fills in the same fields, in the same order.
Standardize your interview feedback template
Your template should include these fields:
- Role, level, and hiring stage, for context.
- Three to five competencies with weighted importance, defined in the intake meeting.
- Behavioral rating anchors that show what a 1 looks like versus a 5 for each competency. Clear anchors keep scores from inflating or drifting across interviewers.
- A required evidence field for every rating, using STAR format where it applies.
- Knockout criteria agreed before the interview, meaning the must-have requirements that rule a candidate out when they’re missing.
- An overall recommendation: strong hire, hire, no hire, or strong no hire.
- Deciding reasons, in one or two sentences that summarize the evidence.
- Up to three strengths and three concerns, each tied to a specific competency.
- What still needs probing, as guidance for the next interview stage.
“You can’t improve what you can’t standardize. For a TA leader, the goal goes beyond one great hire. The goal is a hiring system that gets smarter over time.” – Tracy St. Dic, Global Head of Talent, Zapier
Customize scorecards for each role
Technical roles need competency weighting that reflects the job. For a senior backend role, that could mean giving System Design the heaviest weight, with Fundamentals, Debugging, and Tradeoff Reasoning sharing the rest. Behavioral roles might prioritize Leadership, Collaboration, and Problem-solving. Map each question to a specific competency before the interview so evidence collection has a target.
Use scorecards to resolve hiring manager disagreements
When a hiring manager rejects candidates who match the agreed criteria, use these steps to recalibrate:
- Pull the intake meeting notes and confirm the competencies and weighting you both agreed on before interviews started.
- Compare rejection feedback to the scorecard and identify where the hiring manager’s concerns map to predefined criteria versus new requirements.
- Surface the pattern with specific examples: “Three candidates scored 4/5 on System Design but were rejected for ‘not senior enough,’ which isn’t a defined competency.”
- Ask whether the criteria need updating or whether the hiring manager is reacting to interview style rather than qualifications.
- Revise the scorecard together if the role requirements have genuinely shifted, and document the change so the next sourcing cycle has clear targets.
- Escalate to the Head of TA if the hiring manager continues rejecting on-criteria candidates without job-related justification, as this signals a breakdown in intake alignment.
What interview feedback to share with candidates
Every candidate who interviews should get an answer. Candidate-facing feedback has to be clear and respectful without creating legal exposure for the company.
What you can legally share with candidates
Share job-related gaps with specific evidence. “No hands-on experience with Salesforce administration, a must-have here. Strong on reporting” works because it names the requirement and acknowledges a strength. Limit what you share to what’s essential for judging job qualification. Never reference protected characteristics, even positively. “Great energy for someone your age” references age, which creates legal risk even when it’s meant as a compliment.
Red flags in candidate interview notes
Avoid feedback that describes personality, appearance, or cultural fit. “Not a good culture fit” without job-related evidence invites legal challenge. “Too aggressive” or “not polished enough” are subjective judgments that don’t map to qualifications.
When to send candidate feedback
Set an internal SLA to send feedback within 24 to 72 hours of the interview, and don’t let it stretch past three or four business days. Closing the loop quickly is one of the simplest ways to keep candidates engaged through the end of your process.
Give every rejected candidate a next step
Name the requirement, connect it to what the candidate showed, and point them somewhere useful: “Thank you for walking us through your onboarding redesign. This role needs someone who has owned renewal targets for a book of customers, and your examples focused on implementation rather than renewals. If you take on renewal ownership in a future role, we’d be glad to talk again.”
Candidate interview feedback examples: good vs. bad
Three common rejection scenarios, with wording to use and wording to avoid.
| Scenario | What to write | What to avoid |
|---|---|---|
| Technical gap | “Your background showed strong project coordination experience. We decided to move forward with a candidate whose recent work more closely matched the technical requirements of this role, specifically hands-on experience with our billing system.” | “Not technical enough.” |
| Role scope mismatch | “You communicated your ideas clearly, but we were looking for deeper experience with large-scale data analysis for this position. Your presentation skills are a strength.” | “Not the right fit for the role.” |
| Competitive candidate | “Thank you for interviewing for the Senior Backend role. The team was impressed with your Docker expertise and problem-solving approach. We selected a candidate with more Kubernetes production experience, which is critical for our infrastructure roadmap.” | “We went with someone better.” |
How interview recordings and AI notes improve feedback quality
Manual feedback depends on memory, discipline, and time.
Document interview evidence in real time
Everything so far applies whether or not you use dedicated interview tooling. Here’s how the same workflow runs in BrightHire: it joins every scheduled interview automatically, records and transcribes in real time, and generates structured summaries mapped to the role’s evaluation criteria. Summaries are typically ready within minutes of the interview ending, so the interviewer reviews and confirms instead of writing from scratch.
Reduce recall bias with factual interview notes
BrightHire’s AI Scorecard Auto-fill translates the transcript into a pre-populated scorecard mapped to your evaluation criteria, so ratings start from what the candidate said rather than what the interviewer recalls. As of this writing, BrightHire holds a 4.7 out of 5 rating on G2 across 182 verified reviews.
Draft interview feedback in minutes
The time savings compound across the team. Hours that used to go into writing up notes go back into candidate relationships and hiring manager alignment. BrightHire has captured more than 4 million interviews to date.
| Workflow step | Manual | With BrightHire |
|---|---|---|
| Note-taking | Interviewer types notes during call, misses details while multitasking | Automatic transcription and AI-generated summary capture full conversation |
| Scorecard completion | Interviewer writes from memory hours later | Pre-filled scorecard ready within minutes of call ending |
| Evidence capture | Relies on what interviewer remembered to document | Exact quotes and timestamps preserved in recording |
| Coaching | Manager reviews ATS notes with no visibility into actual interview | Manager reviews recording to see question quality and candidate responses |
Coach interviewers with concrete examples
Interview recordings give managers evidence to coach feedback quality. You can review past interviews and tie coaching to specific moments in the conversation instead of relying on secondhand notes. BrightHire’s Interview Insights surface per-interviewer performance patterns and compliance flags, so coaching can target specific interviewer behaviors.
Request a demo to see how BrightHire syncs with your ATS and what an AI-generated scorecard looks like in your candidate record.
FAQs
One to two sentences per competency with specific evidence, plus an overall recommendation with deciding reasons.
No US federal law requires employers to give candidates feedback. In the UK, though, candidates can request a copy of the personal information you hold about them through a subject access request, and that can include interview notes, so write every note as if the candidate may read it. The operational reason to give feedback is candidate experience: rejected candidates who get a clear answer stay engaged with your employer brand and are more willing to re-apply or refer others.
Focus on specific gaps relative to the role requirements. “Strong on X, but this role requires Y, which wasn’t demonstrated in the interview” gives the debrief evidence to weigh against other candidates and gives the recruiter signal to recalibrate sourcing.
No. Independent ratings help prevent groupthink. Each interviewer submits their scorecard before seeing others’ feedback, and the debrief then compares evidence across interviewers instead of negotiating toward consensus.
Coach with specific examples from their own interviews. Show them what a strong evidence sentence looks like versus what they submitted. If the pattern continues, use interview recordings to identify whether the problem is feedback discipline or interview technique. Persistent issues may require recalibrating the interview panel composition.
Key terms glossary
Behavioral anchors: Written descriptions of what each score level looks like for a competency, such as what a 1 versus a 5 means, so scores stay consistent across interviewers.
Evidence field: The required scorecard field where the interviewer records what the candidate said or did to support a rating.
Intake meeting: The kickoff between recruiter and hiring manager where the role requirements, competencies, and weighting are agreed before interviews start.
Knockout criteria: Must-have requirements, agreed before the interview, that rule a candidate out when they’re missing.
Protected characteristics: Attributes that federal law bars employers from using in hiring decisions, including race, color, religion, sex, national origin, age (40 or older), disability, and genetic information.
Recall bias: The drift from specific observations toward general impressions that happens when feedback is written from memory hours or days after the interview.
STAR method: A format for writing behavioral evidence by recording the Situation, Task, Action, and Result of an example the candidate describes.
Subject access request: A request, available to candidates in the UK, to receive a copy of the personal information an employer holds about them, which can include interview notes.
