You applied and heard nothing back. Here's what to do

You applied eleven days ago. The posting is still up. You've opened the portal enough times that your browser autocompletes it, and the status still says "submitted."

The advice splits between "always follow up after a week" and "never follow up, you'll look desperate." Both are wrong the same way: they treat the follow-up as the lever that decides the outcome. It almost never is.

Here's the real timeline, when a follow-up is worth sending, who to send it to, and the move that does more than any of it.

THE TIMELINE, REALISTICALLY

What happens after you hit submit is less dramatic than the silence makes it feel. Your application lands in an applicant tracking system and gets scored before a person opens it — that's where roughly 75% of resumes are removed. What survives goes into a pile the recruiter reviews in batches, when they have a block of time, not when your application arrives.

Then the human delays start. The hiring manager is interviewing for two other roles. The req is waiting on a sign-off nobody has chased. Someone internal applied on day nine.

Rough shape of a normal process:

• Days 1 to 5. Nothing meaningful. An automated acknowledgement if the system sends one.
• Days 5 to 15. The window where a first screen happens if it's going to happen. Most positive contact lands here.
• Weeks 3 to 6. Still possible. Stalled reqs restart, first-choice candidates decline, budgets unfreeze.
• After that. Roles reopen and old applications get revisited. Real, but not worth waiting on.

Two things people misread. The posting staying up means nothing — most companies leave listings live until an offer is signed. And "no response" is the default outcome, not an insult: most systems only send a rejection when a person manually triggers it, and nobody's review depends on that.

THE EMAIL THAT MAKES IT WORSE

Here's the message almost everyone sends, and why it goes nowhere.

"Hi, I applied for the Operations Coordinator role on July 8th and I just wanted to check in on the status of my application. I'm still very interested in the opportunity. Please let me know if you need anything else from me. Thank you so much!"

Nothing in it is rude. That's not the problem. The problem is that it transfers work and gives nothing back — the only available reply is a status update they may not have.

So it gets deferred, then buried. Answering three weeks late feels worse than not answering, so it never gets answered at all.

There's a second problem in 2026. Recruiters read an enormous volume of AI-drafted correspondence, and polite, fluent, interchangeable follow-ups are the most obvious category of it. If you draft with a tool, cut it down until it contains something only you would have written.

WHO YOU ACTUALLY WRITE TO

The careers inbox, the no-reply confirmation address and the portal's message box are compliance channels. They exist so applications get logged. Nobody's job is to answer them.

Write to the person who feels the pain of the empty seat: the hiring manager, or the team lead the role reports into. Second choice is the named recruiter on the posting. Both have a reason to care that you exist.

Finding them without being weird about it

Read the posting again. It often names the reporting line — "reports to the Director of Finance," "works alongside the Client Services team." That's the title you want. From there: the company's team page, the job's poster, or a search of the company plus that title. Most companies use one predictable email pattern, and any public contact address on their site reveals it.

If you can't find a name, reply to the application confirmation email rather than starting a new thread to the generic inbox. It stays attached to your file.

Rules that keep it from backfiring

• One person, not the manager and the recruiter and two people on the team.
• Email, not a LinkedIn connection request with a paragraph attached.
• Business hours, weekdays. A Sunday night message reads as anxious.
• No calls to the main line, no personal social accounts, and never an escalation to somebody's boss — that one ends your candidacy permanently.

THE FOLLOW-UP THAT ADDS SOMETHING

Reframe what the email is for. It's not a status request. It's a second, smaller application — one specific, relevant thing they didn't already have. Written that way it works even if nobody replies, because the information landed anyway.

What counts as new information: work you finished since applying, a certification that came through, a concrete observation about a problem the posting describes, a relevant work sample, or a clarification the posting implies they'd worry about.

What doesn't count: restating your enthusiasm, restating your years of experience, attaching the same resume again.

Same situation as the "just checking in" email above, written to add rather than ask:

Subject: Operations Coordinator — one thing I left out

Hi [Name],

I applied for the Operations Coordinator role last week. One thing that didn't fit in the application.

