The follow-up email that actually gets replies

Most people send one email and read the silence as a no. It usually is not a no. It is an email that arrived during a bad hour, got scrolled past, and is now four hundred messages down an inbox. The follow-up exists to fix a logistics problem, not to change anyone's mind — and understanding that is what makes it easy to write.

When to send it

Between five and eight working days after the first. Sooner reads as impatience for a hiring process that genuinely takes time. Much later and the role has been filled or the thread has gone cold enough that you are effectively starting again.

Reply to your own original message rather than starting a new thread. It keeps your first email — and your resume — one scroll away instead of gone, and it makes the whole exchange one item in their inbox rather than two.

What it should say

Three lines. It is a nudge, not a second application.

Hi Priya,

Following up on the Backend Engineer role — I know these inboxes fill up.

Since writing I have put the settlement-reconciliation work I mentioned into a
short write-up, in case it is useful context: <one link>

Happy to be told the role has moved on. If it has not, I would still welcome a
short call.

Aryan

Why this one works

• It gives them an out. "Happy to be told the role has moved on" makes a one-word reply socially acceptable, and a one-word reply is still a reply — it frees you to stop waiting.
• It adds something. A link, a write-up, a relevant thing you shipped since. A follow-up that only says "just checking in" asks for their time and offers nothing for it.
• It does not re-pitch. Repeating your qualifications suggests you think the problem was that they read your email and were unconvinced. It almost certainly was not.
• It names the friction. Acknowledging that inboxes fill up costs you nothing and removes the implication that they were rude.

The part that actually goes wrong

Almost nobody fails at writing the follow-up. They fail at remembering it. You sent the email on a Tuesday, and by the following Wednesday it is nine applications ago and completely gone from your head. This is a tracking problem wearing the costume of a writing problem.

Fix it with whatever you will actually maintain — a calendar reminder per application works fine. Replyrate does it by asking: a few days after you mark something applied, it surfaces the ones that have gone quiet, asks whether anyone replied, and writes the follow-up for the ones that did not.