Uploaded October 2026 | Updated November 2026, 1 day ago
AI isn't just changing how we write code. It's changing how we build software, structure teams, and think about what it means to be a software engineer. In this episode of Hanselminutes, Scott Hanselman sits down with Sunita Verma, CTO at Ironclad and a longtime Google engineering veteran, to explore why simply adding AI tools to existing development workflows isn't enough.
They discuss the shift from writing code to directing AI agents, why traditional sequential software development processes may need to evolve, and how smaller engineering teams can compete with much larger organizations. How do engineers adapt when writing code is no longer the primary measure of productivity? What happens to collaboration, ownership, and engineering judgment? And can AI actually reduce burnout, or does it just raise expectations?
Visit serpapi.com/hanselminutes to get started with our new sponsor SerpAPI! You get 250 free searches every month!
00:00 How do we use AI to become more productive and smarter without burning out, when it often creates more work to review?
01:17 Why are you choosing to stick around during this AI moment and help engineering teams navigate it?
02:01 Is it hard to be a technology optimist in this AI moment?
04:37 Is AI actually more intelligent than humans, or does it mainly compress and remix human knowledge without true creativity or paradigm-shifting thinking?
06:54 Is there something you once believed about engineering organizations five years ago that you now believe differently?
10:13 How do I live in a world where there is both IKEA and Japanese carpentry, and appreciate that they both exist?
11:55 Are you getting back into coding, even though you're a CTO?
13:49 What is the optimal team size for an AI-focused engineering team, and should teams be smaller and more independently owned?
18:30 What do you think the optimal size for an AI-augmented team is right now?
21:18 How do you change the structure of an organization into smaller, startup-like teams without necessarily downsizing it?
22:53 What outcomes are we able to deliver in a given timeframe with the size of the team we have, while maintaining quality and customer value?
25:29 Can a risk-based, multi-model approach to AI code review help prevent bottlenecks and reduce bias in the software development process?
27:27 How do we balance AI’s promise of removing toil with the reality that it often creates more review work and contributes to burnout?
29:39 If you were to drop into a standard software engineering organization today as the new CTO, what would you change first to introduce AI in a company that’s years behind?
32:40 How can organizations prepare the next generation of engineers and leaders for a very different future shaped by AI while remaining resilient and not fragile?
AI isn't just changing how we write code. It's changing how we build software, structure teams, and think about what it means to be a software engineer. In this episode of Hanselminutes, Scott Hanselman sits down with Sunita Verma, CTO at Ironclad and a longtime Google engineering veteran, to explore why simply adding AI tools to existing development workflows isn't enough.
They discuss the shift from writing code to directing AI agents, why traditional sequential software development processes may need to evolve, and how smaller engineering teams can compete with much larger organizations. How do engineers adapt when writing code is no longer the primary measure of productivity? What happens to collaboration, ownership, and engineering judgment? And can AI actually reduce burnout, or does it just raise expectations?
Visit serpapi.com/hanselminutes to get started with our new sponsor SerpAPI! You get 250 free searches every month!
00:00 How do we use AI to become more productive and smarter without burning out, when it often creates more work to review?
01:17 Why are you choosing to stick around during this AI moment and help engineering teams navigate it?
02:01 Is it hard to be a technology optimist in this AI moment?
04:37 Is AI actually more intelligent than humans, or does it mainly compress and remix human knowledge without true creativity or paradigm-shifting thinking?
06:54 Is there something you once believed about engineering organizations five years ago that you now believe differently?
10:13 How do I live in a world where there is both IKEA and Japanese carpentry, and appreciate that they both exist?
11:55 Are you getting back into coding, even though you're a CTO?
13:49 What is the optimal team size for an AI-focused engineering team, and should teams be smaller and more independently owned?
18:30 What do you think the optimal size for an AI-augmented team is right now?
21:18 How do you change the structure of an organization into smaller, startup-like teams without necessarily downsizing it?
22:53 What outcomes are we able to deliver in a given timeframe with the size of the team we have, while maintaining quality and customer value?
25:29 Can a risk-based, multi-model approach to AI code review help prevent bottlenecks and reduce bias in the software development process?
27:27 How do we balance AI’s promise of removing toil with the reality that it often creates more review work and contributes to burnout?
29:39 If you were to drop into a standard software engineering organization today as the new CTO, what would you change first to introduce AI in a company that’s years behind?
32:40 How can organizations prepare the next generation of engineers and leaders for a very different future shaped by AI while remaining resilient and not fragile?










