Clear the rounds

Thank-You Emails: 3 Templates + Guide

Aarav and Riya interviewed at the same product company off campus, the same Thursday. Riya sent four lines that evening naming the caching question. Aarav sent nothing. Two weeks later the recruiter wrote to Riya first. It did not win the offer. It won the tie.

9 min readFree, no email neededUpdated 11 September 2026

Before you write anything

Does it matter in India?

📩

Send one

Off-campus applications and referrals.

Product companies and startups.

Any round where one or two people decide.

The final round with a manager.

Do not bother

A campus drive with 400 students and one HR panel.

Aptitude and online coding rounds with no interviewer.

Mass hiring run off a spreadsheet.

When you have no address, only a placement coordinator.

WhenThe same evening, never later than 24 hours. On a day with three rounds, send one mail after the last round, not one after each.

To whomThe person who interviewed you. Two interviewers, two separate mails. If you only have the recruiter, write to them and ask them to pass it on.

The addressUsually in the calendar invite, under organiser and attendees. Otherwise ask at the end of the call: "May I have your email address to send a note after this?" Guessing firstname.lastname@company.com is a last resort.

The four-line structure

A thank-you email is four lines long. Every extra paragraph makes it weaker.

1Thank them, and name the round"Thank you for the fifty minutes this afternoon."It dates the mail and tells them which of today's six candidates you are.

2One specific thing from the conversation"Your follow-up on the meeting-rooms problem stayed with me: what changes if the intervals already arrive sorted."The only line that proves the mail is not a template. Write three keywords down the moment the call ends.

3What it changed, or one line of fit"I wrote both versions after the call — the min-heap one, and the O(n) sweep."A fresher who acts beats a fresher who flatters. Only write it if you did it; they may ask.

4A soft close"Thank you again for your time."No result-chasing, no "eagerly awaiting your positive response", no attachments unless asked for.

The subject line, every timeThank you — Technical round, Software Engineer (Fresher), Aarav Sharma

120 to 150 words, plain text, inside the existing thread if there is one. Signature: name, degree and year, phone, GitHub, LinkedIn — never "Sent from my phone".

Template 1 · Word file included

After the technical round

To rohit.nair@zenviatech.com · Cc priya.menon@zenviatech.com (the recruiter) · Sent 8:40 p.m., the same evening

Subject: Thank you — Technical round, Software Engineer (Fresher), Aarav Sharma

Dear Rohit,

Thank you for the fifty minutes this afternoon. I came in expecting a test and got a discussion, which I enjoyed a lot more.

Line 1. Names the length and the time of day, so he knows exactly which conversation this is. No "esteemed", no "honour".

Your follow-up on the meeting-rooms problem stayed with me: what changes if the intervals already arrive sorted. I went back and wrote both versions after the call — the min-heap one at O(n log n), and the O(n) sweep for pre-sorted input. They are at github.com/aaravsharma/dsa-notes if you ever want to look, though I mostly wrote them for myself.

Line 2 and 3. The specific thing, then the proof he acted on it. "Though I mostly wrote them for myself" keeps it from sounding like homework submitted for marks. The link is offered, not pushed.

The round made me more sure about the kind of work I want. Java and Spring Boot are what I have been building in for the past year, and backend systems like the ones you described are where I would like to keep going.

Line 4. One line of fit, in his words ("backend systems"), not a paragraph about your dreams.

Thank you again for your time.

Aarav Sharma
B.Tech Computer Science, 2027 · XYZ Institute of Technology, Bengaluru
+91 98765 43210 · aarav.sharma26@gmail.com
github.com/aaravsharma · linkedin.com/in/aaravsharma · aaravsharma.dev

Word file: Thank_You_After_Technical_Round.docx — the same email, ready to edit, with a short "what to change" list at the bottom of the page. Word count: 135.

Template 2 · Word file included

After the HR round

To priya.menon@zenviatech.com · Sent 7:10 p.m., the same evening

Subject: Thank you — HR round, Software Engineer (Fresher), Aarav Sharma

Dear Ms. Menon,

Thank you for the call at four o'clock today, and for answering my questions properly instead of only asking your own.

Line 1. HR rounds are usually short and back to back. The time of the call is how she finds you among nine calls.

What you explained about the six-month training in Chennai and the buddy assigned to every new joiner answered the one thing I was unsure about, which was how a fresher gets up to speed at Zenvia. To confirm what I said on the call: I am comfortable relocating to Chennai, I have no active backlogs, and I can join from June 2027.

