Recruiter Ghosting: What to Do After Two Weeks of Silence

You applied. Maybe you even interviewed, and it went well. The recruiter said "we'll get back to you next week." That was three weeks ago.

Ghosting is the most demoralizing part of a job search, mostly because your brain fills the silence with the worst explanation: it's about you. It almost never is. Here's what's actually happening and what to do about it.

Why companies go silent

The boring truth is that silence is rarely a decision; it's a symptom of process:

• The position froze. Budget got cut or reshuffled mid-recruitment, and nobody's job is to tell the candidates.
• An internal candidate appeared. The process continues on paper while the outcome is already decided.
• The recruiter is drowning. One person running fifteen processes deprioritizes the ones that stall.
• The decision is stuck above them. The hiring manager is on vacation, the approval sits in someone's inbox.
• You're the backup. They made an offer to someone else and are keeping you warm in case negotiations fail. Silence, then a sudden revival, is the classic signature of this one.

Notice what's missing from that list: anything you did wrong.

When silence is still normal

Calibrate before you panic:

• After submitting an application: two weeks of silence is standard. Many companies only contact selected candidates at all.
• After a first-round interview: one to two weeks is normal, especially if they mentioned other candidates still in the pipeline.
• After a final round: a week is common, but past two weeks the odds drop noticeably.
• After "we'll send the offer this week": if the promised concrete thing doesn't arrive within a few days of the named date, follow up immediately. Specific promises that slip are the strongest signal on this list.

The one follow-up rule

Send exactly one follow-up per stage of silence, short and unloaded:

"Hi [name], I wanted to check in on the status of my application for [role]. I remain very interested. Happy to provide anything else you need."

That's the whole email. No guilt-tripping, no "I was promised an answer", no second paragraph. If the process is alive, this revives it; recruiters genuinely do lose threads. If it's dead, no wording would have saved it.

Wait about a week after the follow-up. Then move the application to rejected in your head, and let any later reply be a pleasant surprise.

Protect yourself before the ghosting happens

Two habits turn ghosting from a crisis into a statistic:

Save the posting when you apply. Ghosted processes have a habit of reviving a month later, and by then the job posting is gone, along with the requirements and the salary range you'd want to reread before a suddenly scheduled interview. Screenshot the posting when you apply; in OfferKeep you can paste screenshots directly onto the offer, so the source material survives even when the ad doesn't.

Keep the pipeline full. Ghosting only hurts badly when it's your only process. With 10 to 15 active applications, one silent company is a data point, not a catastrophe. A tracker makes the stalled ones visible: sort by last updated, and anything untouched for two weeks is either a follow-up to send or a row to close.

Close it and move on

When a process passes your deadline (follow-up sent, a week of silence after it), mark it rejected yourself. This is surprisingly liberating: you decide, not their silence, and your attention goes back to processes that are actually moving.

Don't burn the bridge, though. No angry LinkedIn messages, no "unbelievable lack of professionalism" emails. Recruiters change companies, and the person who ghosted you at one company is sometimes the person who remembers your graceful reaction at the next one.