Design Systems at Scale with Szymon Chudy (Netflix) | Hawkins, Paved Roads, AI Migrations

What does it take to run a design system that 2,000+ applications depend on, when every team is free to walk away from it?

a Software Engineer on Netflix's Hawkins team, which uses the design system

In this episode of Señors at Scale, Dan sits down with Szymon Chudy, Software Engineer at Netflix on the Hawkins team, the design system used by thousands of engineers across Netflix's internal tools. Before Netflix, Szymon grew from Senior to Staff Frontend Engineer at Lokalise, where he co-owned the design system and led frontend direction across teams. Before tech, he was a professional guitarist with over a thousand concerts and two platinum albums.

Szymon explains why he sees a design system as enablement rather than a component library, why he believes the source of truth lives in code and not in Figma, and how Netflix's "freedom and responsibility" culture forces the Hawkins team to think like a product team that has to earn adoption. We get into the UI paved road, shipping codemods and AI skills with every breaking change, running an alpha, beta and GA release across thousands of apps, and what an on-call incident looks like for a design system.

We also talk about when you should not build a design system, what a visual refresh really involves under the hood, and whether the Netflix culture from No Rules Rules holds up from the inside, including informed captains, farming for dissent and the keeper test.

Key Topics:

- What a design system really is: enablement, not just components

- Source of truth: Figma, code, or a separate component definition

- Why markdown specs and LLMs don't solve the determinism problem

- Hawkins Consumer vs Hawkins Professional at Netflix

- Design police vs full freedom, and the case for a paved road in the AI era

- Why design systems are slower than product, and why that's a feature

- "Legal hacking": letting teams diverge with clear boundaries

- Shipping skills, MCPs and context so agents can use your design system

- Adoption rate as the success metric

- Codemods, AI skills and human in the loop for major migrations

- Alpha, beta, GA: releasing breaking changes to thousands of apps

- On call for a design system: what counts as an incident

- You may not need a design system

- Netflix culture: freedom and responsibility, informed captains, the keeper test

🔗 FOLLOW SZYMON

💼 LinkedIn: https://www.linkedin.com/in/szymonchudy/

🐦 X/Twitter: https://x.com/szymonchudy

🦋 Bluesky: https://bsky.app/profile/chudy.me

🌐 Website: https://chudy.me

🎙️ FOLLOW & SUBSCRIBE

📸 Instagram: https://www.instagram.com/senorsatscale/

📸 Instagram: https://www.instagram.com/neciudev

🎙 Podcast URL: https://neciudan.dev/senors-at-scale

📬 Newsletter: https://neciudan.dev/subscribe

💼 LinkedIn: https://www.linkedin.com/in/neciudan

💼 LinkedIn: https://www.linkedin.com/company/senors-scale/

📚 ADDITIONAL RESOURCES

- Szymon's blog: https://chudy.me/blog

- Lenny's Podcast with Elizabeth Stone (Netflix CPTO) on systems thinkers: https://www.lennysnewsletter.com/p/netflix-cpto-on-ai-and-the-future

- No Rules Rules by Reed Hastings and Erin Meyer

- The Culture Map by Erin Meyer

- Grokking Web Application Security by Malcolm McDonald

- Grokking Algorithms by Aditya Bhargava

- The Pelican Brief by John Grisham

#DesignSystems #Netflix #Hawkins #Frontend #React #Figma #PlatformEngineering #DeveloperExperience #AIAgents #Codemods #WebDevelopment #SoftwareEngineering #SenorsAtScale