Paraphrasing William Gibson, the future of AI is here, but it's nowhere close to evenly distributed yet. This observation captures the current state of enterprise AI adoption more accurately than any sweeping headline. While some organizations race ahead with fleets of AI agents and LLM-generated code, others remain stuck in pilot mode, struggling to move beyond experimentation. The divide is not simply between early adopters and laggards; it cuts across industries, companies, and even teams within the same organization.
The Uneven Landscape of AI Adoption
Recent conversations with engineering leaders in London illustrate this disparity starkly. At a large hedge fund, the head of engineering described teams with multiple AI agents in full production, where LLMs write all new code, and junior hires are deliberately restricted from using these tools to ensure they learn fundamentals. Conversely, a data engineer at a major retail bank reported no agents and minimal LLM usage in her division. Both are in finance, both face similar pressures, yet their AI adoption curves are polar opposites.
This pattern is confirmed by broader data. McKinsey's 2025 survey found that 88% of organizations use AI in at least one business function, but only about one-third have begun scaling AI programs. For agentic AI, just 23% report scaling such systems, while 39% are still experimenting. In no business function do more than 10% of respondents claim to be scaling agents. Deloitte's 2026 enterprise AI research echoes these findings: only 25% of companies have moved 40% or more of their AI pilots into production, and just 34% say they are using AI to deeply transform their businesses. The remaining 37% are applying AI at a surface level with little change to core processes.
These numbers suggest that broad usage does not equal deep institutional change. The real challenge lies not in accessing AI technology, but in integrating it into repeatable workflows and decision-making processes. Organizations that have learned to weave AI into their operational fabric are pulling ahead, while those still treating it as a promising experiment risk falling behind.
AI and the Engineering Job Market
Despite fears that AI will eliminate software jobs, the data tells a different story. 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. More importantly, 44.6% of these roles are entry- or mid-level, compared to 38.3% at senior level and 13.8% at senior-plus. Companies still want engineers, and they want them at all stages of experience.
This is consistent with Jevons paradox, as noted by Box CEO Aaron Levie: when a capability becomes cheaper and easier to consume, demand for it often rises rather than falls. Cloud computing did not reduce the need for compute; it sparked an explosion of new applications. AI-assisted coding is following a similar trajectory. By lowering the cost of producing code, AI encourages organizations to build more software, not less. Stack Overflow's 2025 survey found that 84% of developers use or plan to use AI tools, with just over half using them daily. McKinsey's own research on software development shows that the highest-performing AI-driven organizations see 16–30% improvements in productivity, customer experience, and time to market, along with 31–45% improvements in software quality.
However, these gains do not come automatically. They require reworking roles, workflows, and the entire product development system. Simply sprinkling copilots over unchanged processes yields limited results. The companies that succeed are those that redesign how engineering teams operate, emphasizing specification, review, steering, and orchestration over manual code authoring.
Governance and Organizational Readiness
Why do some teams lag? Governance is a major barrier. Deloitte reports that only 21% of surveyed companies have a mature governance model for autonomous agents, and 73% cite data privacy and security as top risks. Forty-six percent cite governance capabilities and oversight as a concern. These are not trivial issues. Plugging non-deterministic AI systems into deterministic, compliance-heavy environments is inherently messy, especially in regulated industries like finance and healthcare.
OpenAI's enterprise usage data underscores the unevenness. Frontier workers—those in the 95th percentile of adoption intensity—send six times more messages than the median worker. Frontier firms send twice as many messages per seat. The primary constraints, according to OpenAI, are no longer model performance or tools but organizational readiness and implementation. The real divide is between teams that have learned to integrate AI into repeatable work and those still treating it as a promising but dangerous sideshow.
This organizational gap is widening. Every quarter a team spends in pilot mode is a quarter in which more aggressive peers are building operational muscle and learning how to govern AI effectively. The cost of caution is not zero; it is the opportunity cost of falling behind in a fast-moving landscape.
Task vs. Job: The Real Impact
Understanding the difference between task and job is crucial. Writing boilerplate code is a task. Engineering is a job that bundles judgment, trade-offs, accountability, architecture, security, integration, testing, and the messy reality of operating systems in production. AI can automate more tasks, but it has not eliminated the need for the job itself, especially in environments where bad software decisions have serious operational or regulatory consequences.
McKinsey's broader AI survey reinforces this view: high performers stand out precisely because they redesign workflows and treat AI as a catalyst for innovation and growth, not just efficiency. They invest in governance, training, and process redesign. They do not simply give everyone a chatbot and expect headcount reductions. The result is a repricing of software engineering. Code may become cheaper to produce, but the ability to decide what should be built, how components should fit together, and how to prevent breakdowns continues to grow in value.
The hedge fund engineering leader's experience is a glimpse of this future: less time hand-authoring code, more time specifying, reviewing, steering, and orchestrating systems that generate code. But the retail bank's caution is not irrational. In heavily regulated environments, governance is the hard part. The two realities coexist, and they are both legitimate responses to the same technological shift.
Ultimately, AI is not plodding toward a uniform enterprise future where software engineers quietly fade away. Instead, it 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 future of enterprise AI is uneven, messy, and full of organizational learning curves. But for teams willing to adapt, the opportunities are substantial.
Source: InfoWorld News