Rejection in a job search is almost entirely information-free. You get a template email, or nothing at all, and you are left to guess whether you were close, wildly off, or eliminated for a reason that had nothing to do with you.
Feedback closes that loop. It is also harder to get than most advice admits, for reasons that are structural rather than rude — and knowing why makes the difference between asking in a way that works and asking in a way that guarantees a non-answer.
What actually works
- Ask the hiring manager or the recruiter you spoke to, not a generic address
- Ask within a day or two, while you are still a specific person to them
- Ask one narrow question, not “why didn’t I get it?”
- Expect a reply after a late-stage interview; expect nothing after an application
Why so little feedback is given
It is worth understanding the reasons, because they tell you exactly when asking is worth your time.
- Legal caution. Many employers have policies restricting detailed feedback, because a specific reason can become evidence in a discrimination claim. HR departments frequently instruct managers to say nothing beyond “we went with another candidate.”
- Volume. A role with 400 applicants cannot generate 399 personalised responses. Nobody reviewed most of them individually in the first place.
- There often is no reason of the kind you want. Late-stage decisions are frequently a marginal preference between two acceptable people. “The other candidate had done the exact thing before” is the honest answer and feels like no answer.
- Awkwardness. Telling someone their answers were vague is uncomfortable, and most people avoid it.
The practical implication: the further you got, the more likely you are to get something useful. Asking after an automated application rejection is close to pointless. Asking after a final-stage interview with a hiring manager who spent an hour with you is reasonable and often works.
How to ask
Three things determine whether you get a real answer: who you ask, how quickly, and how narrow the question is.
Ask a specific person
The hiring manager, or the recruiter who ran your process. Reply directly to the rejection email if a person sent it. A message to careers@ will not be answered.
Ask quickly
Within 24 to 48 hours. After a week you are one of many candidates in their memory; immediately after the decision, you are still a specific conversation.
Ask one narrow question
“Why didn’t I get the job?” is broad, sounds like a challenge, and invites the safe non-answer. A narrow, forward-looking question is much easier to answer honestly because it does not sound like an appeal.
“Thank you for letting me know — I appreciate you telling me directly rather than leaving it.
If you have a moment, I would find one thing useful: was there a specific gap between what I brought and what the role needed? I am not asking you to reconsider — I would just rather know what to work on than guess.
Either way, thank you for the process. I enjoyed the conversation about the reporting pack.”
Note what that does. It thanks them, explicitly removes any suggestion of appeal, asks one question, and gives them a graceful exit if they cannot answer. That combination gets replies at a far higher rate than a bare request for feedback.
“Thanks for the update. Since you were closer to the decision than I was — was it experience, level, or the salary expectation? Knowing which would help me target the next ones better.”
Offering categories is a useful technique. Choosing between three options is much easier than composing an assessment, and people who would not write a paragraph will happily reply “level, mostly.”
Ask on a call if one is offered
People say things on the phone they will not put in writing, for the legal reasons above. If a recruiter offers to talk it through, take the call.
What to do with what you get
Separate the actionable from the structural
- “The other candidate had direct experience of X.” Structural for this application; actionable over time if X keeps recurring across rejections.
- “Your examples were a bit general.” Directly actionable. Prepare specific stories with numbers.
- “We were concerned about the step up in scope.” Actionable — you need evidence of operating at that level, or you are applying one level too high.
- “It was a very strong field.” Usually genuine and not actionable. Do not read failure into it.
- “We decided to promote internally / pause the role.” Nothing to do with you at all, and more common than candidates realise.
Look for patterns, not single data points
One piece of feedback is one person’s impression on one day. Three rejections that all mention the same gap is a pattern worth acting on. Restructuring your entire approach after a single comment usually overcorrects.
Do not argue
If the feedback seems unfair or based on a misunderstanding, resist correcting it. You will not change the decision, and you will convert a person willing to help into one who regrets replying. One exception: a factual error about your background is worth a single neutral correction — “For what it is worth, I did lead that project rather than support it — possibly I did not explain it clearly” — framed as your own failure to communicate.
Feedback you can get without asking
Employers are the least reliable source of feedback available. Better sources exist:
- Your own notes. Writing down every question you were asked, and which answers you fumbled, produces more usable information than any rejection email. You know when an answer went badly.
- A mock interview. Someone in your field asking you real questions and telling you honestly how the answers landed. Thirty minutes of this is worth more than ten polite rejection replies.
- Recording yourself. Uncomfortable and effective. Answer three questions on camera and watch it back — you will identify the rambling and the vagueness immediately.
- Funnel data. Where applications stop tells you what is wrong: no responses means documents or targeting; interviews that never progress means interview performance; finals that do not convert usually means level or a marginal preference.
The single most useful thing you can do after an interview costs nothing: write down every question you were asked, and mark the ones you answered badly, within an hour while it is fresh. Across a search, that list becomes both an accurate prediction of the next interview and a precise list of what to practise.
Staying on good terms
A rejection at final stage means you were credible enough to be considered seriously. That is a relationship worth keeping.
- Reply warmly to the rejection, whether or not you got feedback.
- Keep the hiring manager’s name in your tracker.
- Where the process was genuinely good, say so — people hear this rarely.
- Roles reopen. The person hired sometimes leaves in four months, and the runner-up who behaved well is the obvious call.
“Thanks for letting me know, and for how straightforward the process was — that is not universal. If something similar opens up, I would be glad to hear from you.”
When you get nothing
Most of the time you will get nothing, and that is the normal case rather than a slight. Ask once, do not chase, and move on. The absence of a reply carries no information about your candidacy, and reading it as a verdict is a common and entirely avoidable source of damage during a long search.
Common questions
Is it unprofessional to ask for feedback?
No — it is normal and generally well received when asked once, briefly, and without any suggestion of appeal. What reads badly is repeated chasing or arguing with the answer.
Should I ask after an automated rejection?
Generally not worth the time. Nobody reviewed it individually, so there is no feedback to give. Save the effort for rejections after an interview with a person.
What if the feedback contradicts what another employer told me?
That is normal, and it is why patterns matter more than single responses. Different employers weight different things, and the same answer can read as thorough to one and long-winded to another.
Can I ask what the successful candidate had that I did not?
You can, phrased carefully — “was there something specific the successful candidate brought that I should be building?” Many employers will not answer for confidentiality reasons, but it is a fair question and occasionally produces the most useful answer available.
Should I ask to be considered for future roles?
Yes, in one sentence at the end of your reply. It costs nothing and it means your name is attached to a positive last interaction rather than a rejection.
