Explore

What is UX Engineering, really?

UX Engineering is one role with many shapes. Here's how different teams define it, how it differs from adjacent roles, and what a real day looks like.

How companies define it
Vercel
engineers who work at the intersection of design and frontend, focused on the craft of the interface itself.
Linear
engineers who build the product’s expressive layer — animation, interaction, polish.
Stripe
engineers embedded with design who specialize in implementation quality and interaction fidelity.
Google
a hybrid role split between design systems engineering and prototype engineering for experiences.
Figma
design engineers who think in components and ship the system the rest of the product is built on.
UXE vs adjacent roles
UX Engineer
vs
Frontend Engineer
A UXE optimizes for how it feels. A FE optimizes for how it scales. The overlap is huge; the orientation is different.
UX Engineer
vs
Product Designer
Both think in interactions. The UXE ships them; the designer specifies them. The best UXEs do both.
UX Engineer
vs
Creative Developer
Creative developers build expressive, often one-off experiences. UXEs build systems that ship and stay.
UX Engineer
vs
Product Engineer
A product engineer owns end-to-end. A UXE owns the surface — but with the same product ownership instinct.
A day in the life
09:30
Sync with design about the upcoming filter UI. Spot a focus-trap edge case in the prototype.
10:15
Prototype 3 motion variants for the new menu in code. Send a Loom to the team.
11:00
Pair with backend on the new endpoint. Push back on a payload shape that would force a loading state.
13:00
Audit the design system’s button. File 4 RFCs about hover states and focus rings.
15:00
Ship the empty state for the dashboard. Write a small post about what changed and why.
16:30
Review a PR from a designer learning React. Leave 12 nice comments.