Paraphrasing William Gibson, the future of AI is here, but it is nowhere close to evenly distributed yet. This reality became starkly clear during two recent conversations in London that shattered any neat narrative about enterprise AI adoption. In one meeting, the head of engineering at a large hedge fund described teams with fleets of AI agents fully in production, with all code written by large language models (LLMs). Interestingly, junior hires at that firm are not allowed to use LLMs for code assistance. In a separate meeting, a data engineer at a large retail bank painted the exact opposite picture: no agents and sparse use of LLMs. Other parts of the bank may be moving faster, but that division clearly is not.

This contrast is not about one company "getting" AI and the other missing out. Instead, it highlights that even within the same organization, adoption curves for new technologies vary wildly. AI is widening the gap between teams that can absorb it operationally and those that cannot. The best recent data confirms this. McKinsey found that 88% of respondents say their organizations use AI in at least one business function, but only about one-third have begun scaling AI programs. For AI agents specifically, 23% report scaling an agentic system somewhere in the enterprise, while 39% are still experimenting. In any given function, no more than 10% are scaling agents.

Broad usage does not equal deep institutional change. There is still time to figure out AI. Companies are not behind, but the window for gaining a competitive edge is narrowing.

The Engineering Boom and the Jevons Paradox

Despite fears that AI will wipe out software engineering jobs, the data tells a different story. Box CEO Aaron Levie invoked Jevons paradox to explain that when a capability becomes cheaper and easier to consume, demand for it often rises. Cloud computing did not lead to less compute; it led to more. The same dynamic is playing out with AI-assisted coding. Engineering openings are at their highest levels in more than three years. TrueUp data shows 67,665 open engineering jobs as of March 2026, up 78.2% from the recent low. Notably, 44.6% of posted engineering roles within tech companies are entry and mid-level, versus 38.3% at senior level and 13.8% at senior-plus. AI is not eliminating roles for junior developers; companies still want engineers, even as AI tools spread.

Stack Overflow's 2025 survey found that 84% of respondents are using or planning to use AI tools in development, and just over half of professional developers use them daily. McKinsey's software development research shows that the highest-performing AI-driven organizations see 16% to 30% improvements in productivity, customer experience, and time to market, along with 31% to 45% improvements in software quality. However, these gains do not come from sprinkling copilots over unchanged processes. They come from reworking roles, workflows, and the full product development system. That is a much harder organizational challenge than buying licenses for a coding assistant.

AI is not killing the need for engineers. It is changing what enterprises want from engineers. The hedge fund leader from London offers a glimpse of where parts of enterprise engineering are headed: less time hand-authoring code, more time specifying, reviewing, steering, and orchestrating systems that generate code. But the retail bank division is not irrationally lagging. In a heavily regulated environment, code generation is not the hard part; governance is.

Governance and the Real Divide

Deloitte's 2026 enterprise AI research found that only 21% of surveyed companies have a mature governance model for autonomous agents—and those 21% are probably kidding themselves. Meanwhile, 73% cite data privacy and security as a top risk, and 46% cite governance capabilities and oversight. This is not bureaucracy for its own sake; it is recognition that plugging non-deterministic systems into deterministic, compliance-heavy environments gets messy fast.

Caution is not free. Every quarter a team spends in pilot mode is a quarter in which more aggressive peers are building operational muscle. OpenAI's enterprise usage data shows how uneven that muscle-building already is. Frontier workers—defined as the 95th percentile of adoption intensity—send six times more messages than the median worker. Frontier firms send twice as many messages per seat. OpenAI says the primary constraints are no longer model performance or tools, but rather organizational readiness and implementation.

This rings true. The real divide is increasingly not between companies that have access to AI and those that do not. It is between teams that have learned to integrate AI into repeatable work and teams still treating it as a promising but dangerous sideshow. The distinction between task and job matters. Writing a chunk of boilerplate code is a task. Engineering is a job. Jobs bundle judgment, trade-offs, accountability, architecture, security, integration, testing, and the ugly reality of operating systems in the real world. AI can automate more tasks, but it has not eliminated the need for jobs, especially in environments where bad software decisions carry real operational or regulatory consequences.

In fact, McKinsey's broader AI survey found that most organizations are still navigating the transition from experimentation to scaled deployment. High performers stand out precisely because they redesign workflows and treat AI as a catalyst for innovation and growth, not just efficiency. That is a very different thing from saying, "We gave everyone a chatbot and now we need fewer people."

So no, AI is not plodding toward one uniform enterprise future where software engineers quietly fade away. Instead, AI is splitting enterprises into fast-learning and slow-learning teams. It is rewarding organizations that redesign work, govern risk, and turn lower software costs into more software, not less. The code may be getting cheaper, but the ability to decide what should be built, how it should fit together, and how to keep it from breaking the business keeps increasing in value. That is not the death of software engineering. It is the repricing of it, and every company and every team is paying different prices.

Source: InfoWorld News