← zabolotny.de
DEENRUUA

Home / Notes

Career · DevOps · Field report

Career change into DevOps in Germany: my plan, my evidence, my gaps

I am looking for a permanent IT job, with DevOps and platform engineering as the best fit. This is an open account of what the market offers according to the numbers, where I come from and how I make my skills verifiable.

Serge Zabolotny ·

What the market offers, by the numbers

According to Bitkom’s survey of 3 September 2026, Germany is currently short of 79,000 IT specialists – 109,000 in 2025 and 149,000 in 2023. The shortage has almost halved but has not disappeared. At the same time 42% of companies use AI in IT; only 10% of those have cut jobs because of it, and 32% expect cuts in future. The interpretation is covered in detail in The world in 10–20 years: three scenarios.

For newcomers the picture is mixed: a Stanford study (“Canaries in the Coal Mine”, Brynjolfsson et al.) found a relative employment decline of 13% for 22–25-year-olds in the most AI-exposed occupations in the US, while experienced workers stayed stable. That is US data and no proof of causation – but a hint that evidence of skill matters more at entry.

Where I come from

My evidence: what you can read on this website

SkillEvidence
Linux, virtualisation, containerssplitting Proxmox and LXC
CI/CD, deploymentGitHub Actions, Next.js and VPS
Security, accesszero trust for the homelab
Backup, operationsbackup 3-2-1 and restore test
A product from idea to operationMeisterMeld and PflegeOasis
AI under human controlAI content with human-in-the-loop

My gaps, stated openly

So far I have not worked in a large team with on-call duty and production responsibility, and my operations mostly run in my own homelab and on individual servers, not in large cloud environments with many people involved. That is the gap I want to close in a permanent role – and the reason I document my work so publicly. I follow regulations such as the CRA, NIS2 and the AI Act because they will shape the everyday life of DevOps teams in Germany.

If you are starting similarly: three practical steps

  1. Run something real, not just tutorial copies: a server, a service, backups, monitoring.
  2. Document it publicly, with decisions and mistakes. A note with commands and limits says more than a list of buzzwords.
  3. Know the framework teams work under: security, reporting duties, evidence.

Sources

Keep reading

DevOps · CI/CD · Next.js

CI/CD for Next.js 15 on a VPS: GitHub Actions, PM2 reload and Caddy

Manual deployments were slow and error-prone. Today a git push is enough – no downtime and no PaaS.

AI · Labour market · DevOps

The world in 10–20 years: three scenarios instead of a forecast

Nobody knows what the world looks like after AI, robots and drones. What one can do: collect measured numbers, derive scenarios from them and ask what stays the same in all of them – from the view of someone working in IT and DevOps.

DevOps · Cloudflare · Zero Trust

Zero Trust for the homelab: Cloudflare Tunnel and Access instead of open dashboards

An internal dashboard was publicly reachable via a subdomain. Here is how I locked it down with Cloudflare Tunnel, Cloudflare Access and Tailscale.

Regulation · Security · DevOps

CRA reporting duty from 11 September 2026: 24 hours, 72 hours, 14 days

Since 11 September 2026, manufacturers of products with digital elements must report actively exploited vulnerabilities – in three stages and on a fixed clock. What this means for development and DevOps teams.

Comments

Join the discussion: comments run on GitHub Discussions (sign in with a GitHub account). Content from GitHub/giscus is only loaded after you click. Privacy

More from practice

Find more notes, case studies and projects on the homepage.

All notes Case study MeisterMeld Case study PflegeOasis Case study Kernbohr-Expert Back to the homepage