Menu
UX Designer
Three components - Automation Resistance, Structural Moat, and Demand - add up to the 37.
The automation signal is severe for entry work because interface production is digital and tool-friendly; observed AI use looks moderate, but modeled vulnerability is much worse, while product judgment and research survive better than screen-making.
Observed AI exposure is about 24.9%, while modeled job-loss risk is about 54.6%. That gap is the key caution: current tool use looks moderate, but vulnerability is severe because screens, prototypes, summaries, copy, and design-system assembly are digital tasks. Product judgment, research framing, accessibility, and stakeholder tradeoffs keep only a narrow core protected.
AI can draft screens, flows, prototypes, research summaries, copy, images, and design-system variations. The worker upside is limited because many UX designers are salaried and employers can keep much of the productivity gain by reducing production hours or raising output expectations.
Protection is practical product trust, not formal law: UX has no license, almost no physical barrier, and a portfolio-heavy bachelor's-level path, with employer trust doing more than credentials inside real product teams and hiring decisions.
UX design is mostly desk, screen, workshop, meeting, and research-session work. Occasional user interviews or team sessions create little physical barrier. The durable difficulty is cognitive and organizational: finding the right problem, handling constraints, and getting teams to act on evidence.
There is no occupational license, board exam, or protected legal scope for UX or digital interface design. Accessibility and privacy rules can raise project stakes, but they do not create a profession-wide gate that protects entry into the job.
Robotics is irrelevant to the main risk. UX design is screen-based product work, so substitution pressure comes from software, AI interface tools, no-code prototypes, design systems, and platform automation. The robotics score is high only because robots are not the channel.
Digital interface designers often have a bachelor's degree in web design, digital design, graphic arts, or a related field, but employers may also accept strong project proof. That creates moderate credential depth without a protected ladder.
Demand is positive because digital products, accessibility, mobile interfaces, and enterprise software still need design work, but no-code prototypes, design systems, and generative UI tools pressure entry production while the ladder gets thinner for beginners.
The digital interface designer base has about 128,900 jobs, roughly 9,100 annual openings, and growth near 7%. The volume signal is positive, but it does not offset the severe pressure on the screen-production layer.
Demand comes from digital products, web and mobile interfaces, accessibility, usability, enterprise software, and product metrics. The quality is held back because no-code tools, design systems, generated UI, and platform consolidation can absorb production work that once justified junior UX seats.
Product/interface work persists, but the active shock is aimed at the first rung: static mockups, design-system assembly, prompt-to-prototype work, research summaries, copy, and simple screen variants. Resilience is stronger only where UX owns evidence, accessibility, product tradeoffs, and stakeholder trust.
The case weakens if teams routinely generate usable screens, flows, copy, and prototypes from prompts or design systems with little junior designer labor. The threshold is fewer paid entry roles and less learning work, not faster wireframes used by the same designers.
The case improves if employers need recurring UX labor for accessibility, testing, documentation, and accountable interface decisions. The trigger is paid work for normal product teams tied to audits, liability, purchasing, or compliance, not optional accessibility language in portfolio projects.
The case improves if entry roles include interviews, usability testing, experiment interpretation, metrics, and cross-functional product decisions. The threshold is real responsibility for evidence and tradeoffs inside paid product teams and internships, not only cleaner screens or faster prototype output.