Ask candidates about a bad hiring experience and almost none say "they rejected me". They say nobody replied, the process dragged, or they never found out what happened.
- ›The four complaints that dominate
- ›Fixes that cost nothing
- ›Why it matters commercially
- ›Measuring it
The four complaints
Silence. Applied and heard nothing, ever. The most common and most damaging, because it costs the company nothing to fix.
Unexplained delays. Told they would hear in a week, heard in four, with no update in between. The waiting is tolerable; the not knowing is not.
Disrespect for their time. Interviews rescheduled repeatedly, interviewers who clearly had not read anything, take-home exercises measured in days.
No closure. Reaching a final stage and getting a template rejection or nothing at all.
Fixes that cost nothing
Acknowledge every application. Automated, immediate, honest about what happens next and when.
Reject promptly and clearly. A prompt rejection is a kindness. A candidate waiting three weeks for a no is worse off than one who heard in three days.
Set expectations and then meet them. If a stage takes two weeks, say two weeks. If it slips, send an update before the deadline passes rather than after.
Prepare your interviewers. An interviewer who has read the application signals respect more than any perk described in the process.
Give real feedback at final stages. Not for everyone, but for candidates who invested in a final round, a specific reason is owed.
Why it matters commercially
Candidates are customers, particularly in consumer and SMB markets. A bad process reaches people who buy from you.
They talk. Publicly, on review sites, and privately in the professional networks where your next candidates live.
Silver medalists are your best future pipeline. The candidate who came second is worth staying warm with, and that only works if they left with a good impression.
Acceptance rates follow experience. Strong candidates in multiple processes choose partly on how they were treated.
Important: Automating acknowledgements and rejections is fine and expected. Automating the final-stage rejection for someone who did four interviews is not, and it is the version candidates remember and mention by name.
Measuring it
- ›Candidate NPS, asked at the end of the process regardless of outcome.
- ›Time to first response after application.
- ›Time from final interview to decision communicated.
- ›Percentage of applicants who received any response. Most companies are worse on this than they believe.
Detractor responses are worth reading individually. They name specific fixable failures more often than any aggregate metric.
FAQ
Do we have to respond to every applicant?
Yes. An automated acknowledgement and an eventual outcome is the floor, and it is achievable at any volume.
How much feedback should we give?
Specific for final-stage candidates, general for earlier stages. Legal considerations vary by jurisdiction, so keep it about the role requirements.
What about candidates in long pipelines?
Update them on a schedule even when nothing has changed. "Still in process, next update by the 15th" is enough.
Brainis Hiring OS includes a candidate portal, stall detection, and candidate NPS with detractor signals. See Hiring OS.
Sharing insights on business operations, AI, and modern team management.
Run your company on Brainis
All 11 Operating Systems on every plan, from $29 a month. No per-seat pricing — you pay for AI capacity, not headcount.
See pricing