Constructive candidate feedback should help a person understand the hiring decision without turning the message into a personal critique. I keep it specific, tied to the role, and limited to information the company is comfortable sharing.
Start with the job requirement
Before writing feedback, I identify the requirement that was not demonstrated strongly enough. “The interview did not go well” is not useful. “The role requires independent ownership of customer escalations, and the example did not show how the candidate made decisions without close direction” gives the message a job-related focus.
I use evidence from the interview and avoid conclusions about character. The difference matters:
- Vague: “You were not confident.”
- Specific: “The answer did not explain how you would present the recommendation to a skeptical stakeholder.”
- Vague: “You lacked leadership.”
- Specific: “We needed an example of setting direction for a team during competing priorities, and the examples discussed focused on individual delivery.”
A respectful feedback pattern
I usually write four short parts:
- Thank the candidate for the time and preparation.
- State the decision or current status clearly.
- Name the relevant strength or gap with evidence.
- Close with an appropriate next step or appreciation.
For example:
“Thank you for speaking with us about the [Role] position. We have decided not to move forward. Your experience with [relevant strength] came through clearly. For this opening, we needed deeper evidence of [role requirement], particularly how you would [specific behavior]. I appreciate the time you invested in the process.”
This structure does not promise that improving one area would lead to a future offer. It explains the decision without implying that the candidate's overall career or ability has been judged.
Examples of constructive language
Too little detail in a technical answer
“Your proposed solution addressed the main user need. We needed more detail about testing, monitoring, and how you would handle failure after launch. That gap influenced our decision for this role.”
Limited evidence of prioritization
“The role involves choosing between several urgent requests. Your examples showed strong execution, but they did not give us enough evidence of how you set priorities when stakeholders want different outcomes.”
Experience did not match the current scope
“Your background is relevant to the function. We selected candidates whose recent work more closely matched the scale and complexity of the position's current responsibilities.”
Risks to avoid
I do not comment on personality, appearance, accent, age, family situation, health, or protected characteristics. I avoid “culture fit” unless the company has a defined, job-related competency and can describe observable behavior. I also avoid sharing interviewer disagreements, rankings, or details about another candidate.
If the organization has a policy limiting individualized feedback, I follow it. I do not improvise legal conclusions in an email. When the message includes sensitive circumstances or a disputed decision, I ask the appropriate HR or legal partner to review it.
Constructive feedback is most useful when it is honest and bounded. I can acknowledge what the candidate did well, explain the role-related reason for the decision, and communicate respectfully without presenting a speculative coaching session as a promise of future consideration.