Uploaded April 2025 | Updated September 2026, 2 weeks ago
How do you get product and engineering to truly operate as one team? Today, I’m joined by Ebi Atawodi, Director of Product Management at YouTube Studio, and a former product leader at Netflix and Uber.
Ebi was the first PM I partnered with after stepping into engineering management at Uber, and we both learned a lot together. We share lessons from our time at Uber and discuss how strong product-engineering partnerships drive better outcomes, grow teams, foster cultures of ownership, and unlock agency, innovation, and trust.
In this episode, we cover:
• Why you need to earn a new team's trust before trying to drive change
• How practices like the "business scorecard" and “State of the Union” updates helped communicate business goals and impact to teams at Uber
• How understanding business impact leads to more ideas and collaboration
• A case for getting to know your team as people, not just employees
• Why junior employees should have a conversation with a recruiter every six months
• Ebi’s approach to solving small problems with the bet that they’ll unlock larger, more impactful solutions
• Why investing time in trust and connection isn't at odds with efficiency
• The qualities of the best engineers—and why they’re the same traits that make people successful in any role
• The three-pronged definition of product: business impact, feasibility, and customer experience
• Why you should treat your career as a project
• And more!
—
Brought to by:
• WorkOS — The modern identity platform for B2B SaaS workos.com
• The Software Engineer’s Guidebook: Written by me (Gergely) – now out in audio form as well engguidebook.com/#buy
—
The Pragmatic Engineer deepdives relevant for this episode:
• The product-minded software engineer blog.pragmaticengineer.com/the-product-minded-engineer
• Working with Product Managers as an Engineering Manager or Engineer newsletter.pragmaticengineer.com/p/working-with-product-managers
• Working with Product Managers: advice from PMs newsletter.pragmaticengineer.com/p/working-with-product-managers-advice-from-pms
• What is Growth Engineering? newsletter.pragmaticengineer.com/p/what-is-growth-engineering
—
Where to find Ebi Atawodi:
• X: https://x.com/ebiatawodi
• LinkedIn: linkedin.com/in/ebiatawodi
Where to find Gergely Orosz:
• X: https://x.com/GergelyOrosz
• LinkedIn: linkedin.com/in/gergelyorosz
• Bluesky: https://bsky.app/profile/gergely.pragmaticengineer.com
• Newsletter and blog: pragmaticengineer.com
—
In this episode, we cover:
(00:00) Intro
(02:19) Engineering and Product working together: a rocky start
(12:35) Working as a startup inside a large company
(30:24) Product-minded engineers
(36:00) Getting headcount for Engineering
(43:58) The importance of a "vision" and meeting people
(50:44) Traits of standout software engineers engineers look like?
(1:06:54) The value of a great PM
(1:11:50) Play the long game
—
See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast
—
Production and marketing by penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.
How do you get product and engineering to truly operate as one team? Today, I’m joined by Ebi Atawodi, Director of Product Management at YouTube Studio, and a former product leader at Netflix and Uber.
Ebi was the first PM I partnered with after stepping into engineering management at Uber, and we both learned a lot together. We share lessons from our time at Uber and discuss how strong product-engineering partnerships drive better outcomes, grow teams, foster cultures of ownership, and unlock agency, innovation, and trust.
In this episode, we cover:
• Why you need to earn a new team's trust before trying to drive change
• How practices like the "business scorecard" and “State of the Union” updates helped communicate business goals and impact to teams at Uber
• How understanding business impact leads to more ideas and collaboration
• A case for getting to know your team as people, not just employees
• Why junior employees should have a conversation with a recruiter every six months
• Ebi’s approach to solving small problems with the bet that they’ll unlock larger, more impactful solutions
• Why investing time in trust and connection isn't at odds with efficiency
• The qualities of the best engineers—and why they’re the same traits that make people successful in any role
• The three-pronged definition of product: business impact, feasibility, and customer experience
• Why you should treat your career as a project
• And more!
—
Brought to by:
• WorkOS — The modern identity platform for B2B SaaS workos.com
• The Software Engineer’s Guidebook: Written by me (Gergely) – now out in audio form as well engguidebook.com/#buy
—
The Pragmatic Engineer deepdives relevant for this episode:
• The product-minded software engineer blog.pragmaticengineer.com/the-product-minded-engineer
• Working with Product Managers as an Engineering Manager or Engineer newsletter.pragmaticengineer.com/p/working-with-product-managers
• Working with Product Managers: advice from PMs newsletter.pragmaticengineer.com/p/working-with-product-managers-advice-from-pms
• What is Growth Engineering? newsletter.pragmaticengineer.com/p/what-is-growth-engineering
—
Where to find Ebi Atawodi:
• X: https://x.com/ebiatawodi
• LinkedIn: linkedin.com/in/ebiatawodi
Where to find Gergely Orosz:
• X: https://x.com/GergelyOrosz
• LinkedIn: linkedin.com/in/gergelyorosz
• Bluesky: https://bsky.app/profile/gergely.pragmaticengineer.com
• Newsletter and blog: pragmaticengineer.com
—
In this episode, we cover:
(00:00) Intro
(02:19) Engineering and Product working together: a rocky start
(12:35) Working as a startup inside a large company
(30:24) Product-minded engineers
(36:00) Getting headcount for Engineering
(43:58) The importance of a "vision" and meeting people
(50:44) Traits of standout software engineers engineers look like?
(1:06:54) The value of a great PM
(1:11:50) Play the long game
—
See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast
—
Production and marketing by penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.








