The Short Answer

Ask once, ask the person who actually spoke to you, and ask one question that can be answered in a sentence.

Hi [Name], thank you for letting me know about [the operations role]. If you have a minute, is there one thing you would point to that made the difference between me and the person you chose? Useful for the next one. Completely fine if you cannot share it.

Three things make that message work. It is one question, not a list, so answering costs under a minute. It asks for something specific, because "any feedback?" is the version people ignore. And it gives explicit permission to decline, which is what gets a reply from someone whose employer has a policy against detailed feedback. Send it two or three working days after the rejection, to the recruiter or manager you dealt with, in the thread you already have. Do not argue with the decision, do not ask them to reconsider, and if nothing comes back after one gentle follow-up, let it go.

Sent it? Set the follow-up now.

The ask works better two or three days after the rejection, which is exactly when you have stopped thinking about it. Set the date now, while you are still annoyed enough to want the answer.

“Remind me on Monday at 10am to ask the recruiter for interview feedback”

Six Messages You Can Copy

Change the bracketed parts and send. One message each time, in the existing thread, so they can see who you are without scrolling.

1. To the recruiter who called or messaged you. The recruiter is usually the right target: they heard the debrief, and they may place you somewhere else later.

Hi [Name], thanks for the update on [the operations role], and for keeping me posted through the process. If it is possible to share, was there one area where I came up short against the person you picked? I would rather know than guess. No problem at all if you cannot say.

2. To the hiring manager you interviewed with directly. Here you can be more specific, because they watched you do the thing.

Hi [Name], thank you for the time last [Tuesday] and for the decision either way. One question if you are willing: on [the stakeholder scenario we talked through], what would a stronger answer have looked like? I am working on exactly that, so it would be genuinely useful.

3. After a final round. At this stage the honest answer is often that someone else was slightly better, so ask for the comparison rather than for a verdict on you.

Hi [Name], disappointed but thank you for telling me straight. Having got to the final two, is there one thing that separated us? Even a single word, such as experience or sector knowledge, tells me where to put the work. Thanks either way.

4. After a take-home task or assignment. Work you submitted is the most answerable question you can ask, because the answer is about a document rather than about a person.

Hi [Name], thanks for letting me know. On the [case study] I sent, would you be able to share what the reviewers flagged? I spent a weekend on it and I would like to know whether the gap was the analysis or the way I presented it. Happy to receive it in one line.

5. When you want to stay in the pipeline. Two asks, in that order, with the easy one first. The feedback is what you want today; the second line is what pays off in three months.

Hi [Name], thanks for the update. Two things. If you can share anything about where I fell short, I would welcome it. And if something closer to [my supply chain background] opens up, I would like to be considered. I will keep an eye out, but a nudge from your side would be appreciated.

6. The reply when real feedback arrives. Short, specific, no defence. The point of this message is that the next candidate who asks them gets an answer too.

That is really helpful, thank you for taking the time. The point about [the numbers in the presentation] is fair and I can work on it. Good luck with the hire, and do keep me in mind.

If what you actually need is a decision rather than a reason, that is a different message: see how to ask about your interview status for the chase before the rejection arrives.

What Every One of These Has in Common

  • The role, named. Recruiters run several processes at once. "The operations role" costs you four words and saves them a search.
  • One question. Three questions reads as a review request and gets nothing. One question gets a sentence, and a sentence is all you need.
  • A specific target. Ask about the final comparison, one answer, or the task you submitted. "Any feedback?" is the version that goes unanswered.
  • An explicit way out. "Completely fine if you cannot share it" is the line that gets replies from people whose employer discourages detail, because it tells them you will not argue with whatever they say.
  • No argument, anywhere in it. Not one clause re-making your case. The moment the message looks like an appeal, the reply becomes a liability and stops being sent.

Also: send it to a person, not into a careers inbox, and keep it in the thread where the conversation already happened. A fresh message to a general number three days later asks them to work out who you are before they decide whether to help.

When to Send It

