Sendil Nellaiyapen, Engineering Manager at Uber, has built systems that scale to millions of users. In this episode he shares what most engineers get wrong about both system design and the move into engineering management
In this episode, we cover:
- Ingredients for designing systems that scale to millions of users
- How to know when to compromise on architecture
- The trade-offs of going from IC to engineering manager and why the role is harder than it looks
- How to handle opinionated engineers, set team guardrails, and build high-performing engineering culture
Whether you're a senior engineer weighing the move into management, or already leading teams and looking to sharpen your system design thinking, this one's for you.
OUTLINE:
00:00:00 - Intro
00:01:05 - The Ingredients for Building Systems at Scale
00:02:23 - When to Compromise on Your Foundation
00:03:42 - Scaling from 2,000 to 5 Million Users
00:06:37 - Why Clarity Beats Seniority Every Time
00:08:27 - The Danger of Muscle Memory in Engineering
00:10:25 - MVP Mindset: What You Can and Can't Compromise
00:13:22 - How High-Performing Teams Handle Growing Complexity
00:15:04 - Who Owns the Assumptions? Shared Team Responsibility
00:17:04 - Building Open Frameworks Instead of Closed Rules
00:19:53 - Latency Is Overrated (Here's Why)
00:22:52 - Recipes for Disaster: The Biggest System Design Pitfalls
00:24:17 - The Scala Horror Story: When Elegance Kills Velocity
00:26:52 - How to Handle Opinionated Engineers on Your Team
00:29:03 - Setting Guardrails: The Manager's Design Responsibility
00:32:01 - The Hardest Trade-Off Going from IC to Engineering Manager
00:34:35 - Should Great Engineers Stay IC or Go into Management?
00:37:11 - BFS vs DFS Engineers: Which Type Makes a Better Manager?
00:39:05 - The Real Cost of Becoming a Manager (And Why It's Worth It)
00:41:52 - Outro
#systemdesign #engineeringmanager #softwareengineering
