What to Write After a Rejection
Almost nobody replies to a rejection, which is what makes replying worth doing. Three or four sentences, sent within a day, and you become the small number of candidates the reader remembers positively for a reason unrelated to the role.
The message is not an appeal. It’s a short, unresentful note that leaves a door where there wasn’t one, and occasionally it produces feedback, a referral, or the next opening before it’s advertised.
When it’s worth sending
Always worth it: after any stage where you spoke to a human, especially a hiring manager or a panel. After a rejection from a team you’d apply to again. After a late-stage no.
Optional: after a first-round screen with an agency recruiter. Fine to send, low return.
Skip it: an automated rejection from a portal with no name attached. There’s nobody to reply to, and a message into a no-reply address is a note to yourself.
The dividing line is whether a person made the decision and whether you know who they are.
The message
Short. Genuinely short — under a hundred words, no argument, no restatement of your case.
Hi Priya,
Thanks for letting me know, and for the time last week. Disappointing, but I appreciate the straight answer rather than silence.
If it’s easy and you’re willing, I’d find it useful to know what tipped it — no obligation at all, and I understand if you can’t say. Either way, the conversation about the regional reporting was the most interesting one I’ve had in this search, and I’d be glad to hear about anything similar on your team later on.
Best of luck with the hire.
Sam
Four short paragraphs, about 95 words. It thanks, asks once with an explicit out, gives a specific reason the interaction mattered, and closes warmly. Nothing in it is asking to be reconsidered.
The feedback ask, done properly
Feedback is the thing people most want and most often ask for badly.
Ask once, with a clear out. If it’s easy and you’re willing does the work. A request that assumes an answer puts the reader in an awkward position, and awkwardness produces boilerplate.
Ask something answerable. “Any feedback?” is a big open question and typically returns “we went with a candidate whose experience was closer to the role,” which is a form of nothing. Narrower questions get real answers:
- Was it the missing sector experience, or something in the interview?
- If I applied for something similar in a year, what would you want to see that wasn’t there?
Accept that you may get nothing. Many employers have a policy against detailed feedback, for reasons involving legal exposure rather than unkindness. A non-answer isn’t a slight, and pressing for more converts a good impression into a bad one instantly.
Believe what you’re told, once. If someone gives you a real reason, don’t argue with it. The reply to feedback is “that’s useful, thank you” — full stop. Rebutting it is the single fastest way to confirm the decision was right.
What never to include
A renewed pitch. I still believe I’d be an excellent fit and would welcome the chance to discuss further. The decision is made. Re-arguing it reads as not hearing no, and it burns the goodwill the message was supposed to build.
A correction. Even if you’re sure they misread something on your resume, a rejection reply is the wrong place. Rarely does it reopen anything, and it always reads as aggrieved.
Any hint of resentment. Including the passive kind — I appreciate you eventually getting back to me — which is louder than people think. If you’re angry, write the message tomorrow.
A request to be kept in mind for “anything at all.” Too vague to act on. Name the kind of work: anything in regulated reporting, anything on the platform side.
A LinkedIn connection request in place of a reply. Send the message. Connect later, if at all.
The two things this occasionally produces
An honest reason. Sometimes genuinely valuable — the gap you didn’t know was visible, the answer that landed badly, the fact that they hired internally and the process was always a formality. That last one is worth knowing because it recalibrates how you read the whole experience.
The next role. This is the real reason to send it. A hiring process usually produces one hire and several people the team liked, and teams hire again. Being the candidate who replied gracefully is a small, cheap advantage the next time a role opens, and it sometimes arrives as a direct message rather than a posting — which is a much better position than the queue.
Neither is guaranteed and neither should be the framing of the message. A note sent transparently in the hope of a future role reads as transactional. Send it because it’s the decent thing and it takes two minutes.
If a future opening does surface this way, the ask is a small one and the same rules apply as to any small ask — see how to ask someone for a referral, where the whole skill is matching the size of the request to the strength of the relationship.
The silent rejection
Different case: no answer at all, ever. Nothing to reply to.
At that point the useful move isn’t a rejection reply, it’s a single short follow-up, and once that’s gone unanswered the search moves on. Chasing silence past one message is spending your attention where there’s no evidence anyone is on the other end. The mechanics of that one message are a matter of timing and channel rather than writing craft.
What it’s actually for
Applications mostly disappear into systems. The few interactions where you spoke to a person are the only durable relationships a job search produces, and a rejection is the moment those relationships either end or don’t.
Three sentences decide which. That’s an unusually good return for the effort, and it’s the same underlying logic as cold outreach: the highest-leverage messages in a search are the short ones nobody else bothers to send.