Line 2 and 3. The specific thing she told you, then the three facts every Indian HR file needs: location, backlogs, joining date. Repeat only what you already said on the call. Never open the salary conversation here.

I have attached the semester mark sheets and the ID proof you asked for. If anything else is needed for the file, please tell me and I will send it the same day.

Line 4. Attachments only because she asked for them. "The same day" is a small promise you can keep, and recruiters remember who kept it.

Thank you again for your time.

Word file: Thank_You_After_HR_Round.docx — the same email, ready to edit, with a short "what to change" list at the bottom of the page. Word count: 125.

Template 3 · Word file included

After the final round

To karthik.iyer@zenviatech.com · Cc priya.menon@zenviatech.com · Sent 9:05 p.m., the same evening

Subject: Thank you — Final round, Software Engineer (Fresher), Aarav Sharma

Dear Karthik,

Thank you for this evening. The final round felt more like a design conversation than an interview, and I left with two pages of notes.

Line 1. A manager's round is a conversation, so the thank-you sounds like one. "Two pages of notes" is a detail only a real listener would write.

The case you gave me — a user taps Pay twice and gets charged twice — is one I had only half-solved in my own project. I read up on idempotency keys properly after the call and added one to the payment endpoint in SplitEase last night; the second request now returns the first result instead of creating a new transfer. Your point about not shipping a payments change on a Friday evening is going straight into how I work.

Line 2 and 3. The strongest thing a fresher can send: you changed real code between the interview and the email. One night, one endpoint, one sentence about it.

If the team decides to go ahead, I would be glad to start in Payments and can join from June 2027. Thank you for the time you and the panel gave me today.

Line 4. "If the team decides to go ahead" leaves the decision with him. It is not "please select me" and it is not "when will I hear back".

Word file: Thank_You_After_Final_Round.docx — the same email, ready to edit, with a short "what to change" list at the bottom of the page. Word count: 146.

8 mistakes

Every one of these is more common than a good thank-you email. Numbers 1, 3 and 4 are the ones recruiters mention.

Too long.Over 150 words it becomes a second interview nobody asked for. Four short paragraphs, then stop.
Flattery instead of content."It was an honour to interact with such an esteemed panel" says nothing. One specific line about the round beats ten adjectives.
Asking for the result."When can I expect to hear back?" turns a thank-you into a demand. Ask that at the end of the interview, or wait a week and send the follow-up on the next page.
One mail to everyone.Eight names in the To line is a circular. One person, one mail, with the recruiter in Cc at most.
Sending it twice.One thank-you per round. A second mail the same evening because you forgot a point reads as anxious. Let it go.
Sending the template unchanged.If two students from your college send the same words, both are ignored. The specific line has to be yours.
A careless sender.coolboy_2003@gmail.com, no signature, "Sent from my phone", or the previous company's name still in the text. Read it once before sending.
Rewriting the answer you fumbled.One clean line is allowed: "the O(n) version I could not get to in the call is in the repo now." Three paragraphs of correction says you are still in the interview.

The one polite follow-up

No reply after a week

Silence in Indian hiring usually means the process is slow, not that you are rejected. Wait seven working days from the last round, or one day past the date they promised, and then send exactly one follow-up — to the recruiter, not the interviewer, inside the same email thread.

To priya.menon@zenviatech.com · Reply inside the original thread · Sent Tuesday, 11 a.m.

Subject: Following up — Software Engineer (Fresher), Aarav Sharma

Dear Ms. Menon,

I hope you are doing well. I interviewed for the Software Engineer (Fresher) role on 12 September and wanted to check where the process stands.

I am still very interested in the role, and happy to share anything else the team needs from my side. If the decision is likely to take longer, even a rough timeline would help me plan my other conversations.

Thank you for your help.

Aarav Sharma · +91 98765 43210 · aarav.sharma26@gmail.com

One follow-up. If there is still no reply, one more after two weeks, and then stop and keep applying.
Never "as per my last email", never "urgent", never a WhatsApp message at 11 p.m.
If you have another offer with a deadline, say it in one plain line. It is the only thing that genuinely speeds a process up.

Want this on your phone?

Everything above, as a PDF built to read on a phone the morning of the interview. It costs nothing — we ask for an email so we can send it, and that is all.

Get the PDF, free See every guide