Two titles, one confusing year
If you've been scrolling job listings lately, you've probably run into a title that didn't exist a few years back: UX Engineer. It sits right next to the familiar UX Designer, and it isn't always obvious what's different, or which one you should be aiming for.
This isn't hype and it isn't a trick question. The way software actually gets made has shifted, and the job titles are just catching up. Let's slow down and look at what really changed.
How making software used to work
For a long time, building anything digital followed a simple line: someone finds the problem, a designer shapes the experience, a developer turns it into working code, and it ships. Each person owned one link in that chain.
It worked, but it was slow, and every handoff was a chance for the original idea to get a little blurry by the time it reached a screen. More teams are shortening that chain now. Instead of a full handoff between design and code, one person carries the idea further, sometimes all the way to a working screen. That single change is behind most of the confusion around these two titles.
What a UX Designer does
A UX designer's job hasn't disappeared, and it hasn't gotten smaller. It still rests on the same core questions: What problem are we actually solving? What do people need, not just what they say they want? Does this make sense the first time someone sees it?
Day to day, that means talking to real users, sketching flows, building clickable prototypes, and testing ideas before they cost anyone real money to build. This is still the hardest and most valuable part of the whole job, no matter which title ends up on the business card.
What a UX Engineer does
A UX engineer does all of that same thinking, and then keeps going. Instead of handing a finished design to someone else, they build the first working version themselves, in real code that runs in a browser.
This isn't the same as being a full software engineer. It's closer to knowing enough HTML, CSS, and JavaScript to turn your own idea into something people can click through, not just a picture of a screen that looks like it works. The point isn't to replace developers. It's to remove one slow, lossy step from the middle of the process.
A simple way to compare them
Both roles do the same early work: talking to users, sketching flows, testing ideas. The difference shows up later, in how much of the final product they build with their own hands.
Both aim for the same thing: a product that makes sense. The difference is just how much of the finished thing they build themselves.
Does one pay more?
Money depends on the company, the country, and your experience, so anyone giving you an exact number is guessing. What's fair to say: people who can do both the research and the building tend to get paid for both skills, not just one.
Where AI actually fits
AI can already write a rough draft of code, and it can summarize a stack of interview notes in seconds. That's real, and it isn't going away. What it still can't do is decide which problem is worth solving, or sit with a confused user and figure out what they actually meant. That part is still yours, no matter which title you choose.
The designers and engineers who'll do best aren't the ones ignoring AI, and they're not the ones leaning on it for everything either. They're the ones using it for the boring parts, and staying sharp for everything else.
So, which one should you be?
You don't have to decide forever, and you don't have to decide today. If you love sitting with a messy, open-ended problem and figuring out what's really going on, lean toward design. If you love that too, but also want to see your own idea working in a real browser instead of a picture of one, lean toward engineering.
Either way, the starting point is the same: pick one screen from your own portfolio, and turn it into a real, working page using plain HTML and CSS. You'll learn more from that one exercise than from ten more articles about which title to chase.
The part that never goes out of style
Job titles will keep shifting. In a few years there'll probably be another new one nobody's heard of yet. What won't change is the one question every good designer has always asked: does this actually make sense to the person using it?
Keep asking that question, stay willing to learn whatever tool shows up next, and the title on your business card will matter a lot less than you think.