UX Designer
You feel it instantly when an app is confusing — and a UX designer is the person paid to find the fix and prove it worked. This page covers what the work actually involves, how UX differs from the three titles employers use interchangeably with it, and what separates a portfolio that gets hired from the thousand that do not.
Typical Pay (US)*
$99kmedian** AI-estimated from general U.S. labor-market patterns — not measured data from the U.S. Bureau of Labor Statistics or any official source. Real pay varies widely by location, employer, experience, and timing.
Outlook
The underlying occupation is growing quickly — around 6% estimated annual growth against roughly 110,000 people employed — and sits in the top few percent of momentum among design and interface occupations. What AI eats is production: generating layout options, filling out component states, producing copy variants, and increasingly first-pass synthesis of research transcripts. What survives is judgment about what should exist at all, interaction design for problems with no established pattern to copy, and stewardship of a design system as a shared contract. The practical consequence is that pixel-pushing juniors are the most exposed group and researchers who can also ship are the least.
What does a UX Designer do?
A UX designer is responsible for making a product understandable and usable by the people who have to use it. The day-to-day is less drawing than most people expect. You spend time working out what the user is actually trying to accomplish and where the current flow betrays them — watching session recordings, reading support tickets, running a five-person usability test on a prototype. Then you design the structure: what steps exist, in what order, what each screen is for, what happens on error, what the empty state says. Then you build it in Figma at enough fidelity that engineers can implement it and stakeholders can react to something real rather than a description. Then you check whether the change worked, which is the part junior portfolios almost always omit.
The titles are a genuine mess and employers are inconsistent about them. A UI designer is scoped to the visual and interaction surface: typography, spacing, colour, component states, motion. A UX designer is scoped to the structure and the flow — where things live, in what sequence, and why. A product designer is usually both of those plus product thinking: participating in what gets built and why, not only how it looks. A UX researcher does the investigation full time — study design, recruiting, interviewing, synthesis — and hands findings to designers rather than shipping screens. In practice most postings titled UX designer are asking for a product designer, and at small companies one person covers all four. Read the responsibilities and the tools list rather than trusting the title.
The bar for entry has risen sharply, and it is worth being blunt about why. Hiring managers now see hundreds of portfolios containing the same three projects: a redesigned Spotify app, a fictional plant-care app, and a food-delivery flow, each presented with the same double-diamond diagram and invented personas. None of it demonstrates the thing they are actually screening for, which is whether you can design under a real constraint for a real user and show a measured outcome. One case study that names an actual client or team, an actual limitation you could not design around, the two options you rejected, and a number that moved afterwards outperforms six polished fictional redesigns.
Design systems are the other thing that separates hireable from not. Most professional UX work happens inside an existing component library rather than on a blank canvas, so fluency with Figma components, variants, auto layout, and variables — and the judgment about when a new component is justified versus when you should reuse — is closer to the daily reality than visual invention.
It suits people who are genuinely curious about other people's confusion and who can hear "I do not understand this screen" about their own work without flinching. It suits people badly if you want your taste to be the final argument, because in this job evidence outranks preference.
A day in the life
- Run three 20-minute usability sessions on a clickable prototype and watch two out of three people miss the primary button entirely
- Redraw a five-step signup as three steps, then find out from engineering that step two is a payment-provider constraint you cannot remove
- Build the flow in Figma with real component variants instead of detached copies, so the handoff does not fork the design system
- Argue in a design critique that a modal is the wrong pattern here, and lose to a launch deadline — then write down the tradeoff so it can be revisited
- Audit the product for every place an error message says something the user cannot act on, and rewrite them
- Add three new states to a component — loading, empty, permission-denied — because the happy path was the only one specced
- Pull last month's completion rate on the flow you redesigned in Q1 to see whether the drop-off actually moved
How to become a UX Designer
- 1
Learn the fundamentals of interaction and visual structure
~2-3 monthsHierarchy, grouping, affordance, contrast, typographic scale, spacing systems, and standard platform patterns for iOS, Android, and web. These are learnable from books and platform guidelines and do not require a programme or a degree.
- 2
Get genuinely fluent in Figma, including design systems
~2 monthsAuto layout, components and variants, variables, prototyping, and multiplayer critique conventions. The distinguishing skill is working inside an existing library without detaching everything, because that is what the job actually asks for daily.
- 3
Learn research methods well enough to run a study yourself
~1-2 monthsModerated usability testing, unmoderated tasks, five-user rule of thumb, writing non-leading questions, and synthesis into findings rather than anecdotes. Design decisions defended with evidence beat design decisions defended with taste in every interview.
- 4
Do one project with a real user and a real constraint
~2-3 monthsA local nonprofit, an open-source tool, a friend's small business, or an internal tool at your current employer. The requirement is a client who can say no and a limitation you have to design around — that is what a fictional redesign can never supply.
- 5
Build a portfolio of three case studies structured as arguments
~1-2 monthsEach one should state the problem, the constraint, the options you rejected and why, the final design, and what happened after it shipped. Cut the personas and the double-diamond diagram; hiring managers read them as filler.
- 6
Practise the whiteboard and portfolio-review interview
~1 monthYou will be asked to design something live and to walk through one case study in depth while people question your choices. Both are performance formats and rehearsing them out loud with a critical listener changes outcomes substantially.
Skills that matter
Learn the actual skills
Tell Mochivia your goal and it builds your personal curriculum — 15 minutes a day.
Build My Path