Design engineer. UX engineer. Front-end dev with opinions. What does it all mean?! In this episode, we sit down with Dave Darnes to untangle the ever-evolving world of design and development (And Dave is our first non-Font Awesomer on the pod!). We talk about why job titles keep getting weirder, whether "engineer" is a fair title for folks who work on the web, and how design systems can bridge the gap between teams. Plus, we explore the future of the role — will tools like Figma and AI replace design engineers, or will the internet always need humans who can actually build things?
🚀 Tune in for a fun, insightful, and slightly existential conversation about the intersection of design, dev, and the titles we give ourselves.
🏆 Key Takeaways
⏱️ Episode Breakdown
🕛 00:00 - Meet Dave Darnes – 🇬🇧 UK-based designer/developer, father of sick children (but still here for the podcast).
🎤 02:30 - The Legendary "David Darnes" Callout – A completely necessary and extremely fun moment of podcast magic.
🛠️ 06:45 - What is a Design Engineer Anyway? – The Venn diagram of design and development overlaps in weird ways.
📛 12:15 - Why Job Titles Get Messy – Specialization vs. generalization and the need to impress hiring managers.
🏗️ 18:30 - Engineer as a Title — Does It Matter? – Structural engineers hold up buildings; do web engineers hold up the internet? (Kinda, yeah.)
🔄 24:00 - The Evolution of Design & Dev Roles – How web components, CSS variables, and other tech are shifting expectations.
🥕 30:45 - How to Get People to Actually Use a Design System – Hint: Be more carrot, less stick.
🤖 35:00 - The Battle Between Figma & AI – Will design engineers survive the encroaching automation?
🔄 40:30 - If You Had to Rename 'Design Engineer'... – Dave's answer is almost annoyingly simple.
🔗 Resources & Links
Stay up to date on all the Font Awesomeness!
