Skill Shift, Not Replacement: What Developers Report About Working With AI

Companies are automating production faster than they are building review and accountability. That gap is the new control debt.

A great deal gets written about AI and developer jobs, mostly on the basis of studies from economics, consulting and HR. Through the Python Software Association Germany we took the opposite route and asked the people doing the work: 383 developers from the PyCon DE community reported how AI is changing their working day. Handelsblatt has reported on the findings. The strongest result is not about whether jobs disappear, which this survey does not measure, but about a structural gap. Intensive AI use creates new reviewing, accountability and assurance work for which the structures are often missing. I call that gap control debt.

At a Glance

• AI use is routine in this community: 96 percent reach for AI tools at least several times a day, and a good one in five automates more than half of their routine tasks. Whether that creates or removes jobs was not surveyed.
• The work is moving rather than disappearing: 68 percent name reviewing and curating AI output as a new task, and only 9 percent see no significant new tasks at all.
• The skill shift has a clear direction: domain knowledge (60 percent), architecture (56 percent) and requirements communication (48 percent) are gaining value, while AI is used most heavily for code, documentation and research.
• The real gap is organisational: 71 percent say accountability for AI-induced defects is not explicitly defined, only 11 percent have a documented framework, and only 30 percent have a formal evaluation. That is exactly where control debt accumulates.

We Asked Practitioners Instead of Talking About Them

Most numbers on the future of developer work come from economic models, analyst reports or HR surveys that observe the people affected from the outside. This survey turns the perspective around and asks the people who put AI to productive use every day.

The sample is self-selected and only partly representative of the German developer market in 2026. Respondents are predominantly experienced, actively invest in keeping their skills current and attend professional conferences: early adopters rather than the average. That is precisely what makes the survey valuable. It shows what is happening where AI is already used intensively. Their experience is an early signal of which changes could become relevant for other development teams as AI use spreads.

The New Work: Reviewing, Curating, Steering

The most robust finding sits on the other side of automation: AI takes tasks over and creates new ones at the same time. 68 percent of respondents name reviewing and curating AI output as a new task. 48 percent write prompts and instructions more often, 38 percent prepare context for the tools. Only 30 respondents see no significant new tasks.

So new work appears alongside the automated kind. AI assists with code, tests, documentation and research, and the control work grows in parallel. Whether the total volume of work rises or falls cannot be derived from this survey. One thing does stand out: across more than 1,200 free-text responses from the 383 participants, not one spontaneously reports job cuts caused by AI. The question was not put directly, which makes this an interesting null finding rather than evidence about the labour market. At the same time, only 4 percent experience their work as devalued, and 45 respondents say they would welcome additional conventional developers in their teams.

Development work is also not a fixed pie. When AI lowers the cost of building, applications become viable that would previously have failed on budget. Automation can therefore create new development work instead of merely replacing existing work (see also the Jevons paradox).

Anyone whose strategy thinks only in terms of replacement underestimates that dynamic. What matters is identifying where the additional value sits and funding it deliberately.

The new work comes at a price. 67 percent describe AI-intensive working days as denser, more demanding, or equally demanding at higher output. Only 6 percent feel noticeably relieved. AI does automate routine, but the capacity it frees is quickly taken up again by review, steering and rising expectations. So far the productivity gain shows up less as relief than as a denser working day.

Development work is turning into review work. Leave it out of the plan and you still get it: unbudgeted, invisible, and paid for out of the substance.

Skill Shift: From Producer to Accountable Reviewer

Putting the two sides next to each other shows most clearly which skills are gaining value and what AI is actually used for:

The left column shows what is newly emerging or gaining value, the right what respondents use AI for, which ranges from assistance to full handover of a task. The pattern is clear either way: judgement, control and context competence are gaining weight, while AI is deployed mainly on the producing side of the work.

Prompting is a new activity for 48 percent, but only 32 percent count it as a skill that gains them value. Context and domain knowledge matter considerably more. That supports the hiring logic of the "domain expert with an appetite for experimentation" I described after PyCon DE & PyData 2026.

The shift looks different depending on the field of work. Data engineers move furthest towards subject-matter depth and business translation. Web developers increasingly take on the architecture and control of generated code. ML engineers use AI most intensively and most often build evals, context pipelines and agent control. A possible new role profile is taking shape here: the eval engineer, already visible in practice before the job ads catch up.

Trust Is Growing Faster Than Control

The most revealing finding sits outside the jobs debate. Trust in AI output has recently risen for 58 percent, while the control structures are not keeping pace. 89 percent review AI output manually, but only 30 percent have a formal eval pipeline. 14 percent mostly go on gut feel.

