Jun 21, 2026 · 1h 39m
Anthropic engineering leader reveals how AI drove an eightfold increase in code output
Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)
As AI tools automate manual coding, engineering leadership must evolve to manage massive code volumes, asynchronous agent workflows, and shifting developer roles.
- 1AI tools have driven an eightfold increase in code output, forcing engineering teams to adopt asynchronous workflows and automated agent routines.
- 2Hiring priorities are shifting toward creative builders with strong product sense and deep systems experts who can orchestrate complex architectures.
- 3Traditional engineering metrics like lines of code are obsolete, replaced by proactive quality monitoring and developer frustration tracking.
Don't miss
Fiona Fung contrasts her early days shipping software on physical CDs at IBM with today's real-time, agent-driven engineering workflows.
The brief
Anthropic engineering leader Fiona Fung manages the teams behind Claude Code and Claude Cowork, experiencing firsthand a world where software engineering output has increased eightfold because coding is no longer the bottleneck.
This massive code spike shifts the developer role from manual syntax writing to high-level system orchestration, requiring engineers to deploy automated routines that coordinate fleets of autonomous AI agents on their behalf.
To manage this rapid output without losing control, Fung relies on proactive quality monitoring, tracking critical errors via specific thresholds and keeping developer frustration low through pairwise programming lunches.
Fung reflects on her 25-year career, comparing the slow feedback loops of shipping database software on physical CDs at IBM to the real-time, agent-driven workflows she manages today.
As traditional metrics like lines of code become obsolete, the most successful engineering teams will prioritize creative builders with strong product sense over developers who merely write code.
What was said on this episode
32 statements · 24 positive · 2 negative · 6 neutral
Anthropic engineers now produce eight times more code per quarter than in 2025.
“Anthropic engineers on average have eight times as much code per quarter as they did compared to 2025.”
Listen at 0:00
AI-assisted coding is no longer the main engineering bottleneck.
“Coding is no longer the bottleneck.”
Listen at 0:05
Extensive agent-based work could make software engineering lonely.
“It could start being a lonely experience because we all started just working with our agents so much”
Listen at 0:36
People worried about AI should engage with it and focus on controllable actions.
“My advice is lean in and ask what can I do about it? What is within my control?”
Listen at 0:58
Higher AI-generated coding throughput shifts engineering attention toward verification.
“How do we think about verification? Like that's kind of this other shift that I'm seeing.”
Listen at 9:23
A Claude Code remote session can give managers visibility across repository work.
“I actually have a cloud code remote session that I enlist in all of our repos. And so this way I have full visibility into the work that everybody's doing.”
Listen at 10:13
Claude enables engineering managers to derive insights that were previously impractical.
“I don't think I would have been able to, you know, have some of these insights with Claude.”
Listen at 12:07
Claude routines can automate managers’ feedback-monitoring workflows.
“now I just have a routine that automates all this for me.”
Listen at 13:11
Human experts should continue reviewing code in areas requiring deep subject expertise.
“for the important like, like areas that need deep subject matter expertise, we definitely want to make sure we have the proper, you know, like humans. Still reviewing.”
Listen at 15:05
Claude effectively validates code against explicitly provided quality frameworks.
“Claude is very good when you give it a framework to validate against those frameworks.”
Listen at 15:20
Teams should store and regularly update product specifications in repositories.
“if you have specs or check those into the repo and then make sure the spec also keeps up to date with the code frequently”
Listen at 15:33
AI automation can make established engineering practices such as TDD more efficient.
“the fact that that's now automated and you can even revisit all these principles that have been around for a while, but now they actually might be even more efficient just because you have the models that can do more of the work for you.”
Listen at 16:39
Claude enables engineers to work beyond their traditional technical specialties.
“It's lifted the ceiling of what anyone is able to do.”
Listen at 19:34
A growth mindset helps workers adapt to AI-driven change.
“A growth mindset really, really helps.”
Listen at 20:05
Cowork can locate specific documents within a disorganized directory.
“we gave Cowork access to the directory, found the menus.”
Listen at 29:22
Cowork can provide local market analysis for a restaurant’s pricing decisions.
“it came back with really cool, almost like market analysis.”
Listen at 29:36
Product teams should continuously use feedback to improve reliability and user experience.
“always listening to feedback and always iterating, trying to make a delightful, reliable, high quality experience”
Listen at 34:08
AI-assisted engineering teams are shifting toward asynchronous work.
“we're shifting more towards async, like asynchronous.”
Listen at 35:36
High-agency teams require correspondingly high accountability.
“with high agency, it's also high accountability.”
Listen at 39:05
Engineering productivity should be evaluated by outcome contribution rather than output volume.
“Is the output really going towards the outcome?”
Listen at 41:11
Teams should regularly reassess whether their metrics still reflect intended outcomes.
“Always keep in mind, is that metric really still serving the outcome that you were aiming for?”
Listen at 42:43
Earlier quality detection is a key priority for AI-assisted product teams.
“the more proactive we can be of like making sure we can get an earlier detection into quality”
Listen at 45:12
Pairwise programming helps engineers learn different AI-assisted workflows from one another.
“when we do pairwise programming, we actually learn so much from each other.”
Listen at 56:57
Engineers should develop stronger product judgment as AI expands their responsibilities.
“having engineers build and keep building that stronger product sense muscle”
Listen at 1:02:39
Leaders who use their products directly maintain closer awareness of product quality.
“being able that helps me keep really close to the pulse”
Listen at 1:04:23
Verifying that AI-built experiences match intended designs remains difficult.
“that one is still a hard one to crack”
Listen at 1:10:50
Future software engineers may need fellowship or apprenticeship-style training.
“I wonder if it's for software engineering. It's almost like you go more towards a fellowship or apprenticeship program.”
Listen at 1:13:55
Understanding underlying systems may reveal opportunities to improve products despite AI abstraction.
“I do think there's something about that double click because I think that's where there might be an opportunity to improve the product or the system.”
Listen at 1:14:47
Teams should revisit previously failed AI automations as models improve.
“it might be worth the time to revisit, because, you know, that now might be a new capability.”
Listen at 1:17:44
Teams should explicitly authorize eliminating processes that no longer provide value.
“explicit permission to kill processes that no longer serve us”
Listen at 1:23:15
Anthropic’s team uses lightweight just-in-time monthly planning.
“we've shrunk it to jit monthly planning.”
Listen at 1:25:14
Longer-term engineering priorities can change rapidly as the AI landscape evolves.
“even those themes change, you know, so fast when the landscape changes.”
Listen at 1:26:44
Statements are attributed to the speaker as said on the episode and reflect their view at the time, not PodLume's. They are not advice.
Books & mentions
Lenny's Podcast: Product | Career | Growth
To hear more deep-dive interviews with world-class product and engineering leaders on scaling teams.