One thank-you email you can adapt in five minutes, the four dates that decide whether a follow-up helps or hurts, and a small tracker so nothing slips between rounds. The timing here reflects common practice, not an official rule. If the interviewer told you "we'll get back to you by Friday," their date wins over everything on this page.
| When | What happens |
|---|---|
| Day 0 | Interview day. Before you leave the call or the room, write down the two specifics you'd want to mention in a follow-up: one thing they said, one thing you did. Memory of a good interview decays faster than people expect. |
| Day 3 | Thank-you email. Send it within the first three days; the template below is the one to send. One message to one person per conversation, in the same thread if you already have one. |
| Day 10 | Check-in. Only if they gave you no date, or that date has passed. Two lines: still interested, is there an update on timing? Nothing attached, nothing demanded. |
| Day 21 | Move on. Three weeks of silence after a check-in usually means the role moved on without you, sometimes because the loop itself stalled. Send one last short note, then put the row in your tracker to sleep and spend the attention on new applications. Roles do reopen; you can re-apply then. |
Day 10 is the one most people skip, and in my experience it's the cheapest to send. The worst realistic outcome is a "no update yet" reply, which costs you a minute to read.
Replace every [bracket] before sending. A follow-up left half-filled reads worse than no follow-up at all, because the recipient can tell it's a form letter that got away from you. The body runs about 120 words, which fits the three jobs it has: thank them, add one piece of value they didn't get in the room, and close without pressure.
Subject: Thank you — [Role] interview
Hi [name],
Thanks for the time you gave the [role] conversation. The part that stuck with me was [one specific thing they said], and I've been thinking about how it fits what your team is trying to do this quarter.
I didn't get to mention it in the room, so I'll say it here. Last quarter I [one relevant project or result], and the setup is close to what you described on the [team/topic] side. Happy to go deeper if that's useful.
Also, the candid answer on [second topic] was appreciated. Job posts rarely give you that level of detail.
No rush on your end. I'm free [day] or [day] if a follow-up conversation fits the loop.
Thanks again,
[Your name]
Two adjustments worth making: if the interviewer gave you a reply date, swap the last paragraph for a simple "looking forward to hearing back by [their date]". If you spoke to several people, send each of them a version with their own specifics in the first paragraph.
Follow-ups fall apart when you can't remember who you last wrote and when. Eight rows is enough to cover an active loop at one or two companies. The example row is made-up; the rest are yours to fill in.
| Company | Stage | Last touch | Next action |
|---|---|---|---|
| Helio Pay | Interviewed Sep 8 | Thank-you sent Sep 10 | Check-in Sep 17 if no reply |
Keep the next-action column as a date plus a verb, the way the example row does. "Follow up" is a wish; "check in Sep 17 if no reply" is something you can see unfinished on your desk.
An open follow-up is only as good as the pipeline behind it. The Web3 Remote Jobs & Hiring Database 2026 lists 147 crypto companies hiring remote, each with a careers URL that was HTTP-checked on 2026-09-05, plus remote policy and open-role counts per row. If your tracker has more sleeping rows than live ones, that's where the next interview comes from. The printable job application tracker covers the earlier stage, logging applications before any interview exists.
Get the Web3 Remote Jobs & Hiring Database — 147 companies →CSV + Markdown, grouped by ecosystem. Personal and commercial use.