The Hidden Cost of a Slow Tech Hire: What a 90-Day Vacancy Really Costs You

Most companies think about hiring in terms of what it costs to fill a role. The recruiter fee. The time spent interviewing. The onboarding investment once someone starts. Very few think about what it costs to not fill a role. Or to fill it slowly. That gap in thinking is expensive. Not metaphorically expensive – measurably, calculably, line-item-on-your-P&L expensive. And for senior engineering roles, where the vacancy period most commonly stretches to 60, 90, or even 120 days, the cost of vacancy frequently exceeds the recruiter fee that could have prevented it – sometimes by a factor of three.

This article breaks down exactly what a slow tech hire costs: the daily productivity loss, the team burnout spiral, the delivery delays, the candidate attrition, and the compound effect of all of them running simultaneously for 90 days. With 2026 data, a calculation framework you can apply to your own open roles, and a clear picture of what the difference between a 21-day fill and a 90-day fill actually means financially.

The Numbers Nobody Puts in the Hiring Budget

Before getting into the anatomy of a slow hire, the headline figures are worth establishing clearly.

An unfilled tech role runs approximately $500 per day in lost productivity according to Deloitte’s Recruitment Efficiency Report (2024) – that is the fully-loaded salary divided by working days, plus the overhead cost of work that does not get done or gets deferred onto people who were already at capacity.

Each unfilled position costs companies an average of $4,129 over a 42-day vacancy period according to Forbes. For revenue-generating roles, costs can jump to $7,000–$10,000 per month, and even $25,000+/month for certain tech/engineering positions.

Technology roles take a median of 48 days to hire – 26% slower than the global median across all industries. High-demand roles such as cloud engineers, data scientists, and security specialists often take 60 to 120 days to fill.

Put those three numbers together and the picture sharpens fast. The average tech role vacancy runs 48 days. At $500 per day, that is $24,000 in baseline productivity cost before a single recruiter is involved. For a 90-day vacancy – which is not unusual for a senior engineering search run through internal HR without specialist support – the baseline cost is $45,000.

That $45,000 does not appear on any balance sheet. It does not trigger a budget conversation. It is invisible in the same way that a slow leak is invisible – until you notice the structural damage it has caused.

IDC predicts IT talent shortage will cost $5.5 trillion in losses globally by 2026. Your share of that number depends on how fast you fill critical roles.

How to Calculate Your Own Cost of Vacancy

The $500 per day figure is a useful benchmark. The more precise calculation depends on the specific role you are trying to fill and the revenue model of your business.

Here is the framework, adapted from Built In’s cost of vacancy methodology:

• Step 1 – Daily productivity value of the role – Take the engineer’s annual salary equivalent and divide by 260 working days. For a senior Polish engineer billing 25,000 PLN per month (~$84,000 per year), the daily productivity value is approximately $323. For a US senior engineer at $160,000 per year, it is approximately $615 per day.
• Step 2 – Apply a revenue impact multiplier – Not all roles have equal downstream impact. A senior engineer owning a core product function – one whose vacancy stalls a release, blocks a team, or delays a customer delivery – carries a revenue multiplier of two to three times the daily salary value. A vacant software developer role costing $657 per day in payroll savings actually costs the company $84,000 over 65 days once the revenue impact multiplier is applied – a net loss of $41,295 on a role the company thought it was saving money by leaving open.
• Step 3 – Add the team absorption cost – Work does not disappear when a role is vacant. It redistributes. The cost of that redistribution is real: senior engineers covering junior tasks, team leads absorbing additional code review, managers pulled into operational work they should not be doing. This overhead is typically estimated at 20–30% of additional burden on the remaining team.
• Step 4 – Add recruitment process cost – Internal HR time spent on a slow, unsuccessful search has a cost too. Hiring manager time across multiple interview rounds for candidates who decline or fail to progress – at senior leadership rates – can represent $5,000–$15,000 in pure time cost across a 90-day search, before any external fee is paid.
• Step 5 – Add downstream project cost – This is the hardest to quantify and the largest in practice. A product release delayed by six weeks due to an unfilled senior engineering role has a revenue impact that depends entirely on your business – but for a SaaS company missing a launch, the cost is measured in customer acquisition delays, competitive positioning, and contractual milestone risk, not in salary equivalents.

For a senior engineering role at a growth-stage technology company, a conservative 90-day vacancy cost calculation – productivity loss plus team overhead plus management time plus delayed delivery – typically lands between $60,000 and $120,000, before the recruitment fee required to close the search.

The recruitment fee for a specialist agency placement is typically $15,000–$18,000 for a senior Polish engineer. The math does not need elaborating.

The Five Cost of Vacancy Layers in Case of a Slow Tech Hire

