How to Write a Follow-Up Email After an Interview

You want to know how to write a follow-up email that wins a reply. Here is a clear way to do it. Keep it short, kind, and packed with real value.

How to Write a Follow-Up Email: A Value-First Plan

You asked how to send a follow-up that stands out. Use this five-part plan. It takes five minutes and keeps your note tight.

• Subject with one clear goal
• Thanks plus one line of value
• Proof in one short line
• One ask, not three
• Easy close with next step

1) Pick the right goal

First, choose your goal. Do you want to thank, add proof, or ask for the next step? Pick one. Then write it at the top of your draft. This keeps the note on track.

2) Write a tight subject line

Use seven words or less. Aim for clear, not cute.

• Thanks + next step on design role
• Quick note on the API plan we discussed
• One idea to cut ticket time 15%
• Small sample: dashboard chart fix

3) Lead with thanks and value

Start with one warm line. Then add a useful insight. Keep both lines short.

• Thank you for your time today.
• I ran the numbers from your case. Here is a 10% cut plan.

4) Add proof in one line

Show, do not tell. Share a link to a tiny sample, repo, or doc. Make it easy to view on a phone.

• Here is a 3-slide draft with the steps.
• Code diff with comments: link in the doc.

For timing tips and more cases, see this guide. It covers when to send and how often. This post stays on what to write.

Make it personal with notes and value

Use the words the team used. Name the tools and pain. Tie your skill to one hard thing they face.

• You use Figma and run weekly crit. I do the same.
• You ship in two-week sprints. I can join that pace.
• You track MTTR. I have cut it by 30% before.

Also, add one micro sample. Think 5–10 minutes of work. A one page doc, a small query, or a test plan. Link to a public file or a view-only doc. Do not ask them to sign in.

Subject lines that get opens

Match the subject to your goal. Try one of these:

• Next step + small idea on onboarding
• Thank you — notes from our data chat
• Sketch: improve checkout tap count
• Two risks I can own in week one
• Brief recap + one metric to watch

Short template you can use

Copy, paste, and tweak the lines to fit your chat. Keep each line tight.

Subject: Quick note on [topic you discussed]

Hi [Name],

Thanks for the talk about [role] today. I enjoyed it.

You raised [pain point]. I made a small draft that may help.

[One line on what you made] — link: [URL]

Here is proof this works: [one metric, result, or short win].

Are you free this week to chat next steps?

Thanks,
[Your Name] | [Phone] | [LinkedIn]

Want to drill your pitch lines before you send? You can start practicing with live prompts and instant tips.

Common mistakes to avoid

• Long walls of text. Aim for 120–180 words.
• Vague claims. Add one number or link as proof.
• Three asks in one note. Use one clear ask.
• Big files or strange links. Share a light, open link.
• Stiff tone. Write like you talk at work.
• New subject thread. Reply on the same thread when you can.

Send to the right people

Reply to the last thread when you have it. CC the recruiter if they run the process. Keep the list small. Two to three people is enough. If you met a panel, send one note to your main contact. Then send a short thank you to each person you met.

When and how to follow up again

Wait five to seven days if you do not hear back. Then send one short nudge. Be kind. Share one new proof point, not the same one. Finally, if there is no reply after that, you can pause or move on. If you want more advice on tone and timing, read this post.

Bring it all together

Now you can write a strong follow-up that earns replies. Keep it short. Start with thanks. Add one clear value line. Share proof. Ask for one next step. Want more tips and tools? Check the latest posts on Interviewseek’s blog and then practice your pitch before you hit send.