Paraphrasing William Gibson, the future of AI is here, but it's nowhere close to evenly distributed yet. This observation captures the essence of enterprise AI adoption today: a landscape marked by extreme disparity across companies, industries, and even within the same organization. Two recent conversations in London illustrate this perfectly. In one meeting, the head of engineering at a large hedge fund described teams with fleets of fully operational AI agents, where all code is now written by large language models. Interestingly, junior hires are not allowed to use LLMs for code assistance. In another meeting, a data engineer at a large retail bank described a completely opposite scenario: no agents, sparse use of LLMs, and a division that remains cautious about embracing AI. These anecdotes are not outliers; they reflect a broader pattern of uneven adoption that is reshaping enterprise technology landscapes.

This unevenness is not simply about one company "getting" AI while another lags. Rather, it highlights a deeper organizational challenge: even within the same company, different teams have wildly divergent adoption curves for new technologies. AI is widening the gap between teams that can absorb it operationally and those that cannot. Recent data from McKinsey supports this view. Their research found that 88% of respondents say their organizations are using AI in at least one business function, but only about one-third have begun scaling AI programs. When it comes to AI agents, the numbers are even lower: 23% report scaling an agentic AI system somewhere in the enterprise, while 39% are still experimenting. In any given function, no more than 10% say they are scaling agents. Broad usage, therefore, is not the same thing as deep institutional change. The message is clear: there is still time to figure out AI, and most organizations are not behind.

Cue the engineering boom

The narrative that "finance is cautious" or "regulated industries are behind" oversimplifies a complex reality. Some financial firms are moving aggressively, while others are not. Some teams inside the same firm are doing both at once. Deloitte's 2026 enterprise AI research reinforces this point. Only 25% of respondents said they had moved 40% or more of their AI pilots into production. Just 34% say they are using AI to deeply transform their businesses (a number that may be more aspirational than actual), while 37% are still using AI at a surface level with little or no change to core processes. This picture looks less like a tidal wave and more like a messy, uneven organizational test. It is the same story that has played out with every major technological shift: adoption is never uniform, and the real gains come from systemic integration, not tool deployment.

This uneven adoption feeds into the ongoing debate about whether AI will wipe out software jobs. The evidence suggests otherwise. The interesting thing about AI coding tools is not that they make software cheaper to produce; it is what companies do with that lower cost. Box CEO Aaron Levie has invoked Jevons paradox to explain this dynamic: when a capability becomes cheaper and easier to consume, demand for it often rises rather than falls. Cloud computing did not lead companies to need less compute; it made them build more things that consumed compute. Similarly, AI-assisted coding may be doing the same for software itself. Data on engineering jobs supports this view. Lenny Rachitsky recently highlighted that 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. Critically, this growth is not concentrated at the senior level. TrueUp's breakdown shows 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. The data does not indicate that AI is eliminating roles for junior developers; rather, it suggests that companies still want many engineers, even as AI tools spread throughout the profession.

There is a cleaner way to understand what is happening. AI is not killing the need for engineers; it is changing what enterprises want from engineers. 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 highlights that the highest-performing AI-driven software organizations are seeing 16% to 30% improvements in productivity, customer experience, and time to market, along with 31% to 45% improvements in software quality. But McKinsey's crucial point is that these gains do not come from sprinkling copilots over an unchanged process. 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.

Software engineering is alive and well

Returning to the London conversations, the hedge fund leader may represent an early glimpse of where parts of enterprise engineering are headed: less time hand-authoring code, and more time specifying, reviewing, steering, and orchestrating systems that increasingly generate code. But that does not mean the retail bank division is irrationally lagging. In a heavily regulated environment, code generation is not the hard part; governance is. Deloitte reports that only 21% of surveyed companies currently have a mature governance model for autonomous agents (and those 21% are probably kidding themselves). At the same time, 73% cite data privacy and security as a top risk, and 46% cite governance capabilities and oversight. That is not bureaucracy for its own sake; it is a recognition that plugging non-deterministic systems into deterministic, compliance-heavy environments gets messy fast.

Still, 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 states that 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 how to integrate AI into repeatable work and teams that are still treating it as a promising but dangerous sideshow.

This is also why emphasizing the distinction between task and job is critical. 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. McKinsey's broader AI survey reinforces this: most organizations are still navigating the transition from experimentation to scaled deployment, and 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 or rocketing toward one uniform enterprise future in which 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