The UX career ladder is not getting harder to climb — it is changing shape. The designers who will matter in five years are not the ones who got better at designing. They are the ones who understood which direction to grow toward before the industry made it obvious.
In the last article I wrote about seniority, I argued that the conditions that produce Senior Designers are disappearing — that companies want experienced practitioners but are systematically eliminating the environments that create them. A few people responded by asking the logical follow-up question: if that is the situation, what is a working designer supposed to do about it?
It is the right question, and I want to answer it honestly rather than optimistically. The honest answer is not that you should get better at UX. It is that the category 'UX designer' is being squeezed from multiple directions at once, and the designers who will have leverage in five years are the ones building skills that put them at intersections the category alone does not cover.
I have been in this industry for sixteen years. I have watched several rounds of 'design is changing everything' rhetoric come and go. What is happening now feels structurally different — not because of AI specifically, but because AI is accelerating a shift in what design organizations actually need that was already underway. The execution layer of design — wireframes, flows, component variants, basic research synthesis — is being compressed. The strategic layer — translating ambiguous business problems into clear design direction — is more valuable than it has ever been. The designers who were living in the execution layer without developing roots in the strategic one are in the most precarious position.
What follows is not a universal prescription. It is the map I would draw if I were starting over with everything I know now.
The designers who will matter in five years are not the ones who got better at designing. They are the ones who understood which direction to grow toward before the industry made it obvious.
— Roy Villasana
The Four Directions Worth Growing Toward
I am not going to list every emerging title in the industry. Most of them are repackaged versions of older roles with AI in the name. Instead, I want to describe four directions of growth that are genuinely differentiating right now — not as job titles but as capability profiles. You may end up with a different title depending on the company. The capabilities are what matter.
1. The Design Engineer
This is the role I see companies competing hardest for right now, and the one most traditional UX designers have the most resistance to pursuing. A Design Engineer can build what they design — not at a senior frontend engineer level, but competently enough to prototype in production code, work directly in a design system's component library, and close the gap between a Figma file and a shipped product without a translation layer.
The value is not the code itself. It is the reduction of the distance between design intent and implementation reality. Designers who can only communicate through static artifacts are operating through an interpreter. Designers who can touch the codebase directly are in the room where decisions actually happen.
What this requires: familiarity with React or a comparable component model, enough CSS to control layout and typography with precision, and experience contributing to or owning a design system at the token and component level. You do not need to become an engineer. You need to become fluent enough to be dangerous.
2. The AI Product Designer
Not a designer who uses AI tools — every designer will use AI tools. I mean a designer who has developed genuine expertise in designing products that contain AI behavior: recommendation systems, generative features, autonomous agents, predictive interfaces. This is a different design problem than anything the discipline has dealt with before, and most designers are not equipped for it yet.
Designing AI behavior requires thinking about error states as a primary design challenge rather than an edge case. It requires understanding probabilistic outputs well enough to set appropriate user expectations. It requires designing for trust calibration — the ongoing process by which a user learns what a system can and cannot be relied upon to do. None of these are in a standard UX curriculum. All of them are in high demand from product teams shipping AI features.
What this requires: hands-on experience shipping at least one AI feature through a full cycle — brief, research, design, testing, and post-launch evaluation. Reading about this is not enough. The conceptual vocabulary is accessible; the practical judgment only comes from doing it.
3. The Product Strategist
This one is less about a new skill domain and more about expanding the operating altitude at which you work. A Product Strategist — regardless of whether that is their title — is a designer who has moved from answering 'how should this be designed' to being in the conversation about 'what should we build and why.' They can run a problem framing workshop with a C-suite audience. They can translate a business objective into a research question and a research question into a design direction. They carry enough business literacy to push back on a product requirement with a commercial argument, not just a usability argument.
This evolution does not require leaving design. It requires deciding that your value is not in the quality of your artifacts but in the quality of your decisions — and that the decisions upstream of design are your business too.
What this requires: deliberate exposure to business strategy conversations, not just product strategy. Understanding unit economics, retention loops, and market positioning at a level that lets you speak to them credibly. Getting into the room with executives and learning to operate there before you feel ready for it.
4. The Systems Designer
Design systems work has been undervalued for most of its existence. That is changing. As organizations scale digital products across platforms, markets, and teams, the designers who can build and govern a coherent design system are the ones holding the whole thing together. This is infrastructure work, and infrastructure work is strategic work — even when it does not feel that way from the inside.
The Systems Designer role has also evolved significantly. It is no longer primarily about maintaining a component library. It is about setting the design decisions that scale across a product organization — token architecture, theming strategy, accessibility standards, contribution models, documentation quality. It requires a different kind of rigor than product design and a different relationship to influence. You are not designing the product. You are designing the conditions under which the product gets designed.
What this requires: willingness to work at a slower cadence than product design, comfort with abstraction over specificity, and genuine investment in how other designers work — not just in how users experience the product.
What All Four Have in Common
Looking at this list, one pattern is consistent across all four directions: they require moving closer to the places where consequential decisions are made. The execution layer of design — the wireframes, the flows, the component variants — is being automated or commoditized. The judgment layer — what to build, how to structure it to scale, how to make AI behavior trustworthy, how to bridge design intent and engineering reality — is not.
The uncomfortable truth is that many working designers have spent their careers optimizing for the execution layer. The speed of your wireframes, the quality of your component library, the elegance of your Figma organization — these things mattered and still matter, but they are table stakes now, not differentiators. The differentiation is in judgment, not output.
The Specific Moves That Matter Right Now
If I were advising a mid-level or senior designer who wanted to move toward one of these profiles in the next eighteen months, I would say the following:
Pick one direction and go deep, not three directions and go shallow. The designers who are genuinely differentiated right now did not sample several new skill areas. They committed to one and built enough depth to be credible. Shallow familiarity with multiple new domains is less valuable than real fluency in one.
Find a current project where you can work at the edge of your capability. This is the same principle that produces senior designers: ownership of hard problems builds judgment faster than supporting work on smooth ones. If your current role does not offer this, look for the adjacent project that does — or consider whether your current role is the right environment for growth at this stage.
Build in public at the decision level, not the output level. Most design portfolios showcase artifacts. The practitioners who are gaining traction right now are the ones showing their decision-making — writing about the trade-offs they navigated, speaking about the research that changed a product direction, sharing the strategic framing behind a design system architecture. The artifact is evidence. The judgment is the point.
Get closer to the business problem than feels comfortable. Designers who understand commercial context make better decisions than designers who understand only user needs. This is not a betrayal of user-centered design. It is an acknowledgment that you are designing within a system that has to sustain itself financially in order to serve users at all.
The Honest Part
None of these directions are easy, and none of them can be completed in a six-week course or a new tool subscription. They require the same thing seniority always required: accumulated context from hard problems, honest feedback from people with more experience, and enough time in environments where your decisions had real consequences.
The industry is not going to slow down and wait for designers to catch up. The organizations that are winning right now are hiring people who sit at these intersections today — or growing the people they have toward them with enough intention that the gap is closing. If neither of those is happening in your current environment, that is diagnostic information. Use it.
The designers who matter in the next phase of this industry will not be the ones who learned the new tools first. They will be the ones who understood what the tools were replacing, what they were not replacing, and what that meant about where to grow. That understanding does not come from following the discourse. It comes from doing the work, watching what happens, and being honest about what you see.
Keywords
UX career growth, product designer career path, design engineer, AI product design, product strategy, design systems, senior designer next steps, UX career evolution, design leadership, future of UX design