Flattening the Hierarchy of UX Design
Flattening the Hierarchy of UX Design: Opening the Door for the Next Gen. of Designers – Here we go again, right on schedule – as expected c-suit and product teams are making Claude Code rich with all the code refactoring and prompting. I just had an inbox exchange with a major staffing agency over a live contract role in San Antonio and Plano, Texas. The job description: entry-level UX Designer role focused on execution (Join, Onboarding, Rewards), explicitly seeking recent grads or juniors to “hit the ground running and make stuff.” The rate: $35 to $45 an hour.
This is a structural shift that I support. I have first-hand experience with the over-inflated, six-figure UX specialists at the executive tier for Lead, Principle and Senior UX roles – I was one of them, unfortunately mislabeled by a misinformed industry about my real craft. The industry is realizing now that software designers handle UX, management and DesignOps; the classic “10 Heuristics of Usability” are functional at a base level. Interface design craft isn’t a sacred design milestone anymore; it’s a commoditized baseline – AI governance/business ethics and agentic usability is the new complex problem to solve.
My direct response to the recruiter was simple: An undergraduate degree should be more than sufficient. We need to stop demanding 2–4 years of phantom corporate experience for entry-level work from young people starting out. UX design is not rocket science and we all know that, however it is not AI capable and probably never will be. Empathy and mental model evaluation – maybe a little delight is required for adoption, which is not the forte of stochastic algorithmic computing (AI).
We need to relegate UX practice to young designers who have the training and drive to execute while embedded in engineering teams. For the seniors and lead designers holding onto legacy silos, it is time to mature your skills and start producing frontend working AI-driven prototypes that will be handed off to engineering. Additionally, designers must provide governance for the entire agentic lifecycle, which will be a huge part of software design in the near future. If you aren’t using MCP to inform coding, mapping JSON schemas for Ai-native designs and using Visual Studio to build out working product demos, running code validation, or hardcoding deterministic AI guardrails to stop autonomous agent liabilities, then you are running out of runway. These are the purview of the software designer, not a product designer or UX alone.
UX design is not a sovereign department; it is a workflow methodology. It belongs embedded directly inside engineering, serving data safety and corporate profitability. The era of corporate feature factories run by siloed design teams is closing. We are taking the discipline back, restoring psychological safety to developers/designers, and building systems where technology is structurally bound by Agile methods to ensure that human beings flourish in this new era.

