<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn" -->

---
title: Meta tried to shrink engineering teams around AI | daily.dev
description: Meta's attempt to shrink engineering teams into AI-assisted 'pods' of three to five workers reportedly backfired: code changes rose 220% year-on-year, but...
canonical: https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Meta tried to shrink engineering teams around AI | daily.dev
og:description: Meta's attempt to shrink engineering teams into AI-assisted 'pods' of three to five workers reportedly backfired: code changes rose 220% year-on-year, but...
og:url: https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn
og:image: https://api.daily.dev/og/posts/KfIBt4OMN.png
og:image:alt: Meta tried to shrink engineering teams around AI
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Meta tried to shrink engineering teams around AI

**[LeadDev](https://daily.dev/sources/leaddev)** · 4 min read · 1 upvotes · 1 comments

## Summary

Meta's attempt to shrink engineering teams into AI-assisted 'pods' of three to five workers reportedly backfired: code changes rose 220% year-on-year, but shipped features grew only 36%, while major technical and security incidents jumped 40% and firefighting time rose 70%. A separate DX study across 500+ organizations found pull request throughput up 37% over four quarters, yet the Developer Experience Index fell from 67 to 65. Experts including Peter Bell (Gather.dev) argue right-sized teams are five to eight people, that platform and product engineering roles become more critical with AI, and that team shrinking should come at the end of an AI transformation, not the start.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://leaddev.com/ai/meta-tried-to-shrink-engineering-teams-around-ai>

## Questions this post answers

### Did Meta's AI-driven engineering pods actually improve productivity?

Not proportionally. Meta's AI pods increased internal code changes by 220% year-on-year, but the number of changes that resulted in shipped features rose only 36%. Major technical and security incidents increased 40%, and time spent firefighting them rose 70%, showing output gains did not translate into outcome gains.

_Engineering leaders weighing AI-driven restructuring can follow real-world results like this on daily.dev._

### What is the ideal team size for an AI-native engineering team?

Around five to eight people, according to Peter Bell, founder and CTO of Gather.dev. Even if only one or two engineers work directly on the same repository, this size limits the volume of simultaneous AI-generated changes to a manageable level while still preserving a sense of human connection within the team.

_Teams restructuring around AI tools can compare sizing guidance like this on daily.dev._

### How did AI coding tools affect developer experience across companies, according to DX's research?

Developer experience declined even as raw output rose. Across more than 500 organizations, DX found median weekly pull request throughput rose 37% over four quarters, but its Developer Experience Index fell from 67 to 65, and the share of engineering time spent building new capabilities stayed flat, since engineers spent more time reviewing and fixing AI-generated code.

_Anyone tracking AI's real impact on developer experience can follow findings like this on daily.dev._

## Community discussion

Top comments from developers on daily.dev.

**@elmarchavez** · 0 upvotes

> Yes, faster code generation does not mean great quality code. These metrics are now more important than ever.

## Similar posts on daily.dev

- [Right-Sizing Engineering Teams for AI](https://daily.dev/posts/right-sizing-engineering-teams-for-ai-et26zcdz6) · RUBYLAND · 0 upvotes · 0 comments
- [AI Shrinks the Team, Not the Problem, CodeGood](https://daily.dev/posts/ai-shrinks-the-team-not-the-problem-codegood-j9xr42zpg) · CodeGood · 0 upvotes · 0 comments
- [AI has us asking, does \(team\) size still matter?](https://daily.dev/posts/ai-has-us-asking-does-team-size-still-matter--qw5pkolu3) · LeadDev · 0 upvotes · 0 comments
- [Report: Lower Performing Software Engineering Teams Benefit More from AI](https://daily.dev/posts/report-lower-performing-software-engineering-teams-benefit-more-from-ai-jld1vj29x) · DevOps.com · 0 upvotes · 0 comments
- [AI coding got faster. Why didn’t engineering?](https://daily.dev/posts/ai-coding-got-faster-why-didn-t-engineering--epmtgpec2) · The New Stack · 0 upvotes · 0 comments

---

Tags: [#productivity](https://daily.dev/tags/productivity), [#leadership](https://daily.dev/tags/leadership), [#ai-coding](https://daily.dev/tags/ai-coding)

[View this post on daily.dev](https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Meta tried to shrink engineering teams around AI","url":"https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn"},"datePublished":"2026-09-07T06:57:49.104Z","dateModified":"2026-09-14T07:44:56.467Z","description":"Meta's attempt to shrink engineering teams into AI-assisted 'pods' of three to five workers reportedly backfired: code changes rose 220% year-on-year, but...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/db30636e26651bd088f5eaf5d623b5dc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/db30636e26651bd088f5eaf5d623b5dc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"LeadDev","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LeadDev","logo":"https://media.daily.dev/image/upload/s--u_Q34nzh--/f_auto,q_auto/v1774514111/logos/leaddev?_a=BAMAMiWQ0","url":"https://daily.dev/sources/leaddev"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"productivity,leadership,ai-coding","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LeadDev","item":"https://daily.dev/sources/leaddev"},{"@type":"ListItem","position":3,"name":"Meta tried to shrink engineering teams around AI"}]}
{"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn","comment":[{"@type":"Comment","text":"Yes, faster code generation does not mean great quality code. These metrics are now more important than ever.","datePublished":"2026-09-07T11:06:58.852Z","url":"https://daily.dev/posts/KfIBt4OMN#c-tTsIbqaZX","author":{"@type":"Person","name":"Elmar Chavez","url":"https://daily.dev/elmarchavez","image":"https://media.daily.dev/image/upload/s--7PjH979T--/f_auto/v1780994221/avatars/avatar_bK85rJb2OXXID2LX2wi5y?_a=BAMAMiWQ0"}}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/meta-tried-to-shrink-engineering-teams-around-ai-kfibt4omn#faq","mainEntity":[{"@type":"Question","name":"Did Meta's AI-driven engineering pods actually improve productivity?","acceptedAnswer":{"@type":"Answer","text":"Not proportionally. Meta's AI pods increased internal code changes by 220% year-on-year, but the number of changes that resulted in shipped features rose only 36%. Major technical and security incidents increased 40%, and time spent firefighting them rose 70%, showing output gains did not translate into outcome gains. Engineering leaders weighing AI-driven restructuring can follow real-world results like this on daily.dev."}},{"@type":"Question","name":"What is the ideal team size for an AI-native engineering team?","acceptedAnswer":{"@type":"Answer","text":"Around five to eight people, according to Peter Bell, founder and CTO of Gather.dev. Even if only one or two engineers work directly on the same repository, this size limits the volume of simultaneous AI-generated changes to a manageable level while still preserving a sense of human connection within the team. Teams restructuring around AI tools can compare sizing guidance like this on daily.dev."}},{"@type":"Question","name":"How did AI coding tools affect developer experience across companies, according to DX's research?","acceptedAnswer":{"@type":"Answer","text":"Developer experience declined even as raw output rose. Across more than 500 organizations, DX found median weekly pull request throughput rose 37% over four quarters, but its Developer Experience Index fell from 67 to 65, and the share of engineering time spent building new capabilities stayed flat, since engineers spent more time reviewing and fixing AI-generated code. Anyone tracking AI's real impact on developer experience can follow findings like this on daily.dev."}}]}
```

