How to Follow Up After an Interview: The Full Sequence, With Templates

Send a short thank-you within 24 hours. Then wait for the date they gave you. If that date passes, send one status check. If that gets no reply, send one more a week later — and then stop. Two follow-ups, spaced and specific, is the entire method.

The whole sequence, at a glance

Most advice on how to follow up after an interview obsesses over wording. Wording matters far less than timing and restraint: the same email that reads as keen on day seven reads as anxious on day two. Here is the full cadence, assuming a standard process.

1. 1Before you leave the room (or the call): ask when they expect to decide, and who you should contact in the meantime.
2. 2Within 24 hours: a short thank-you to everyone you spoke with, each one different.
3. 3One business day after the date they gave you — or on business day seven if they gave you nothing: one status check, to the recruiter.
4. 4Seven business days after that: one final follow-up that gives them an easy out.
5. 5After that: stop. Keep applying elsewhere and let the role come back to you if it's going to.
6. 6If you're rejected: one gracious reply within 48 hours, aimed at the next opening rather than this one.

Everything below is the detail underneath those six lines: what each message should contain, what it should not, and how the sequence changes between a 25-minute recruiter screen and a final round with the person you'd report to.

The question that makes every later email easy

Almost every awkward follow-up traces back to the same missing piece of information: you don't know when a decision was supposed to happen, so you're guessing. Two questions asked in the last minute of the interview remove the guesswork entirely, and both are completely normal to ask.

• "What does the timeline look like from here — when do you expect to be making a decision?" The answer becomes the date your follow-up is anchored to. "End of next week" means you write on the Monday after.
• "Who's the best person for me to check in with, and how do you prefer I do it?" This one is worth more than it looks. It gets you a named contact, a channel, and implicit permission — so your later email is a thing you were invited to send, not an intrusion.

If you forgot to ask, don't invent a deadline. Default to seven business days after the interview for the first check-in. And if the recruiter volunteers something vague like "we're still early in the process," treat that as a longer timeline, not a shorter one — it usually means other candidates are still being scheduled.

Getting these questions out cleanly is a small performance in itself, and it belongs to the same skill as the opening — our guide to introducing yourself in an interview covers the first 90 seconds; this piece covers everything that happens after the last 90.

The thank-you note: within 24 hours, and short

The thank-you email is the only follow-up with a hard deadline. Send it the same day if you can, the next morning at the latest. After 48 hours it stops reading as gratitude and starts reading as an afterthought, which is worse than not sending one at all.

The most-cited data on this is old but still directionally useful: in a 2017 Accountemps survey of more than 300 HR managers at U.S. companies with 20 or more employees, 80% said thank-you messages are helpful when deciding whom to hire (22% "very helpful," 58% "somewhat helpful"), while only 24% of applicants were said to actually send one — down from 51% a decade earlier. Treat that as a floor, not a promise: no note has ever rescued a bad interview. But in a close call between two candidates, being one of the few who wrote is cheap leverage.

Why it has to be short

A long thank-you email invites re-evaluation. Every extra paragraph is another chance to raise a doubt, restate something you already said better in person, or sound like you're negotiating for a decision that hasn't been made. Four to six sentences is right. The reader should be able to take it in on a phone, at a glance, between meetings.

What one specific reference does that a generic thank-you cannot

A generic thank-you proves only that you know the convention. A specific one proves you were listening, and — more usefully — it re-plants a memory. Interviewers evaluate several people in a week and the conversations blur. Naming a concrete moment from yours reattaches your face to a topic rather than to a slot on a calendar.

• Generic: "Thank you for your time today. I'm very excited about the opportunity and I think I'd be a great fit for the team." This is indistinguishable from every other candidate's note.
• Specific: "The part about rebuilding onboarding before the platform migration is exactly the kind of sequencing problem I like — I ran into the same ordering question at my last company and would happily tell you how we got it wrong the first time." This one is unforgeable by anyone who wasn't in the room.
• Specific plus useful: add one sentence of substance you didn't get to say — the first question you'd ask in week one, or a comparable problem you've solved. It gives the interviewer something to quote when they advocate for you internally.

Subject: Thank you — [Role] interview<br><br>Hi [Name],<br><br>Thank you for the time this morning. I left more interested in the role than when I walked in, particularly the part about [specific thing they said].<br><br>One thought I didn't get to: [one sentence of real substance — an approach you'd try, or a comparable problem you've handled].<br><br>Happy to send [work sample / references] if that's useful at any point. Looking forward to hearing how the process goes.<br><br>Best,<br>[Your name]

When you met four people

Write four different emails. This matters more than it sounds: colleagues forward these to each other, and four identical notes with the names swapped is a worse signal than one note sent to the panel. Give each person the thing you actually discussed with them. If you only have one email address — often the recruiter's — send one message and ask them to pass on your thanks, naming each person and one detail each.

The status check: when the stated date comes and goes

This is the email most people get wrong, usually by sending it too early. Give the date they gave you one full business day of grace before you write. Internal delays are the norm, not a signal about you: a panel member is on leave, the budget approval slipped, two other candidates are still being scheduled.

