Follow-Up Email After an IT Interview: 6 Samples That Work

A good follow-up email after an IT interview is short, specific and sent at the right time: a thank-you note within 24 hours that mentions one real detail from the conversation, then a polite status check only after the timeline they gave you has passed, usually about a week. Keep it under 120 words, use a clear subject line with the role and your name, and never sound desperate or demanding. Below are six follow-up email samples for IT interviews you can copy and adjust.

Most applicants in the Philippines either never follow up or follow up too much. Neither helps. One well-timed, specific email won't turn a weak interview into an offer, but it can keep you top of mind when two candidates are close, and it shows the professional communication IT teams care about, since half of IT work is written updates.

Should you send a follow-up email after an IT interview?

Yes. Send a short thank-you within a day of every interview, and one status follow-up if the promised timeline passes. It's a small courtesy that takes five minutes. Interviewers in IT services firms, BPO IT departments and startups talk to many candidates in a week, so a clear note with a detail from your conversation helps them remember which one you were.

What a follow-up email won't do: change a decision that's already made, or make up for a technical round that went badly. Think of it as good manners plus a reminder, not a second interview.

When to send each follow-up

Timing matters more than wording. Use this as your schedule:

1. Same day or next morning: a thank-you email to the interviewer or recruiter.
2. When their stated timeline passes: if they said "you'll hear from us within a week," wait a week plus one or two working days, then send a status check.
3. No timeline given: wait about a week, then check in once.
4. Still nothing a week after that: one final short note, then move on in your tracker and keep applying.
5. If you get another offer: follow up right away, even mid-process.

Send emails during working hours in the company's time zone, Monday to Thursday if possible. A 2 AM email after your night shift ends can wait in drafts until morning. Gmail's schedule send helps here.

Who should you send it to?

Send it to the person who interviewed you, or the recruiter who scheduled it if you don't have the interviewer's email. If there were two or three interviewers, you can send one email to the recruiter and ask them to pass on your thanks, or send short separate notes that each mention something different. Get email addresses at the end of the interview. "May I have your email in case I have follow-up questions?" is a normal thing to ask.

What subject line should a follow-up email have?

Use a plain subject line that says what the email is, the role, and your name, so the recruiter can find it later in a crowded inbox. Recruiters search their email by candidate name and role all the time, so give them both. Good patterns:

• Thank you, IT Support Associate interview, Mark Dela Cruz
• Following up, QA Tester interview on Oct 14
• Update on my application, Junior Developer, Bea Lim
• Re: (reply in the same thread the recruiter started, if there is one)

Replying inside the existing email thread is often the best option, since the whole history stays in one place. Avoid subject lines like "Hello po," "Urgent," or "Any update???" They look like spam or pressure. Also check the basics before you hit send: your email address should be a professional one (first name and last name, not a nickname from high school), and your signature should have your phone number so they can call you directly.

Six follow-up email samples for IT interviews

Each sample below is written for a real situation Filipino IT applicants run into. Change the names, dates and details to match yours, and keep the length.

Sample 1: the same-day thank-you email

Subject: Thank you, IT Support Associate interview, Mark Dela Cruz

Hi Ms. Reyes,

Thank you for taking the time to talk with me today about
the IT Support Associate role. I enjoyed hearing how your
team handles onboarding for new hires across the Manila
and Cebu offices.

Our conversation about password reset volume made me even
more interested. It's the kind of repetitive issue I'd like
to help document clearly so users can solve it faster.

I'm happy to send anything else you need. Thank you again.

Best regards,
Mark Dela Cruz
0917 000 0000

The second paragraph is what makes it work. Mention one real thing from the interview. A generic "thank you for the opportunity, I look forward to hearing from you" is fine but forgettable.

Sample 2: following up when you haven't heard back

Subject: Following up, QA Tester interview on Oct 14

Hi Mr. Tan,

I hope your week is going well. I'm following up on my
interview for the Junior QA Tester role last October 14.
I'm still very interested, especially in the e-commerce
testing your team does.

May I ask if there's an update on the timeline? Thank you
for your time.

Best regards,
Ana Santos

