A consumer electronics retailer runs a graduate scheme that attracts 2,400 applications for 30 places. The process has five stages. Candidates who fail the online test receive an automated email within the hour. Candidates who reach the final assessment day, having given up three days in total and travelled at their own cost, hear nothing for five weeks. Then they receive the same automated email, beginning “Dear Applicant”.
One of them posts the email on a careers forum with a description of the assessment day. The thread collects several hundred replies, many from people with similar stories. The talent team finds out when the following year’s applications fall by a fifth and a store manager mentions that a customer brought it up at the till. No one had decided to treat finalists badly. No one had decided anything. Rejection was the part of the process that belonged to nobody.
Hiring is mostly rejection. A vacancy with a hundred applicants produces one offer and ninety-nine people who are told no, or who are told nothing. Organisations put real thought into attracting those hundred people and almost none into how ninety-nine of them leave.
That is a mistake on commercial grounds alone, since rejected candidates are also customers, referrers and future applicants. But the more interesting question is psychological: why does being turned down by one employer leave some people with goodwill and others with a grievance they repeat for years? The answer has less to do with the decision than with the way it was reached and delivered.
People judge the process.
Rejected candidates who found the process relevant, respectful and honest often keep a good opinion of the employer.
Silence is the worst message.
Ghosting leaves people to supply their own explanation, and they choose the harshest one.
Match effort with effort.
The further a candidate got, the more personal and specific the rejection should be.
Why does rejection hurt so much?
Because the brain processes social exclusion with some of the same machinery it uses for physical pain. Experiments by Naomi Eisenberger, Matthew Lieberman and Kipling Williams, in which participants were left out of a simple ball-tossing game, found activity in brain regions also associated with the distress of physical pain. Being excluded is not a metaphorical hurt.
A job application raises the stakes further. The candidate has imagined the job, told family about the interview and offered a version of themselves for judgment. A rejection is easily read as a verdict on the person, not on the match between one person and one vacancy.
Silence is worse than a clear no. Without information, people fill the gap with the least flattering explanation, and they keep returning to it. Psychologists have long observed that unfinished business holds attention in a way that completed business does not. A candidate who has been told no can close the file. A candidate who has been ghosted checks their inbox for a month.
What makes a rejection feel fair?
The most useful framework comes from research on organisational justice applied to selection. Stephen Gilliland proposed in 1993 that candidates judge a hiring process on rules such as whether the tests were relevant to the job, whether they had a chance to show what they could do, whether they were treated with respect, and whether they received timely and honest information.
Applicants’ perceptions of procedural fairness predict their attitudes to the organisation, their intention to recommend it and their willingness to accept or reapply, to a degree that often matches or exceeds the effect of the outcome itself. Job-relatedness and the chance to perform are among the strongest drivers.
In other words, a rejected candidate who believes the process was relevant, respectful and honest can still think well of the employer. A candidate who was offered the job after a process they found arbitrary may accept it with reservations. This “fair process effect” appears throughout HR, and it is explored in depth in our guide to organisational justice.
Why do employers ghost candidates?
Rarely out of contempt. The usual causes are structural and psychological.
Nobody owns it. Recruiters are measured on time to hire and offers accepted. Telling people no appears on no dashboard.
Avoidance. Delivering bad news is unpleasant, and people postpone unpleasant tasks. Psychologists call the reluctance to pass on bad news the “mum effect”. The recruiter who intends to call the finalists on Friday is still intending to the following Friday.
Keeping options open. The second-choice candidate is kept waiting in case the first choice declines. This is rational for the employer and corrosive for the candidate, who can usually tell.
Fear of saying the wrong thing. Legal caution turns into saying nothing at all.
People are reluctant to deliver bad news, partly from discomfort and partly from fear of being blamed for it. The result is delay, vagueness or silence, each of which makes the news worse when it lands.
What should a rejection message say?
It depends on how far the candidate got. Effort invested by the candidate should be matched by effort from the employer.
| Stage reached | Channel | What to include |
|---|---|---|
| Application only | Email, within two weeks | Clear decision, thanks, no false encouragement |
| Screening call or test | Personal email | Decision, one line on what the shortlist had in common |
| First interview | Personal email or call | Decision, one or two specific observations, offer of brief feedback |
| Final stage | Phone call from the hiring manager | Decision first, genuine strengths, the deciding factor, whether you would like them to reapply |
Whatever the stage, four rules hold. Give the decision in the first two sentences; people skim for it and resent having to hunt. Be specific where you can. Do not offer hope you do not mean: “we’ll keep your CV on file” is heard as a promise. And send it when you said you would.
Should you give feedback, and how much?
Finalists nearly always want it, and giving it is one of the few things that reliably leaves a rejected candidate feeling respected. The risks are manageable if feedback is tied to the job criteria and to what was observed.
Good feedback is short: one thing the candidate did well, one thing that would have strengthened their case, both tied to evidence from the interview. “Your examples were strong on analysis. We were looking for more evidence of leading a team through a change, and the examples you gave were as a team member.” Bad feedback compares the person with other candidates, comments on personality, or invents a reason that sounds kinder than the true one.
Never give a reason that is not the real reason. A candidate told “we went with someone more experienced” who then sees a less experienced person in the role has grounds for suspicion, and in a discrimination claim the mismatch between the stated and the actual reason is exactly what a tribunal or court will look at. If you cannot state the reason, say less, not something false.
This is also where structured hiring pays for itself a second time. If interviewers have scored answers against criteria, as described in the case for structured interviews, feedback writes itself. If the record says “lacked spark”, there is nothing honest to say.
How do you reject an internal candidate?
With more care than an external one, because they come to work the next morning. Internal candidates should hear the decision in person, from the hiring manager, before any announcement. They should be told what would make them a stronger candidate next time, and their own manager should be briefed to follow up. The full playbook is in how to tell someone they did not get the promotion.
What is the business case?
Three effects are well documented in candidate-experience research, even if the exact figures vary by survey and sector.
Rejected candidates talk. People share bad experiences more readily than good ones, and review sites make those accounts permanent. Rejected candidates are customers. For consumer brands, the applicant pool and the customer base overlap heavily, and several large employers have estimated meaningful lost revenue from applicants who took their custom elsewhere. And rejected candidates are a talent pool. The person who came second for one role is, by your own assessment, nearly good enough to hire; treating them well is the cheapest sourcing you will ever do.
Pick one number and put a name against it: “share of interviewed candidates who received a personal decision within five working days”. What is owned and counted gets done. Everything else in this guide follows from someone being responsible for that figure.
- Every applicant gets an answer, including automated ones for early stages
- Decision time is promised at each stage and met
- Anyone interviewed gets a personal message with one specific observation
- Finalists get a call from the hiring manager
- Feedback is tied to job criteria and to what was actually observed
- Second-choice candidates are told honestly where they stand
- Someone owns the numbers
The retailer in the opening example changed two things. Finalists now receive a call within three working days, and every assessment-day candidate gets a short written summary of their scores against the published criteria. The cost was about two days of recruiter time per intake. The forum thread is still there, but the newer replies tell a different story.
Frequently asked questions
Is it better to reject candidates by phone or email?
Email is acceptable and often preferred for early stages, because it lets people absorb the news privately. Anyone who reached a final interview has earned a phone call from the hiring manager, followed by a short email confirming what was said.
How quickly should you reject a candidate?
As soon as the decision is certain, and always by the date you gave them. For early stages, within two weeks of application. After an interview, within five working days. If the decision is delayed, tell candidates so; an honest holding message is far better than silence.
Do you legally have to give feedback to rejected candidates?
In most countries there is no general duty to explain a hiring decision, though data protection law in some jurisdictions lets candidates request the notes held about them, and discrimination law everywhere makes false or inconsistent reasons risky. Check local rules. Whatever the law, honest feedback tied to job criteria is the safer practice.
What should you not say in a rejection?
Avoid comparisons with other named or described candidates, comments on personality or personal circumstances, reasons that are not the real reason, and promises about future roles that you do not intend to keep.
Discover more from Kurums | Business Intelligence
Subscribe to get the latest posts sent to your email.