It is worth knowing how long these processes genuinely take. SHRM's 2026 recruiting benchmarking reported a median of 39 calendar days to fill a nonexecutive role — down from 44 the previous year — and 45 days for executive roles. Ashby, analysing more than 54 million applications and 93,000 jobs from January 2021 through March 2026, found a median of 17.9 days from first to last interview for technical roles and 14.4 days for business roles. In other words: the interviewing stretch alone routinely runs two to three weeks, and the full process about six. Silence at day ten means almost nothing.

Three rules for this message. Reply inside the existing email thread rather than starting a new one, so the whole history is one click away. Reference the date they themselves named, which makes the email a response to their commitment rather than a demand. And ask a real question, so there is something concrete to answer.

Subject: Re: [Role] — interview on [date]<br><br>Hi [Name],<br><br>Following up on our conversation on [date]. You mentioned you expected to have an update around [date they gave] — I wanted to check where things stand.<br><br>I'm still very interested, and happy to provide anything else that would be helpful on your end.<br><br>Thanks,<br>[Your name]

Do not add new arguments for your candidacy here, do not attach a revised portfolio, and do not mention a competing offer you don't have. The only job of this email is to make replying take fifteen seconds.

The second follow-up, and where pestering actually begins

You get one more. Send it about seven business days after the status check went unanswered, and write it differently: this one should hand them an exit. Counter-intuitively, an email that makes it easy to say "the role is on hold" gets answered more often than one that only makes room for good news.

Hi [Name],<br><br>Checking in once more on the [Role] search. If the timeline has shifted or the role is on hold, that's genuinely fine — I'd just appreciate knowing so I can plan around it.<br><br>Either way, thank you for the time earlier this month. I'd welcome being considered for anything similar on the team down the line.<br><br>Best,<br>[Your name]

The line into pestering isn't a number of emails. It's a pattern. The same three behaviours are what turn a candidate from keen into difficult, and none of them is about volume alone:

• Cadence that tightens. Day 7, then day 14 reads as diligence. Day 3, then day 5, then day 6 reads as anxiety, no matter how politely each message is worded.
• Repetition with no new information. A second email that says exactly what the first one said tells the reader you weren't listening to the silence. Change the ask — from "where do things stand" to "should I assume this has moved on?"
• Channel escalation. Email, then LinkedIn, then a phone call, then a message to someone's colleague is the sequence that gets people marked as a problem. Pick one channel and stay on it unless you're invited elsewhere.

After the second follow-up, stop. Not because a third email would be rude in isolation, but because at that point you've learned what you needed to learn: this employer does not close loops. That is useful information about them, and your energy is better spent on the next application.

First screen versus final round: not the same follow-up

Calibrate the weight of your follow-up to the weight of the conversation. A 20-minute recruiter screen and a two-hour final round with your prospective manager are different social contracts, and treating them identically is the most common way candidates get the tone wrong in either direction.

After a first screen or recruiter call

Keep it to three sentences. The recruiter is managing dozens of candidates across several roles and is optimising for throughput; a long, effusive note after a 20-minute call is disproportionate and slightly odd. Confirm interest, confirm one logistical fact if there is one (salary range, location expectation, start date), and get out of their inbox. Follow up on status at day seven, not day three — screens are usually batched, and the recruiter is often waiting on a hiring manager who hasn't looked at the shortlist yet.

After a final round

Here the extra paragraph is earned. You've spent real time with people who will have opinions about you in a room you're not in, so give them something quotable. Address the concern you sensed but didn't fully resolve — if someone probed twice on whether you'd managed a team this size, say the number and the context plainly in writing. Note that after a final round the decision usually involves more people, so the timeline commonly slips even when everyone likes you. Extend your patience accordingly: check in one business day after the stated date, and give the second follow-up ten business days rather than seven.

Email the recruiter, or message the hiring manager on LinkedIn?

Default to email, to the person who has been coordinating with you. It's where the process lives, it's on the record, and it doesn't ask anyone to switch contexts. LinkedIn is the second channel, not the parallel one — and using both for the same message is the escalation that annoys people.

A few situations do justify LinkedIn. Use it when you have no email address for someone you clearly connected with, when the recruiter's address has bounced or they've left the company mid-process, or when the interview itself ended with something like "feel free to connect." What LinkedIn should never be is a second attempt at a message the recruiter hasn't answered yet.

Hi [Name] — thank you again for the conversation on [date] about the [Role]. I know [recruiter] is coordinating so I won't chase things here; I mainly wanted to say that the [specific detail] part of the job is exactly the work I want to be doing. Happy to answer anything else that comes up.

When a connection request is appropriate

After a substantive interview — a final round, a long panel, a conversation with the person you'd report to — a connection request with a short note is fine and often welcome. After a five-minute screening call with a recruiter you'll never speak to again, it's presumptuous. The test is simple: would this person recognise your name in their feed in six months? If yes, connect.

Keep the note to two sentences. LinkedIn caps the length of an invitation note, and it has repeatedly changed how many personalised invitations a free account can send — recent limits have been tight enough that a basic account gets only a handful of noted invitations a month. Check what your own account allows before planning anything longer. Short notes tend to be accepted more readily anyway.