Short, polite, no guilt-tripping. Don't write "I haven't received any response" or "I've been waiting." Busy recruiters respond better to a light nudge.

Sample 3: after a technical interview where you fumbled a question

Subject: Thank you, and a follow-up on the DNS question

Hi Paolo,

Thank you for the technical interview today. I appreciated
the scenario questions, they felt like real tickets.

I wanted to follow up on the question about a user who can
reach websites by IP but not by name. I said "check the
network," but the clearer answer is that it points to DNS.
I'd check the DNS server settings with ipconfig /all, try
nslookup, and flush the cache with ipconfig /flushdns.

Thanks again for your time.

Best,
Ana Santos

Use this only once, for one question, and only if your correction is short and right. It shows you reflect and learn, which teams value in junior hires. Don't rewrite the whole interview. For common questions to prepare, see our IT support interview questions and technical interview tips.

Sample 4: when you have another offer

Subject: Update on my application, Junior Developer, Bea Lim

Hi Ms. Cruz,

Thank you again for the interview last week. I wanted to
let you know that I've received another offer and have
been asked to reply by Friday, October 24.

Your team is still my first choice because of the mentoring
setup you described. Is there any chance of an update
before then? I completely understand if the timing doesn't
work.

Best regards,
Bea Lim

Only send this if the other offer is real. Inventing one to speed things up can backfire badly, since HR may simply say "go ahead and accept it." If both offers come through, our post on negotiating your first IT job offer helps you compare the full packages.

Sample 5: replying to a rejection

Subject: Re: Your application for IT Support Associate

Hi Ms. Reyes,

Thank you for letting me know, and for the time your team
spent with me. I'd appreciate any feedback you can share
on how I could improve.

I'd be glad to be considered for future openings. Best of
luck with the role.

Best regards,
Mark Dela Cruz

Many companies won't give detailed feedback, and that's okay. A gracious reply keeps the door open. Recruiters do sometimes come back to good runner-up candidates when another role opens.

Sample 6: a LinkedIn message instead of email

If you only have the interviewer's LinkedIn, send a connection request with a short note (LinkedIn limits the length):

Hi Ms. Reyes, thank you for the interview today for the IT
Support Associate role. I enjoyed learning about your
onboarding process across offices. I'd like to stay
connected.

Follow-up mistakes to avoid

• Following up every two days. It reads as pressure. One thank-you, one status check, one final note at most.
• Writing a wall of text. Under 120 words. Recruiters read on their phones between calls.
• Copy-paste errors. The wrong name or company in a follow-up hurts more than no follow-up. Read it once before sending.
• Messaging on Facebook or personal numbers unless they gave them to you for that purpose. Stick to email, LinkedIn or the channel the recruiter used.
• Stopping your search while you wait. Keep applying until you've signed an offer. Log every follow-up in your job tracker so you don't lose count.

Writing these emails is easy once you have a template. The harder part is having something specific to say, which comes from a good conversation, which comes from practice. In the Career Shifter Track you do two mock interviews, in weeks 5 and 6, with a coach's written feedback, and the week 6 application plan sets aside a Friday slot for follow-ups on applications older than 7 to 10 days, so it becomes routine instead of guesswork. Try a lesson first at the free career shifter preview, or get the free IT Job Starter Kit. If you're still on the earlier stage, the HR interview questions post covers the round before this email.

Frequently asked questions

How soon should I send a thank-you email after an IT interview?

Send it the same day or the next morning, within 24 hours. Send it during the company's working hours if you can.

How long should I wait before following up on an interview?

Wait until the timeline they gave you has passed, plus one or two working days. If they gave no timeline, wait about a week before one polite check-in.

Is it okay to follow up through LinkedIn instead of email?

Yes, if you don't have the interviewer's email or the recruiter has been using LinkedIn with you. Keep the message short and professional.

What if I don't hear back after two follow-ups?

Stop following up and treat it as a likely no, while staying open if they reply later. Put your energy into new applications.

Should I send a follow-up email after an HR screening call?

A short thank-you is a nice touch but optional for a quick screening call. Always send one after a full interview with HR or the hiring team.