Accountability is usually unresolved as well. 71 percent say it is not explicitly defined who answers for a defect caused by AI. In practice it lands with the developer who accepted the code. Only 11 percent have a documented framework with mandatory review, sign-off and audit trail. This is exactly where control debt builds up: production is automated faster than review, accountability and governance can grow. Like technical debt it stays invisible at first, right up to the point where it falls due.

The data also shows that AI adoption is not merely a technology problem. Asked for the biggest bottlenecks, respondents name unclear responsibilities (40 percent) plus security, data protection and the EU AI Act (36 percent), not the tools themselves. The decisive problems arise at the interfaces between the executive level, engineering and compliance.

The 59 incidents described make that concrete: scope changed silently, hidden code duplicates, proposals to delete production data despite guardrails. One respondent sums up the underlying pattern:

"It happens fairly often when generating code that package versions are simply invented […] If you trust that blindly, you quickly end up in a spiral of hallucinations and debugging in completely the wrong place." (translated from German)

The new review work only becomes durable as a system: as a harness of evals, audit trail and governed release. I described the same pattern through trust boundaries in Agents in Production. Left as individual heroics at a departmental boundary, the control work simply drains away.

Rethink, Don't Replicate

A finding is not yet an instruction, so here is the reading. Map existing processes one-for-one onto AI and you automate their weaknesses along with them. The Economist describes this pattern using India as its example: plenty of parties solve their part of the task, yet without integration no working whole emerges. AI agents carry the same risk. Each individual result can be plausible while accountability and control over the end-to-end process are missing. The answer is not more manual review but control as a system, plus the willingness to reorder processes and accountability. How harness, evaluation and governance fit together is something I set out in The New AI Architecture in 2026.

For Decision-Makers, This Means

First: Budget Control Work as Real Work

Reviewing, curating and steering AI output is daily reality for 68 percent. That work takes time and therefore belongs in the plan. Leave it out and you risk overload and lost quality. That is the first instalment falling due on the control debt.

Second: Organise Governance as a Cross-Cutting Function

The bottleneck is not only technical, it is unresolved accountability. For 71 percent it is not explicitly defined who answers for defects caused by AI. Durable AI use therefore needs a shared accountability model across the executive level, engineering, security and compliance: mandatory review, sign-off and audit trail, carried jointly instead of delegated downwards.

Third: Scale Manual Review With Evals

89 percent review AI output manually, but only 30 percent have a formal evaluation. As AI use grows, that review load can become the bottleneck. Manual review stays important, but it needs a scalable, reproducible and evidenced complement: your own versioned eval sets with clear subject-matter ownership.

Fourth: Rethink Profiles and Collaboration

The survey measures no employment effects, but it does show a clear skill shift. Domain knowledge, architectural judgement and eval competence are gaining weight. Roles, skill development and recruiting should be aligned to that.

Nor is this a one-way street for developers. AI also enables business functions to take on tasks that previously depended on development teams, and new forms of collaboration follow from that. The decisive question is less which task belongs rigidly to which role, and more this: who does what best, and how does the team work with AI to greatest effect?

That several respondents miss having additional conventional developers in their teams underlines the point. Automation does not automatically remove the need for development.

The common denominator across these four points is a question of organisation, not of tooling. Control debt accumulates at the seams between the executive level, engineering and compliance, wherever accountability is not clearly defined.

That gap does not close from inside a single department. It takes someone who is taken seriously from the executive floor down to the developer team and who translates in both directions. That is my work as an independent advisor: connecting the levels, putting what AI actually delivers into perspective, and turning control work into governance that holds. If you want to know where your own control debt is largest, the Boardroom-to-Code Session is the structured way in.

The more intensively developers use AI, the more important the work that hardly any company has organised: reviewing, assigning accountability, securing quality.

On the Methodology

The figures come from a self-completion survey run by the Python Software Association Germany in the PyCon DE community, which I co-led, fielded in early June 2026 via Tally. 383 people took part, 340 of them completing it. The sample is self-selected, senior-heavy, AI-fluent and predominantly based in Germany. It delivers an early signal, not a representative average.

The response base varies by question between 317 and 381 people, and all percentages refer to the base of the respective question. For central findings the base is named in the text. Employment effects such as hiring, job cuts or team sizes were not surveyed. Free-text answers were analysed by keyword and should be read as lower bounds. Handelsblatt has reported on the findings.

About the Python Software Association Germany

The Python Software Association Germany (Python Software Verband e. V.) has promoted the Python programming language in the German-speaking world for more than 20 years. It runs formats such as PyCon DE and EuroSciPy, supports free software and community initiatives, and is entirely volunteer-run. Its chairs are Dr. Mike Müller and Alexander C. S. Hendorf.