[Name] — really enjoyed our conversation about [topic] on [date]. Would like to stay connected however the [Role] search lands.

One practical consequence of following up on LinkedIn: you are sending a hiring manager to your profile, at the exact moment they're forming a view of you. Most people never look at what that page communicates in the 90 seconds after a message lands. It's worth an hour — our complete guide to LinkedIn profile pictures covers what to fix first, while the 12 mistakes that cost interviews is the faster diagnostic if you just want to know whether your current photo is actively hurting you. If your photo is more than a few years old, how often to update your LinkedIn photo gives the honest rule.

What you wore to the interview is a separate problem with its own answers — interview outfits decided by the company you're interviewing at handles the in-person case and what to wear to a video interview handles what a webcam changes. This piece is only about the communication after the interview is over.

When the recruiter goes silent entirely

This is common enough that it needs its own plan rather than an emotional response. In an iHire survey of 1,024 job seekers published in October 2025, 53% said they had been ghosted by a prospective employer during their job search. The stage breakdown is the useful part: the most common point was after submitting an application (28%), but 20% were ghosted after a full interview and 16% after an initial phone screen.

So assume it's structural rather than personal. Roles get frozen, the internal candidate wins, the requisition gets absorbed into another team, or the recruiter left and nobody inherited the pipeline. None of that produces a polite closing email, because nobody in the company is measured on sending one.

Your last message, after the second follow-up has gone unanswered, should close the loop yourself. It's the only follow-up that reliably produces a reply, because it costs the recipient nothing but a correction if you're wrong.

Hi [Name],<br><br>I haven't heard back on the [Role] since [date], so I'll assume the team has gone in a different direction and stop following up. No hard feelings — I know how these processes go.<br><br>If that's not right and I'm still in consideration, just let me know and I'll keep my availability open.<br><br>Best,<br>[Your name]

Then actually stop. Two further things are worth doing, neither of which involves another email to the same person: keep your profile visible to recruiters searching for your title — the green frame versus recruiters-only decision matters more here than people think — and, if the company is one you genuinely want, set a reminder to check their careers page in eight weeks. Frozen requisitions reopen constantly, and a candidate who already interviewed is the cheapest hire on the shortlist.

Following up after a rejection, without sounding wounded

The rejection reply is the highest-leverage email in this whole sequence, and the one almost nobody sends. The person rejecting you already has your interview notes, has just confirmed you were credible enough to interview, and now has no decision to defend. That combination makes them unusually willing to help you later.

Reply within 48 hours, keep it to four sentences, and do three things: thank them without irony, name the specific thing you enjoyed, and state plainly that you'd like to be considered again. Ask for feedback softly and give them an explicit way to decline — many companies have a policy against giving it, and pressing turns a warm contact cold.

Hi [Name],<br><br>Thanks for letting me know, and for telling me directly rather than leaving it open — I appreciate that.<br><br>I really enjoyed the conversation about [specific thing], and I'd be glad to be considered if something similar opens up on the team. If there's one thing that would have made me a stronger candidate, I'd genuinely like to hear it — no obligation at all if that's not something you can share.<br><br>Best of luck with [project or team],<br>[Your name]

What actually keeps the door open is what you do in the months afterwards, not the email itself.

• Connect with the hiring manager, not just the recruiter. Recruiters change companies; the manager stays with the problem you'd have been hired to solve.
• Stay visible without performing. A thoughtful comment on something they post twice a year is enough. You are trying to remain a real person in their memory, not run a campaign.
• Re-apply deliberately. Three to six months is the normal interval for a different role at the same company; reapplying to the same role two weeks later reads as not having heard the answer.
• Bank the specifics. Write down, that week, what you were asked and where you stumbled. It is the only feedback you're guaranteed to get, and it's more accurate than the version you'll remember in a month.

The small mechanics that make every follow-up land better

None of these will win you a job on their own, but each of them removes a small reason for someone not to reply. Together they're the difference between a follow-up that feels frictionless and one that feels like a task on someone's list.

• Reply in the existing thread. A new email with a new subject line makes the recruiter search for context. A reply carries the whole history with it.
• Put the role in the subject line. Recruiters run several searches at once; "Following up" tells them nothing, "[Role] — interview on 14 May" tells them everything.
• Send Tuesday to Thursday, mid-morning. Monday inboxes are triage and Friday afternoons are abandoned. This is a small effect, but it's free.
• Don't attach anything unless asked. Attachments turn a fifteen-second reply into a five-minute task, and some corporate filters quarantine them entirely.
• Don't cc the whole panel. Individual notes, individual replies. Group follow-ups read as broadcasting.
• Don't phone unless the recruiter told you to. An unexpected call is an interruption you've asked someone to absorb on your behalf.
• Proofread the company name twice. The single most damaging typo in a follow-up email is the name of a company you're also interviewing with.

The last mechanic is the least technical and the most important: keep applying while you wait. Every unhealthy follow-up behaviour — the day-three email, the LinkedIn escalation, the third message — comes from having one live process and too much attention to spend on it. Candidates with four conversations running rarely send a bad follow-up, because they simply don't have the bandwidth to overthink any single one.