The rejection email arrives, two polite lines long, and it tells you nothing about why. Asking for feedback is reasonable. It is also a request most employers answer thinly or not at all, and knowing the reasons changes how you ask and how much weight you put on whatever comes back.
Why employers say so little
Start with the part nobody likes: you are not owed an answer, and the people who could give one have reasons to hold back.
- Legal caution. Many companies tell hiring teams to keep rejection reasons generic. A specific remark, written down, can be quoted later in a complaint, so the safe policy is to say nothing specific to anyone.
- Volume. A recruiter closing one role may be turning down several finalists and a few hundred applicants in the same week. Individual notes do not fit in that week.
- Awkwardness. Telling a stranger that their answers rambled is uncomfortable, and there is no reward for doing it well.
- Distance. The recruiter who writes to you often did not sit in the room. They are passing on a decision, sometimes from a one-line summary.
That last point matters more than candidates assume. Detailed notes do exist: interviewers usually fill in a scorecard after you leave, and that is where the real feedback lives. What reaches you, when anything does, is a softened summary of a summary.
Who to ask: the recruiter or the interviewer
Ask the person who told you no. In most processes that is the recruiter or the HR contact, and going around them to the hiring manager reads as refusing the channel you were given.
One exception: if the hiring manager delivered the rejection personally, reply to them.
An external agency recruiter is a different case, and often the best source. They are paid when a candidate lands, they may put you forward again next month, and they have probably already heard the client's reasons on the phone. They tend to be blunter than anyone in-house. Use that.
What about a LinkedIn message, a week later, to the interviewer you got on well with? I would skip it. You force them to choose between ignoring you and going off script, and neither helps you with that employer.
Timing, and the thank-you that comes first
Reply within a day or two of the rejection. Wait longer and the recruiter has moved to the next role, the panel has forgotten which candidate said what, and the notes are filed.
The order inside the message matters: thank them, accept the decision plainly, then ask. The acceptance is what makes the request safe to answer. A recruiter who senses that a reply will open a negotiation will not reply.
One question they can answer in two lines
Another article on this blog, about rejections that come with a promise to stay in touch, already makes the point that a general "any feedback?" gets fog. Take that as given and go one step further: what does a good specific question look like?
It is narrow enough to answer in two sentences. It concerns something you can change. And it lets the person reply without criticising you head-on.
Compare these:
- "Do you have any feedback for me?" asks them to write an assessment from scratch.
- "Was there one area where the person you chose was clearly stronger?" asks for a comparison, which is easier to give than a verdict.
- "If I applied for a similar role in a year, what would you want to see more of?" points forward, and forward is comfortable.
- "I felt the case study was my weakest part. Is that how it looked from your side?" gives them something to confirm or correct. This is the easiest of all to answer, because you have said the hard part for them.
Pick one. Two questions halve your chances; a list of five ends them.
A request email you can adapt
Subject: Thank you, and one question
Hello Ms Okafor,
Thank you for letting me know, and for the time the team gave me across both rounds. I am disappointed, but I understand the decision and I am not asking you to revisit it.
One question, if you are able to answer it: was there a single area where the candidate you selected was noticeably stronger than me? Even one line would help me prepare for similar roles.
If it is not something you can share, no problem at all. I enjoyed meeting the team and wish you well with the hire.
Kind regards,
Dana Whitlock
Notice what is missing: no restating of your strengths, no "I was surprised", no request for a meeting.
Email or a short call
Email first, nearly always. It lets the recruiter answer when they have a minute and check what they are allowed to say.
A call is worth it in two situations: the recruiter offers one, or they are an agency recruiter you already speak to. People say on the phone what they will not put in writing, which is the legal caution from earlier working in your favour for once. If you get a call, keep it to ten minutes, ask your one question, then stop talking and take notes. Silence does more work than a second question.
Reading vague and coded answers
Most replies that do arrive are polite and thin. A few common ones, and what they can and cannot tell you:
- "We went with someone with more experience." Sometimes literally true. Often it means another candidate had already done this exact job in this exact sector, and you would have had to learn part of it. It rarely means you were unqualified, since you reached the interview.
- "We felt the fit wasn't quite right." The emptiest of the set. It can cover anything from team dynamics to salary expectations. Count it as a non-answer.
- "We'd have liked more concrete examples." This one is real. Nobody invents a specific criticism to be polite. If you hear something this precise, write it down word for word.
A rule of thumb: the more specific and slightly uncomfortable the remark, the more likely it reflects what was said in the debrief.
Never argue, never re-pitch
Whatever comes back, your reply is two lines of thanks. That is all.
Do not explain that you do have the experience they mentioned. Do not send the portfolio piece you forgot to bring. Do not ask them to reconsider. The decision is closed, and every recruiter remembers a candidate who turned feedback into a debate, which is one more reason the next candidate gets nothing.
As a last resort, some jurisdictions (the GDPR in Europe, for example) may let you request the personal data an employer holds about you, interview notes sometimes included, but the rules and exceptions vary, the route is slow and rarely friendly, and none of this is legal advice.
What to do with what you get
One remark from one employer is an anecdote. It reflects one panel, one role, one afternoon. Rebuilding your whole approach around it is a mistake.
Keep a simple log instead: date, role, stage reached, and the exact words of any feedback, or your own honest guess when you got none. After four or five rejections, read it in one sitting. If "more concrete examples" shows up twice, or you keep going out at the same stage, that is a pattern, and a pattern is worth acting on. Going out before the interview usually points at the CV, which is where a tool like Postulit, which turns a LinkedIn profile into a CV tailored to each role, earns its place. Going out in the final round points at how you interview.
And if you get nothing? That is the normal outcome, not a verdict on your manners or your candidacy. Getting over the rejection itself is a separate subject, handled in our piece on job rejection.
Ask once, ask one answerable question, say thank you whatever happens, and judge yourself on the pattern across several rejections, never on one sentence from one employer.
So the next time a no arrives: sleep on it, send the short email above with your own question in it, log whatever comes back, and return to your applications. Do not send a reminder.