An after rejection email ai prompt should do one of three jobs: ask for the feedback you actually need, close a loop you left open, or ask to stay in contact. What it should never do is argue, apologise for applying, or ask the hiring manager to reconsider on the same facts.
Below are three templates, one per job, plus the rule that decides which one to send and when not to send anything at all. Every template is under 150 words, because the email is read on a phone between other tasks.
Decide what the email is for before you write it
Most people skip this step and then send a paragraph that does all three jobs badly. It congratulates the company, asks for feedback, asks about other roles, mentions a referral, and apologises. The reader takes nothing from it.
Pick one purpose and delete the rest.
- Feedback. You interviewed, you were rejected, and you want to know what to fix. This is the highest-value version and the one people are most afraid to send.
- Loop closure. Something is unresolved: a take-home you submitted, a reference they asked for, an expense, a system you used. Close it so it does not sit open on their side.
- Stay in touch. You liked the team and want to be considered next time. This one needs the least and should be the shortest.
If you cannot name the purpose in a sentence, you are not ready to write it.
The feedback request after a rejection
Draft a short email to [hiring manager name] after I was not selected for [role]. I interviewed on [date] with [interviewers]. Thank them for their time in one sentence, without sounding relieved or apologetic. Then ask for one specific piece of feedback: [the exact thing, for example where my answer on system design fell short]. Explain why that answer matters for the role I am aiming at. Under 120 words. Do not contest the decision. Do not ask whether they would reconsider. Do not mention other roles you applied for. Do not use the words "just wondering" or "any feedback at all." Do not ask for a phone call. End by thanking them once, without a second request.
Fill in these details
- Name and role: Use the person's actual name if you had the email.
- Interview detail: The date and who you spoke with. It confirms which application you mean.
- The one question: Narrow beats broad. "Any feedback" gets nothing; "where did my architecture answer get thin" sometimes gets a paragraph.
A specific question is also the polite part. Asking for one narrow thing tells the reader the email is short to answer, which is the only reason it gets answered.
The loop-closure email
Use this when you are waiting on something from them, or when you are waiting on them regarding something you sent.
Draft a brief email to [name] closing an open item from my application for [role]. The open item is [what is outstanding and from which side]. My status is [what you have done, for example "the take-home was submitted on the 3rd"]. Say clearly that you are not asking them to reopen the decision, only to confirm [the specific thing you need, for example "whether the file reached the right inbox"]. Under 90 words. Do not apologise for following up. Do not add a request for feedback. Offer one easy way to reply.
Short matters more here than anywhere. A closure email exists to remove work from someone else's plate, and every extra sentence adds a reason to put it off.
There is one more variant worth having. If you are waiting on a decision rather than a task, write to confirm you are still waiting rather than to prompt them. The distinction matters: the first is administrative and easy to answer, the second reads as pressure and invites silence. State the date you are waiting from, name what you expect, and offer a clean way to close it either way, including withdrawing your application if the role has been filled.
The keep-in-touch email
Draft an email to [name] after I was not selected for [role]. I was [the part of the role or team that genuinely interested me, in one concrete line]. Say I would like to be considered for future openings in [area], and give one reason I would be a good fit based on [the work we discussed]. Under 100 words. Do not repeat my resume. Do not ask when roles open. Do not ask them to pass my name along. Sign off without a request.
The strongest version of this email names something from the conversation rather than the job posting. Recalling a specific discussion is what separates it from the hundreds of identical messages a recruiter receives.
How to edit the draft so it sounds like you
Cut every sentence that asks for nothing
Most draft replies to rejection are padded with gratitude that carries no information. Keep one thank-you, in the first or last line, and remove the rest.
Remove the apology for applying
You did not do something wrong by being considered. Sentences that apologise for your candidacy read as low confidence and change how the rest of the email lands.
Check the length before you send
Two hundred words is too long. If your draft is over 150, you are probably covering three purposes in one message. Cut until one remains.
Read it out loud
If you would not say it to the person in the room, do not send it. This catches tone problems that rereading does not.
Common after rejection email mistakes
- Asking for reconsideration. The decision has been made, and this makes the next application harder.
- Sending it the same hour. A short wait reads as considered; an instant reply reads as automated.
- Two purposes in one email. Feedback plus a referral request gets neither.
- Long gratitude paragraphs. Keep it to one sentence and move on.
- Following up twice with no reply. One follow-up is normal. A third is noise.
Frequently asked questions
Is it normal to email after being rejected?
It is normal and expected in most professional contexts, particularly after an interview. Keep it short, pick one purpose, and send it once.
Should I mention that I am still interested in other roles?
Only if that is the sole purpose of the message, and only with something specific that connects you to the team. Combining it with a feedback request makes the email harder to answer.
How long should I wait before following up?
After an interview, a few days is reasonable. After a long silence following a submission, one polite follow-up is fine. Beyond that, close the loop on your side and move on.
Send one email, then close the loop
Pick the version that matches your purpose, fill every bracket with something the reader will recognise, and cut it to under 150 words before you send it. Then stop. That single short email is worth more than a dozen longer ones, and it keeps your name decent for the next role. For the longer process these emails belong to, browse the career development collection.