The Rise of Product Design Engineers
The old workflow was lossy: design in Figma, hope in handoff. Product Design Engineers design in the medium itself, and AI finally made that scale.
Drag to compare lossy handoff vs. in-code craft
For decades, digital products had a fundamental flaw built into the process.
A designer would design the thing. An engineer would build the thing. A PM would inspect the almost-thing and start pointing out what got lost in translation.
The spacing was off. Design tokens were ignored. Hover states were missing. Breakpoints between mobile and desktop mockups were missing. Somewhere between the Figma file and the browser, the craft leaked out.
Like compressing a PNG into a JPG, the workflow was lossy. Design intent and implementation reality were separated by process.
AI is changing that.
Not because AI pumps out perfect code. It doesn't. Monday.com's engineering team found that AI-generated UI often hard-coded colors, overrode typography, ignored tokens, and missed the underlying design system entirely. The real unlock isn't "AI writes frontend."
The real unlock is that designers can now work much closer to the actual medium.
They can design in code. They can tune spacing, states, motion, responsiveness, and components directly inside the product itself.
For seasoned designers who did this before the AI boom, their output is now 1000x.
Companies that move the fastest hired Product Design Engineers. This is precisely how Vercel outpaced their competitors. They employed high-output individuals who combined aesthetic sensibility with technical skill that could "design, build, and ship autonomously."
If you're a designer, don't get left behind. Whatever time you're spending in Figma, reallocate 50–90% of that time to code*. The future isn't product design. It's product craft.
The old workflow asked designers to craft a design, then hope. The new workflow?
Design and build the thing yourself.
Engineers are still as important as ever. Along with cleaning up after your designer, you still own the architecture, reliability, performance, systems, and scale. But it's time to let your designer into the implementation layer.
And designers who cross that wall first will define the next generation of software.
Sorry Figma. We still love you.