Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

The hosts cite a Bedrock team rebuilding its inference engine with six engineers in 76 days, work that would have taken 40 people a year. Jassy agrees the experience was eye-opening and says four or five people prototyped an agent idea over a weekend. It shows how small teams now build.

Related Insights

To accelerate development, Grok Bot's parent company created a small, focused team and physically isolated them from the rest of the company. This "cave" environment enabled rapid micro-decision making without the bureaucracy or distraction of a larger organization.

At OpenAI, teams of just one or two engineers leverage AI agents to own entire product lines. This model reduces human collaboration overhead and empowers engineers to make most micro-decisions autonomously, increasing speed and ownership.

To adapt to AI-driven productivity, Block abandoned large, static feature teams for small squads of 1-6 people that can flexibly move between products. This structure, combined with cutting management layers by over 50%, allows for faster information flow and rapid, AI-powered development cycles.

CEO Roger Lynch reveals a radical reorganization of tech teams. By using AI for coding and QA, Condé Nast has reduced project teams from 10-12 people to just 3-4. These smaller, nimbler teams are now developing products three times faster, eliminating entire roles like QA engineers.

By using AI to write and QA code, Condé Nast has redesigned its product development teams. Teams that were 10-12 people are now just 3-4, eliminating roles like technical project managers and QA engineers. These smaller, AI-augmented teams can move three times faster.

Inside AWS, engineering teams are transitioning from writing code to managing fleets of agents. Matt Garman notes this has shrunk team sizes needed per initiative from ten engineers down to three or four. Because these smaller teams deliver features significantly faster, organizations face the operational challenge of continually redeploying engineers across projects while sustaining ongoing maintenance.

David Singleton, CEO of Dreamer, reveals that the complex platform—encompassing an agent studio, tool ecosystem, and OS-like architecture—was built by a core team of only about six people. This highlights the incredible productivity and leverage that small, high-talent-density teams can achieve in the AI era.

As agents and AI automate code creation and review, the bottleneck of software shifts entirely to determining what is worth building and validating customer value. Because execution speed is dramatically higher, Lopitaux predicts that development team sizes will shrink, the developer-to-PM ratio will decrease, and the traditional 'two-pizza team' standard will disappear in favor of smaller, agile units.

By deploying multiple AI agents that work in parallel, a developer measured 48 "agent-hours" of productive work completed in a single 24-hour day. This illustrates a fundamental shift from sequential human work to parallelized AI execution, effectively compressing project timelines.

The belief that adding people to a late project makes it later (Brooks's Law) may not apply in an AI-assisted world. Early reports from OpenAI suggest that when using agents, adding more developers actually increases velocity, a potential paradigm shift for engineering management and team scaling.

Six engineers rebuilt Bedrock's inference engine in 76 days | RiffOn