How to ask for useful feedback after a job rejection

Decide what you need to learn

Start with the stage you reached. After an application-only rejection, the employer has seen your submitted evidence, not how you work in an interview. After a presentation or interview, you can ask about a particular example, question or assessment criterion.

Write down the question you are actually trying to answer. Was an important responsibility missing from your examples? Did the example describe a task without explaining your contribution? Was there a requirement you did not understand? Choose one question rather than asking for a full critique of your career.

If the employer has not communicated an outcome, this is a different situation. Use our guide to following up after an interview rather than treating silence as a confirmed rejection.

Make a small, specific request

Use the recruiting contact and the communication channel you have already been given. Check the rejection message for any stated feedback process or limit. Do not search for an interviewer's personal contact details or recruit colleagues to pursue an answer on your behalf.

After an interview, adaptable wording is: “Thank you for letting me know. I understand the decision. To help me prepare for future interviews, was there one part of my example about [responsibility] where clearer evidence would have helped? A short pointer would be useful if you are able to share one.”

After an application-only rejection, try: “I understand that you may not be able to provide individual feedback. If you can share a short pointer, which essential requirement was least clearly evidenced in my application?” Use this only if it fits the process; a high-volume application system may offer no individual route.

These are suggested questions, not scripts that guarantee a reply. You do not need to praise a process you found frustrating. Keep the message factual, brief and free of demands for comparisons with another candidate.

Do not confuse feedback with an appeal

Asking what to improve and challenging a decision are different tasks. “What would make my example clearer?” invites a practical observation. “Prove that the other person was better” asks for justification and information the employer may not share.

For readers in Great Britain, Acas explains that you can ask about a rejection or request feedback, but employers do not have to provide it^[1]. That is jurisdiction-specific guidance, not a statement about every country's rules or every organisation's commitments.

If you believe a process involved discrimination or a serious breach of its stated rules, do not treat a polite feedback email as your only option. Keep the relevant records and seek appropriate local advice about the process and any time limits. This article is about learning from an application, not deciding whether you have a legal claim.

Look for an observation, not a verdict

Useful feedback connects a criterion to something observable: “Your example described the team's result, but we could not identify the decision you personally made.” That gives you something to review. “You were not senior enough” is much harder to act on without context.

Separate three things in your notes: what the employer actually said, what you remember doing, and what you are guessing. Do not quietly turn “we needed more evidence of budgeting” into “I am bad with money” or “I must take a finance course.” Neither conclusion follows automatically.

If a reply is ambiguous and the contact invites further questions, ask one clarification about the criterion or example. Otherwise, leave it there. A missing reply or a short answer does not establish why you were rejected, and repeatedly asking is not a reliable way to obtain a fuller explanation.

A fictional example: from vague feedback to one change

Consider Zoë, a fictional project coordinator who interviewed for a role involving competing team priorities. The feedback says her answer needed to demonstrate more ownership. She initially thinks she must make every example sound more senior.

Instead, she asks which part of her priorities example needed clearer evidence. In this fictional exchange, the recruiter says the panel understood the schedule but could not tell which trade-off Zoë had recommended and why. That is narrower than a judgement about all of her experience.

Zoë reviews her notes. Her example spent most of its time describing the project and the team's work. She had barely explained her own recommendation, the constraints she considered or how the decision was reached. Her next practice task is to make those elements explicit, using only what actually happened.

She prepares five prompts: the competing priorities, her responsibility, the options she considered, her recommendation and the observed result or unresolved limitation. She does not add budget authority she never had, invent a numerical result or claim that this change would have won the original job.

Turn the reply into one practice task

Choose an action that matches the evidence. If your contribution was unclear, practise explaining it. If a requirement was genuinely missing, investigate whether you need a qualification, supervised experience or a different target role. Stronger wording cannot replace a required capability.

If the feedback concerns your application, check whether the relevant evidence is present and easy to find before rewriting the whole CV. Our guide to turning responsibilities into CV evidence can help you make that distinction without inventing numbers.

For an interview answer, make a short set of prompts and try saying it aloud. The National Careers Service recommends reflecting on difficult interview questions and asking for feedback after an unsuccessful interview^[2]. Our interview preparation guide develops this into practice without memorising a performance.

Keep what is useful, leave what is uncertain

One panel's feedback can identify a useful gap without becoming a permanent rule for every application. Compare it with the responsibilities of the next role and with your own evidence. If similar specific observations recur, investigate the pattern; do not count repeated generic rejection messages as the same kind of evidence.

You can also improve without a reply. Write down one question you struggled with, the answer you gave and the part you would clarify next time. Label this your own reflection, not the employer's confirmed reason. Keep employer and client information private, and use anonymised notes when practising with someone else.

Your next action is small: choose one recent, confirmed rejection, decide whether a feedback request fits the stated process, and draft one focused question. If useful information arrives, turn it into one honest practice task. If it does not, continue your search without filling the silence with a verdict about yourself.