Following up after you apply
A follow-up is not a reminder that you exist. Whoever is hiring has a list, and your name is on it or it is not; nudging rarely moves a name up. What a follow-up can do is narrower and still worth having: it puts a person in front of a process, it gives them an excuse to look at your application while it is in their inbox rather than in a queue, and — most usefully — it ends the waiting, one way or the other.
That last one is the real prize. An answer of “no” frees the row in your list. Silence does not.
After you apply
If the application went into a form and no human is named anywhere, a follow-up has nowhere to land. Nobody reads a generic careers inbox looking for enthusiasm. Skip it, and spend the twenty minutes on the next application.
If you know who posted it — a hiring manager on the posting, a recruiter who messaged you, someone who forwarded it — then one message, about a week after you applied, is reasonable and normal. A week is long enough that they have started reading, and short enough that the role is still open in their head.
Keep it to three things, in this order:
- Which role, in the subject line. “Platform Engineer application — [your name]”. They may be filling four positions; do not make them work out which one this is.
- That you applied, and when. One clause. “I applied on the 12th through the careers page.”
- One new thing. Not “I am still very interested” — that is not information. Something they did not have: a piece of work that is relevant, a detail you left out because the form had no field for it, a question about the team that shows you read the posting properly.
Four or five sentences in total. If it is longer than the screen of a phone, it will be read later, which means never.
After an interview
Send it the same day or the next morning, and make it specific. The value is not politeness — it is that the person is writing up their notes about you, and a concrete sentence from you can end up in those notes.
Reference one actual thing from the conversation. “You mentioned the migration off the old billing system is the next big piece — I have done exactly that once, and the part that bit us was X.” That is a sentence they can repeat to a colleague. “Thank you for your time, I enjoyed our conversation” is not.
If you fumbled an answer, this is the one chance to fix it, in two sentences, without apologising twice. Say the better answer and move on.
When they gave you a date and it passed
“We will get back to you by Friday” and it is Monday: write on Monday. This is the easiest follow-up to send, because you are not asking for a favour — you are asking about a commitment they made. Keep it friendly and factual: you were expecting to hear by Friday, are they still working through it, and is there anything else you can send.
Dates slip for reasons that have nothing to do with you: the other candidate is on holiday, the budget is being re-approved, the interviewer is out sick. Ask, and you usually get the real reason.
One channel, one message
The most common mistake is not sending too few follow-ups but sending one in three places at once — the recruiter’s inbox, a LinkedIn message, and a call to the main switchboard. From your side it feels thorough. From theirs it is the same person arriving three times in one morning.
Pick the channel the conversation was already happening in. If there has been no conversation, email.
A second follow-up, a week after the first, is fine. A third is not persistence; it is a story they tell someone else.
When to stop
If two follow-ups have gone unanswered, the answer is no. It is a bad no — nobody said it out loud, and you had to work it out yourself — but it is still information, so use it: close the row in your list.
Closing is not burning anything down. People move companies, requisitions reopen, the person they hired does not work out. Leave the last message warm and short, and leave the door on the latch: “Understood — if something opens up later I would be glad to hear about it.”
Then get the row off the list. The point of the list is to show you what is actually live, and an application that has stopped answering is not live, no matter how much you want it to be.
Everything here works on paper. If you would rather not keep the paper,the app does this bit — paste a posting and it fills in the details, and it all stays on your own computer.