Vacancy cost is not a single number. It is five overlapping cost centres, each running independently and compounding against each other over time.

Layer 1: Direct Productivity Loss

The most visible layer – and the one most consistently underestimated because it does not appear as an expense.

Every day the role is unfilled, the work that person would have done either does not happen, happens later, or happens at a lower quality level because someone else is doing it alongside their own full workload. For a senior backend engineer who should be owning a core platform function, 90 days of absence is 90 days of deferred architectural decisions, slower ticket resolution, and lower code quality across the work their absence touches.

At the industry-average 48-day fill for a backend engineer, the vacancy cost is $24,000 in deferred output before the recruiter is ever involved. A 90-day search produces $45,000 in deferred output – not counting what happens when the AI initiative or product feature tied to that role slips into the next quarter or gets killed entirely because the team could not staff it.

Layer 2: Team Overload and the Burnout Spiral

This is the layer that is hardest to see on a spreadsheet and most damaging in practice.

When a senior engineering role is open, the work does not wait. It redistributes to the engineers who are present – and they absorb it, initially willingly, because they are professionals who care about delivery. The problem is that this absorption has a ceiling, and most companies do not notice when it has been crossed.

36% of workers reported heavier workloads due to unfilled positions in 2024. Of employees who report increased workloads due to staff shortages, 61% also report feelings of burnout. SHMR Report.

Burned-out employees are nearly three times more likely to say they plan to leave their employer in the coming year.

Follow that chain to its end. An open senior engineering role creates overload on the remaining team. Overload produces burnout. Burnout produces departure intent. A second senior engineer resigns. You are now managing two open roles and a team that has just watched a colleague leave under exactly the conditions that are making them consider leaving too.

According to LeadDev’s Engineering Leadership Report 2025, 22% of engineering leaders and developers reported facing critical levels of burnout. 65% reported expanded responsibilities, with 40% managing more direct reports – a direct reflection of the vacancy-driven overload pattern.

The cost of the secondary departure triggered by a slow original hire is not captured in any vacancy cost formula. It is, in practice, the most expensive downstream consequence of a 90-day search.

Layer 3: Candidate Attrition During a Slow Process

Here is the feedback loop most hiring managers do not see until it is too late.

A slow internal hiring process does not just cost you in productivity terms. It costs you the best candidates – specifically and disproportionately. The strongest senior engineers in the Polish market are not passively waiting for your process to conclude. They are evaluating two, three, or four processes simultaneously. The top candidates in fast-moving technical disciplines are typically off the market within days of becoming available.

A company that takes a week between each interview round, requires five stages before an offer, or lets internal approval chains extend the decision by ten days will consistently lose the first-choice candidate to a company that moves in 48 hours. What remains in the pool after that filtering is not a comparable alternative. It is whoever the faster-moving companies did not want.

This is not a hypothetical. In our documented placements at Itentio, the engagements that achieve the fastest outcomes – 3 working days for an Engineering Lead, 7 working days for a Senior Golang Developer, 14 working days for a CTO – are uniformly the ones where the client scheduled interviews within 48 hours of receiving a shortlist and provided feedback within 24 hours of each round. The clients whose searches stretched longer almost always experienced at least one first-choice candidate accepting a competing offer mid-process.

Layer 4: Delivery Delay and Missed Milestones

Technical debt is a well-understood concept in engineering. Hiring debt is not – but it should be.

Every week an engineering role is open, your product roadmap absorbs the equivalent of one engineer-week of absent output. Over 90 days, that is approximately 13 engineer-weeks of work that did not happen – features not shipped, bugs not fixed, architectural improvements not made, technical debt not addressed.

A team missing two engineers for three months can see a 12-week project stretch to 16 weeks, resulting in 34% delay. Vacant technical roles ripple across the entire business: cloud architects stall migrations, developers slip releases, security engineers leave vulnerabilities unaddressed.

For a company with contractual milestone obligations to customers, an enterprise release deadline, or a fundraise dependent on a product demonstration, those delays have direct financial consequences. The cost of a missed milestone is not measurable in salary-equivalent terms – it is measured in contract penalties, deferred revenue, and competitive disadvantage.

Businesses delaying essential hires can experience up to a 30% decrease in innovation over time due to the lack of specialised skills. Key departments such as R&D and product development may face delays that impact competitive advantage with every missed hire.

Layer 5: Management Distraction and Decision-Making Lag

When a senior engineering role is open, someone fills the gap in the organisation chart – and it is usually the CTO, VP of Engineering, or a senior team lead who was already at capacity.

The cost of their distraction is not the work they now absorb. It is the work they stop doing. Strategic technical decisions get deferred. Architecture reviews slip. The conversations that drive the product’s medium-term direction do not happen because the person who should be having them is triaging code reviews for a team that is two engineers short.

The Harvard Business Review highlights that unfilled C-suite and leadership positions can create ripple effects throughout the company, delaying crucial projects, hindering strategic decision-making, and stalling company-wide initiatives. The same dynamic applies at team lead and senior individual contributor level in high-functioning engineering organisations – the work that stops is not always visible, but its absence compounds over months.

The 90-Day Cost of Vacancy: What It Looks Like, Week by Week

Abstract cost figures are useful. A concrete timeline is more useful.

Here is what a 90-day vacancy typically looks like in a growth-stage technology company, broken into phases:

• Weeks 1–2: Optimism. The role is open. The team absorbs the workload. The search begins, usually through a job posting. Internal morale is unaffected – this is temporary, the thinking goes. The CTO is confident the hire will happen within a month.
• Weeks 3–4: Friction. Applications are coming in but quality is lower than expected. The strong candidates who applied in week one have already accepted offers elsewhere – because they were fielding competing processes the whole time. The hiring manager starts to feel the calendar impact of interview scheduling. The team is starting to notice the workload accumulation.
• Weeks 5–7: Recalibration. A candidate gets to final stage and declines. The brief is reconsidered. Compensation is revisited. The job description is rewritten. The search essentially starts again. The team is now aware that this is not going to be resolved quickly. The first conversations about burnout begin – informally, in one-to-ones, as observations about pace and workload.
• Weeks 8–10: Cost acceleration. A second round of candidates. The best profiles seen so far are no longer available – they accepted offers in weeks 4–5. What is left is the pool that has been on the market longer than the best candidates typically remain. An offer is extended to someone who is 80% of what was originally wanted. They accept, but with a three-month notice period. The role will not actually be filled for another 12 weeks.
• Weeks 11–13: Compounding damage. One of the senior engineers who has been covering the gap resigns. They cite workload, reduced quality of work environment, and a better offer from a company that moved faster on their application. The 90-day vacancy is now also a trigger event for a second search.

By the end of week 13, the company has spent approximately $45,000 in direct vacancy cost, made a compromise hire that will take three months to start, and created the conditions for a second departure. Total cost, conservatively calculated: $90,000-$130,000, excluding the second search and the cultural damage that does not have a formula.

The Comparison: What a 21-Day Fill Changes

Every number above describes a process left to run at its own pace. Here is what changes when the same search is run with urgency, structure, and specialist support.

A specialist IT recruitment agency with a maintained candidate network begins sourcing against a confirmed brief within 24 hours. The first candidates are presented within the first week, fully pre-screened with evaluation reports that eliminate the discovery phase from client interviews. The client interviews three candidates over two days. An offer is extended within 48 hours of the final interview. The offer is accepted because it was calibrated against current market benchmarks before it was issued. The role closes on working day 21.

Vacancy cost at 21 days at $500 per day: $10,500. Recruitment fee: ~$16,000. Total first-year hire cost at 21 days: $26,500.

Vacancy cost at 90 days at $500 per day: $45,000. Management distraction and team absorption overhead: $15,000–$30,000. Delivery delay cost on one blocked feature: $10,000–$40,000 (conservative). Secondary departure risk cost: $50,000–$100,000 (if it materialises). Total 90-day vacancy impact: $70,000–$170,000+.

The recruitment fee that was being evaluated against the budget is not a cost to be minimised. It is the mechanism by which a $45,000–$170,000 risk is converted into a $26,500 solved problem.

This is precisely the calculation our clients are making when they contact us about a role that has been open for six weeks internally. Not always by choice – usually after the first compromise candidate declines and the CTO has done the quiet arithmetic.

Why Tech Roles Take Longer Than Any Other Vacancy

Senior engineering roles are not like most open positions, and the factors that extend their vacancy period are specific and identifiable.

1. The best candidates are not visible. The senior engineers worth hiring are employed, doing interesting work, and not updating their CVs. They are reachable through direct outreach and existing professional relationships – not through job board applications. A company that sources entirely through inbound applications is accessing a fraction of the available talent pool, skewed toward candidates who are between roles for identifiable reasons.
2. Technical evaluation adds stages. A senior engineering hire typically requires three rounds minimum: an initial screen, a technical assessment, and a final stakeholder conversation. Each round adds days, and each gap between rounds is a window for competing offers to arrive and be accepted.
3. Compensation benchmarks move faster than most companies update them. The Polish IT market has seen 38% salary growth between 2020 and 2024. A company working from benchmarks that are two years old will build offers that lose candidates at the final stage – after four weeks of process investment. The search restarts from zero.
4. The seniority premium stretches timelines significantly. Senior and staff roles sit at 45 to 90+ days to fill, because these candidates are extremely rarely looking for work on their own – recruiters have to engage in proactive passive hunting and lengthy negotiations. The added complication is that senior candidates have the most competing options and the shortest availability windows. Speed is not just convenient in a senior search. It is determinative of whether you hire from the top of the pool or the remainder.

