Most companies respond within one to two weeks of an interview; final rounds often move faster, and anything under three weeks is unremarkable silence, not rejection. If they named a date, wait two business days past it, then send one short nudge. Silence usually means process — approvals, other candidates, vacations — not a decision about you.
Behind the quiet is almost always logistics: the loop has other candidates mid-process, feedback is sitting in someone's drafts, the hiring manager is traveling, finance is re-approving the headcount, or the recruiter owns forty requisitions. Companies decide slowly and communicate slower — the gap between an internal yes and your offer call can alone be a week of approvals.
The practical takeaway: silence carries almost no information for the first two weeks. Candidates read rejection into day three; recruiters are usually just buried. What does carry information is a blown named deadline plus a further week of silence after your nudge — that pattern predicts either a stalled req or a first-choice candidate who isn't you, and both mean: keep applying elsewhere.
If they gave a date, nudge two business days after it passes. If they didn't, nudge at the one-week mark for early rounds, ten days for finals. One nudge, then one more a week later if needed — beyond two unanswered messages, additional ones only convert you from candidate to chore.
Script: "Hi Sam — checking in on the senior analyst process. I remain very interested, and I'm happy to share anything else that would help the decision. Any update on timing?" Three sentences, zero pressure, no guilt-tripping about their delay. If you have a real deadline — another offer expiring — say so plainly: deadlines you actually hold are the one thing that reliably accelerates a process.
The only reliable defense against wait anxiety is parallel process: keep applying and interviewing until an offer is signed, regardless of how well the last round felt. Pipelines collapse for reasons that have nothing to do with candidates — reorgs, freezes, an internal transfer — and a portfolio of processes converts each one from existential to informational.
Log each application's stage and promised dates somewhere, so nudges fire on schedule instead of on anxiety. And when a process does go permanently dark — it happens, and it's unprofessional but common — let the record show you nudged twice and moved on. Ghosting is information about them, not about you.
Two business days after any date they named, otherwise one week after early rounds and about ten days after finals. Send one short, warm nudge; one more a week later if needed; then redirect energy to other processes.
Neither is reliable. Fast rejections and slow offers are both routine — approvals, competing candidates, and vacations dominate timing. The only strong signal is a blown named deadline plus continued silence after your nudge.
Yes, if it's real. "I have an offer with a deadline of Friday, and you're my preference — is there any way to accelerate?" is the single most effective legitimate accelerator. Never invent one; bluffs get called.
The best cure for waiting is a stronger pipeline — score your resume free and keep applications flowing while any single process deliberates.
