The thank-you email isn't a formality. It's a last, low-effort chance to move a 'probably yes' into a 'definitely yes' — and more importantly, it's a chance to address any weakness you felt in the interview before the debrief happens. Here's the exact structure that works in 2026.

Timing: within 4 hours

Send the thank-you the same day, within 4 hours of the interview ending. Most debriefs happen within 24 hours — if your note arrives after the debrief, it's too late to influence the decision.

Subject line

Two formats that work:

  • 'Thanks for today, [Name]' — conversational, high open rate
  • 'Following up on our [role] conversation' — more formal, for executive-level interviews

Avoid the generic 'Thank you for your time' — it reads as boilerplate before they open.

The four-paragraph template

Paragraph 1: Thank them, name one specific thing from the conversation that stuck with you.

Paragraph 2: Address one follow-up to a question you weren't 100% happy with — 'I thought more about your question on X, and one thing I didn't mention…'

Paragraph 3: Reaffirm your excitement with one specific reason — a project they mentioned, a team challenge, a product direction.

Paragraph 4: Close with a clear next step — 'Let me know if there's anything else that would be helpful. Happy to [share a sample / connect with X / do a follow-up].'

The follow-up save
Paragraph 2 is the secret weapon. If you fumbled a question or gave a weak answer, this is your chance to add the missing context — which is often what tips the interviewer in your favor at debrief.

Example: software engineering interview

Hi Maya, Thanks so much for the conversation today — really enjoyed getting into the design of your event-driven architecture, and the tradeoff you walked me through on at-least-once vs. exactly-once delivery was the most interesting part of my week. One thing I wanted to circle back on: when you asked how I'd approach the backfill problem, I gave you the straightforward 'replay from Kafka' answer, but I didn't mention that I'd also want to short-circuit duplicate side effects with an idempotency key on the consumer. That's what I did at [previous company] for the order pipeline, and it's what I'd likely reach for here. I'm more excited about this role after today than I was going in — the scope of what your team owns is exactly the kind of problem space I'm looking for. Happy to share the design doc I wrote for the pipeline at [previous company] if it would be useful. Otherwise, looking forward to hearing about next steps. Best, Alex

Send to everyone, but vary the content

If you interviewed with three people, send three separate notes — not a group email. Each should reference something specific to that person's conversation. The recipients will compare notes, so identical emails read as lazy.

What NOT to do

  1. Send the same copy-paste email to three interviewers — they compare notes
  2. Send a LinkedIn connection request with a thank-you in the note — use email
  3. Attach files unless specifically asked — they won't open attachments from a candidate
  4. Write more than 200 words — they'll skim the subject line and the first sentence only
  5. Apologize for any part of the interview — it draws attention to weakness they may not have noticed