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
Labels:

Comments

Post a Comment

Popular posts from this blog

Cloudbees Is A Launch Partner For Google Cloud Run As Product Goes Ga

Industry Leaders Collaborate to Offer Streamlined Deployment of Containerized Applications, Better Access to CloudBees Solutions on Google Cloud Platform Marketplace   GOOGLE CLOUD NEXT, LONDON AND SAN JOSE, CA. – November 20, 2019 – CloudBees, the enterprise DevOps leader powering the continuous economy, today announced an extension of its partnership with Google. As a Google […] The post Cloudbees Is A Launch Partner For Google Cloud Run As Product Goes Ga appeared first on DevOps.com . from DevOps.com https://ift.tt/2XuFTxc
Post a Comment
Read more

Carbon-Aware DevOps: Turning CI/CD Pipelines Into Emissions-Controlled Workloads 

Turning continuous integration and continuous delivery (CI/CD) pipelines into emissions‑controlled workloads is a strategy businesses adopt to reduce the carbon footprint of their pipelines. This article examines how a Carbon-Aware DevOps strategy can help optimize CI/CD pipelines for sustainability by reducing their carbon footprint while also decreasing costs and meeting the increasing demand for innovative, eco-friendly solutions.   Understanding the Problem   Today’s organizations take advantage of CI/CD pipelines to streamline and accelerate their software delivery. However, these CI/CD pipelines can become a hindrance to sustainability because of the resources required to create, build, test and ultimately deploy software into production.   Typically, CI/CD pipelines run tens of thousands of automated builds, tests and deployments daily, thereby consuming significant compute and energy resources. If you don’t take the steps necessary to reduce the emissions generated by these ...
Post a Comment
Read more

Why Endpoint Protection Matters More than Ever in CI/CD Environments

CI/CD environments depend on far more than repositories and deployment infrastructure. Developer endpoints hold sensitive data: cloud credentials, SSH keys, deployment permissions, direct access to internal systems. Endpoint security and control are part of daily operational risk management. Engineering teams are shifting more and more toward distributed workflows, so discussions around CI/CD security include the security posture of the devices connected to the pipeline. Many organizations already focus their CI/CD security efforts on secrets management , dependency scanning and supply chain controls. However, advanced endpoint security solutions are also relevant in cloud-native development environments, where local devices maintain direct access to production workflows. Endpoint Compromise Can Bypass Mature CI/CD Controls CI/CD security discussions mostly focus on repositories, containers, infrastructure, and deployment automation. Developer endpoints are often overlooked as a par...
Post a Comment
Read more