The posting mentions moving scheduling off spreadsheets. I did that for a 40-person field team at my last job: built the rotation in the new system, wrote the handover doc, ran coverage myself for two months while people adjusted. The hard part wasn't the software. It was getting supervisors to stop keeping a private copy on the side.

Happy to send that doc over if it's useful. Either way, good luck with the search.

[Your name]

The difference isn't tone. It's direction. One asks for information and one supplies it.

Four things make it work. It's short — under 150 words. It names something in their posting rather than something generic about you. It includes a detail nobody would invent, which is what makes the rest believable. And it doesn't demand a reply, which is exactly why it's likelier to get one.

If writing that paragraph is hard, notice what it's telling you: your original application probably didn't make this argument either. That's the real finding.

HOW MANY FOLLOW-UPS IS TOO MANY

One, roughly seven to ten business days after you applied. A second is optional, two weeks later, and only if you have something genuinely new to say. Then stop.

A third message doesn't read as persistence. It converts you from "candidate we didn't get to" into "candidate we remember for the wrong reason," and roles reopen more often than people expect.

If someone replies "we're still reviewing," that's your answer for at least three weeks — a courtesy reply isn't an opening. If they reply with an actual no, ask once for a sentence of feedback and leave it there.

Stopping means stopping the chase, not the search.

SILENCE IS DATA — READ IT INSTEAD OF CHASING IT

This is the part that changes your results. Chasing one application returns almost nothing. Ten silent applications, looked at together, tell you something specific and fixable. The stage where things go quiet is the diagnostic.

No response at all, on anything

You're being filtered before a human reads a word. That's a mechanical problem with mechanical fixes: the resume isn't parsing cleanly, or it isn't carrying the language the posting weights. Start with how ATS filtering actually works, then how to find the keywords a posting really weights. Neither is about gaming anything — it's about being legible to the first reader, which is software.

Screening calls, then silence

You're getting read; the story isn't matching the role. The resume says what you did and never says why that makes you right for this job. The recruiter can't make that argument for you.

Interviews, then silence

Different problem, and not a resume problem. Covered in what to do after a late-stage rejection.

One more pattern. If you're sending the same document to twenty roles a week, silence is the expected result, not a mystery. AI-assisted screening is routine now and volume applying has never been cheaper for anyone, so a generic application competes against a stack of equally generic ones. Five tailored applications beat twenty copies of one file.

WHEN YOUR PATH ISN'T LINEAR

Career changers. Silence usually means nobody could tell why you'd be good at this specific job. The follow-up is one of the few places to say it in one plain sentence, without the resume format fighting you.

Employment gaps. Don't explain a gap in a follow-up. Nobody has raised it, and volunteering a defence makes it the headline.

Contract and freelance. Say when you're available. A manager reading a contract history often can't tell whether you're between engagements or six months out, and ambiguity is a reason to move on.

New grads. Follow-ups work better for you than for most people, because you're more often applying to smaller teams where the hiring manager is genuinely reachable. Send one, to a named person.

Anyone with a connection inside. One message to someone who already works there beats every email in this article. Ask them to flag your application internally before you write to a stranger.

WHAT TO DO THIS WEEK

1. List your last ten applications with dates. Anything past six weeks with no contact: close it.
2. Pick the two or three you actually want. For each, find one named person — the hiring manager or team lead, not the careers inbox.
3. Write one follow-up per role containing one concrete thing they don't already have. Under 150 words. No status request.
4. Send them, set a note two weeks out, and don't touch those threads until then.
5. Look at the pattern across all ten. No screens at all means the application is the problem, not the follow-up.
6. Rebuild the application for the posting you want most — matched language, and a letter that argues for that job specifically.
7. Cap the chasing at thirty minutes a week. The rest goes into new applications.

THE REFRAME

Following up is a small lever. Sometimes it surfaces you at the moment a manager is deciding who to screen, and that's worth ten minutes. It will not rescue an application that was never going to land.

Silence is cheap for them and expensive for you. That asymmetry is the reason to spend as little as possible on it — one good email, no refreshing, no rewriting the same message in your head at midnight — and put the rest into the next application, made specific enough that it doesn't produce silence.

← Back to Blog