1.2 The two lenses

The Role · Section 1.2

Google splits UX Engineering into two concentrations. It is the most useful map for working out where you fit — and where you will have to stretch.


The two

🎨 Design lens. Stronger in visual design, interaction, prototyping. Still codes.

⚙️ Engineering lens. Stronger in frontend architecture, performance, systems. Still designs.

Both share the same core:

programming fundamentals
strong UX advocacy
the ability to speak pixels AND code

Neither is the senior version of the other. They are different centres of gravity in the same role.


You are the engineering lens

Coming from development, this is your natural starting position — and it is worth knowing what that means in practice.

What comes easily. Architecture, performance, systems thinking, build tooling. When the conversation turns to how something should be structured, you are already fluent. Your prototypes run at production quality because you cannot help it.

What does not. Deciding what it should look like. Knowing which of three acceptable layouts is the right one. Noticing that the spacing is off before someone tells you. These are trained skills, not innate ones, and they are what chapters 2–5 exist for.

The specific trap. Engineering-lens people tend to over-index on the system and under-index on the surface. You will build an immaculate component API for a component that does not look right. Both halves have to ship.


The variants you will see in job posts

The lenses show up in titles, unevenly:

Product design engineers. Design systems, UI components, shipping directly to product. Usually engineering-lens.

Marketing design engineers. Landing pages, launch experiences, pushing CSS/WebGL/animation. Usually design-lens, and the most visually demanding.

Autonomous design engineers. Sketch it in Figma or code, get feedback, ship it. No handoff. Requires both lenses at strength.

Read the requirements, not the title. "Design Engineer" at two companies can mean very different daily work — Cursor asks for TypeScript, React, SolidJS and CSS animations with equal comfort in Figma and the editor; Vercel's team includes people doing Three.js, GLSL shaders and video editing.


Using this

Pick the lens you are starting from, then deliberately spend time on the other one. The role is defined by the overlap, and the overlap is where your value is.

For you, that means resisting the pull toward problems you already know how to solve.

On this page