skip to content

How often should a candidate check in with a recruiter who has gone silent after an onsite?

level: middleimportance: must knowfreq 66%

answer

  1. Count from their promise, not from the interview
  2. Business days, never hours
  3. Reply inside the thread you already opened
  4. Roughly a working week between nudges
  5. After two empty replies, change the ask

basics

~20 s

Wait out the timeline you were given, then check in about every five to seven business days, replying inside your existing thread. Two or three spaced, short nudges is the normal ceiling before you ask for a decision date instead.

solid answer

~50 s

Start the clock from whatever date the recruiter gave you, and add a couple of business days of slack before the first nudge, because slipping a stated timeline by a little is routine. After that, a cadence of roughly five to seven business days between messages is polite and effective; anything faster reads as pressure and anything slower makes you look like you have lost interest. Keep each message to three or four lines, send it as a reply inside your own thank-you thread so the context is attached, and ask one specific question rather than "any updates?". After two or three of these with no substance, change the request: ask directly for a date by which you can expect a decision, or state your own timeline. If that also gets nothing, treat the process as stalled and keep interviewing.

go deeper

for a junior

Know that silence after a final round is normal and usually logistical, that a polite check-in about once a working week is acceptable, and that the recruiter is the person you write to.

for a middle

Be able to explain the cadence and its reasoning: start from the date you were promised plus a small buffer, space messages by business days, reply inside the existing thread, and ask one answerable question per message.

for a senior

Show judgment about escalation and stopping. Decide when to change the ask from an update to a decision date, when going past the recruiter is justified, and when to declare a process stalled without burning the relationship.

for a principal

Own the tradeoff between keeping a slow process warm and spending your own attention on it. Decide what a stalled pipeline is worth, and be willing to close a conversation cleanly rather than maintaining it out of hope.

## Start the clock correctly Most candidates start counting from the interview. Count from the commitment instead: the recruiter almost always says something like "we should have an answer by the end of next week". Add a small buffer to that — two business days is enough — before the first check-in. Timelines slip constantly for reasons unrelated to you, and nudging on the exact stated day makes you the candidate who cannot absorb a normal delay. If you were given no date at all, ask for one in your thank-you note, and if you have neither, five business days after the final round is a reasonable first check. ## The cadence After the first check-in, five to seven business days between messages is the working range. That spacing has a reason on both sides. Faster than that and you land in the recruiter's inbox before anything could plausibly have changed, which converts a neutral impression into an irritation and, in the worst case, turns your name into an anecdote. Slower than that — a candidate who says nothing for three weeks — reads as disengaged, and it is genuinely how people lose a slot: a hiring manager with two acceptable candidates and one headcount takes the one who is clearly still interested and reachable. ## Where the message goes Reply inside your own thank-you thread rather than starting a fresh message. The context travels with the reply, the recruiter can see the whole history in one place, and it makes the check-in feel like a continuation rather than a new demand. Keep the recruiter as the primary channel; going around them to an interviewer or the hiring manager because the recruiter is slow is the escalation that most reliably damages the relationship. The exception is when the recruiter has gone completely dark for two cycles and you were explicitly told to contact someone else in that case. ## What the message says Three or four lines: 1. One line of continuity — the role and the date of the final round. 2. One specific question rather than a vague nudge. "Is the panel debrief scheduled yet?" or "Has the team decided whether to run the extra round we discussed?" is answerable; "any updates?" invites a reply that says nothing. 3. One line of information the recruiter can use — that you remain interested, or that your own timeline has changed. 4. A close that does not demand an immediate reply. No apology for following up, no explanation of how long you have waited, and no restated case for your candidacy. ## Worked example A junior backend candidate finishes an onsite at a seed-stage startup on a Thursday and is told a decision is expected "early next week". She sends thank-you notes about eighteen hours later. Early next week passes with nothing, so on the third business day after the promised window she replies inside her own thank-you thread with four lines asking whether the panel debrief has happened. The recruiter answers two days later: one interviewer is out and the debrief has moved. She waits, then checks again six business days after that reply, and mentions that she is now in final rounds elsewhere and would like to understand the timing. That message gets a real answer, because it contains information the recruiter can act on rather than another request for one. Count the messages: three across roughly three weeks. That is the whole cadence, and it is enough. ## The two failure modes The first is nudging daily. It usually starts after the thank-you note goes unanswered, and it escalates: five messages in a week, each shorter and more anxious. It never produces information the recruiter did not have, and it is remembered. The second is the opposite: reading silence as rejection, saying nothing for three weeks, and finding the slot has gone. Silence after a loop is almost always logistics — an absent interviewer, an approval, a scheduling backlog — and it very rarely encodes the answer. Assuming it does is how people talk themselves out of processes that were still alive. ## When to stop After two or three substantive-free replies, change the ask rather than repeating it: request a specific date by which you will hear, or state your own constraint plainly. If that produces nothing, treat the process as stalled, keep your other conversations moving, and leave the thread open and warm — stalled processes reanimate more often than candidates expect, and the tone of your last message is what you will be reanimating into.

  • The recruiter has not replied to two spaced check-ins. Would you contact the hiring manager directly?
    Only as a last resort, and only if the recruiter has been silent across two full cycles. Going around a slow recruiter is the escalation they remember, and it often produces a forwarded message rather than an answer. I would send one final note to the recruiter asking for a date, say I will follow up with the hiring manager if I do not hear back, and then do exactly that once.
  • Instead of a vague any-updates ping, what would you actually write to the recruiter?
    A question with a fact in it: whether the panel debrief has happened, whether the extra round we discussed is being scheduled, or whether a date exists by which I should expect an answer. Specific questions get specific answers. I would also include something the recruiter can use, such as a change in my own timeline, so the message gives as well as asks.
  • How long is silence after an onsite before you should assume it is a no?
    Longer than most candidates assume, and I would not assume at all. Silence is normally logistics: an absent interviewer, an approval, a matching step. I keep to the check-in cadence, keep other processes moving so the outcome matters less, and treat the process as stalled rather than rejected until someone actually says no.

saying these in an interview costs you the question

  • Nudges daily after the first unanswered message
  • Goes silent for three weeks and loses the slot
  • Starts a fresh cold message instead of replying in the thread
  • Sends a vague any-updates ping with no answerable question
  • Escalates past the recruiter after a single missed reply
  • Apologises at length for following up at all

context