The Real Cost of an Empty Seat
OKAYA
Vacant IT roles cost more than the salary math suggests. Where the money actually goes — and what shortening time-to-fill is really worth.
Nobody budgets for vacancy. There's no line item for "the six weeks nobody owned the data pipeline." But that cost is real, and after two decades of watching roles sit open, we'd argue it's usually bigger than the fee anyone eventually pays to fill them.
Start with the visible layer. A $130,000 engineer produces roughly $2,500 of value a week, and that's the floor — most companies hire people expecting a multiple of salary in output, not parity. Eight weeks of vacancy on that seat is $20,000 gone at the floor, and quite possibly two or three times that in the honest accounting.
But the visible layer isn't where the damage concentrates. It's here:
The team absorbs the work, badly
The missing engineer's tickets don't disappear; they get split across four people who already had full plates. Delivery slows everywhere, not just on one project. And overloaded engineers are exactly the ones who start returning recruiter calls. We've watched one vacancy quietly turn into two more times than we can count.
Projects slip in ways that compound
A sprint slips, then a release, then a commitment someone made to a customer. The vacancy that "only" lasted two months shows up in revenue two quarters later, wearing a different name.
Managers stop managing
A hiring manager running a search on top of their day job spends five or more hours a week on resume screens, interviews, and scheduling. That's an eighth of their working life doing recruiting, poorly, instead of their actual job.
The search itself decays
Roles open past sixty days develop a smell. Candidates see the posting date and wonder what's wrong. Internally, the bar quietly drops — by month three, teams start talking themselves into candidates they'd have passed on in week two. Those compromise hires cost the most of all.
So what's the fix? Not panic hiring — a bad hire is the only thing more expensive than a vacancy. The fix is compressing the parts of the search that waste time without touching the parts that need it. In practice:
Write the requisition around the five things the person will actually do, not a wish list of twelve technologies. Wish lists slow sourcing and scare off good realists.
Decide the interview loop before the first candidate, not during. Three focused conversations beat five vague ones, and candidates with options won't sit through five anyway.
Give feedback on submittals within 48 hours. Search momentum is a real thing; every silent week costs you the best people in the pipeline.
If the seat is urgent and the work can't wait, put a contractor in it while the permanent search runs properly. Paying a premium for eight weeks is cheaper than rushing a hire you'll live with for years.
The companies that fill roles fastest aren't lucky and they don't have secret candidate pools. They've just decided that an open seat is a live cost, not a paused one — and they run their process like they believe it.
Common questions
What's a reasonable time-to-fill for IT roles? For mainstream skills with a prepared process: three to five weeks to offer. Past sixty days, something in the process — the req, the loop, the feedback speed — is usually broken.
Is it wasteful to pay contractor rates while running a permanent search? Compare the contractor premium for two months against the fully-loaded cost of the vacancy plus a rushed hire. In most cases we've seen, the bridge contractor is the cheaper option.