And Most People Entering the Field Don’t Know That Yet.
Somewhere around 2020, something shifted. The tech industry exploded, remote work became the norm, and suddenly everyone on LinkedIn had a new job title: UX Designer. Boot camps ran ads promising six-figure salaries in twelve weeks. YouTube thumbnails screamed, “become a UX designer with no experience.” Twitter threads listed the “5 tools you need to break into UX” as if the whole discipline could fit inside a Figma file. And just like that, UX became the side door into tech.
I’m not here to gatekeep.
More people in design is a good thing. But there’s a growing problem in this field that nobody wants to say out loud: a massive number of people calling themselves UX designers have never actually studied what UX means. They learned the interface. They skipped the experience. The Surface Level Version of UX Here’s how the typical entry story goes. Someone is tired of their current job. They hear that UI/UX pays well and doesn’t require coding. They find a no code tool, learn to drag and drop components onto a canvas, watch a few tutorials on auto layout, pick up some Figma shortcuts, and within a few months they’re applying for UX roles with a portfolio full of redesigned apps they’ve never user tested. They know what a wireframe looks like. They know what a design system is. They can talk about colour contrast and button states. But ask them to explain the difference between a mental model and a conceptual model, and the room goes quiet. This isn’t a personal failure. It’s a systemic one.
The industry sold UX as a visual craft when it’s actually a research discipline dressed in visual clothing.
What UX Actually Contains If you peeled back the surface of UX and looked at what it really demands, here’s what you’d find underneath: Cognitive psychology — Understanding how humans process information, make decisions, and form habits. Why does a user abandon a checkout flow? It’s not always because the button was the wrong colour. Sometimes it’s cognitive overload. Sometimes it’s decision fatigue. Sometimes it’s learned helplessness from too many failed attempts. Without understanding how the mind works, you’re decorating a problem instead of solving it. Behavioural economics — The study of why people don’t always act rationally. Loss aversion, anchoring, the paradox of choice ,these aren’t just academic concepts. They directly influence how you design pricing pages, onboarding flows, and notification systems. A good UX designer knows when they’re using a dark pattern and when they’re genuinely reducing friction. That boundary requires theory, not just instinct. Research methodology — Qualitative and quantitative. Ethnographic studies, contextual inquiry, diary studies, usability testing, A/B testing, survey design, heuristic evaluation, card sorting, tree testing. Each method answers a different question, and knowing which one to use when is what separates a designer who guesses from a designer who knows. Information architecture — Not just sitemap design. Real IA is about the structural design of shared information environments. It’s about organising, labelling, and creating navigation systems that help people find what they need and understand where they are. It draws from library science, linguistics, and cognitive load theory. Interaction design — The design of behaviour over time. How does the system respond to what a user does? What feedback does it give? How does it handle errors? Interaction design isn’t about making things look pretty when you click them. It’s about making the relationship between a person and a system feel natural, predictable, and trustworthy. Service design — Looking beyond the screen entirely. How does a digital product fit into the larger ecosystem of a service? What happens before the user opens the app? What happens after they close it? How does the front stage experience connect to the backstage operations? This is where UX meets business, logistics, and human systems at scale. Designing for the full range of human ability. Not as an afterthought, not as a compliance checkbox, but as a fundamental constraint that shapes every decision from colour choice to interaction pattern. Nearly fifteen percent of the world’s population lives with some form of disability. If your design doesn’t account for that, it isn’t good UX. It’s just UX for some people. That’s not a twelve week curriculum. That’s a career.
Why the Shallow Entry Hurts Everyone When the field gets flooded with people who only understand the visual layer, a few things happen.
First, companies start to believe that UX is just “making things look nice.” They hire designers expecting wireframes and pixel-polished screens, not research insights and strategic recommendations. The role gets reduced to a production function , a pair of hands in Figma instead of a thinking discipline that shapes product direction. Second, salaries plateau. When the market is saturated with people who can push pixels but can’t synthesise research, the perceived value of the role drops. Companies that once hired senior UX researchers now just ask the UI designer to “talk to a few users.” The rigour gets replaced by gut feeling with a design thinking workshop slapped on top. Third, and this is the one that really stings users suffer. Products get built that look beautiful and feel hollow. Onboarding flows that test well in screenshots but confuse real people. Dashboards that win design awards but require a tutorial to navigate. Interfaces that prioritise visual trends over usability because the person who designed them learned aesthetics but never learned behaviour. The Depth Is What Makes It Interesting Here’s the thing nobody tells you: the deep end of UX is far more interesting than the shallow end. When you understand cognitive psychology, you start seeing patterns everywhere not just in apps, but in physical spaces, in conversations, in how cities are designed and how hospitals are laid out. When you learn research methodology properly, you stop guessing and start knowing. There’s a confidence that comes from building a product on real evidence instead of assumptions. When you study information architecture, you realise that the most elegant designs aren’t the ones with the best gradients they’re the ones where people never get lost. When you understand accessibility deeply, your empathy sharpens in ways that make you better at every other aspect of design. The people who go deep in UX don’t just become better designers. They become better thinkers. They become the ones product managers actually listen to. They become the ones who get pulled into strategy meetings and founder conversations because they can connect user behaviour to business outcomes with evidence, not opinion.
The Difference Between Knowing the Tools and Understanding the Craft There’s a moment in every UX career where you realise Figma is not the skill.
The skill is sitting across from a user who’s struggling with something you designed and understanding really understanding what went wrong in their mental model, not in your layout. The skill is reading a research transcript and finding the insight that changes the entire product direction. The skill is standing in a room full of stakeholders who want different things and knowing which user need should win the argument. That moment doesn’t come from a twelve week boot camp. It comes from reading psychology, running real research, studying how people navigate complexity, and caring enough about the discipline to go beyond the surface. It comes from treating UX like what it is a field with decades of academic and practical foundation not a career hack with good job postings. The designers I respect most aren’t the ones with the cleanest Dribbble profiles. They’re the ones who can explain the reasoning behind every decision in their portfolio without once mentioning what font they used. The Invite Is Still Open None of this is meant to scare you away from UX. Quite the opposite. The field needs curious, dedicated people who are willing to go deep.
The world has enough designers who can make a login page look sleek. What it needs are designers who can look at a broken system, understand why it’s broken, and design something that actually works for the people using it.
UX is not a shortcut into tech.
It’s one of the most intellectually demanding and rewarding design disciplines that exists. And if you’re willing to treat it with the depth it deserves, you won’t just have a career you’ll have a craft. The door is wide open. Just don’t mistake the lobby for the whole building.
