Editorial illustration for Google leaders, Hassabis, refute uneven AI adoption, cite 40K SWEs agentic coding
Google's AI Coding Revolution: 40K Engineers Adapt Now
Google leaders, Hassabis, refute uneven AI adoption, cite 40K SWEs agentic coding
Why does the debate over AI uptake inside Google matter now? A recent internal memo claimed that many engineers still struggle to access the company’s latest coding assistants, suggesting a patchy rollout across teams. While the tech is impressive, critics have pointed to anecdotes that paint a picture of uneven adoption.
But here's the thing: senior leadership has pushed back, insisting the narrative misses the broader reality. Demis Hassabis, DeepMind chief, and other executives have highlighted a suite of internal resources—custom models, specialized CLIs, and multi‑cloud platforms—that are supposedly available to anyone with a Google email. Yet skeptics keep asking whether those tools are truly in everyday use or just shiny prototypes on the shelf.
The answer, according to a Google Cloud AI director, directly challenges the earlier account and quantifies the reach of “agentic coding” across the firm.
Addy Osmani, a director at Google Cloud AI, wrote that Yegge's account "doesn't match the state of agentic coding at our company." He added, "Over 40K SWEs use agentic coding weekly here."
Addy Osmani, a director at Google Cloud AI, wrote that Yegge's account "doesn't match the state of agentic coding at our company." He added, "Over 40K SWEs use agentic coding weekly here." Osmani said Googlers have access to internal tools and systems including "custom models, skills, CLIs and MCPs," and pushed back on the idea that Google employees are sealed off from outside models, writing that "folks can even use @AnthropicAI's models on Vertex" and concluding that "Google is anything but average." Other current Google employees reinforced that message. Jaana Dogan, a software engineer at Google, wrote in a quote tweet: "Everyone I work with uses @antigravity like every second of the day," later following up with another X post stating: "Unpopular opinion: If you think tokens burned is a productivity metric, no one should take you seriously. Imagine you are a top 0.0001% writer and they are only counting the tokens you produce." Paige Bailey, a DevX engineering lead at Google DeepMind, said teams had agents "running 24/7." Several other Google and DeepMind figures also challenged Yegge's characterization, some disputing the factual basis of his claims and others suggesting he lacked visibility into current internal usage.
Yegge’s post sparked a swift response. Google’s senior AI figures, including Demis Hassabis, pushed back, saying the picture of uneven adoption is inaccurate. Addy Osmani, director of Google Cloud AI, countered with concrete numbers: more than 40,000 software engineers run agentic coding tools every week.
According to Osmani, those engineers tap internal models, custom skills, command‑line interfaces and MCPs that the company has built for internal use. The contrast between Yegge’s anecdote and the internal statistics highlights a gap in public perception versus internal practice. Yet the exact depth of reliance on the latest generation of coding assistants remains unclear, as the statements provide usage frequency but not detail on how integral the tools are to daily workflows.
What this exchange shows is a willingness among Google leaders to publicly defend their internal AI strategy while acknowledging that adoption metrics are still being measured. Whether the reported weekly usage translates into broader productivity gains is a question that the company has not answered.
Further Reading
- Google Cloud Study Reveals 52% of Executives Say Their Organizations Have Deployed AI Agents, Unlocking a New Wave of Business Value - Google Cloud Press Corner
- The Agentic AI Adoption Paradox: Why 40% Penetration Doesn't Mean 40% Success - Towards AI
- Somebody Is Lying About Agentic AI Adoption—and You're Paying ... - Cloud Computing Insider
- A Year Just Happened in a Week - by Keith Teare - That Was The Week
Related Reading
Browse all Google news →
Market Trends Rajan says AI-native fundamentals let new grads outpace senior devs
Market Trends India's startups move into hardware as they design AI-native data centres
Market Trends 60% of singles label AI relationships as cheating, sparking divorce concerns
Related Topic Google AI Advisors Let Users Probe Performance with Conversational “Why” Queries
Research & Benchmarks
Related Topic Google adds “Skills” to Chrome, enabling one‑click reuse of Gemini prompts
LLMs & Generative AI
From Archives Google ADK tutorial: Python agents load CSVs, create sample datasets
From Archives OpenAI acquires TBPN to accelerate global AI conversation, memo says
From Archives Developer says he reverse‑engineered Google DeepMind’s SynthID watermark tool
Open Source
From Archives Google AI's Vantage protocol shows Executive LLM beats agents on 8 metrics
LLMs & Generative AI
Common Questions Answered
How many software engineers at Google are using agentic coding tools weekly?
According to Addy Osmani, director of Google Cloud AI, over 40,000 software engineers are using agentic coding tools on a weekly basis. This number directly challenges claims of uneven AI tool adoption within the company.
What internal tools and systems do Google engineers have access to for agentic coding?
Google engineers can access custom models, skills, command-line interfaces (CLIs), and multi-cloud platforms (MCPs) for agentic coding. Additionally, they can even use Anthropic's models on Google's Vertex platform, demonstrating a broad range of AI coding tools available internally.
How did Google leadership respond to claims of uneven AI tool adoption?
Google's senior AI leaders, including Demis Hassabis and Addy Osmani, quickly refuted the narrative of patchy AI tool rollout. Osmani specifically countered the claims by providing concrete evidence of widespread agentic coding tool usage across the company's engineering teams.