AI’s coding shift is hitting women returning from leave especially hard

The AI transformation of software work has a timing problem as well as a labor problem

For software developers returning from parental leave, the industry’s rapid turn toward AI-assisted coding is creating a particular kind of reentry shock. A WIRED report on women coming back to engineering roles after maternity leave describes a workplace that in many cases changed substantially during their absence, shifting from conventional development practices toward expectations that code will increasingly be generated, completed, or supervised through AI tools.

The broad debate over AI in software has mostly focused on productivity, job security, and the future of programming as a profession. This reporting adds another dimension: timing. The burden of adapting to a fast-moving tool shift does not land evenly across workers. Those who happened to be away from their desks while the change accelerated can return to jobs that feel materially different from the ones they left.

A profession changing during absence

The article centers on developers who stepped out of work before AI coding tools became normalized and returned to find those tools embedded in daily expectations. One software developer told WIRED that the rote development skills she had learned were now expected to be outsourced to AI. Another worker on maternity leave said a manager suggested she should spend part of that leave brushing up on AI, a request that highlighted both pressure and vulnerability.

That pressure is not simply about learning a new product. It is about professional legitimacy. If a workplace shifts from judging engineers mainly on direct composition to judging them on prompt design, review, orchestration, and supervision of machine-generated output, then time away can produce a larger perceived skills gap than in slower technological transitions.

The article frames this as especially acute for new mothers, but the underlying pattern is broader. Any worker who takes extended leave during a period of sharp technical transition risks returning to a changed competency baseline. AI has intensified that effect because the pace of change in developer tooling has been unusually fast and heavily publicized by executives promising near-term transformation.

The workplace expectation problem

One of the most important details in the report is that expectations shifted even where the technical challenge of learning the tools may not be overwhelming. The issue is not merely whether developers can figure out AI coding assistants. It is whether they can do so while reentering work, navigating new caregiving demands, and catching up with peers who have already spent months adapting.

That difference between theoretical learnability and practical fairness matters. A tool can be simple to use and still change workplace power dynamics if some employees are effectively asked to train on their own time while others adapt during paid work. In that sense, the article’s examples are about more than AI. They are about who absorbs transition costs when a field is retooled quickly.

The software industry has long portrayed itself as meritocratic and unusually adaptable. But that self-image can obscure how unevenly adaptation burdens are distributed. A person returning from leave may be entering a team where norms, workflows, and performance signals have shifted under them without formal retraining or protected ramp-up time.

Why the story matters beyond software

The article also captures a larger social theme likely to appear in other white-collar sectors. Executives in AI have repeatedly said that law, finance, consulting, sales, and programming will all be reshaped by generative systems. If those shifts happen quickly, the friction documented here may become a common feature of professional life: workers returning from leave, illness, caregiving, or other interruptions will face not just resumption, but requalification.

That creates a policy and management question. Should adaptation to AI-heavy workflows be treated as an individual responsibility, or as an employer responsibility tied to training and equitable reintegration? The report suggests many workers already feel the answer is drifting too far toward the former.

There is also a cultural contradiction embedded in the story. The tech industry often celebrates AI as reducing drudgery and opening higher-level work. But for people reentering the field, the same shift can feel like a destabilization of the very skills that once made the profession a route to security. That does not mean the transformation is unreal or reversible. It means its costs are showing up first in places the industry has not prioritized.

What makes the piece resonant is that it treats AI not as an abstract productivity wave, but as a workplace change with uneven human timing. In software, the future of coding may increasingly involve guiding machines. For workers returning from leave, the immediate challenge is that the future arrived while they were gone.

This article is based on reporting by Wired. Read the original article.