How to ask what went wrong after a rejection

Asking for feedback after a rejection works when you ask about one specific thing, make it answerable in a single sentence, and accept whatever comes back without arguing. Broad requests for feedback almost never get answered, and the reason is not rudeness.

The person who rejected you is worried about two things: saying something that sounds like a legal problem, and starting a conversation they cannot end.

Every part of a good ask is designed to remove one of those worries.

Ask a yes-or-no question about the thing you suspect

Make the question narrow enough that it can be answered with one word, because the expensive part for the other person is deciding what to say at all.

"Was the gap in payments experience the main thing, or was it something else?" That shape works because it gives them an exit that is not silence. Quite often they answer the narrow question and then add the real reason unprompted, having been given somewhere easy to start.

Pick the thing you genuinely suspect rather than the thing that sounds humble. If you have no suspicion at all, ask about the closest call: "Was I close, or was this not the right shape from the start?"

Send it once, quickly, and make the exit obvious

Reply within a day or two of the rejection, while you are still a person to them rather than a name in a folder.

Keep it to about four sentences. Thank them without ceremony, name the one thing you want to know, and say explicitly that you understand if they cannot say.

That last clause does more work than anything else in the message. It tells them you will not push back, will not appeal, and will not make this into a thread. People answer far more often when the request comes with a visible way out.

Then send it once. If nothing comes back, that is the answer, and following up converts a graceful ask into an awkward one.

A version you can adjust to sound like you

Something close to this, adjusted to sound like you.

• Thanks for letting me know, and for being quick about it.
• One question if you have a moment: was it mostly the missing infrastructure experience, or something else?
• Asking so I know what to work on, not to reopen anything.
• Completely fine if you would rather not say.

Four lines. No paragraph about how much you enjoyed the process, no restatement of your qualifications, no hint that you think the decision was wrong.

The third line is the one people leave out and it is the one that unlocks answers. Saying what you want the information for removes the fear that you are building a case.

Reply with thanks and stop there

Whatever comes back, answer it with gratitude and nothing else, even when the stated reason is wrong.

The decision is already made, so a correction cannot change it. What a correction does communicate, clearly, is that answering you was a mistake. That person may hire again in a year, or move somewhere else and remember one thing about you, which will be how you took a no.

The exception is a factual error that will follow you, such as a reference problem or a mixed-up identity. Set that straight once, briefly, and let it go.

Read the answer for what it is not saying

Feedback after a rejection is filtered, and the filter is predictable enough to read through.

"We went with someone with more direct experience" is the standard formulation and it is often true and rarely complete. What it usually means is that the decision was comparative, so the useful follow-up thought is not "I need more experience" but "someone in this pool looked like a safer bet".

Softer than that is even less informative. "It was a strong field" is a polite closing sentence with no content in it, and treating it as data will send you off improving something that was never the problem.

Where you should pay real attention is any specific noun. If they name a skill, a tool, or a stage of the process, that noun got past the filter for a reason, and it is worth more than three paragraphs of general encouragement.

The recruiter usually knows more than the decision maker will say

If there was a recruiter, an internal contact, or somebody who ran a single round, they are often the better person to ask.

Recruiters in particular hear the debrief and are usually less constrained about summarizing it. They also have an incentive to keep you warm for the next role, which means answering you is in their interest as well as yours.

This applies outside hiring too. A rejected proposal, a declined pitch, a client who went elsewhere: there is almost always somebody adjacent to the decision who can tell you more than the person who had to write the no.

I have sent both versions of this message. The one that asked whether there was "anything I could improve for next time" got a warm paragraph containing no information. The one that named a single item and asked whether it was the deciding factor got a two-word answer that was worth more than the paragraph, and I only learned the difference by writing the useless one first.

When to skip the ask entirely

Some rejections carry no information, and asking about those is a way of prolonging something that is finished.

Automated rejections, rejections from an application you never had contact on, rejections that arrived within an hour: nobody at the other end has anything to tell you. There was no human deliberation to report.

The ask is worth it when a person spent real time on you: an interview, or a proposal somebody read properly. In those cases they have an opinion, and some of them will share a piece of it if you make it cheap enough to give.

The rest of the time, close the tab. Being rejected well is a skill, and part of it is knowing which doors are worth knocking on twice.