---
title: "Becoming an AI Team"
description: "Becoming an AI team requires more than adding assistants to existing workflows: it changes ownership, planning, roles, and execution. At Pinterest, infrastructure teams face the scale of serving billions of Pins, boards, ads, and real-time signals, making AI adoption an operational necessity for reliability, cost efficiency, and developer productivity. AI code-generation and transformation models can turn a widespread legacy-codebase refactor, such as replacing “foo” with “bar,” from a months-long effort into work completed and verified in a week or less. As routine execution is increasingly augmented or automated, engineers, product managers, and designers are expected to spend more time on strategy, problem definition, and user validation, while managers emphasize vision, trade-offs, mentorship, and collective impact. The conclusion is that teams must continuously optimize an AI-driven operating system rather than treat AI as a side project."
---

# Becoming an AI Team

[Pinterest](https://yomu.fyi/company/pinterest) · Pinterest Engineering · Sep 1, 2026

**Type:** Explainer

## Summary

Becoming an AI team requires more than adding assistants to existing workflows: it changes ownership, planning, roles, and execution. At Pinterest, infrastructure teams face the scale of serving billions of Pins, boards, ads, and real-time signals, making AI adoption an operational necessity for reliability, cost efficiency, and developer productivity. AI code-generation and transformation models can turn a widespread legacy-codebase refactor, such as replacing “foo” with “bar,” from a months-long effort into work completed and verified in a week or less. As routine execution is increasingly augmented or automated, engineers, product managers, and designers are expected to spend more time on strategy, problem definition, and user validation, while managers emphasize vision, trade-offs, mentorship, and collective impact. The conclusion is that teams must continuously optimize an AI-driven operating system rather than treat AI as a side project.

## Context

Traditional playbooks are insufficient for scaling reliability, cost efficiency, and developer productivity at Pinterest’s infrastructure scale. The broader shift also expands the set of feasible projects, changes individual responsibilities, and makes strategic prioritization more important.

## Approach / What changed

The post describes embedding AI tools and agents into engineering and cross-functional workflows, including code generation, large-scale refactoring, Spark-job creation and validation, alert triage, data exploration, rollout planning, and database monitoring. It also emphasizes learning sessions, information sharing, experimentation, psychological safety, strategic management, and mentorship.

## Takeaways

- The expanded set of feasible projects makes prioritization more important; feasibility alone does not establish strategic value.
- Pinterest examples include agents that write and validate Spark jobs, triage alerts, and help product teams explore data without deep query expertise.
- The transition calls for experimentation, information-sharing forums, and psychological safety so teams can learn from unsuccessful attempts as well as successful deployments.

**Tags:** [AI](https://yomu.fyi/topic/ai), [AI Agents](https://yomu.fyi/topic/ai-agents), [Generative AI](https://yomu.fyi/topic/generative-ai)

- Source: [Pinterest](https://medium.com/pinterest-engineering/becoming-an-ai-team-866d6b567803)
- Source URL: https://medium.com/pinterest-engineering/becoming-an-ai-team-866d6b567803
- Ingested by Yomu: 2026-09-01T16:00:48.264Z

[Read original post](https://medium.com/pinterest-engineering/becoming-an-ai-team-866d6b567803)