![Building Claude Code with Boris Cherny
Boris Cherny is the creator and Head of Claude Code at Anthropic. He previously spent five years at Meta as a Principal Engineer and is the author of the book Programming TypeScript.
In this episode of Pragmatic Engineer, we went through how Claude Code was built and what it means when engineers no longer write most of the code themselves.
We discuss how Claude Code evolved from a side project into a core internal tool at Anthropic and how Boris uses it day-to-day. We go deep into workflow details, including parallel agents, PR structure, deterministic review patterns, and how the system retrieves context from large codebases. We also get into how Claude Cowork was built.
As coding becomes more accessible, the role of engineers shifts rather than shrinks. We examine what that shift means in practice, which skills become more important, and why the lines between product, engineering, and design are blurring.
—
*Brought to you by our season partners:*
• Statsig — The unified platform for flags, analytics, experiments, and more. http://statsig.com/pragmatic
• Sonar – The makers of SonarQube, the industry standard for automated code review. https://www.sonarsource.com/pragmatic/?utm_medium=paid&utm_source=pragmaticengineer&ut[…]egory=Paid&s_source=Paid%20Other&s_origin=pragmaticengineer
• WorkOS – Everything you need to make your app enterprise ready. https://workos.com/
—
*The Pragmatic Engineer deepdives relevant for this episode:*
• How Claude Code is built https://newsletter.pragmaticengineer.com/p/how-claude-code-is-built
• How Anthropic built Artifacts https://newsletter.pragmaticengineer.com/p/how-anthropic-built-artifacts
• How Codex is built https://newsletter.pragmaticengineer.com/p/how-codex-is-built
• Real-world engineering challenges: building Cursor https://newsletter.pragmaticengineer.com/p/cursor
—
*Where to find Boris Cherny:*
• X: https://x.com/bcherny
• LinkedIn: https://www.linkedin.com/in/bcherny
• Website: https://borischerny.com
—
*In this episode, we cover:*
(00:00) Intro
(11:15) Lessons from Meta
(19:46) Joining Anthropic
(23:08) The origins of Claude Code
(32:55) Boriss Claude Code workflow
(36:27) Parallel agents
(40:25) Code reviews
(47:18) Claude Codes architecture
(52:38) Permissions and sandboxing
(55:05) Engineering culture at Anthropic
(1:05:15) Claude Cowork
(1:12:48) Observability and privacy
(1:14:45) Agent swarms
(1:21:16) LLMs and the printing press analogy
(1:30:16) Standout engineer archetypes
(1:32:12) What skills still matter for engineers
(1:35:24) Book recommendations
—
See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast
—
Production and marketing by https://penname.co/. Building Claude Code with Boris Cherny](https://i.ytimg.com/vi/julbw1JuAz0/mqdefault.jpg)

