Home / Blog / Interview Thank-You Note After a Coding Round (With Templates)

Interview Thank-You Note After a Coding Round (With Templates)

Published 2026-10-05 · Luna Interview

Thank-you notes after technical interviews are a gray area. Some engineers say they never read them. Some recruiters appreciate them. Some candidates worry a note after a rough coding round will make it worse.

Here is the honest version: a thank-you note will rarely change a hiring decision on its own, especially after a coding round where interviewers submit structured feedback. But a short, specific, professional note costs you five minutes, keeps your relationship with the recruiter warm, and can leave a good final impression. This guide covers when to send an interview thank-you note after a coding round, who it goes to, and what to say.

Should you send one at all?

When in doubt, send it to the recruiter or coordinator. They are your main contact and can pass along thanks if appropriate.

When to send it

Within about 24 hours of the interview is a common, sensible window. Sending it the same evening is fine. Sending it a week later is less useful.

Do not send it during a multi-round day between interviews. Wait until the loop is finished.

What makes a good note after a coding round

Keep it to three to five sentences:

1. Thanks for their time.
2. One specific detail from the conversation: the problem, a follow-up, or something about the team.
3. Continued interest in the role.
4. Optional: a brief, relevant follow-up thought.

What to avoid:

• Long paragraphs about how much you want the job
• Apologizing for your performance
• Sending a full corrected solution unprompted
• Asking about the outcome in the same note
• Generic copy-paste text that could fit any company

Template 1: the round went well

Subject: Thank you, [Role] interview

Hi [Name],

Thank you for setting up today's coding interview. I enjoyed working through the [interval merging] problem with [Interviewer], especially the follow-up about handling a stream of new intervals. It made me even more interested in the [team/product] work. Please let me know if there's anything else you need from me.

Best,

[Your name]

Template 2: the round was rough

You do not need to pretend it went perfectly, and you should not apologize either.

Subject: Thank you, [Role] interview

Hi [Name],

Thanks for organizing today's interview. I appreciated [Interviewer]'s patience while we worked through the graph problem. I've been thinking about it since, and it was a good reminder to start with a simple BFS before optimizing. I'm still very interested in the role and the team.

Best,

[Your name]

This shows reflection without dwelling on the mistake. One sentence about what you learned is plenty.

Template 3: after an onsite or full loop

Subject: Thank you, [Role] onsite

Hi [Name],

Thank you for coordinating today's onsite. I enjoyed meeting [names or "the team"], and the system design conversation about [topic] was a highlight. Learning more about how the team [ships, tests, works with product] made me more excited about the role. Thanks again for making the day run smoothly.

Best,

[Your name]

Template 4: direct to the interviewer (only if appropriate)

Use only if they gave you their contact or the company encourages it.

Hi [Interviewer],

Thanks for the interview today. I enjoyed the [string parsing] problem, particularly your question about unicode input. I hadn't thought about that case before, and I've been reading about it since. I hope to work with you.

Best,

[Your name]

Should you include a corrected solution?

Usually no. Unrequested code can come across as trying to re-take the round, and many interviewers have already submitted feedback.

Exceptions:

• The interviewer or recruiter explicitly said you could send follow-up thoughts.
• It is a take-home or a round where follow-up was part of the format.

If you do, keep it short: one or two sentences describing the better approach, or a link to a small gist if it was invited. Never imply the original round should be regraded.

Where to mention what you learned

A one-sentence reflection can be useful, particularly after a rough round:

• "It was a good reminder to ask about input size before choosing an approach."
• "I've been practicing dry-running edge cases out loud since."

This is about showing self-awareness, not asking for a second chance.

Tone and format tips

• Use the same email thread the recruiter used if possible.
• Plain text, no attachments.
• Proofread names and the company spelling.
• Match their formality. If they are casual, you can be a bit less formal.
• One note per round is enough; do not send follow-ups to your follow-up.

Common mistakes

• Sending nothing to the recruiter because "engineers don't read them"
• Writing an essay
• Apologizing ("Sorry I was so slow on the second problem")
• Asking "Did I pass?"
• Messaging interviewers on social networks without an invitation
• Sending the same generic note to every company

Soft practice note

The best follow-up note is the one you write after a round you felt prepared for. If you want a Chrome side panel to rehearse coding rounds out loud before the real thing, Luna Interview is built for calm, structured practice. It is for preparation, not for anything that breaks interview rules.

Day-of checklist (after the round)

• [ ] Note sent within about 24 hours
• [ ] Addressed to the recruiter (and interviewer only if appropriate)
• [ ] Three to five sentences
• [ ] One specific detail from the conversation
• [ ] No apology, no outcome question, no unrequested code
• [ ] Names and company spelled correctly
• [ ] Then close the laptop and stop replaying the round

A good thank-you note will not rescue a round or make one, but it is a small, professional finish that keeps the door open.

Rehearse with an AI interview copilot, then browse commonly reported interview questions.