IT Skills Shortage in Germany 2026: What the New Bitkom Numbers Mean for Your Software

Bitkom published its latest labor market study on September 3, 2026, and the headline number looks like good news: the IT skills shortage in Germany 2026 stands at 79,000 unfilled positions, down from 109,000 in 2025 and 149,000 in 2023. Almost half the gap has closed in three years. If you run a company that depends on custom software and employs one or two developers to keep it running, the headline is worth reading past, because the numbers underneath it tell a different story for businesses your size.

The IT skills shortage in Germany 2026: what the Bitkom numbers actually say

The study is based on phone interviews with 853 and 602 companies with at least three employees, conducted between weeks 18 and 25 of 2026. The 79,000 figure is real and the trend is real. But two other numbers from the same survey matter more for a company that is not actively recruiting a full IT department:

78 percent of companies still report a shortage of IT talent, even with the total gap shrinking. And 97 percent of companies with open IT roles say they have trouble filling them. Almost a third, 31 percent, get close to no applications at all. The market has fewer open positions in total, but it has not gotten meaningfully easier for any individual company to hire when a role comes open.

Bitkom also asked what kind of roles are hardest to fill. IT administration and systems operation lead at 26 percent, followed by software development and architecture at 17 percent, then cloud and infrastructure at 14 percent. If your company runs a Symfony backend or a React frontend maintained by a small team, you are competing for exactly the roles employers report as hardest to staff.

Why the shrinking gap does not help a two-developer team

The Bitkom numbers describe the aggregate market, which is dominated by large employers with dedicated recruiting teams, employer brands, and the budget to wait out a six-month search. A company running on a lean internal team does not experience the market the same way.

When you employ one developer for your core application, you do not have a shortage problem in the Bitkom sense. You have a single point of failure. That developer takes parental leave, gets a better offer, or simply wants four weeks off, and the software that runs your invoicing, your customer portal, or your internal tools has nobody behind it until they return or until you find a replacement. Bitkom's own numbers suggest that replacement search will take months: with 97 percent of companies struggling to fill IT roles and notice periods of two to three months common in Germany, a single vacancy can leave a small team exposed for a long stretch.

Two developers is better, but only somewhat. If both work on the same codebase and one leaves, the other inherits undocumented decisions, tribal knowledge, and twice the workload, often with no overlap period to hand anything over properly.

None of this shows up in a quarterly report until it does. A company can run for years on a thin bench without incident, then lose a key developer in the same month a major client asks for a new integration, and suddenly the gap between "we have a shortage" and "our software is unmaintained" is a matter of weeks, not months.

The real risk is not hiring, it's coverage

Framed as a hiring problem, the shortage looks abstract, something HR handles. Framed as a coverage problem, it becomes concrete: what happens to your software in the weeks or months between one developer leaving and the next one starting.

This is where the AI angle in the Bitkom study is worth a second look. Of the companies that have already cut IT positions or expect to, 35 percent are using AI to fill roles they could not or would not staff otherwise, and 42 percent of companies with IT roles already use AI somewhere in their IT department or their developers' daily work. That is a meaningful shift, but it is not a substitute for a developer who understands your specific system. AI tools speed up the person who already knows the codebase. They do not replace that person, and they do not fix a bus-factor-of-one problem on their own.

For a company that has never had to hire a developer before, the exposure is often invisible until it becomes urgent. Nobody plans around code that only one person understands until that person is unavailable and a customer-facing feature breaks.

What actually works when your team is this small

There is no single fix, but three approaches consistently reduce the risk, and they are not mutually exclusive.

Document as you go, not after someone leaves. A short handover doc covering deployment steps, third-party accounts, and the reasoning behind non-obvious decisions costs an afternoon now and saves weeks later. Most small teams skip this until it is too late, because it never feels urgent while everyone is still there.

Get an outside read on the codebase before you need one. A review from someone who has never touched your system tells you where the risk actually sits: what parts only make sense to the person who wrote them, what has no tests, what would take a new hire weeks to understand versus days. Companies usually commission this kind of review only after a departure forces the question, when it would have been far more useful three months earlier.

Plan for absences you can see coming. A developer's parental leave, a planned sabbatical, or a long notice period at a new job are not surprises. Starting the handover early, while the departing developer is still reachable for questions, is far cheaper than starting it after they are gone.

Bring in outside cover for the gap itself, rather than trying to permanently replace a role you may only need to bridge. A short engagement with an outside developer or consultancy who can read an unfamiliar codebase quickly, keep it running, and hand it back cleanly is often a better fit than a rushed full-time hire made under pressure. This is close to what teams in Berlin's startup scene are already doing to manage stack decisions and hiring pressure at the same time, as covered in our look at the Berlin startup engineering ecosystem.

If your business runs on a codebase that only one or two people understand, it is worth getting an outside read on how exposed you actually are before a gap forces the question. Wolf-Tech works with companies in exactly this position, reviewing existing PHP, Symfony, and React applications and covering development gaps while a permanent hire is underway. You can reach us through our custom software development services page or write directly to hello@wolf-tech.io.

The Bitkom numbers will likely keep improving over the next few survey cycles. That is good news for the labor market as a whole, and it says nothing about whether your own team can absorb the next departure. The market getting easier in aggregate and your company being exposed are two separate questions, and only one of them is something you can act on directly. It does very little for a company that needs its software running next month, with the two developers it has today, or the one it might have tomorrow.