An open engineering position appears in the monthly management report as a positive variance: salary budgeted, salary not paid. That framing is misleading. The company hired for a reason, and every month without the engineer means planned work does not happen. According to Bitkom's 2025 survey of 855 German companies, there are around 109,000 unfilled IT positions in Germany, and filling an IT role takes 7.7 months on average. A vacancy of that length is not a rounding error. This analysis offers three methods to put a number on it, from conservative to strategic, so that the cost of waiting can be compared with the cost of alternatives.

The macro picture

The company-level cost of a vacancy adds up to a national one. IW Köln estimated in 2024 that the skilled-labour shortage cost the German economy about EUR 49 billion in lost output that year, equal to 1.1 percent of production potential, and projected about EUR 74 billion by 2027. The IT segment is not easing as fast as headlines suggest. IW Köln found that open IT positions fell 26.2 percent in 2024, yet around 70 percent of the remaining positions could statistically not be filled with suitably qualified jobseekers. Bitkom's 2025 survey shows 85 percent of companies reporting a shortage of IT specialists, and Bitkom projects a gap of 663,000 IT specialists by 2040 if nothing changes.

For your own planning, these numbers are context, not inputs. They explain why the 7.7-month average is unlikely to shrink on its own, and why a vacancy should be treated as a recurring cost line rather than a temporary saving.

Method 1: The cost floor

The most conservative assumption is that an engineer creates value at least equal to their loaded cost. If that were not true, the company would not hire. Under this assumption, the minimum monthly cost of a vacancy equals the loaded monthly cost of the role.

In our separate analysis of a German senior hire, we arrived at an illustrative steady-state loaded cost of about EUR 106,600 per year, or about EUR 8,900 per month, for a gross salary of EUR 80,000. Over the 7.7 months reported by Bitkom, the floor is roughly EUR 68,400 of value not created. This number is deliberately low. It is useful precisely because nobody can argue it is inflated.

Method 2: The value multiple

Technology companies hire engineers because they expect them to produce more value than they cost. Some companies express this through revenue per employee, others through gross margin targets or internal business cases. If your company works with an explicit multiple, for example that an engineer must generate value of two times their loaded cost to justify the role, apply it.

Illustrative calculation: with a multiple of 2, the monthly cost of the vacancy is about EUR 17,800, and over 7.7 months about EUR 137,000. The multiple is a company-specific assumption. Do not borrow one from another company or an industry benchmark without understanding its basis; derive it from your own business case for the role.

Method 3: Cost of delay

The most precise method links the vacancy to specific roadmap items. Ask: which deliverables depend on this role, and what does each week of delay cost?

  • A customer feature promised for a contract renewal: the cost of delay may be the renewal value at risk.
  • A product launch: the cost of delay is the margin of the weeks of sales lost, plus any competitive disadvantage.
  • A compliance deadline, for example in medtech or for regulatory reporting: the cost of delay may be a penalty, a blocked market or a delayed certification.
  • An internal efficiency project: the cost of delay is the monthly saving not yet realised.

Illustrative calculation: a vacancy delays a product module by four months. The module is expected to generate EUR 40,000 gross margin per month once live. The cost of delay is EUR 160,000, before any second-order effects. This method produces the most convincing numbers for executive discussions because it speaks the language of the business plan rather than of HR.

Which method for which purpose

The methods are complementary. Method 1 suits internal controlling because it is uncontroversial. Method 2 helps prioritise between several open roles, if the company has a well-founded multiple. Method 3 is strongest for an executive decision on interim budget, because it names concrete deliverables and dates.

Second-order effects

All three methods understate the true cost because they ignore what happens to the rest of the team during a long vacancy:

  • Overload. Remaining engineers absorb part of the work, often through overtime and by postponing maintenance and technical debt reduction.
  • Attrition risk. Sustained overload is a common reason why engineers leave. One vacancy can create a second.
  • Leadership distraction. Engineering leads spend significant time interviewing, which reduces their time for architecture and mentoring.
  • Compromised hiring decisions. The longer a role stays open, the stronger the pressure to accept a weaker candidate.

These effects are hard to quantify but real. In a business case, list them qualitatively next to the number from your chosen method.

A one-page vacancy cost sheet

ItemInput
Role and seniorityFor example: Senior Backend Engineer
Loaded monthly costFrom your cost model
Expected time to fillYour historical data, or the Bitkom average of 7.7 months as a reference
Expected ramp-up after hireMonths to full productivity
Method 1: cost floorLoaded monthly cost multiplied by months vacant
Method 2: value multipleMethod 1 multiplied by your business case multiple
Method 3: cost of delaySum of delay costs of dependent roadmap items
Second-order risksQualitative list

Using the result

The point of quantifying a vacancy is not to create alarm but to enable a comparison. Once you know what a month of vacancy costs, you can evaluate interim measures on equal terms: a higher salary offer to close faster, a retained search, an interim freelancer, or a managed team that covers the work package until the hire is productive. If an interim option costs less per month than the vacancy, it is economically justified even if its rate is higher than the salary of the eventual hire.

Two cautions apply. First, interim capacity must be set up so that it does not create new legal risk; freelancers need a genuinely independent scope to avoid Scheinselbständigkeit issues under SGB IV §7, and external teams should work on defined deliverables rather than under day-to-day direction from your managers. Second, interim capacity also needs onboarding, so the earlier it starts, the more value it captures.

Whichever interim option you consider, start with the number: a vacancy is not a saving, it is a cost that does not appear on an invoice.

This analysis is general information, not legal or tax advice.

Once the monthly cost of a vacancy is on the table, the remaining question is how quickly interim capacity can produce accepted output. niogod™ structures this as a three-person pod under a Werkvertrag, with a sprint-based Leistungsbeschreibung and Abnahme, so the work package is covered without your managers directing individual engineers. If a critical role has already been open for a quarter, that comparison is worth running now.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights