Silence Is Not a Bandwidth Problem

I have sat on both sides of a senior hiring process enough times now to recognise the shape of this one before it finishes. A shortlist. Two or three rounds with the executive team, the CEO, the CTO, a VP or two, each one framed as a serious, mutual conversation. An assessment that takes real hours to do properly. Then, at the exact moment the process should either close or continue, nothing. Not a decision. Not a delay. Not even the sentence it takes to say we haven’t decided yet.

The explanation offered, when one is offered at all, is almost always the same: scale. Too many candidates, not enough hours in a recruiter’s week. I no longer believe it, and the reason is simple arithmetic. The same team that cannot find thirty seconds to send a status update found the hours to schedule five separate conversations with its most senior, most expensive people. Bandwidth was never the constraint. It was spent, deliberately, on the parts of the process that make the company look good to itself. What was left over, the two lines that make a candidate feel like a person rather than a line item, didn’t lose to a lack of time. It lost to a lack of priority.

That is the reframe I keep coming back to. Courtesy in a hiring process is not a soft nicety that gets cut when things get busy. It is close to free, a template, an owner, thirty seconds of somebody’s attention, which is exactly what makes its absence so revealing. You cannot claim the constraint is cost when the actual cost is nearly zero. What you can claim, honestly, is that nobody with the authority to fix it decided it mattered enough to fix. Priority is a decision. A company makes it every day about who is worth the trouble of a reply, and a candidate who has just spent three rounds giving a company his time finds out, in the silence, exactly where he sits on that list.

I think about who stays visible in a process like this and who doesn’t, because the pattern is not random. The interviewers stay visible to each other, the debrief happens, the calendar holds. The recruiter stays visible to the hiring manager. The one person with the least institutional standing in the room, the candidate, is the first to become invisible the moment he stops being useful to interview. That is not a coincidence of bandwidth. It is what happens by default when nobody has decided that a candidate’s experience is worth protecting on its own terms, independent of whether he ends up on the payroll. I have spent a long time arguing, in other contexts, that people are not throughput. A candidate is a person before he is ever an employee, and a company that cannot manage its manners toward someone it hasn’t hired yet is telling you, with real precision, how it will eventually treat someone it has.

I have run hiring loops at real scale, and I know exactly how unglamorous the fix is, which is part of why I have so little patience for the excuse. It is not a cultural transformation. It is an owner for every open requisition who is accountable for closing every candidate who reached a certain stage, a template that takes less time to send than this paragraph took to write, and a simple internal rule: nobody stays in limbo longer than a week without hearing something, even if the something is just we don’t have an update yet. None of that requires more headcount. It requires someone deciding this is a discipline worth holding, the same way you’d hold a deploy gate or a rollback plan, not because skipping it causes a visible fire, but because skipping it quietly tells everyone downstream what actually gets protected under pressure and what doesn’t.

What makes the pattern sting is the asymmetry with how the same companies treat everyone else they depend on. No enterprise sales team goes quiet on a client mid-negotiation and calls it bandwidth. No board expects silence from a CEO between updates. Vendors get status calls. Customers get renewal check-ins. Somewhere in the hierarchy of who gets a reply, the candidate sits below all of them, and the only honest reason is that a candidate, unlike a client or a board, has no immediate leverage to make the silence expensive. It costs a company nothing, in the short run, to leave someone hanging. That it costs nothing is precisely the test. What an organisation does when there is no penalty for indifference is the truest measure of what it actually values, because that is the only moment its stated culture and its real one are allowed to diverge without consequence.

So I have started reading it as data rather than as an insult. A company that runs five rounds with its leadership and then goes silent has already told me, more honestly than any interview answer could, what happens to people inside it once they stop being useful to watch. And if I am ever again the person deciding how a hiring process is run, that is the one discipline I will hold without exception, long after the reasons for holding it stop being visible to anyone but me. Closing the loop costs almost nothing. What it buys, every time, is the only proof a candidate ever gets of who you actually are, before he has any reason to trust your word for it.