Tokyo Coined the Design Engineer Role. Carlos Lastres on Why So Few Work There

Tokyo, the city credited with coining the term "design engineer," employs strikingly few people under that title — and Carlos Lastres, a design engineer working in the Japanese capital, says he can explain why.

The role itself sits at the intersection of design and code. A design engineer prototypes in production-grade front-end tools, builds the design system components other teams consume, and moves between Figma and the codebase without a handoff. Companies such as Vercel and Stripe have made the title a hiring category in the United States and Europe. Tokyo, despite its claim as the term's origin point, has not followed.

Lastres, who holds the role in Tokyo, frames the shortage as a structural problem rather than a talent problem. The city that named the position has built career ladders that make the position hard to staff, hard to define inside traditional organizations, and hard to grow into from either discipline alone.

What does a design engineer actually do?

The position differs from both of its parent roles. A designer hands off specifications; a front-end developer receives them. A design engineer does neither in isolation — the same person specifies the interface pattern and implements it, which removes the translation layer where design intent typically degrades.

That collapse of the handoff is the role's core economic argument. When one person owns both the mockup and the shipped component, interface decisions reach users faster and with fewer regressions between what was approved and what was built.

Why does Tokyo struggle to fill the role it named?

Lastres points to how the city's engineering and design organizations are structured. The explanation he offers centers on the difficulty of the hybrid position inside companies that hire, evaluate, and promote along single-discipline lines.

A candidate who spends half their time in a code editor and half in design tooling fits neither a pure engineering ladder nor a pure design ladder. Titles, salary bands, and promotion criteria in Tokyo's established companies rarely account for the split, which suppresses both supply and demand for the role.

Does the shortage matter for product teams?

For teams building interface-heavy products, the absence of the role has practical consequences. Design systems need someone who can author both the visual specification and the production component. Without that overlap, teams either duplicate the work across two roles or ship components that drift from their intended behavior.

Tokyo's position as the term's originator makes the gap more visible. The city demonstrated that it could name the discipline; Lastres's account suggests the local employment structures have not yet caught up with what the name describes.

Whether Tokyo's employers restructure their career frameworks to accommodate hybrid practitioners will determine whether the role grows beyond a handful of people like Lastres — or remains a title the city coined and largely failed to hire.