The Compound Effect: When Slow Hiring Becomes a Pattern

A single 90-day vacancy is a significant but recoverable cost event. A culture of slow hiring – where every role routinely takes three months, the process is rebuilt from scratch each time, and the best candidates are consistently lost mid-process – is a structural competitive disadvantage.

Over time, persistent vacancy cycles lead to reduced service levels, missed deadlines, and client dissatisfaction. Rebuilding lost trust with customers affected by delivery delays caused by understaffing is far more difficult than maintaining it in the first place.

The companies that build sustainable engineering teams – the ones that scale their technical capability in line with their product ambitions rather than constantly playing catch-up – are the ones that treat hiring speed as a performance metric with the same seriousness they apply to sprint velocity, deployment frequency, or sales cycle length.

Our average client lifespan of 4.2 years reflects what happens when companies make that shift: they stop treating each search as an isolated event and start treating hiring as a continuous process with a specialist partner who already knows their stack, their culture, and their hiring standards. The cost of vacancy on their third and fourth searches with us is materially lower than it was on the first – because the brief-to-candidate timeline compresses with each engagement as our understanding of the client deepens.

The Cost of Vacancy Calculator: Apply It to Your Open Role

Use this simplified framework to estimate what your current open role is costing you.

• Daily productivity loss: Annual salary equivalent ÷ 260 = daily cost For a senior Polish engineer at $84,000/year: $323/day For a US equivalent at $160,000/year: $615/day
• Team absorption overhead (add 25%): $323/day × 1.25 = $404/day (Polish senior) $615/day × 1.25 = $769/day (US senior)
• Days vacant so far: Multiply your daily cost by the number of days the role has been open.
• Delivery delay factor: If the open role is blocking a product delivery or team function, add the estimated revenue or milestone value of what is delayed, divided by the weeks of delay.
• Burnout and secondary departure risk: If your team is visibly absorbing the workload of the missing role, add a 20–40% probability-weighted cost of one secondary departure (replacement cost is typically 50–200% of annual salary for a senior engineer).

Most companies who run this calculation find that the cost of vacancy on a senior engineering role open for 60 or more days has already exceeded the recruitment fee required to close it. The decision to engage a specialist agency is not a cost decision. It is the point at which the alternative becomes more expensive than the solution.

What the Data Says About Closing the Gap

The industry average time to fill for a senior tech role is 48 to 90 days. Itentio’s documented average across senior IT roles in Poland is 3 to 4 weeks – with specific cases closed in 3 working days, 7 working days, and 18 working days for two simultaneous senior hires.

The full methodology behind that figure – what the clock measures, what produces the speed, and what conditions it depends on – is documented in our time to fill methodology article.

The short version: sourcing begins within 24 hours of a confirmed brief. A pre-built database of 37,000+ IT professionals eliminates the two to three week cold-sourcing phase that a company starting from scratch cannot avoid. Every candidate is presented with a comprehensive evaluation report that eliminates the discovery phase from client interviews. And our 99% candidate retention rate means the placement that closes the vacancy holds – eliminating the secondary search that a poor-fit hire would eventually require.

The gap between the industry average and Itentio’s average time to fill, applied to your open role, is measurable in dollars. At $500 per day, the difference between a 21-day fill and a 60-day fill is $19,500 in direct productivity cost alone – before team overhead, delivery delays, or management distraction are included.

If you want to understand what that calculation looks like for your specific open role – the profile, the Polish market supply picture, and the realistic timeline – that is the conversation we start with.

Frequently Asked Questions

Stop Treating the Vacancy as the Neutral Option

The most persistent misconception in tech hiring is that an open role is a cost-neutral holding position. The salary is not being paid, the logic goes, so the company is saving money until the right person is found.

The data says otherwise. When companies decide not to hire because it is “not in the budget”, they inadvertently prioritise short-term savings over long-term success – because the cost of the vacancy accumulates silently while the decision is deferred.

A 90-day vacancy on a senior engineering role at a growth-stage technology company is not a neutral event. It is a $45,000–$120,000 cost event, dressed up as patience.

The question is not whether you can afford to hire. It is whether you can afford not to – and how much of that vacancy cost has already been spent.

Explore Itentio’s IT recruitment services in Poland →

See documented hiring timelines across real case studies →

Read the full time to fill methodology →

Contact us to discuss your open role →