
The slow percolation of this new title is something I've monitored for a long time. In a bygone era, some might have used the name "Rockstar Web Designer" or "Unicorn", but thankfully, we've at least somewhat matured. So what is a "Design Engineer", and what prevalence will it have in 2025? Let's discuss.
To answer this question, I made what some might see as a regrettable decision to ask the internet. So, with my blissful ignorance shielding me, I asked on LinkedIn, Mastodon, Bluesky, and Threads… "What does the title Design Engineer mean to you?"
For me, it's an etymology of a group of tech hybrids, who depending on the year or industry in question, may have been called web designers, ui/ux developers, frontend devs/engineers, creative technologists, and now Design Engineers. I've seen all these used in relation to design system work.
A very common answer came up: someone who straddles or bridges the gap between design and development. Someone who can translate for both sides of the coin and also work alongside those parties to achieve the best result for all involved.
A developer who can balance technical needs and design needs in near-equal measure.
The responses I received were really varied; some were very zoomed out, while others were very zoomed in on the details.
A little silly, but literally all I think of is: if you have that title you're one of those people who build those slick little details into user interfaces that people drool over. And it means you have the skills to think of them, design them, and implement them.
While somewhat unsurprising, these answers did paint a varied picture depending on people's personal experiences and expectations. The overlap was very noticeable despite the variation. What I didn't expect was the pushback on combining these words.
A couple of interesting threads formed in the replies to my question, including whether "Design Engineer" is appropriate as a title and whether using the word "Engineer" is allowed in the context of software development.
A design engineer makes me think more of hardware, product design, engineering for manufacture etc.
At least that was my degree, which was called Engineering Design - using it for software sort of makes sense but using the term would bring overlap and confusion with non-software engineering.
When we call ourselves engineers, I do have to ask, have we earned it? Do we take our responsibility seriously?
Initially, I was against the prospect of effectively gatekeeping our work with higher education hurdles. I feel very privileged to have had the time and funding to earn a degree in my field; not many can say that.
However, if we were able to set aside the problems with education systems, then the adversity of using the word "Engineer" would make more sense. In an ideal world, the respect and value held against engineers would be mirrored in other disciplines, such as software development. In turn, that high regard would be reflected in more protected titles and roles.
IMO not enough clarity and alignment on the title. Design systems need design-centric engineers and engineering-centric designers. From what I’ve seen, any time “engineer” is in the title, the role slowly becomes synonymous with “front end product engineer” which is a shame. I avoid it for that.
Nate's words are a bit of a bitter pill to swallow. The almost magnetic pull of development within companies can, by proxy, deplete design capacity and focus.
Ultimately, I don't think there's that much harm in using this title, but these points should be considered. Is it appropriate in your context, or will it give the wrong impression to others?
If you're having doubts about the Design Engineer title itself, then maybe try some of the following for size. Thanks to the community for chipping these into the bucket:
Even if you're unable to use these as your current job title, see them as SEO keywords for design systems work. While not exclusively the type of role working on design systems today, they do intersect heavily.
So I have to ask, do you think you're a Design Engineer? Or maybe a Design Technologist? A UX Engineer? Maybe the title doesn't matter so much to you, but the work at hand does. And therein lies the rub. It's not the title that's important; it's what that title means to your work peers.
I presume you're reading this article because you either want to enter this line of work or clarify what you already do at work. If so, I have some additional resources that might help you on your quest.
Egor Kloos wrote "The Gap" back in 2022, but I only stumbled into it recently, which is what sent me down this rabbit hole. It's a good read and explores the gaps that have formed as everyone in the product development chain (design and code) has been stretched.
Diana Mounter, Head of Design at GitHub, shared her talk on Design Engineering, which I found really eye-opening. Apparently, the talk has since been updated, but it's definitely still worth a watch.
Bob Monsour shared this article from Sean Voisen, Director of Design Engineering at Adobe, which contains even more resources.
Finally, during my investigation, people reached out and were kind enough to share their experiences of work that they regarded as "Design Engineering." I realize these might be a little awkward to share and read, but I think they're super insightful.
Caree Youngman, Senior Engineering Manager at Stitch Fix, shared a little about their collaboration efforts with the design team over on LinkedIn. Adam Luptak from Stripe also shared what Design Engineering means to the team at Stripe with an extensive thread on Bluesky. If either of you are reading this, you should turn these into blog posts!
That's all from me. How about you? We would love to hear from you via our socials about what you believe a Design Engineer to be. I look forward to hearing your thoughts!