Most companies decline to give specific feedback after a rejection, usually for legal and liability reasons rather than indifference — an offhand comment about a candidate can become a legal exposure if it's ever characterized as discriminatory, even unintentionally, so many companies adopt a blanket policy of giving none at all. Knowing this in advance changes how to ask: not whether you'll get an answer, but how to maximize the odds of getting a genuinely useful one from a company willing to give it.

Ask soon, and ask specifically

A generic request ("do you have any feedback?") is easy to decline with a form response. A specific, narrow question is both easier to answer and more likely to get a real one: "Was there a specific area of my background or interview that was the deciding factor?" gives the person something concrete to respond to, rather than an open-ended invitation to write an essay they don't have time for.

A template that respects their time

Subject: Thank you — [Role] interview

Hi [Name],

Thank you for letting me know about the decision, and for the time you and the team spent on the process. I know feedback isn't always possible to share, but if there's anything specific about my background or interview that stood out as the deciding factor, I'd genuinely appreciate hearing it — it would help me going forward.

Either way, thank you again for the opportunity, and I hope our paths cross again.

[Your name]

This works because it explicitly acknowledges they might say no, asks for something specific rather than open-ended, and ends on genuine goodwill rather than visible disappointment — all of which make it easier for someone to actually respond.

What to do with a generic non-answer

Most responses will be some version of "we had many strong candidates and made a difficult decision" — genuinely uninformative, and not worth pushing back on. Don't ask a second time or push for more detail; a repeated request after a generic decline reads as pressure, not genuine curiosity, and can affect whether they'd consider you for a future role.

What to do with real, specific feedback

If you do get something specific and useful, resist the urge to argue or explain it away, even if you disagree — the goal of the conversation was information, not a chance to relitigate the decision. Write it down, and if there's a real pattern across specific feedback from more than one rejection, treat it as a genuine signal worth addressing before your next several applications, not a one-off comment to dismiss.

When silence itself is the feedback

If a company doesn't respond to a feedback request at all, that's not a sign anything went specifically wrong beyond a normal decline — many hiring teams are simply moving fast onto other things and don't reply to any post-decision emails, whether or not the request included a feedback question. Treat non-response the same as a generic "not moving forward" and continue your search without reading additional meaning into the silence.

Where this fits into a broader search

Feedback requests are a small, low-cost habit worth doing consistently, not a strategy to lean on heavily — most attempts get nothing usable, but the occasional specific, useful response is worth the minimal effort it takes to ask. See our guide on following up after a job interview for the broader etiquette around post-interview communication, and our guide on red flags to watch for during an interview if a pattern in the feedback you do receive points toward something worth reconsidering about how you're presenting yourself. Our Interview Prep Generator can help you prepare more thoroughly for the specific gap, once you actually know what it is.