What design engineers actually do
The day to day, the skills that matter and how to make the move.

Zander Whitehurst
11 min read
Design engineer is one of the fastest growing titles in product teams, and also one of the least clearly defined. Ask five companies what it means and you will get five answers. Here is how we think about it, based on working with hundreds of designers making the move.
When people ask me what I do, I sometimes say design engineer and watch their face try to work out whether that is a real job. It is, I promise. It is also, in my slightly biased opinion, one of the most fun jobs in tech, because you get to care about the tiny details and actually ship them yourself.
The short version
A design engineer owns the gap between a design and a shipped interface. They care about how something looks and how it is built, and they are trusted to make decisions in both.
That trust is the important part. Plenty of designers can code a little and plenty of engineers have good taste. A design engineer is someone the team relies on to make the final call on the details that make an interface feel right.
Why the role is growing
Products are judged more and more on feel. Smooth motion, thoughtful empty states and interfaces that respond instantly are no longer extras. They are what users expect, and they are exactly the details that tend to get lost between design and engineering.
At the same time, AI has made building UI far faster. That shifts the bottleneck away from writing code and towards knowing what good looks like. Teams increasingly need people who can direct that speed with taste, and that is the design engineer's core strength.
What the day to day looks like
In practice the work tends to fall into a few buckets:
- Building and polishing UI. Taking a direction and getting it to production quality, including motion, responsive behaviour and accessibility.
- Owning the component library. Making sure the design system works in code, not just in Figma.
- Prototyping ideas quickly. Turning a rough concept into something the team can actually use and react to.
- Raising the quality bar. Catching the small details that separate a good product from a great one.
A typical week might include pairing with a designer on a new flow, building a prototype for a user test, refining an animation that feels slightly off and reviewing pull requests for visual consistency. The variety is part of the appeal.
How it differs from frontend engineering
Frontend engineers and design engineers overlap a lot, but their centre of gravity is different. A frontend engineer usually focuses on application architecture, data, performance and reliability. A design engineer focuses on the interface layer: how it looks, moves and feels.
Both matter, and on good teams they work closely together. The design engineer makes sure the experience is right. The frontend engineer makes sure it scales and stays fast. Neither role replaces the other.
How it differs from product design
Product designers spend more time on problems, flows and research. They decide what to build and why. Design engineers usually pick up once the direction is clear and focus on making it real at a high level of craft.
In smaller teams these roles often blur, and many design engineers still do plenty of product design. The difference is less about tasks and more about where each person adds the most value.
The skills that matter
You do not need a computer science degree. The designers we see move into this role successfully usually build these skills in order:
- Solid HTML and CSS, especially layout and responsive design
- Comfort with a component framework such as React
- Working fluently with AI coding tools like Claude Code and Cursor
- A strong eye for interaction and motion
- Enough Git to collaborate without fear
AI has made the third point the great accelerator. Designers who learn to direct agents well can contribute production code far sooner than was possible even two years ago.
It is worth saying that AI does not remove the need for the first two. Understanding layout and components is what lets you judge whether the agent's output is good, fix it when it is not and explain what you want clearly in the first place. Our AI Design Engineering Bootcamp covers each of these, from HTML and CSS through to Git.
The skills people overlook
Beyond the technical basics, a few softer skills make a big difference:
- Communication. Explaining design decisions to engineers and technical constraints to designers.
- Prioritisation. Knowing which details matter most when time is short.
- Reviewing well. Giving clear, kind feedback on code and design alike.
These are often what separate a good design engineer from a great one, because the role sits at the meeting point of two disciplines.
My first pull request was a two line change to the padding on a button. I was so nervous I asked an engineer to review it three times. He approved it with a single thumbs up emoji and I felt like I had won an award. Start small. Nobody remembers your first PR except you.
How to make the move
Start by shipping something real, however small. Fix a spacing bug in your own product. Build a component and open a pull request. Each one teaches you how your team's codebase works and builds trust with engineers.
Ask an engineer you trust to review your first few pull requests in detail. Most are happy to help someone who is clearly trying to learn, and their feedback will speed you up enormously.
Build a small public project too. A personal site, a component playground or a recreation of an interface you admire. It gives you somewhere to practise without pressure and something concrete to show.
The title usually follows the work, not the other way round. Do the job for a while, make it visible and the role tends to find you.
Memorisely