This FAQ answers the most common questions about candidate interview feedback — what to say, when to send it, how to automate it safely, and who deserves a human response. For the full system behind these answers, see the scalable feedback process guide.

Jump to a question: Who deserves feedback? · What do you say? · When do you send it? · Is automation impersonal? · What’s the legal risk? · Do you offer a call? · How do you scale it?

Who deserves interview feedback?

Every candidate who completes an interview deserves a human response.

The line sits at the interview itself. Someone filtered out by automated pre-screening before any human contact gets a clear, prompt templated rejection. But anyone who took time off, prepared, and sat across from your team earned a real reply. As one hiring manager put it, you cannot fix the automated pre-interview rejections, but you absolutely can fix the response for everyone you actually interviewed. That is the right and sustainable boundary to draw.

What do you actually say in the feedback?

One genuine strength and one specific, job-related growth area.

You are not choosing between brutal honesty and meaningless fluff — both miss. You give one true, useful, defensible observation anchored to a competency and an observed behavior. Lead with the genuine strength, then deliver the growth area in role-language: what the position required and what specifically fell short in the interview. See how to give constructive feedback for the exact method.

When do you send interview feedback?

Within two to three business days of the decision.

Finalists hear back within two business days; earlier stages within three. A thoughtful message sent weeks late still reads as an afterthought, so timing is part of the substance, not separate from it. This is what a feedback SLA formalizes — a committed deadline per stage so timely feedback becomes the default rather than something that depends on a recruiter remembering.

Does automating feedback make it impersonal?

No — not when a human approves each message.

The cold “generic AI rejection” everyone dreads is under-automated: a dumb template with no structured input behind it. Real automation drafts from the candidate’s actual scorecard data and routes to a human for approval, so the result reads as personal because a person signed off on it. The candidate cannot tell automation was involved, which is the entire point. Automation removes the friction; the human approval keeps the voice.

What is the legal risk in giving feedback?

Low, when feedback is competency-anchored and consistent.

Inconsistent, ad-hoc feedback actually carries more risk than a standardized process, because inconsistency is what discrimination claims feed on. Tie every statement to a job-related competency and an observed behavior, deliver it through approved templates, and the structure becomes your defense rather than your liability. The silence that teams choose out of legal fear is itself a risk, because uneven treatment across candidates is harder to defend than a uniform, documented process.

Should you offer a live feedback call?

Yes — to finalists only.

A calendar link in the finalist rejection lets candidates self-book a short call if they want one. Most will not, but the offer itself signals genuine respect, and the small finalist volume keeps it sustainable. Reserving live calls for finalists is what keeps the highest-touch response from overwhelming the team while still giving the highest-investment candidates the depth they earned.

How do you scale feedback across many roles?

Standardize scorecards, automate the templates and timing, and reserve personal calls for finalists.

The combination keeps per-candidate effort under a minute for most stages while preserving a human touch where it counts. Scorecards turn interviews into structured data; automation drafts and times the messages; the human approval keeps each one warm. This is the same tiered approach compared in automated vs personal feedback, and it is what lets a small team respond to every interviewed candidate without drowning.

What if a candidate replies wanting to argue the decision?

Restate the specific, documented point calmly — you are reporting an assessment, not defending an opinion.

Because every piece of feedback traces to a competency and an observed behavior, your reply is simply to reaffirm it: the role required X, and in the interview Y was observed. There is no obligation to relitigate the decision or provide an exhaustive accounting. A brief, warm reaffirmation of the one specific point is appropriate and sufficient. These replies are rare, and they are rarer still when the original feedback was specific, because specificity is visibly fair and hard to argue with.