How to Ask for Interview Feedback After Rejection

You can ask for interview feedback after a rejection, and it is worth doing once, briefly. Send a short message to the recruiter within about 48 hours: thank them, accept the decision in one line, and ask two or three narrow questions about specific moments in the interview. Many employers reply briefly or not at all, and that is normal. Treat whatever comes back as one input to your practice, not a verdict on you.

Ask for interview feedback after rejection: once, small, fast

Three rules make the difference between a reply and silence.

One message only. Send it to one person. A second chase is fine; a third is not.
Two or three narrow questions. Broad questions get form replies because they are hard to answer without sounding harsh or disclosing things about other candidates.
Within about 48 hours. The interviewer still remembers your session. A week later, you are a name in a spreadsheet.

Here is why narrow works. "Why was I rejected?" asks an employer to justify a decision they have already made, in writing, to someone who might dispute it. Most people avoid that. "Was there anything in my system design walkthrough that felt unclear?" asks about a moment, not a verdict. It is easy to answer, low-risk, and often gets a sentence or two of something real.

Set your expectation before you send. Plenty of employers reply with one polite line, and some never reply at all. That is not a second rejection; it is a busy person choosing not to put a decision in writing.

Who to ask

Default to the recruiter who sent the rejection. They own the relationship, they know the process, and they can forward your questions to the hiring manager if it makes sense. You are not asking them to overrule anyone.

Reply to the hiring manager directly only when you interviewed with them late in the process and had direct contact — a final round, a long conversation, an email thread that was already two-way. In that case a short note is natural.

Avoid asking the interviewer who seemed most positive. They are usually told not to discuss outcomes, so you put a friendly person in an awkward spot and often get nothing back. If they offer to stay in touch, take them up on it later, when you have something to say.

A copyable script for asking for interview feedback

This is the full email. It is under 120 words, it does not re-argue the decision, and it gives the reader an easy way to reply.

Subject: Thank you — one quick question
Hi,
Thank you for the update, and for the time your team gave me. I enjoyed meeting everyone and I accept the decision.
If you have a moment, I would value two short answers: was there a part of the [case / coding / behavioural] round where my answer was hard to follow, and is there a skill the team needed that I did not show evidence of?
Either way, I would like to stay in touch.
Best, Alex

Every sentence is doing a job. The thanks close the loop politely. "I accept the decision" removes any hint that you are asking them to reconsider. The two questions are specific enough to answer in a line each. The closing line keeps the door open without asking for anything.

For LinkedIn or a recruiter chat thread, shorten it:

Hi, thanks for the update — I understand. If you have a minute, was there anything in the [round] that felt unclear, or a skill the team needed that I didn't show? Either way, good to stay connected.

If you were rejected before any interview, at the application stage, the honest answer is that feedback is almost never given. There is no interview to comment on. A one-line thank-you is enough, and it keeps the relationship warm for next time.

The three questions that get useful answers

Use these as your shortlist and pick the two that fit the round you actually had.

A specific moment. "Was there a part of the [case / coding / behavioural] round where my answer was hard to follow?" This works because it asks about clarity, which is a craft question, not a judgement of you.
A gap. "Is there a skill or experience the team needed that I didn't show evidence of?" This works because it invites a factual answer about the role, and it is the question most likely to produce a phrase you can act on.
A forward-looking one. "If I applied for a similar role in six months, what would be most worth working on?" This works because it is about the future, so the employer is not defending the past.

None of these require the employer to disclose anything sensitive, compare you to another candidate, or put a criticism of your personality in writing. That is exactly why they get answered. "What did the other candidate have that I didn't?" does the opposite: it asks them to talk about someone else, which most employers will not do.

A weak-then-stronger rewrite makes the difference plain.

Weak: "Why was I rejected?"
Stronger: "In the case round, was my recommendation clear enough, or did it get lost in the detail?"

The second version names a round, names a moment, and offers two possible answers. It is easy to reply to, and it tells you something you can practise.

What employers can and can't say back

