The Rise of the Design Engineer: Why UX Is Entering Its Next Iteration
I stopped opening Figma as often as I used to.
After spending the last few years deep in product design, building design systems, component libraries, and workflows, something shifted. In the past month or two, I’ve only opened Figma a handful of times. And when I do, it’s usually just to sketch an idea quickly so I can pass it as instruction to an AI design or coding tool.
What used to take hours of manual work now takes minutes once intent is clear. That change is not about losing interest in design. It’s about where the work is moving.
Design has always evolved alongside its tools. We started with ideas on paper. Then came digital canvases, stylus-driven workflows, desktop software, and eventually browser-based, cloud-native tools. Each shift didn’t eliminate designers. It changed what designers were responsible for.
I believe we are now entering the next iteration of that evolution, especially in UX and UI. And it requires a new kind of role.
The Evolution of Design Roles
If you look back 15 or 20 years, most digital experiences were created by graphic or visual designers. As the web matured, those roles shifted into web designers who worked closer to implementation. Over time, that split into UX designers, UI designers, and interaction designers. Eventually, many of those merged into what we now call product designers.
Each transition reflected increasing complexity and tighter coupling between design and technology.
The next iteration follows the same pattern.
Today, it’s possible to create real, interactive, working product concepts without going through long handoff cycles. Not static mockups, but functional experiences that behave like real applications. When you combine UX thinking, UI craft, and interaction design with an understanding of how systems work, you arrive at something new.
That is what I call the design engineer.
Not someone who replaces engineers. Not someone who codes everything by hand. But someone who understands how to shape intent, constraints, and behavior well enough that systems can generate, iterate, and refine experiences quickly.
That role goes by several names already. Some teams call it a design engineer. Others use titles like UX engineer, design developer, product engineer, or even frontend product designer. The naming will continue to evolve, just as it did with UX and product design.
What matters is not the title, but the capability. Designers who can operate in this space will have disproportionate impact over the next few years.
What the Design Engineer Actually Does
At its core, the design engineer role is about orchestration.
Instead of manually building every screen, the design engineer defines intent clearly enough that AI systems can generate usable outputs. That intent is refined through selection, feedback, and additional instruction. You are no longer designing a single artifact. You are steering a system.
Prompting becomes a core skill here, but not in a superficial sense. This isn’t about clever phrasing. It’s about structured direction. Design prompting means guiding an agent toward the right experience, not just the right layout. Think PRDs and user-stories.
This also changes how designers relate to code. You don’t need to write everything line by line, but you do need to understand what the system is producing, how it behaves, and where to intervene. Selecting elements, asking for revisions, shaping behavior, and understanding constraints become part of the design process.
In my own work, I now treat design tools as a way to express intent rather than a destination. Figma has become an input mechanism (on rare occasions), not the final workspace anymore. The real work happens in how quickly an idea becomes something testable.
The Expanding Tooling Stack
This shift is being accelerated by a new generation of tools.
On the entry and intermediate side, there are prompt-based, cloud tools that allow designers to experiment quickly. Tools like Vercel v0, Lovable, Replit, Bolt, and others let you describe what you want and iterate from there. They are not magic. They still require direction. But they dramatically lower the barrier to creating real concepts.
The next layer is where designers start working closer to developer tooling. Editors like Cursor, Windsurf, and Copilot bring AI directly into environments where code runs locally. This is where I spend most of my time. You can talk to an agent, inspect code, make changes, and see results immediately. You gain far more control without needing to be a traditional engineer.
There is also a deeper layer where engineers move toward design, working directly in terminals and infrastructure. Designers don’t need to live there, but understanding how the front end communicates with APIs and data systems is becoming increasingly valuable.
What matters is not mastering every tool. It’s understanding how far down the stack you need to go to express intent clearly and validate ideas quickly.
Why This Role Matters Now
The biggest shift is speed.
You can now take an idea from a discovery session and turn it into a working prototype in hours. Not a concept deck. Not wireframes waiting for approval. A real, interactive experience that can be validated or killed quickly.
The traditional flow of requirements, wireframes, visual design, handoff, and development is increasingly out of sync with what is now possible. Time to first usable version matters more than early polish. V0 beats concept.
This also enables leaner teams. When fewer handoffs are required and validation happens earlier, waste is reduced. Designers stop working in isolation. Engineers stop building the wrong thing. Teams learn faster.
This is also why I believe traditional tools like Figma are heading toward the same fate as earlier incumbents. It’s not the first time this has happened. Photoshop, Fireworks, Sketch and then Adobe XD once dominated until better workflows replaced them. Figma changed the paradigm with a cloud collaboration tool and pushed them out.
AI-driven design and generation is doing the same thing now.
This isn’t something to fear. It’s an opportunity to rethink how we work, relearn core skills, and rebuild workflows around speed, clarity, and feedback.
Concluding thoughts
Every major shift in design follows a familiar arc. Tools change first. Roles adapt next. Value concentrates around those who evolve early.
The design engineer is not a rejection of design craft. It is an expansion of it. Judgment still matters. Taste still matters. What changes is where that judgment is applied.
Designers who learn to write intent, understand constraints, and orchestrate systems will design at a scale that manual workflows cannot match. They will move faster from idea to reality and make better decisions earlier.
The future of UX is not that designers will code everything. Whether the role is called design engineer, UX engineer, design developer, or product engineer, the underlying shift is the same.
It’s that designers will orchestrate code, systems, and AI with clarity and purpose.
Continue reading...