PlainResume

Thank You Email After an Interview: What to Write

A practical guide from the team behind PlainResume, the free resume builder.

The short answer: Send it within 24 hours, send a separate one to each interviewer with different content, and keep it under 150 words: one line of thanks, one specific thing from that conversation, one sentence that adds something new, and a clean close. The note rarely wins you the job on its own โ€” but a specific one keeps you vivid during the debrief, and it's the only sanctioned chance you get to improve an answer you fumbled.

Most thank-you notes are interchangeable, which is why most of them do nothing. The version that works is short, specific to one person, and carries exactly one piece of new value.

Timing: same day, or within 24 hours

Hiring teams often debrief within a day or two, so a note that lands before that conversation can still be in someone's head during it. Same-day afternoon or evening is ideal โ€” enough distance to write something considered, soon enough to matter. If you're past that window, send it anyway; a late note is better than none, and nobody was ever rejected for writing one.

Email is the default. A handwritten card is a pleasant extra in a few traditional or local-business contexts, but it arrives days later, so it never replaces the email.

One note per interviewer, with different content

Interviewers compare notes. Four identical emails to four people is noticeable and undoes the point of writing at all. Reference what you discussed with that person: the migration the engineer walked you through, the staffing concern the hiring manager raised, the team structure the director explained.

Missing addresses? Ask the recruiter or coordinator โ€” that's a normal request โ€” or ask for cards at the end of the interview. Failing that, send one to the recruiter and ask them to pass along your thanks, naming each person. Guessing at an email pattern is fine when you're confident and harmless when you're wrong, but a bounced message is a wasted note.

The structure: four lines, then stop

โœ— "Thank you so much for the opportunity to interview for this position. I really enjoyed learning more about the company and I believe my skills and experience make me a strong fit for the role. I am very passionate about this industry and would love the chance to contribute to your team. Please let me know if you need anything else. I look forward to hearing from you."

โœ“ "Hi Dana โ€” thanks for the time this morning.

The part that stuck with me was what you said about the billing migration slipping twice because nobody owned the reconciliation step. That's close to the mess I walked into at Orsini, where we fixed it by making one person accountable for the daily variance report before we touched the code.

You asked how I'd handle the first 90 days with a team that's mid-migration โ€” I gave a vaguer answer than I meant to. Concretely: two weeks shadowing the reconciliation process end to end before proposing anything.

I'd be glad to keep going. Happy to send the process doc I mentioned if it's useful."

Four moves, in order: thanks (one line, no throat-clearing), one specific reference that proves you listened, one sentence that adds something, and a close that states interest without pleading. Subject line: "Thanks โ€” [role] interview" or just "Thank you, Dana." Plain text, no attachments, no restating your resume โ€” they have it, and repeating it reads as anxiety. The same restraint that makes a good cover letter work applies here, in a quarter of the space.

The repair, used once

This is the most underused function of the note. If you gave a weak answer, fix it in two sentences โ€” not apologetically ("I'm so sorry, I completely blanked"), just better: "You asked about X; the clearer answer is Y." Interviewers read that as self-awareness, which is itself a signal. Use it for one thing only. A note that relitigates three answers reads as someone who left the room and spiraled.

What to leave out

No salary talk โ€” that belongs to the recruiter conversation, and a note is the wrong place to introduce a number. No pressure about timelines; if nobody mentioned next steps, one neutral line ("happy to hear about next steps whenever you have a sense of them") is the ceiling. No flattery that isn't true, no "as you can see from my resume," no long paragraphs of enthusiasm. And nothing you'd be embarrassed to have forwarded โ€” because it will be.

Two variants worth knowing. After a recruiter phone screen, send an even shorter version: thanks, one line confirming your interest and fit, done. And after a rejection, a brief gracious note genuinely does keep you in the pipeline โ€” candidates get called back when the first choice declines, and the person who took losing well is easy to call.

Interview coming up? Make sure the resume they're holding is the one you want to be asked about. PlainResume is free, no sign-up, no paywall on the PDF โ€” everything stays in your browser.

Build your resume free โ†’

Frequently asked questions

How soon should you send it?

Within 24 hours, same day ideally โ€” teams often debrief within a day or two. Late is still far better than never.

Send one to every interviewer?

Yes, individually and with different content. Interviewers compare notes, and identical emails defeat the purpose.

What should it say?

Thanks, one specific thing from that conversation, one sentence that adds value or improves an answer, and a clean close. Under 150 words.