There is usually no formal right to interview feedback; it is a courtesy, not an obligation. Treat this as general context rather than legal advice.

What you will typically get is process feedback: "we went with someone with more direct experience in X." That is a fact about the competition, not a critique of you, and it is often the most honest thing an employer can safely say.

Many employers keep it generic for three reasons. Consistency across candidates, so no one is treated differently. Caution about disputes, since a written critique can be read as a judgement on a person. And internal policy, which often tells interviewers to route everything through the recruiter. None of that is personal, even when it feels like it.

How to read a vague reply

Three replies come up often. Here is what each does and does not tell you.

"We went with a stronger candidate." Tells you the bar was met by someone else; does not tell you where you fell short. Useful only if you can get one specific follow-up.
"Not enough experience." Often means a specific kind of experience, not years in total. Ask which kind if you get the chance.
"We'll keep your details on file." A polite close, not a promise. Do not build a plan around it.

If you get silence, one polite follow-up about a week later is fine. After that, stop. The fallback is to reconstruct your own feedback: write down the two moments in the interview where you felt least sure, and treat those as your practice targets. Your memory of uncertainty is usually accurate about where the weak spots were.

Turn the feedback into a practice plan

Whatever comes back, convert it into three columns: what they said, what it probably means, what you will practise this week. One reply, one row. Keep it short enough that you will actually use it.

Two worked examples, both illustrative:

They said "answers were a bit long." That probably means your points were buried. This week, practise answering with three talking points and a stop — see our guide on sounding natural with talking points.
They said "we wanted more ownership examples." That probably means your stories described the team, not your decisions. This week, rewrite two stories with a clear situation, your action and the result, using our ownership interview questions article.

Then rehearse the weak area out loud, not by reading. Say the answer, time it, and cut it. If the feedback was about clarity or structure, our communication interview questions article has frameworks you can say aloud.

Three mistakes that burn the bridge

Arguing with the decision or asking them to reconsider in the same message. It turns a request into a dispute, and the reply you wanted never comes.
Sending a long list of questions or a paragraph about how the process was unfair. Length reads as grievance. Two questions read as professionalism.
Asking weeks later, or asking several people at the same company at once. Late messages get forgotten, and multiple requests look like pressure.

The fix for all three is the same: one short message, one person, two questions, sent quickly.

Before your next interview

Feedback is one input, not a verdict. Send the short message within a day or two, ask two specific questions, and accept whatever comes back without reading a second rejection into it. Then take the one thing you can act on and rehearse it out loud before your next interview. If you want a structured way to practise, start with our blog and pick the guide that matches the round you found hardest.

Frequently asked questions

Should I ask for feedback if I was rejected at the application stage, before any interview?

Usually not, beyond a one-line thank-you. There is no interview performance to comment on, so most employers have nothing specific to give and will send a standard reply or none at all. Keep the note brief and stay on good terms for a future opening.

Is it okay to ask for feedback on LinkedIn rather than by email?

Yes, if that is where you already have contact with the recruiter. Keep it to two or three sentences, thank them, and ask your two specific questions. Email tends to get a fuller reply because it is easier to forward internally, so use email when you have an address.

Can I ask for feedback if I was rejected after a final-round interview?

Yes, and this is often the best case for it. You met more people and invested more time, so a short note to the recruiter or the hiring manager is reasonable. Ask about one specific round rather than the whole process, and accept that the reply may still be general.

What should I do if the feedback contradicts what the interviewer said in the room?

Do not argue. Interviewers often give encouraging signals in person and a different account later, and the written version reflects the hiring decision. Note the gap, ask one clarifying question if you have a good relationship, and focus on the part of the feedback you can act on.

Should I mention the rejection feedback when I apply to the same company again?

Only if it is relevant and brief. A line in your application or interview saying you took the earlier feedback on board and what you changed shows self-awareness. Do not relitigate the old decision or ask for a re-score; let the new interview stand on its own.

Practise the weak spot out loud with our blog guides.