GuideAdvanced

Leading Teams That Build with Agents Guide

When agents write a large share of the code, the job of whoever leads the team changes. There is no shortage of people who write: the shortage is people who decide what gets built, people who review what comes out, and people who answer for every line. This guide teaches you to reorganize an engineering team for that world: where the bottleneck moved, which roles change, how much review your team can absorb, who owns code that nobody wrote by hand, what usage rules to set, how juniors keep growing, and how to take the team from "everyone decides for themselves" to an operating model you can defend in front of leadership. You learn it as the new VP of Engineering at **Kubo Seguros**, an insurtech with 45 engineers in 6 squads. After six months of agents with no rules, PRs doubled, review got stuck, there were two incidents caused by unreviewed code, and the CEO asks in the leadership meeting whether the team is actually faster. Module by module you build the answer: a diagnosis, an org chart, a review policy, an accountability matrix, an agent usage policy, a plan for juniors, and a 90-day adoption plan. There is no code to write. The math is done in tables and by hand, and the studies (DORA, METR, industry surveys) come with their source and date.