Five interviews, a take home task that took 7 hours, and then a rejection of exactly two sentences. That is a common ending for a final round candidate, and it leaves an obvious question: what went wrong? The answer exists. Somewhere there are interview notes, a scorecard and a debrief where four people discussed you for 20 minutes. The only route to that information is a short email, and most candidates either skip it or write one that nobody can answer.
This guide treats the feedback request as a small problem with variables you can influence: the stage you reached, who you write to, how fast you send it and how specific the question is. It gives a 3 day timeline from rejection to sent message, templates for each interview stage, a simple formula for estimating what to expect, an illustrative case and a way to read the reply, including silence.
What decides whether anyone replies
Before writing anything, it helps to understand why so many requests go unanswered. Recruiters handle dozens of open roles, and a feedback email has no deadline attached, so it sinks below urgent work. Many companies also discourage detailed feedback because of legal caution: a careless sentence about a candidate can become evidence in a discrimination complaint. Some hiring managers simply find it uncomfortable.
Against those forces, four variables work in your favour.
Stage reached: how far you got in the process. After a 20 minute recruiter screen there is little written about you. After a final round there are scorecards from 3 to 5 interviewers, and someone already summarised them for the decision.
Relationship: whether the person you write to spent real time with you. A hiring manager who interviewed you for an hour is more likely to reply than a recruiter who scheduled your calls.
Response window: the period after the rejection during which the people involved still remember you clearly. In practice it is about one week, and the first 48 hours are the strongest part of it.
Answerability: how easy your question is to answer in two or three sentences. “Any feedback?” requires the reader to compose an assessment. “Was there one area where my answers fell short of what you needed?” requires them to pick one thing they already know.
Of the four, answerability is the one candidates control most and use least. The other three explain why the same email can get a warm reply from one company and silence from another.
A formula for setting expectations
Candidates often take silence personally. It is more useful to treat the feedback request as a numbers game with modest odds, and to estimate those odds before sending. A rough way to do it:
Expected useful replies = Requests sent x Reply rate x Usefulness rate
Reply rate: share of requests that get any answer
Usefulness rate: share of answers that contain something specific you can act on
The rates below are illustrative assumptions, not measured figures, but they reflect the pattern most recruiters will recognise: later stages and personal relationships get more and better replies.
Worked example. Over a two month search, a product manager is rejected 14 times: 8 times after a recruiter screen, 4 times after a hiring manager interview and 2 times after a final round. She assumes a reply rate of 20% after screens, 40% after hiring manager interviews and 60% after final rounds. That gives 8 x 0.2 = 1.6, plus 4 x 0.4 = 1.6, plus 2 x 0.6 = 1.2, so about 4.4 replies from 14 requests.
If half of the replies after screens are generic, and about 70% of the later ones are specific, useful replies come to roughly 0.8 + 1.1 + 0.8, about 2.8. So 14 emails, each taking about 10 minutes, are likely to produce 2 or 3 pieces of concrete feedback. For under 2.5 hours of writing, that is a good trade, and it also shows why the final round requests deserve the most care.
The formula has a limit worth stating: it ignores the relationship value of a gracious reply. Some candidates who ask well get remembered for the next opening, which no reply rate captures.
The 3 day timeline from rejection to sent email
The best requests are sent fast, but not in the first emotional hour. A 3 day timeline keeps you inside the response window without writing in frustration.
Day 0, the day of the rejection. Read the email, reply with nothing yet, and write down for yourself what you think happened in each interview. Note any question where you felt unsure. This becomes the basis for a specific request, and it is useful even if nobody ever replies.
Day 1. Decide whom to write to. If you met the hiring manager and the rejection came from a recruiter, you can reply to the recruiter and ask whether the hiring manager would be open to sharing a short comment, or write to the manager directly if you already had email contact. Draft the message using one of the templates below, and pick one specific question based on your Day 0 notes.
Day 2. Reread the draft, cut it to under 120 words, and send it in the morning of a working day in the recipient’s time zone. Thank them briefly, ask one question, and make clear that a two line answer is enough.
After that, wait. If there is no reply after 7 to 10 days, one follow up is acceptable, ideally as a reply in the same thread so the context is visible. Keep the follow up to two sentences, such as a polite note that you understand if feedback is not possible. After that follow up, stop. A third message turns a reasonable request into a burden and can undo the good impression the first one made.
Email templates for each stage
Each template below is short on purpose. Adapt the details, keep the single question, and remove anything that sounds like an argument with the decision.
After a recruiter screen:
Hi Dana, thank you for letting me know, and for your time on the call last week. If it is easy to share, was there one requirement for this role where my background did not match closely enough? A sentence would help me target my applications better. Best regards, Alex
After a hiring manager interview:
Hi Sam, thanks for the update and for the conversation on Tuesday. I enjoyed hearing how your team approaches pricing experiments. I would be grateful for one piece of feedback: was there a part of the interview where my answers fell short of what you were looking for? Even two lines would be very useful. All the best, Alex
After a final round:
Hi Priya, thank you for telling me personally, and for the time your team spent across the five interviews. I am disappointed, but I respect the decision. If you are able to share it, what was the main difference between my candidacy and the person you chose? I would also be glad to stay in touch if a similar role opens later. Kind regards, Alex
All three share the same structure: thanks, one specific question, an explicit small ask. None of them asks the company to reconsider, and none lists your strengths again. Those two additions are the fastest way to get no reply, because they make answering feel like the start of a negotiation.
Mini-case: one candidate, six requests
This case is illustrative, built from patterns that career coaches commonly describe.
A data analyst with 4 years of experience applied for 20 roles over 6 weeks and reached interviews for 9. She was rejected 6 times after interviews. For the first 3 rejections she sent a reply saying “Thank you, could you share any feedback?” and got one answer: “We went with a candidate whose experience matched more closely.”
For the next 3, she used the 3 day timeline and a specific question. After a hiring manager interview at a logistics company, she asked whether her SQL exercise had met the bar. The manager replied the next day: the queries were correct, but she had not explained her assumptions about missing data, which the team considered essential.
After a final round at a fintech, she asked about the main difference from the chosen candidate. The recruiter wrote that the other person had direct experience with credit risk models. The third request got no answer, even after one follow up sent 8 days later.
Two of 3 specific requests produced something useful, against 0 of 3 generic ones. The first answer changed how she approached technical exercises: she began writing her assumptions as comments at the top of every query. Two interviews later, an interviewer praised exactly that habit while they reviewed her exercise together. The second answer told her that some rejections were about fit with a specific domain, not about her skills, and she stopped rewriting her resume after every refusal.
Reading the reply and using silence
Feedback comes in three kinds, and each needs different handling.
Specific feedback names a behaviour or a gap: “you did not explain your assumptions”, “we needed someone who had managed a budget above a certain size”. Treat it as data from one interview panel. Act on it if it matches something you also noticed, or if you hear it twice from different companies.
Generic feedback says “another candidate was a closer match” or “we had many strong applicants”. This is not evasive by intent; often it is all the person is allowed to say. Reply with a one line thank you and move on. Do not ask again for details, because the answer was already the limit.
Silence is the most common outcome, and it tells you very little about your candidacy. It mostly reflects the recruiter’s workload or company policy. Log it in the same spreadsheet where you track applications, with the stage and the date, and keep going. A column for feedback received makes the pattern visible after 10 or 15 processes.
Over a search, the more valuable output is the pattern across replies. If 3 companies mention structured problem solving, that is a theme worth working on. If one company mentions it, it may be about that panel. Resist the urge to rebuild your whole approach around a single comment, especially one from a process where you reached only the first call.
Your concrete next step is simple: open the last rejection email you received in the past week, write down one specific question about that process, and send a reply of under 120 words before the end of tomorrow.