# The 12 goals Google uses to define AI-driven engineering | LinearB Blog

> Discover Google's 12 goals for AI-driven engineering. Learn the blueprint top teams use to master AI development and gain a competitive edge.

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._


```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://linearb.io/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "The 12 goals Google uses to define AI-driven engineering",
      "item": "https://linearb.io/blog/google-ai-engineering-12-core-goals"
    }
  ]
}
```

[Home](https://linearb.io/)

/

[Blog](https://linearb.io/blog)

/

The 12 goals Google uses to define AI-driven engineering

# The 12 goals Google uses to define AI-driven engineering

![Photo of Ben Lloyd Pearson](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/blp_headshot_1_ee25d527aa?_a=BAVMn6ID0)

By [Ben Lloyd Pearson](https://linearb.io/blog/google-ai-engineering-12-core-goals#ben-lloyd-pearson)

|

June 27, 2025

![Blog_Google_Skills_Map_2400x1256_d3e86fd63c](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Google_Skills_Map_2400x1256_d3e86fd63c?_a=BAVMn6ID0)

The writing is on the wall: AI is reshaping what it means to be a software engineer. While most developers are already experimenting with AI tools, the gap between casual usage and true AI mastery is widening fast. The engineers who determine how to harness AI's full potential will solve fundamentally different problems and deliver previously out-of-reach solutions.

Google released [research](https://arxiv.org/pdf/2506.00202) that cuts through the hype to reveal precisely what separates AI-native developers. Their comprehensive study maps out the 12 core competencies and systematic approaches defining world-class AI-driven engineering and offers a clear blueprint for developer excellence in 2025 and beyond.

If you're leading an engineering team, this is the foundation for building a competitive advantage in an AI-first world.

## **The 12 goals that define AI-driven engineering**

Google partnered with the Education Development Center to conduct a 5-month study using the DACUM methodology. They recruited 21 participants who are experienced developers at the cutting edge of AI tool usage. They work in organizations where AI coding tools are deployed team-wide, with extensive daily experience using GenAI tools for at least 6 months. They submit PRs several times per week containing AI-generated code that has undergone significant iterations. Additionally, participants needed to demonstrate that AI had a "major" or "transformative" impact on their workflows, contribute novel AI use cases not yet reported in literature, and actively mentor colleagues in AI tool adoption.

The research revealed that AI-enhanced developers organize their work around 12 distinct goals that span the entire software development lifecycle.

### **Planning and investigation** 

1. **Contextualize work comprehensively** \- Using AI to synthesize user feedback, analyze competitors, and understand system architecture.
2. **Locate relevant information** \- Leveraging AI to research technologies, libraries, and documentation.
3. **Explore technical solutions** \- Using AI to optimize performance, complexity, cost, and maintainability.
4. **Develop documented plans** \- Creating implementation roadmaps with AI assistance.

### **Implementation and quality**

1. **Produce high-quality code** \- Converting designs to code and reducing complexity.
2. **Create holistic test coverage** \- Using AI to identify failure points and generate comprehensive tests.
3. **Generate assets** \- Creating images, captions, and other resources through AI tools.
4. **Produce up-to-date documentation** \- Generating and maintaining comprehensive documentation.

### **Compliance and operations** 

1. **Ensure legal/privacy compliance** \- Using AI to assess potential violations and generate security tests.
2. **Monitor and generate insights** \- Combining AI with traditional approaches for anomaly detection.
3. **Investigate production issues** \- Using AI to analyze logs, traces, and error patterns.
4. **Improve system reliability** \- Proactively identifying failure conditions and mitigation strategies.

The researchers created an extensive list of 75 tasks that fit into these goals and mapped them to the software development lifecycle.

![ai tasks sdlc.png](https://assets.linearb.io/image/upload/v1751035905/ai_tasks_sdlc_60e05ed78b.png)

The research also identifies a consistent 6-step AI usage pattern that the participants applied to working with AI at all steps of the development process:

1. **Identify** \- Determine what information AI tools need based on their understanding of AI capabilities and the business/technical context.
2. **Engage** \- Express needs with proper context, problem statements, and desired outcomes beyond simple prompting.
3. **Evaluate** \- Critically evaluate AI-generated artifacts against domain knowledge, including sandbox testing and comparison with expected results.
4. **Calibrate** \- Guide AI tools toward desired outcomes with feedback and additional context about systems, products, goals, and trade-offs.
5. **Tweak** \- Improve AI-generated artifacts based on knowledge of expected standards and requirements.
6. **Finalize** \- Produce final documentation and communicate decisions and approaches.

## **The T-shaped map for how to level up in the AI era**

The researchers argue that software engineers must use AI to level up deep expertise and broad knowledge by understanding and effectively using generative AI, including its capabilities, limitations, and interaction patterns. At the core, engineers must maintain strong software engineering fundamentals, including coding proficiency, system design, risk assessment, and debugging skills. This is where most of the first generation of AI tools has focused because they help developers acquire technical knowledge and write code more efficiently.

Beyond this foundation, engineers must expand their knowledge in two key areas: staying updated with adjacent software engineering domains such as cybersecurity, industry regulations, and emerging trends, and developing awareness of non-engineering factors like business context, user needs, and market dynamics.

![t-shaped ai-drive.png](https://assets.linearb.io/image/upload/v1751035904/t_shaped_ai_drive_5df40e6547.png)

The researchers offer four significant pieces of advice to help your engineering organization responsibly adopt AI:

1. **Junior developers need more support.** Less-experienced developers often take longer to solve complex tasks using AI. They need additional training in foundational programming principles before they can effectively leverage AI tools for more advanced use cases.
2. **The future developer looks like today's senior developer.** To fully realize AI's productivity benefits, developers need the skills and knowledge of today's senior developers. This means significant upskilling initiatives across your organization.
3. **Planning work is expanding.** AI frees developers from repetitive tasks, allowing them to spend more time in the planning stages, better understand requirements, explore solutions, and make technical decisions.
4. **Soft skills are more critical than ever.** Strong communication and collaboration skills enable developers to seek help when they reach AI's limits and forge meaningful relationships as AI handles routine interactions.

## **Use AI to achieve a competitive advantage**

Organizations that master AI-enhanced development will be fundamentally different; they'll make better technical decisions, optimize for business and engineering metrics, and continuously experiment under shorter cycles to find optimal solutions. Research is showing growing productivity improvements for developers using AI tools effectively. However, the real advantage comes from elevating the entire development process, from planning through operations to a higher level of sophistication and decision-making quality.

Google’s research represents one of the most comprehensive studies of professional AI-enhanced software development to date. For engineering leaders ready to future-proof their organizations, these insights provide the foundation for building truly competitive development capabilities in the age of AI.

If you want to build on the ideas in this post, we’ve published a detailed [DevEx guide to AI-driven software development](https://linearb.io/resources/devex-guide-ai-driven-software-development) that closely examines how teams adopt AI in practice. It introduces the AI collaboration matrix, a framework for understanding where your organization sits on the spectrum from human-led to AI-led work, and shares survey data from over 400 engineering leaders about their real-world adoption patterns.

The guide also explores common pitfalls teams face when integrating AI, like shallow experimentation or lack of context, and it provides case studies of how companies like Meta and Google use AI to improve testing and speed up large-scale migrations. The guide helps you think more systematically about where AI fits in the SDLC, how to support developers effectively, and what strategic choices can make AI a true force multiplier rather than a one-off tool.

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

![blp_headshot_1_ee25d527aa](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/blp_headshot_1_ee25d527aa?_a=BAVMn6ID0)

## Ben Lloyd Pearson

Ben hosts Dev Interrupted, a podcast and newsletter for engineering leaders, and is Director of DevEx Strategy at LinearB. Ben has spent the last decade working in platform engineering and developer advocacy to help teams improve workflows, foster internal and external communities, and deliver better developer experiences.

### Connect with

[](https://www.linkedin.com/in/benlloydpearson)
[](https://substack.com/@benlloydpearson)

## Your next read

[![Cover image for Code generation is faster than ever, but shipping value isn't](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_AI_code_review_bottleneck_2400x1256_d73333ea46?_a=BAVMn6ID0)](https://linearb.io/blog/code-generation-faster-shipping-isnt)

DevEx

[Code generation is faster than ever, but shipping value isn't](https://linearb.io/blog/code-generation-faster-shipping-isnt)

Your team writes more code than ever, but less reaches production. AI moved the bottleneck to code review. Here's how to measure it and unblock your pipeline.&n...

[![Cover image for What to look for in an engineering productivity platform](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Developer_productivity_platform_2400x1256_0d47bff68e?_a=BAVMn6ID0)](https://linearb.io/blog/what-to-look-for-engineering-productivity-platform)

DevEx

[What to look for in an engineering productivity platform](https://linearb.io/blog/what-to-look-for-engineering-productivity-platform)

AI made dashboards trivial, but the data foundation underneath still matters. How to evaluate an engineering productivity platform across four key outcomes.

[![Cover image for Why OpenAI Codex builds the agent first, not the product](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Redefining_agentic_autonomy_2400x1256_98ff8e15fc?_a=BAVMn6ID0)](https://linearb.io/blog/openai-codex-thibault-sottiaux-agentic-autonomy)

DevEx

[Why OpenAI Codex builds the agent first, not the product](https://linearb.io/blog/openai-codex-thibault-sottiaux-agentic-autonomy)

OpenAI’s Thibault Sottiaux reveals how the Codex team ruthlessly simplifies agent design by removing manual scaffolding, solving context compaction at the...

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io/",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "The 12 goals Google uses to define AI-driven engineering",
  "url": "https://linearb.io/blog/google-ai-engineering-12-core-goals",
  "author": {
    "@type": "Person",
    "name": "Ben Lloyd Pearson"
  },
  "datePublished": "2025-06-27T14:30:00.000Z",
  "dateModified": "2025-06-27T14:30:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1751035822/Blog_Google_Skills_Map_2400x1256_d3e86fd63c.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Discover Google's 12 goals for AI-driven engineering. Learn the blueprint top teams use to master AI development and gain a competitive edge."
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)