Guides What is a design engineer?

Updated November 20, 2026

AI-generated from Mike Stilling's work, notes, and writing.

What is a design engineer?

Mike Stilling started writing real code at 14, went to school for traditional print design, and has spent a career somewhere between designer and developer, with job titles that rarely matched the actual work. This guide covers what "design engineer" means in software, and Mike's answer to the forever-debate about whether designers should code.

The short answer

In software, a design engineer is someone who designs interfaces and builds them in real code. They live where design and front-end development overlap: interaction, motion, layout, typography, and the details that make a product feel good to use. The title is newer than the work. Plenty of people have done this job for years under titles like "web designer," "UX engineer," or "designer who codes."

Heads up: "design engineer" also means something completely different in mechanical and industrial engineering. This guide is about software and the web.

What design engineers do

The exact mix depends on the company. Most design engineers spend their time on some combination of:

  • Prototyping in code to test ideas with real data, real interactions, and real performance.
  • Building production UI, especially pages and components where craft matters: marketing sites, onboarding, and core product flows.
  • Owning design systems in code, so the tokens, components, and documentation people actually use match the design intent.
  • Closing the gap between design and engineering, by making decisions where the two meet instead of throwing specs over a wall.

Here's what that looked like for Mike at FireHydrant. In the first week, Mike rebuilt the homepage overnight to show what a full rebuild could be. Then Mike redesigned and rebuilt the entire marketing site in under three weeks: 300+ pages, 25+ templates rebuilt, 50% fewer dependencies, and Lighthouse scores up 56%+. No hand-off would have made that timeline possible. (Full case study.)

How it compares to other roles

Role Primary tool Owns
Product designer Design tools like Figma The experience and visual design, handed to engineering
Design engineer Code, with design tools as needed Design decisions and the front-end implementation of them
Front-end engineer Code Application architecture, data, performance, and implementation
Web designer/developer Both Marketing and content sites, often end to end

Titles are messy. A "design engineer" at one company is a "senior web developer and designer" at another. Mike's FireHydrant title was literally that.

Should designers learn to code?

Yes. One of Mike's hot takes is that HTML, CSS, and Git should have been required knowledge for designers. So much software gets purchased, and so much work happens, purely because people don't understand those three things.

You don't need to become a software engineer. But some code knowledge pays off in very practical ways:

  • Your designs get more realistic. You know what's cheap, what's expensive, and what's impossible before anyone else has to tell you.
  • You can prototype in the real medium. A working prototype convinces people in ways a static mock can't. At FireHydrant, building an example first was more persuasive than asking permission. At Stripe, a peer noted that one of Mike's prototypes was "instrumental in gaining leadership approval."
  • You skip hand-offs. Fewer translation layers means fewer things lost along the way, and faster shipping.
  • You can judge craft properly. Saying something is great and making it great are two different things. Knowing whether a design is truly great requires understanding how it's built. Otherwise you're only evaluating surface detail.

The counterargument is that designers should go deep on research, strategy, and visual craft instead. That's fair, and not every designer needs to ship production code. But basic code literacy rarely makes a designer worse.

What to learn first

A realistic path, in order:

  1. HTML. Semantic structure: headings, lists, links, buttons, forms. Build a page from a blank file.
  2. CSS. The box model, then flexbox and grid. Then spacing, typography, and color. This is where design actually lives on the web.
  3. Utility-first CSS. Tools like Tailwind make designing directly in a code editor simple, exact, and fast. Mike considers utility-first CSS the best design tool created so far.
  4. Git. Branch, commit, open a pull request. It's how you contribute to a real codebase without fear.
  5. A little JavaScript. Enough to toggle states, handle a form, and read what an AI tool wrote for you.
  6. A static site generator. Something like Eleventy shows how pages, layouts, and components fit together without a heavy framework.

There's more on the HTML, CSS, and Tailwind part in designing in code.

Does AI change this?

AI coding tools have made it far easier for designers to build working prototypes. Tools like Cursor and Claude Code are a big part of Mike's day. But they make code literacy more valuable, not less. AI is a multiplier, and a thousand times nothing is still nothing. Someone still has to judge the output, fix what's broken, and refuse to ship slop. If you know how things work, you get dramatically more out of these tools. There's a practical walkthrough in prototyping in code for designers.

Frequently asked questions

What is a design engineer in software?

In software, a design engineer is someone who works across design and front-end development. They design interfaces and build them in production code, usually with a strong focus on interaction, motion, visual detail, and the parts of the front end where small details make a big difference. This is different from the mechanical or industrial 'design engineer' title.

Should designers learn to code?

Yes, at least HTML, CSS, and Git. You do not need to become a software engineer, but understanding how the web is built makes your designs more realistic, lets you prototype in the real medium, and removes many hand-offs. With AI-assisted coding tools, the barrier to building working prototypes is lower than it has ever been.

What is the difference between a design engineer and a front-end engineer?

A front-end engineer is primarily responsible for building and maintaining application code. A design engineer leans toward design: they often own the visual and interaction decisions themselves and use code as their main design tool. There is a lot of overlap, and titles vary from company to company.

How much code does a designer need to know?

Enough to build a static page with HTML and CSS from scratch, to understand the box model and layout with flexbox and grid, to read and tweak a component in your team's codebase, and to use Git to branch and open a pull request. That is a realistic starting point and it covers most of the value.

Will AI replace the need for designers to code?

AI tools can now write a lot of code, but someone still needs to judge whether the output is good, fix what is broken, and know what is technically reasonable. Designers who understand code get far more out of these tools than designers who do not.