One title, two job listings that want nearly opposite people. Here's how I read the role, where I sit on it, and why the mess makes this the best time to be in the field.
Read two design engineer job listings in the same week and you'd think they were for different jobs. One wants a backend engineer who can also design, with Figma listed as a plus. The other barely asks about design at all: if you're good with AI, you're in. Same title, nearly opposite people.
Neither listing is wrong. The title is young, and nobody has agreed on what it means yet. Right now it's the wild west.
The most useful way to see it is a line between design and engineering. Design engineering is a region on that line, rather than one fixed point on it.
Here's the line. Drag the marker along it.
The backend listing sits near the engineering end and treats design as a bonus. The AI listing doesn't sit anywhere: it hopes the agent covers the whole line. That's why the title feels so slippery. It can mean any stretch of it.
There's a reason the role exists at all. The further intent travels, the more it changes. Every handoff between product, design and engineering is a chance for it to bend, through technical limits, deadlines, or plain translation. A design engineer keeps more of the path in one pair of hands, so the judgment that started the work is still there when it ships. Here's how much of the path the role owns in three of its versions.
Look at the last two columns. The startup version takes the frontend and leaves intent to someone else. Mine starts at intent and carries it most of the way into the frontend. At a lot of fast-growing startups, the role's centre of gravity is moving toward engineering. I start at the design end and walk toward the code.
I'm a design engineer who is design first. I build the system underneath: the tokens, the components, and the studio where variants get made and judged. The code is how the taste ships. If I can defend every design decision, I'm still in charge, whoever or whatever wrote the line of code.
That's also my answer to the AI listing. Agents make code cheap, so the scarce part moves up the line, to knowing what's worth building and what to take out. An agent will happily say yes to everything. Judgment is mostly no's.
A messy title usually means the work changed faster than the words for it. Designers are learning to code, engineers are growing product instincts, and agents are taking the friction out of building. Nobody has written the rules for how a small team makes product in that world yet, so the people doing the work right now are the ones writing them.
That's the part I love. Few fields let you help decide what the job is while you're doing it.
If you're reading the listings and wondering which one you are, ask two questions. Where on the line do you start? And how many of the steps can you carry on your own? Then show something you shipped end to end. It says more than any title.