At Notion, engineers build features to 80-90% completion. Designers then take over, shipping small, focused pull requests for the final visual polish, animation, and craft. This "last mile" is a designer's superpower where LLMs currently fall short.

High-performing teams are creating small 'pods' with a product manager (business context), a designer (UI/UX), and an engineer (technical execution) who work together in shared AI coding sessions. This collaborative model ensures features are viable, usable, and well-built from the start, breaking down traditional silos.

At Perplexity, the design system lives in the codebase, not Figma. Designers contribute directly to the frontend, creating a single source of truth that eliminates drift between design files and production code, forcing a highly practical and collaborative process.

To keep pace with AI development, the barrier between design and engineering must fall. Intercom made it a non-negotiable job requirement for every product designer to ship code to production. This empowers them to fix UI bugs directly and accelerates the entire development cycle.

Instead of siloing roles, encourage engineers to design and designers to code. This cross-functional approach breaks down artificial barriers and helps the entire team think more holistically about the end-to-end user experience, as a real user does not see these internal divisions.

A design engineer's true value isn't just coding ability, but a designer's mindset applied to shipping products. They are distinguished by their focus on creativity, craft, and the delightful details in the final 10% of the work, which separates them from traditional front-end engineers.

The co-founder, a designer, learned React to bypass the classic frustration of developers misinterpreting high-fidelity mockups. By designing directly in code, he maintains full control over the final UI, eliminates the handoff process, and saves significant time and back-and-forth.

To maximize speed, V0 operates with a "no handoffs" philosophy. Everyone, including designers and product managers, is expected to contribute code and submit their own pull requests. This "full-stack PM" model minimizes the coordination costs and wasted cycles of explaining changes.

For engineers working on user-facing features, the highest-leverage partnership isn't with a senior technical architect, but with a top-tier designer. Ryan Peterman's strategy was to become the go-to engineer for the best designers, allowing their exceptional product sense and vision to flow through his work, multiplying his own impact.