A thank-you email is the easy part. The hard part is the email you send after — the one where the interview went fine, the manager said "we'll be in touch by Friday," and then it is the following Wednesday and you have heard nothing. Send that nudge wrong and you look needy. Send it too late and the requisition is filled.
Over ten weeks this spring I tracked 40 of these silence-breaking follow-ups across real job loops — same seniority band, same role mix — and recorded which ones got a human reply and which ones vanished. The single biggest lever was not the wording. It was when the email landed. A day-7 nudge with one piece of new information replied at roughly three times the rate of an anxious day-2 nudge.
Below is the data, the timing rule I now follow, and what surprised me.
How the sample was collected
Forty post-interview follow-ups, all sent after a real interview where the candidate had been given a timeline ("we'll get back to you by X") or had passed a round with no timeline and then hit silence. Companies sat in the 50–2000 employee band, US and EU. Role mix: software engineering (24), data (10), product (6). I either sat the loop myself or coached the candidate and drafted the follow-up with them, so I saw both the send and the response thread.
"Reply" means a human at the company responded with something other than an out-of-office auto-reply — a status line ("still finalizing, end of next week"), a substantive note, or a next-step. "Silence" means nothing within 7 days of the nudge. I did not count a follow-up as a success just because an offer eventually came; offers move on the recruiting team's own clock and I could not cleanly attribute them to the nudge. Reply rate is the honest metric here.
The standard advice — wait about a week, keep it short, be polite — is well covered by Indeed's follow-up guidance and The Muse's recruiter-sourced version, but neither breaks the outcome down by exact day or by whether you add something to the thread. That gap is what I was trying to fill.
Reply rate by timing
The curve is not linear and that surprised me. Nudging too early (day 1–2) replied worst of all four windows — worse even than waiting almost two weeks. The day-6–8 window was the clear peak. Pushing past day 12 brought the rate back down, partly because by then several of those roles had simply been filled and the reply, when it came, was a rejection.
My read: a nudge that lands one or two days after the promised date reads as impatience. Hiring slips by a few days constantly — interviewers are out, a panel member is traveling, an approval is pending — and the candidate who pings on day 2 signals they do not understand how the process breathes. By day 6–8 the delay is real enough that a check-in is reasonable, the manager often feels a small amount of guilt about the silence, and the email gives them a low-friction place to discharge it. That guilt window is the thing you are actually aiming for.
The content shape mattered almost as much
Within the day-6–8 peak window, I split sends between a pure status-check ("just checking in on where things stand") and a status-check plus one new thing — a relevant piece of work, a short answer to something raised in the loop, or a genuinely new data point about my situation (a competing timeline, a project shipped). The plus-new-information version replied at 6 of 7; the pure status-check replied at 2 of 5. Same week, same opener shape, different outcome — because the new information gives the thread a reason to exist beyond your anxiety.
The version that worked was three sentences of substance. It names the role (recruiters run several at once), states continued interest without grovelling, drops one concrete new fact that reopens the thread, and asks for a timing update rather than a yes/no. The "happy to share the write-up" line is the hook — it gives the manager a reason to reply that is not "tell the candidate no."
The version that got me shut down
For contrast, the day-2, multi-paragraph, high-anxiety follow-up I sent early in the experiment — before the timing data was in — got a reply, but the reply ended the conversation:
Hi Charlie — we're still in process and will reach out when we have an update. No need to follow up again before then.
That is a polite block. It read as needy because it was sent before the timeline had even lapsed, it carried no new information, and the exclamation density signalled anxiety rather than confidence. Two of the day-1–2 sends got this exact kind of "please stop" reply. None of the day-6–8 sends did.
What I expected to find that was not there
Three priors did not survive the data. First, "send it the morning after the deadline so you're top of the inbox" — false; the day-1–2 window was the worst performer, not the best. Second, warmth and enthusiasm move the needle — within a window, the enthusiastic-tone sends did slightly worse than the concise ones, because enthusiasm at the follow-up stage reads as pressure, not interest. Third, following up through the recruiter is always safer than the hiring manager — recruiters replied at about the same rate but with vaguer information; when I had a direct hiring-manager thread from a good thank-you email, the follow-up there got more specific answers.
The timing rule I now follow
- Do not nudge before the promised date has actually passed, and give it at least a couple of business days of slack after that. A nudge inside the promised window is the single fastest way to look impatient. If no date was given, count from the interview and wait a full week.
- Aim the first nudge at roughly day 6–8 past the expected response. That is the window where the delay is real, the manager feels mild guilt, and a check-in is clearly reasonable rather than anxious.
- Bring one new thing. A shipped project, a short answer to something from the loop, a genuine competing-timeline update. The new information is the difference between a 67% reply and a 40% reply in the same week.
- Keep it to three or four sentences and ask for a timing update, not a decision. "When you have an update on timing" gives the manager an easy, non-final thing to reply with.
- One nudge, then a single second one around day 12–14 if still silent. Beyond two, you are training the manager to dread your name. If the role is gone, it is gone.
To keep the structure constant across all 40 sends — instead of over-writing each one under the emotional load of waiting — I drafted most of them with a free interview-follow-up email generator (no signup, runs in the browser) and then edited in the one specific detail. The full study, both complete email templates, and that generator are on the original post linked below.
Methodology footnote
Forty follow-ups is a small sample and the timing groups were not randomized — they reflect when each real loop happened to go silent, so the windows are observational rather than a controlled trial. Reply-rate differences between adjacent windows (40% vs 67%) are inside the noise band for cells of 10–12; the trustworthy signal is the shape of the curve (early-nudge worst, day-6–8 best, very-late tapering) and the within-window content effect, both of which held up across role types. Roles were software / data / product; client-facing or non-technical roles may follow a different rhythm. Reply rate, not offer rate, is the metric — they correlate but are not the same thing.
Originally published on charliemorrison.dev, where the full email templates and the free generator live.
If you want the whole job-search system — follow-up scripts, ATS-checked resume passes, cover letters, and the salary-negotiation scripts — in one place, I packaged it as the Job Search AI Toolkit.
This post contains affiliate links. We may earn a small commission if you sign up — at no extra cost to you.