Skip to main content

Google CEO Says 75% of New Code is AI-Generated

The era of the “human-only” software engineer is rapidly receding into the rearview mirror.

Google CEO Sundar Pichai revealed Wednesday that a whopping 75% of the company’s new code is now generated by artificial intelligence (AI), marking a major shift in how the tech giant builds its products.

The velocity of this transition has caught even industry observers off guard. Just 18 months ago, in early 2024, AI-generated code accounted for only a quarter of Google’s output. By late 2025, that figure had climbed to 50%. Today’s 75% milestone signals that AI has moved from a supplemental “autocomplete” tool to the primary engine of production at Google.

Pichai noted that the workflow has evolved into something “truly agentic.”

Instead of human engineers laboriously writing lines of code or using AI to finish a single sentence, they are now supervising autonomous digital teams. These AI agents can plan, execute, and refactor entire codebases with minimal human intervention.

The efficiency gains are difficult to ignore. Pichai highlighted a recent complex code migration that was completed six times faster than was possible just one year ago. “Engineers are increasingly orchestrating systems,” Pichai said, moving the human role away from manual input and toward high-level system architecture and oversight.

Google is not alone in this aggressive pivot. The tech sector is racing toward an AI-first development model.

Meta Platforms Inc. has set internal targets for 2026 and expects 65% of its engineers to use AI for more than 75% of their committed code. Snap Inc. recently reported that 65% of its new code is AI-generated, a shift so profound it reportedly led to immediate adjustments in planned headcount. And Microsoft Corp. Chief Technology Officer Kevin Scott previously predicted that 95% of all code would be AI-generated within five years, a timeline that looks increasingly plausible.

While productivity is soaring, the human cost is becoming visible at the entry level. The rapid adoption of AI is effectively hollowing out the traditional career ladder. Because AI can now handle the routine tasks typically assigned to interns and new graduates, junior engineers are finding themselves an endangered species.

A recent Stanford University analysis found that employment rates among younger software developers have plummeted 20% since the peak in late 2022. As AI agents take over codebase migrations and routine refactoring, the entry-level bar is being raised to heights many graduates struggle to reach.

The transition hasn’t been without its growing pains. Within Google DeepMind, some teams have reportedly pushed to use external tools like Anthropic’s Claude Code alongside Google’s own Gemini models. This has created internal friction around tool standardization and the company’s broader AI strategy.

Ultimately, the message from Google is clear: the craft of programming is being redefined. At Google, the primary “writer” is now the machine, and the engineer has become the editor-in-chief.



from DevOps.com https://ift.tt/bmuf2qO

Comments

Popular posts from this blog

Why the Software Development Tools you Choose Directly Affect Your CI/CD Reliability 

Most conversations about CI/CD reliability start in the wrong place. Teams debug flaky pipelines, investigate intermittent failures, tune alerting thresholds and optimize build times. All of that work is legitimate. However, the decisions that most directly determine whether a CI/CD pipeline is reliable or not were made months or years earlier, during tool selection. By the time teams are debugging pipeline reliability, they are usually dealing with the downstream consequences of upstream decisions that seemed reasonable at the time.   The software development tools a team chooses shape their CI/CD pipeline in ways that are not always visible during evaluation. Understanding those connections is the most practical starting point for teams that want reliable pipelines rather than better pipeline firefighting.   The Integration Surface Problem   Every tool in a software development stack creates an integration surface. Integration surface is the set of connections a tool has with oth...

They Survived Covid. Now They Need New Lungs.

They Survived Covid. Now They Need New Lungs. By Daniela J. Lamas from NYT Opinion https://ift.tt/3aQtonL Transplants, Lungs, Coronavirus (2019-nCoV), Hospitals