Not just “designing AI features” but understanding how LLMs, agents, and probabilistic systems behave — designing for non-deterministic outputs, graceful failure, trust calibration, and human oversight. This is the single biggest differentiator in hiring right now.

Teams expect designers to go from idea to working interactive prototype in hours, not weeks — using tools like Figma Make, v0, Cursor, or Claude to build real, testable artifacts rather than static mocks.

Designing flows, states, permissions, and edge cases across an ecosystem — not polishing individual screens. Senior roles especially are judged on how you handle complexity, not composition.

Comfort running lightweight research (interviews, usability tests, surveys), reading product analytics, and knowing when qualitative vs. quantitative evidence is the right instrument. “I think” loses to “here’s what we saw.”

Framing design decisions in terms of metrics, cost, risk, and strategy. The designers who survive org cuts are the ones who can articulate why their work moves a number leadership cares about.

UX writing, content design, and — increasingly — prompt and conversation design. As interfaces get more conversational, the words are the interface.

Working within (and contributing to) tokens, components, and documentation. Knowing when to extend the system versus when to break it, and how to keep design and code in sync.

You don’t need to ship production code, but you need to understand APIs, data models, front-end constraints, and now model capabilities, latency, and cost — enough to design things that can actually be built.

WCAG isn’t a checklist item anymore; regulatory pressure (like the European Accessibility Act) has made it a legal and hiring requirement, and AI interfaces raise brand-new accessibility questions.

Presenting work persuasively, facilitating alignment across engineering, PM, and leadership, and defending decisions under pressure. At senior levels, your ability to move a room matters as much as your craft.