Google has tripled its AI-generated code share in just 18 months, reaching 75% of all new code as of April 2026. CEO Sundar Pichai announced the milestone at Google Cloud Next 2026, revealing a dramatic acceleration in how the company's engineering teams build software. The jump from roughly 25% in October 2024 to 50% by fall 2025 and then to 75% by spring 2026 signals a fundamental shift in what coding work looks like at scale.

What Does "AI-Generated Code" Actually Mean at Google?

When Pichai cites the 75% figure, he's referring to code that AI systems suggest and humans then review, edit, or approve before it gets merged. Every commit still passes through human review and automated tests. AI isn't deploying code on its own; instead, it's accelerating the suggestion and iteration phase. The primary tool driving this is Gemini 3.1 Pro, Google's in-house large language model (LLM), which engineers use for code generation, refactoring, and large-scale migrations.

The real-world impact is measurable. Pichai pointed to a concrete example: a complex code migration that would have taken engineers significantly longer to complete alone finished 6 times faster when engineers and AI agents worked together. This isn't about replacing engineers; it's about changing what their time is spent on.

Why Is Google's Internal Reality More Complicated Than the Headlines?

Here's where the story gets interesting. While Google officially credits Gemini 3.1 Pro for its AI-code dominance, multiple public sources reveal that a meaningful number of Google engineers are actually using Claude Code, Anthropic's competing AI coding agent, internally. In January 2026, Jaana Dogan, a principal engineer on Google's Gemini API team, posted publicly that Claude Code reproduced a complex distributed-systems design her team had spent a year developing in roughly one hour. The post garnered 5.4 million views in 24 hours.

Business reporting from April 2026 indicated that parts of Google DeepMind have official access to Claude Code. This two-tier setup, where engineers have access to both Gemini and Claude tools, reflects a broader reality in the AI-coding landscape: no single tool dominates completely, even within companies that build their own models.

How Is This Reshaping Engineering Work?

The shift toward AI-generated code is fundamentally changing what engineers spend their time on. Less time is spent on typing and routine code generation. More time goes to code review, architectural design decisions, and judgment calls that require human expertise. This isn't a reduction in engineering work; it's a reallocation of effort toward higher-level problem-solving.

The broader context matters here. As of May 2026, Claude dominates the coding-tool space by a significant margin. A Pragmatic Engineer survey from February 2026 found that Claude Code was named the "most loved coding tool" by 46% of respondents, compared to 19% for Cursor and 9% for GitHub Copilot. On coding benchmarks, Claude Sonnet 4.6 scored 82.1% on SWE-bench Verified, an 18-point lead over Gemini 3 at 63.8%.

Steps to Understanding AI-Code Integration in Your Organization

• Layer 1 (Individual Tools): Engineers use AI coding assistants daily, but no organizational metrics reflect the impact yet. Most companies are stuck here, with tools deployed but no bridge to business outcomes.
• Layer 2 (Operations): AI-code metrics start showing up in team productivity numbers, code review times, and deployment velocity. Google's 75% figure is a Layer 2 metric.
• Layer 3 (Customer-Facing Product): AI-generated code directly improves customer-facing features, performance, or time-to-market. This requires integration with product roadmaps and customer feedback loops.
• Layer 4 (Multi-Agent Autonomous Execution): Multiple AI agents run in parallel on different tasks, with humans approving only key decisions. This is the frontier; Anthropic itself operates this way internally.

Google's 75% figure suggests the company has pushed well into Layer 2 and is experimenting with Layer 3 and Layer 4 capabilities. The gap between Google's numbers and what most other companies report reflects not just tool adoption, but organizational integration at multiple levels.

What Does This Mean for the Future of Coding?

The acceleration from 25% to 75% in 18 months isn't a one-time jump; it reflects a compounding effect. As AI tools improve, engineers get faster at using them. As engineers get faster, they can tackle more complex problems, which in turn generates better training data for the next generation of models. This feedback loop is likely to continue accelerating.

The fact that Google engineers are using Claude Code alongside Gemini suggests that the future of AI-assisted coding won't be dominated by a single vendor. Instead, engineers will likely have access to multiple tools and choose based on the task at hand. This mirrors how software development already works: teams use different languages, frameworks, and platforms for different problems.

For organizations watching Google's progress, the takeaway is clear: AI-generated code isn't a future possibility; it's reshaping how engineering work happens right now. The question isn't whether to adopt AI coding tools, but how to integrate them into your organization's workflows, review processes, and skill development in ways that actually move business metrics.