Skip to main content
Full Stack Radio

124: Leslie Cohn-Wein & Rafael Conde - Designing the User Interface at Netlify

56 min episode · 2 min read
·
Adam Wadden,Leslie Cohn-Wein,Rafael Conde

Episode

56 min

Read time

2 min

Topics

Investing, Fundraising & VC, Design & UX

AI-Generated Summary

Key Takeaways

  • Design handoff elimination: Netlify maintains constant conversation between designers and front-end engineers throughout feature development rather than traditional handoff processes, with daily design meetings where both teams provide feedback and solve problems collaboratively before implementation begins.
  • Conservative component philosophy: The team deliberately avoids introducing new UI patterns, rejecting common elements like toggle switches and tabs to maintain consistency. They reuse existing patterns like cards and striped lists, forcing creative solutions within constraints to reduce maintenance burden and visual complexity.
  • Library evaluation framework: When selecting Highcharts for analytics, the team created comparison matrices ranking libraries against prioritized features including chart types, responsive behavior, accessibility modules with ARIA labels, and customization ease, then prototyped top three candidates before final selection.
  • Design tools as middle ground: Sketch mockups serve as conceptual guides rather than pixel-perfect specifications. Engineers catch inconsistencies like random padding values and normalize them to system variables, with designers welcoming pushback since code represents the actual source of truth for the product.

What It Covers

Leslie Cohn-Wein and Rafael Conde explain Netlify's UI design process, covering collaboration between designers and engineers, design system constraints, tool choices including Sketch and Abstract, and shipping the analytics dashboard feature using systematic workflows.

Key Questions Answered

  • Design handoff elimination: Netlify maintains constant conversation between designers and front-end engineers throughout feature development rather than traditional handoff processes, with daily design meetings where both teams provide feedback and solve problems collaboratively before implementation begins.
  • Conservative component philosophy: The team deliberately avoids introducing new UI patterns, rejecting common elements like toggle switches and tabs to maintain consistency. They reuse existing patterns like cards and striped lists, forcing creative solutions within constraints to reduce maintenance burden and visual complexity.
  • Library evaluation framework: When selecting Highcharts for analytics, the team created comparison matrices ranking libraries against prioritized features including chart types, responsive behavior, accessibility modules with ARIA labels, and customization ease, then prototyped top three candidates before final selection.
  • Design tools as middle ground: Sketch mockups serve as conceptual guides rather than pixel-perfect specifications. Engineers catch inconsistencies like random padding values and normalize them to system variables, with designers welcoming pushback since code represents the actual source of truth for the product.

Notable Moment

Rafael reveals Netlify uses six pixel border radius for elements inside eight pixel cards because the inner radius of curved corners requires mathematical adjustment to appear visually harmonious, demonstrating how breaking systematic rules sometimes creates better visual results than strict adherence.

Know someone who'd find this useful?

Episode Transcript

In this episode of Fullstack Radio, I talked to Leslie Cohenwine and Rafael Konda about designing new features at Netlify. This is Fullstack Radio episode one twenty four. Hey, everyone. Welcome to another episode of the Fullstack Radio podcast. I'm your host, Adam Wadden. And today, it's my pleasure to be speaking with Leslie Kohnwein and Rafa Konda of Netlify who both, work on sort of the user interface at Netlify. So, for anyone who isn't familiar with either of you, do you mind introducing yourselves? Maybe Leslie start first. Sure. Hey, Hey, everyone. I'm Leslie Konewine. I am a front end engineer at Netlify. Sort of came, came to development through agency work. So previously, I was working on marketing marketing stuff for all kinds of fun clients, in New York City, and now based in Dallas, Texas and, work on all things sort of UX at Netlify. Awesome. What about you, Rafa? So, like yeah. Like I said, Rafa I go by Rafa. I am technically now the principal designer at Netlify, and I I was an early hire a joint a while ago, and I've been working mainly on the app, but also marketing stuff. And before Netlify, I was doing some indie things, building games and sites, I guess. So yeah. The reason I want to have you both on, the show today was to sort of talk, a bit about what it looks like to sort of build new UI features, at Netlify and how sort of the team collaborates and what the design process and the implementation process sort of looks like. I had Matt on the show a couple weeks ago talking about sort of sort of the architecture of the React SPA and getting deep into some of, like, those sort of technical details. And I'm sort of curious to talk to you guys for the same reason which is basically just that I find the Netlify dashboard experience to just be one of the absolute most delightful apps I get to interact with on a day to day basis. So you're both definitely doing awesome work there and I think there's a lot that, we can learn from how you build things. Thank you. Yeah. That's awesome to hear. So so maybe the first thing I I guess that I'd be interested to, learn more about is, Leslie, you identify as a front end engineer at Netlify. And Rafa, you focus more on design, but how much would you say your skills, like, sort of cross over? Like, Leslie, do you feel like you have really good design chops too? And Rafa, do you do any, like, programming and stuff in Netlify too? Or are you mostly working in design tools? And, Leslie, are you mostly just implementing the designs that are, like, kind of built or sorry, designed by the designers. So maybe, Leslie, you can answer first. Yeah. So, you know, design was actually kind of what led me …

Get the full transcript (11,306 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Full Stack Radio transcripts →

You just read a 3-minute summary of a 53-minute episode.

Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • When selecting Highcharts for analytics, the team created comparison matrices ranking libraries against prioritized features
  • tool choices including Sketch and Abstract
  • tool choices including Sketch and Abstract

More from Full Stack Radio

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Investing & Markets Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Full Stack Radio.

Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime