How to Request Interview Feedback

Most candidates who get turned down after an interview move straight on to the next application without asking why. That is understandable. Rejection does not put you in the mood to ask for more information. But skipping the question means giving up on the one thing that interview might still have to offer you: a piece of specific, usable feedback about how you came across.

When to Ask

Ask shortly after the rejection, ideally within a day or two, while the interview is still fresh for the person on the other end. Reply directly to the rejection email rather than opening a new thread. It saves the recruiter or hiring manager the work of finding the context and makes your message easier to answer. Waiting a few weeks and then asking why you didn't get the job rarely works, because by then the interviewer has moved on to other candidates and the specifics have faded even for them.

How to Ask in a Way That Makes It Easy to Say Yes

The request that gets answered is short, specific and low effort for the person reading it. An open question like "why didn't I get the job" asks the interviewer to construct an explanation from scratch, which most people will not do for a candidate they are no longer evaluating. A narrower version works better: "If you have a moment, I'd appreciate one thing I could focus on for future interviews." That is something someone can answer in two sentences without much thought, and it signals that you are looking to improve rather than looking to contest the decision.

Keep the tone appreciative rather than aggrieved, even if you are disappointed. A message that reads as a complaint, or that pushes back on the decision, tends to get ignored or answered defensively. Thank them for their time first, then ask.

What Response Rate and Depth to Expect

Keep your expectations realistic. Many recruiters and hiring managers will not reply to a feedback request at all, not because they are being rude, but because detailed feedback carries legal and reputational risk for the company, and answering takes time they have little incentive to spend on a candidate they have already turned down. Of those who do reply, a good share give something close to boilerplate: a line about moving forward with a candidate whose background was a closer match for the role. That is a real answer. It just is not a specific one.

Occasionally, and this is why the request is worth sending, you get something specific: a note that your technical answers were solid but your examples were too abstract, or that another candidate had a particular piece of domain experience you were missing. One useful data point across several feedback requests is a realistic outcome, not a disappointing one.

What to Do With Vague Feedback

If the answer you get is generic, something like "we went with someone with more experience" or "the team felt another candidate was a stronger fit", you can probe once, gently, but do not go further than that. A reasonable follow-up: "Thanks, that's helpful. Was there a specific skill or type of experience that stood out, so I know what to prioritise?" This asks for one more layer of detail without demanding a justification for the decision. If the reply to that is still vague, or if there is no reply at all, treat the first answer as final. Repeated requests for specifics read as contesting the outcome rather than learning from it, and that is not the impression you want to leave, particularly at a company you might apply to again.

Structuring the Email

You do not need a full script, but the request works best in four short parts: a thank you for their time and the opportunity to interview, a brief note that you are asking to improve rather than to argue the decision, the specific low-effort question itself, and a short, warm sign-off. The whole message should fit in four or five sentences. Anything longer starts to read as a case for reconsideration rather than a request for feedback.

If You Get No Response

If nothing comes back, accept it and move your attention elsewhere. Silence after one request is common, and it is not itself a signal about anything except how that particular company handles rejected candidates. Sending a second or third message rarely changes the outcome. It mostly costs you time better spent on the next application. Ask once, take whatever comes back, and put the energy into what happens next in your search.

Related guides

• How to Handle a Job Rejection
• How to Write a Thank You Email After an Interview