It's a Numbers Game

By Shapes.IO

Guides

How to follow up on a job application

When to follow up, who to send it to, and four short emails you can copy — after applying, after an interview, when a deadline passes, and when you need to walk away.

A follow-up does two things. It occasionally moves an application that had stalled for an ordinary reason — the hiring manager was away, the req was paused, your email went to a filtered folder. And it tells you, by producing no reply, that the application is over, which lets you stop thinking about it.

The second use is the reliable one. Treat a follow-up as a way to close a question rather than a way to win, and it stops feeling like begging.

When

The timing that matters is measured from the last thing that happened, not from when you applied.

  • After applying, with no acknowledgement: around ten working days. Sooner reads as impatient given that most applications sit in a queue; much later and the shortlist is drawn.
  • After an interview: a thank-you within a day, then wait for whatever date they gave you. If they said "end of next week", follow up two working days after that, not on the day.
  • After a stated deadline passes with nothing: follow up immediately. You are not chasing here, you are noting that a commitment they made has lapsed, which is a different and much stronger position.
  • Second follow-up: one more, a week or so later. Then stop.

Two unanswered follow-ups is the end. A third changes nothing about the outcome and costs you the last of the goodwill.

Who

In order of usefulness: the person who interviewed you, the recruiter who contacted you, a named hiring manager on the posting. Reply on the existing email thread wherever one exists — it carries the context, the dates and the role, and it lands in a thread the recipient already recognises.

If your only route in was a web form with no human attached, there is usually nobody to follow up with, and a generic careers inbox rarely produces a reply. That is worth knowing in advance rather than taking personally.

The emails

Short. Three or four sentences. No apology for the intrusion, no restatement of your CV, and one specific detail that proves this is not a template you sent to forty companies — even though it is a template.

After applying

Subject: Senior Designer application — Priya Raman

Hi Sam,

I applied for the Senior Designer role on 2 September and wanted to check the application reached you. Still very interested — the part of the posting about rebuilding the onboarding flow is close to what I did at my last company, and I'd welcome the chance to talk about it.

Happy to send anything else that would help. Thanks.

The date in the first line does the real work: it makes the email answerable in one lookup.

After an interview

Hi Sam,

Thanks for the conversation on Tuesday. The bit about the migration you're planning for Q1 stuck with me — I ran something similar and the sequencing question you raised is exactly where ours got difficult, so I'd be glad to talk it through properly if it's useful.

You mentioned you expected to have news by the end of next week. I'll look out for it.

The last line is the one to keep. Repeating their timeline back to them, in writing, is what makes the follow-up after it lapses straightforward.

After a deadline passes

Hi Sam,

Following up on the Senior Designer role — you'd mentioned hearing back by the 12th. Is there an update, or has the timeline moved?

No problem either way, I'd just like to know where things stand.

"Has the timeline moved?" gives them an easy, face-saving answer that is not yes or no, which makes a reply more likely than a question that forces a decision.

Withdrawing

Hi Sam,

I wanted to let you know I've accepted another offer, so I'm withdrawing from the Senior Designer process. Thanks for your time — I enjoyed the conversation with the team and hope our paths cross again.

Send it. Industries are small, recruiters move companies, and withdrawing cleanly is remembered for longer than the application is.

What not to do

  • Don't invent a deadline you don't have. "I have another offer" when you don't is a bluff you may have to fold on, and it can end the process in one reply.
  • Don't send the same message to four people at the company. They talk, and it reads as pressure rather than enthusiasm.
  • Don't attach the CV again. It is in their system. Re-attaching implies you think they lost it.
  • Don't ask for feedback in the same email as the chase. Two requests in one message reliably gets you neither. Ask for feedback after a rejection, separately, and expect that most companies won't give it.

The part that makes this work

All of the above depends on knowing, without thinking about it, when you applied, what was said, what date they promised, and whether you have already followed up once. That is not memory, that is a record — and if you are running more than a handful of applications it needs to be written down at the time.

A log per application, with one dated line per event, is enough: how to track job applications covers what to put in it. The single most useful entry is the one that records a date somebody gave you, because that is the date that makes the follow-up easy to write and impossible to argue with.

Or let something else hold it

It's a Numbers Game is a free tracker built around exactly this: a board per application, a log per conversation, and a profile that fills in the questions every form asks twice. No trial, no card, no upsell.