The guidance here genuinely disagrees, so it is worth knowing both positions before you pick. Career guides are unanimous that asking is appropriate at all: it is a normal request and employers expect it (NerdWallet, Duke's career hub, Proofed). On timing they split: some advise asking within about 24 hours of the notice, while others advise letting the dust settle for a few days first.

Both have a point, and the practical rule we would give sits between them:

  • If the rejection came by phone, ask on the call. You have a human being, in the moment, with the debrief fresh. This is the single highest-yield version of the whole question, and it is the one most people are too stunned to use. One career guide makes the same point.
  • If it came as a message or an email, wait two or three working days. Long enough that your message is not read as a reaction, short enough that the decision is still in their head.
  • One follow-up, after about a week, then stop. "Just closing the loop on my question from [Monday], no problem at all if feedback is not something you can share" is the whole message. A second chase converts a polite non-answer into an awkward one.
  • Never in the same hour as the rejection. Whatever you write in that hour will read exactly like what it is.

Your Actual Odds of a Reply, and Why

It is worth going in with a realistic expectation, because a non-answer is not a verdict on your message. The candidate-experience surveys all land in the same region: roughly half of rejected candidates get no feedback at all.

  • 56 percent of candidates in 2025 received no feedback after being rejected during screening or interviewing, in Survale's 2025 CandE benchmark research, which draws on tens of thousands of candidate surveys.
  • 50.5 percent of US job seekers had at least one rejection with no human feedback in the previous year, in a self-reported survey published by Enhancv in April 2026, on a small sample.
  • 55 percent reported no updates or feedback after applying, in Monster's application black box report (a Pollfish survey of around a thousand employed US workers, February 2026). That question covers the application stage rather than post-interview rejection specifically.

Those three numbers are not directly comparable: different populations, different wording, different definitions of feedback. Read them as a range rather than a statistic. What they agree on is the shape: no reply is the normal outcome, not a sign you asked badly.

The reason is usually policy rather than rudeness. In most places there is no general obligation on an employer to explain why you were not hired, and the commonest explanation given by HR and employment-law commentary is that a documented specific reason can become evidence in a discrimination claim that vague wording would not have created (an employment law firm's note on exactly this). The example HR guides use is "we wanted someone more energetic", which can be read as a judgement about age (People HR). The same commentary notes that these rules are typically set by legal or senior management rather than by the recruiter you are messaging. Both sources are secondary commentary rather than legal authority, and we found no primary ruling to cite, so treat it as the widely given explanation rather than settled law in your country.

The practical consequence is the line in every script above: give them a way to say no. A recruiter who cannot give you detail can often still give you one word, and one word is useful.

What to Do With the Answer

One piece of feedback is an anecdote. Three pieces of feedback that say the same thing is a pattern, and only the pattern is worth changing your preparation over.

So write it down the day it arrives, in the same place every time, with the role and the date beside it. Two rejections saying "we wanted someone who had run a team of that size" is a gap you can plan around. One rejection saying it might only mean the other candidate had run a team of that size.

The second thing worth keeping is the promise, if you got one. "Keep an eye out, there is something similar coming in the new year" is a real lead with a date attached, and it is the one people lose. A note and a reminder turn it into a message you send in January instead of a conversation you half remember.

Remind me on Monday at 10am to ask the recruiter for interview feedback Remind me on 5 January at 10am to check back with Priya about the ops role she mentioned Remind me every Monday at 9am to follow up on open applications

If You Are Running Several Applications at Once

NagMeLater is a WhatsApp contact. You send it "remind me on Monday at 10am to ask the recruiter for interview feedback" and it comes back as a message you can answer with one word. You send it "note recruiter Priya said something similar may open in January" and the line is there in January. No app to install, no account, nothing new to open. The first 7 days are free and unlimited, then it is a monthly plan or a one-time lifetime plan.

A search that runs for months is mostly dates: when to follow up, when to ask again, when a promised opening was supposed to appear. A recurring reminder covers the weekly sweep in one sentence, and what each recruiter said belongs in a note rather than in your memory. The rest of the sequence has its own scripts: messaging HR about a job, proposing or moving an interview slot, and asking where your application stands.

Your first 7 days are free and unlimited

No app, no account. Save the number, send a message, done.

Frequently Asked Questions

Is it okay to ask for feedback after a job rejection?

Yes. Career guides treat it as a normal and expected request, and the people who run hiring processes are used to being asked. What makes it unwelcome is not the asking but the shape of the ask: a list of questions, a request to reconsider the decision, or anything that reads as an appeal. One specific question, with permission to decline, is a request almost nobody minds receiving.

How long should I wait before asking for feedback?

Two or three working days if the rejection arrived as a message or an email: long enough not to look like a reaction, short enough that the decision is still fresh. If the rejection came by phone, ask during the call itself, which is the version most likely to get a real answer. The published advice does differ here, with some guides recommending asking within 24 hours and others recommending a few days' gap.

Why do companies refuse to give interview feedback?

Usually policy rather than rudeness. There is generally no obligation on an employer to explain why you were not hired, and HR and employment-law commentary says the common reason for a blanket no-feedback rule is that a specific documented reason can become evidence in a discrimination claim. The standard example is 'we wanted someone more energetic', which can be read as a comment about age. Those rules are normally set by legal or senior management, not by the recruiter you are messaging.

Should I ask for feedback on WhatsApp or by email?

Use whichever channel the conversation already happened in. If a recruiter has been messaging you on WhatsApp, that is where your question gets read and answered quickly. If everything has been email, keep it there. The one thing to avoid is sending the question to a general careers inbox, where nobody owns it and nobody remembers you.

How many times should I follow up if nobody replies?

Once, after about a week, and then stop. One short line closing the loop is fine and occasionally works. A second chase turns a polite non-answer into an awkward one and can cost you the relationship with a recruiter who might place you somewhere else later.

What should I say if the feedback is critical?

Thank them, name the specific point, and do not defend yourself. 'That is fair and I can work on it' is the whole reply. Arguing with feedback you asked for is the fastest way to ensure you never get any from that person again, and it also tends to confirm whatever concern they just described.

Does asking for feedback hurt my chances of being hired there later?

Asking well does not. A short, specific, gracious question is often remembered positively, and the fifth script above deliberately pairs the feedback request with a line asking to be considered for something closer to your background. What does hurt is pushing after a non-answer, or replying to criticism with a rebuttal.