How to write a follow-up email after an interview (with templates)

You just walked out of the interview. It went well, you think. The conversation flowed, you had good answers for the tough questions, the interviewer laughed at your joke about legacy code. Now you're sitting in your car or walking to the train, and the adrenaline is wearing off.

Send the follow-up email before that feeling fades. Not in the parking lot. But today.

Timing

Within 24 hours. Not because of some arbitrary rule, but because hiring teams often debrief the same day. Your email should land while the interviewer still remembers what you talked about.

Morning interview? Send by end of business. Afternoon interview? Next morning is fine. Sending it fifteen minutes after you leave the building feels overeager. Sending it three days later feels like you forgot.

If you met with multiple people, send a separate email to each one. Not the same email. Different emails that reference your specific conversation with that person.

What goes in it

A follow-up email has five parts. The whole thing should be 150 to 200 words. Shorter is fine. Longer is not.

Subject line. Keep it obvious. "Thank you, [Role Title] interview" works. "Following up on our conversation about the [Role Title] position" works. "Quick note!" does not work.

Opening. Thank them for their time. Reference something specific from the conversation so they know this isn't a template.

The callback. This is the part that matters. Pick a moment from the interview, a challenge they described, a project they mentioned, a question that led to a good exchange, and add something to it.

"When you described the challenge of migrating your monolith to microservices, it reminded me of a similar project where we phased the migration over six months to avoid disrupting active users. I'd be excited to bring that experience to your team's effort."

Two things happen here. You prove you were listening. And you reinforce your qualifications with a specific example. If there was something you wished you'd said during the interview, this is your window.

Interest statement. One or two sentences about why you want this specific role. Be concrete. "The combination of the technical challenges and the team's approach to code review is exactly what I'm looking for" beats "I'm very excited about this opportunity."

Closing. Short. "Let me know if you need anything else from me. Looking forward to the next step."

Templates

Use these as starting points. If you send one verbatim without personalizing it, you've missed the point.

After a phone screen

Subject: Thank you, [Role Title] phone screen

Hi [Name],

Thank you for the conversation today about the [Role Title] role. I appreciated learning about [specific thing discussed].

Based on what you described, I'm particularly interested in [specific aspect]. My experience with [relevant skill or project] connects directly to that, and I'd welcome the chance to discuss it further.

Thanks again for your time.

Best, [Your Name]

After an onsite or panel

Subject: Thank you, [Role Title] interview

Hi [Name],

Thank you for spending time with me today. I enjoyed our conversation about [specific topic], especially [specific detail].

Your description of [challenge or project] resonated with me. At [your company], I [brief relevant experience]. I'd be glad to bring that perspective to the team.

Please let me know if there's anything else I can provide.

Best, [Your Name]

After a final round

Subject: Thank you, [Role Title] final interview

Hi [Name],

Thank you for the thorough process. Today's conversation about [specific topic] confirmed that this is the kind of work I want to be doing.

Throughout the interviews, I've been impressed by [specific observation about the team or product]. The emphasis on [specific value] matches how I work best.

I'm looking forward to the possibility of contributing to [specific goal or project].

Best, [Your Name]

After a rejection

This surprises people, but a gracious note after a rejection keeps the door open. Hiring managers remember candidates who handle disappointment well.

Subject: Thank you for the update

Hi [Name],

Thank you for letting me know. I'm disappointed, but I genuinely enjoyed learning about the team and the work you're doing with [specific project].

If a similar role opens up, I'd welcome the chance to be considered. I was impressed by [specific thing], and I think my background in [relevant area] could be a strong fit for the right opportunity.

Wishing the team continued success.

Best, [Your Name]

Mistakes that hurt more than silence

Writing too much. The interviewer is busy. If your follow-up is four paragraphs, you've lost them. Say what you need to say and stop.

Being generic. "Thank you for the interview. I enjoyed learning about the company. I'm excited about the opportunity." That could go to any company for any role. It adds nothing. If your email doesn't reference something specific from the conversation, don't send it.

Sounding desperate. "I really want this job" raises red flags. Enthusiasm is good. Neediness is not. There's a line.

Relitigating your answers. Unless you said something factually wrong that could disqualify you, don't use the follow-up to redo the interview. "I realized I could have given a better answer to the SQL question" draws attention to a weakness the interviewer may have already forgotten.

Following up too many times. One thank-you after the interview. One check-in if you haven't heard back after the stated timeline. That's it. Three or more emails crosses a line.

When you don't hear back

Silence is frustrating. It's also normal. Hiring processes take longer than anyone estimates.

Day 1: Send your thank-you email.

One week past the stated timeline: Brief check-in. "Wanted to follow up on the [Role Title] position. Still very interested and would appreciate any update when you have a chance."

Two weeks past the stated timeline: One more. "Checking in on the [Role Title] role. I understand timelines shift. Just wanted to reiterate my interest."

After that: Stop. If two follow-ups beyond the stated timeline haven't gotten a response, the company has either moved forward with someone else or their process is significantly delayed. More emails won't change the outcome. Keep applying elsewhere.

One more thing

If writing the email feels hard while the interview is fresh, jot down two or three specific things from the conversation before you do anything else. The project they mentioned, the challenge they described, the thing that made you more interested in the role. You can turn those notes into an email later. But the details fade fast, and specificity is the entire difference between a follow-up that helps and one that gets deleted.

Four-Leaf's email assistant can help structure your notes into a polished draft if you're stuck. Same rule applies: use the output as a starting point, then make it yours.

---

Related reading:

• How to practice for interviews by yourself covers preparation techniques that will make you more confident walking out of the interview in the first place.