The subject line for a thank-you email

Reply to the existing thread. When there is no thread, four subject lines that work, the four patterns that read as spam, and why the third line of the email is the part that decides anything.

Last reviewed

The short answer

Reply to the existing thread. If there is no thread, the subject is “Thank you — [Role] interview” and you should spend the rest of your effort on the two lines that actually decide anything.

The subject line is a routing label. It has one job: make the email findable and obviously not spam, in an inbox where the reader is on their fourth interview of the day. Nobody has ever been hired because of one, and a clever one is a small risk with no upside.

The best answer is not to write one

If the interviewer emailed you the calendar invite or the scheduling confirmation, hit reply on that. You inherit the subject, the thread and the context, and your note lands underneath the conversation it belongs to rather than as a stray email the reader has to place.

This matters more than the wording. A recruiter running a pipeline sorts by candidate, and a threaded reply files itself.

Inbox

  • Rahul Mehta

    Re: Interview — Backend Engineer, Wed 11:00

    Thanks for the conversation today. On the rate-limiter question…

  • LinkedIn

    You appeared in 9 searches this week

    See who's looking at your profile…

  • Rahul Mehta

    Quick question!!

    Hi, just wanted to reach out and say thank you so much for…

  • Priya S.

    Thank you — Product Designer interview

    Thank you for walking me through the onboarding redesign…

What a hiring manager's inbox looks like at 6pm. The threaded reply and the plain label get opened; “Quick question!!” looks like everything else they are ignoring.

When you do need to write one

Usually because you got the address from a business card, a signature, or a colleague. Then: name the thing, name the role, stop.

  • Thank you — Backend Engineer interview
  • Thanks for your time today — Product Designer role
  • Following up on our conversation — Analyst position
  • Thank you, Priya — Wednesday’s interview

By situation

AfterSubject line
A recruiter phone screenThanks for the call — [Role] at [Company]
A hiring-manager interviewThank you — [Role] interview
A panel (one email each)Thank you, [First name] — [Role] panel
A technical or case roundThanks for today — and the [problem] follow-up
The final roundThank you — final interview, [Role]
An informal coffee or referral chatThanks for the chat, [First name]
A video interview that dropped or ran overThank you — and the answer I ran out of time for

All of these are fine. Pick one, do not agonise. If you interviewed with four people, send four separate emails with the same subject — not one email with four names in the To field.

What not to put in it

  • Nothing that reads as a sales email. “Quick question”, “Following up!!”, “Re:” on an email that is not a reply. These are the exact patterns spam filters and busy people both discount.
  • No pitch. “Why I’m the right fit for Backend Engineer” makes the reader defensive before they open it.
  • No urgency you do not have. “Time-sensitive” is false and reads as false.
  • Nothing longer than about eight words. Mobile clients truncate, and the useful half is the front.

Discounted on sight

Following up!! / Why I'm the right fit for Backend Engineer / Time-sensitive: interview follow-up

Opened

Thank you — Backend Engineer interview
Under eight words, no punctuation doing the shouting, and the role name in the first half so a phone does not truncate it.

The part that actually matters

The subject gets it opened. The third line decides whether it did anything. That line is one specific piece of evidence — the answer you wish you had given, the link to the thing you mentioned, the follow-up thought on their problem.

Email · to Rahul Mehta

Subject: Thank you — Backend Engineer interview

Hi Rahul,

Thank you for the time today, and for the detail on how the payments team is splitting the monolith.

On the rate-limiter question — I said token bucket, but for the burst pattern you described, a sliding-window log is the better fit. I wrote up the trade-off in half a page here: [link].

Looking forward to hearing about next steps.

Asha

The third paragraph is the whole email. Everything else is courtesy. The thank-you email after an interview has a full version you can send and the rules that keep it from reading as a template.

Timing

Within 24 hours, during working hours where the reader is. A note that arrives at 2am reads as anxious, and one that arrives four days later reads as an afterthought. If you interviewed on a Friday evening, Monday morning is fine and better than Saturday.

And if nothing comes back

A thank-you email is not a follow-up and should not be treated as one. Silence after it is normal and usually means the process is slower than they said it would be. What to send when there is no reply covers the second message — when to send it, and what to do with the answer.

Read next

  • No reply after the interview: what to send

    Their date plus two working days, four lines, to the person who owns the process. A version you can send, the closing note that ends the waiting, and what silence actually means.

  • Referral messages you can copy

    Three messages for three distances — a former colleague, a near stranger, a cold LinkedIn request — plus the third-person paragraph to hand your referrer so they do not have to write one.

  • How many skills should a resume list?

    Eight to fifteen, grouped, every one defensible in an interview. The count by career stage, the four things to cut first, and why the bullets are where the keyword match is actually won.