To ask for feedback after job rejection, first confirm that the decision is final, then send a brief, courteous request to the contact you already know. Identify the role and ask about one part of your application or interview that could help you improve. Do not argue for reconsideration, ask for another candidate’s details or assume a reply is guaranteed. Use any answer as one observation about this process, not as a complete explanation of your abilities.
Separate a rejection from an unanswered application
A message saying the employer will not continue with your application is different from silence after an interview. If the decision is still pending, your question concerns the timeline or application status. After an explicit rejection, the question is what you can learn. Mixing those goals can make a polite request sound like an attempt to reopen the selection.
Read the actual message before interpreting it. “We chose a profile that better matched our requirements” does not identify which requirement mattered or prove that your interview went badly. Keep the wording as a fact and your explanation as a hypothesis. You do not need to invent a hidden reason to decide on a practical next step.
The National Careers Service interview guidance suggests reflecting on difficult questions and asking for feedback if you did not get the role. Our interview preparation guide covers preparation more broadly. This article deals with the narrower task of requesting and using feedback after a confirmed negative decision, not chasing an overdue response.
Feedback after job rejection: choose the contact and purpose
Start with the recruiter or interviewer who communicated with you during the process. Use the existing thread when its reply address accepts messages. If the rejection came from an automated address, use an appropriate contact already provided for this recruitment. Do not send the same request to several managers or search for private contact details to bypass a closed channel.
You can wait until you can write calmly. There is no universal ideal number of hours or days. The useful distinction is whether you are asking a considered question about a recent, identifiable process or reacting to disappointment. A short request can be worthwhile after a substantive interview; a very early screening rejection may leave the recipient with less specific information to share.
Decide what you want to understand before opening the email. Was your example too vague? Was an essential skill unclear in the written application? These are different questions. Select one that the person could reasonably answer from their involvement. If your real aim is to challenge the outcome, recognise that this is not the same conversation as a learning request.
Build a short request around one answerable question
A useful message has a recognisable context, an acknowledgement of the decision and a narrow question. Include the role title and, if helpful, an application reference or interview date. The recipient should not have to reconstruct which process you mean. Match the level of formality used in the previous exchange rather than adopting an unusually intimate tone.
- Thank the person for communicating the decision, without pretending you enjoyed being rejected.
- Make clear that your purpose is to improve future applications.
- Ask for one observation about a relevant aspect they saw.
- Leave room for them to decline or provide only a brief answer.
Avoid attaching your whole application again unless requested. Do not add a list of your qualifications to prove they should have hired you. That changes the message from a request into an argument. Equally, you do not need to apologise for being disappointed or ask the employer to reassure you about your general worth.
Keep the subject clear, for example “Feedback request: operations assistant application”. If you reply within the existing thread, retaining its subject can preserve context. There is no wording that makes a detailed answer inevitable. The goal is a manageable question, not a formula that promises a response.
Example one: ask about the interview without disputing it
In this fictional example, Nora interviewed for a scheduling role. She described how she handled a handover, but the answer felt unfocused afterwards. She has received a rejection and wants to improve the explanation for another relevant interview. The employer has not given a specific reason.
I met every requirement and thought the interview went perfectly. Why was I rejected? Please tell me exactly how the successful candidate was better and reconsider my application.
Dear Ms Patel, thank you for letting me know the decision on the scheduling coordinator role. I understand that my application will not continue. To prepare more clearly for future interviews, could you share a brief observation on how I explained my handover experience? I would particularly value knowing whether my own responsibility was clear. I appreciate that you may not be able to provide individual feedback. Kind regards, Nora.
The revised request identifies a part of the conversation the interviewer actually heard. It does not claim that this caused the rejection. It also removes the request for another person’s information. Nora is asking what was understood, not demanding a comparison with someone she does not know.
If the interviewer replies that her responsibility was unclear, Nora can revisit that example. If they say the decision concerned a different requirement, she should not insist on her original explanation. The request creates an opportunity to learn; it does not control which observation the person can share.
Example two: adapt the question when there was no interview
Samir’s fictional application for an administration role was rejected at the written stage. There was no interview or assessment. The advert asked for experience maintaining equipment records. His resume described “general office support”, although he had actually checked an equipment register in a previous job.
Please tell me which interview answers were weak and why I did not fit your team. I would like a full assessment of my personality and performance.
Dear recruitment team, thank you for updating me on my administration assistant application, reference A17. For future applications, could you indicate whether my written experience with maintaining equipment records was sufficiently clear? I am reviewing how I describe that work and would welcome a brief observation if you are able to share one. Thank you for your time. Kind regards, Samir.
This asks about something the recipient could have reviewed, without inventing an interview or requesting a personality judgement. It still may not receive a reply. Samir can independently compare the advert with the exact submitted document using our resume guidance. The genuine task was present in his history but missing from the description.
That finding supports a clearer next description; it does not prove why this application was rejected. If he did not actually have the required experience, the right response would be to acknowledge the gap or choose a more suitable vacancy, not to add a task he never performed.
Read an answer without turning it into a verdict
Separate specific observations, general preferences and incomplete explanations. “Your example did not show which decisions you made” gives you something to revise. “Another profile was closer to what we needed” does not establish a personal defect or identify a particular change. Treat “be more confident” as a prompt to ask what was unclear only if a continuing exchange is welcome.
Compare the feedback with your own notes and the vacancy. If it refers to something you can check, such as a missing qualification or an unclear task, check it. If it conflicts with your recollection, you can note the difference without accusing the person of bad faith. One recipient’s impression is not automatically a fact about every future employer.
Record the original comment separately from your interpretation and planned action. The application organisation guide helps retain the exact sent version. “The recruiter said my example was unclear” is different from “I am bad at interviews”. Keep the first statement available without letting the second become your working assumption.
Choose a next step even if no feedback arrives
A request can remain unanswered or receive a standard response. Neither tells you why the application was rejected. Do not interpret silence as proof of an automated filter, discrimination, a missing keyword or a hidden appointment. This guide does not determine legal rights or complaint procedures; seek appropriate qualified advice separately if that is your concern.
For a voluntary learning request, one courteous message is usually a sensible stopping point. If the recipient invited you to speak later or promised an answer, follow that arrangement rather than repeatedly contacting new people. If they decline, acknowledge it and stop. You can continue applying while a possible reply remains pending.
Carry out a review you can control: check whether you met essential requirements, whether the submitted document made the relevant work visible and whether an interview example explained your action clearly. Choose one useful change for the next comparable application. Keep the original file so you can distinguish an actual revision from a vague intention to “do better”.
Ask a trusted adviser to review the material if you cannot identify a useful change yourself. Give them the vacancy and submitted version, not just the rejection. You can accept support without granting a single comment authority over your whole career.
Final check before sending and moving forward
Read the request once as the recipient. Can they identify the role and the part you want feedback on? Remove sentences whose main purpose is to prove the decision was wrong. Then read it as your future self: will an answer help you make a concrete, honest change?
Check the request
- The rejection is confirmed, not merely assumed.
- The channel and contact belong to this recruitment.
- The role or reference is identifiable.
- There is one focused question.
- The question fits the stage you reached.
- No other candidate’s private information is requested.
- The message does not argue for reconsideration.
- You have a next step even without a reply.
If an answer arrives, thank the person and record the useful detail. You do not need to defend every point in return. Thoughtful feedback can support a better next application, but it is neither a complete explanation of the decision nor a guarantee of a future offer.
Frequently asked questions
Should I reply to every rejection?
No. A request is most useful when you have a focused question and an appropriate contact. You can decide that an early standard rejection does not merit more of your time.
What if the reply address is automated?
Use a relevant contact already provided for the recruitment, if there is one. Do not bypass a closed channel by contacting several unrelated employees.
Can I ask who was hired instead?
Keep the request about your own application. Another candidate’s identity, documents or interview answers are not needed to improve your next attempt.
What should I do with vague feedback?
Keep the wording as a limited observation. Review the vacancy and your own materials; do not invent a cause or make a major change unsupported by the comment.
Does silence mean my application was filtered automatically?
No. An unanswered feedback request does not identify the selection method or reason. Review what you can check without claiming to know what happened.