User experience design is one of the most visible professional fields to emerge from the digital product boom of the past two decades, yet it remains persistently misunderstood — both by people outside it and, sometimes, by organisations that employ UX designers without fully understanding what they are buying. The popular image of the UX designer as someone who makes apps look attractive confuses the work with its outputs. A UX designer's primary job is not to produce aesthetically pleasing interfaces but to ensure that a product works in a way that matches how real users think, what they need, and how they behave. The visual layer is the last step of a process that begins long before anyone opens Figma.
The field has grown substantially. According to the Bureau of Labor Statistics, employment of web designers and digital designers — a category that includes UX designers — was projected to grow 16% from 2022 to 2032, significantly faster than the average for all occupations. This growth reflects the expansion of digital products into every industry: healthcare, finance, government services, education, retail, and manufacturing all now compete in part on the quality of their digital experiences, and all need people who understand how to design those experiences for human beings rather than for the engineers who build them.
This guide explains what UX designers actually do across the full project lifecycle — from initial user research through wireframing, prototyping, and testing — along with the tools of the trade, salary ranges at different career levels, portfolio guidance, and an honest account of how UX relates to the adjacent titles of UI designer and product designer.
"Design is not just what it looks like and feels like. Design is how it works." — Steve Jobs, in a 2003 interview with the New York Times
Key Definitions
User experience (UX): The overall quality of a person's interaction with a product or system, encompassing usability, accessibility, efficiency, and satisfaction. UX design is the practice of shaping that experience intentionally.
Wireframe: A low-fidelity visual representation of a screen or interface, showing layout and structure without visual styling. Wireframes communicate what goes where without committing to how it looks.
Prototype: An interactive simulation of a design, used to test user flows before engineering builds the actual product. Prototypes range from paper sketches to high-fidelity clickable interfaces in Figma.
Usability testing: A research method in which real users attempt to complete tasks with a product or prototype while the researcher observes and records where they succeed, struggle, or fail. Results directly inform design improvements.
Design system: A shared library of reusable components, patterns, and guidelines that ensures visual and interaction consistency across a product. Maintaining or contributing to a design system is a significant part of mid-to-senior UX and product design work.
What a UX Designer Does: The Full Process
Unlike roles defined by a single repeating task — an accountant reconciling accounts, an engineer writing code — UX design work varies substantially across the project lifecycle. Understanding that lifecycle illuminates what the job actually involves.
Discovery and User Research
Every serious UX project begins with research. Before designing anything, the UX designer needs to understand who the users are, what tasks they are trying to accomplish, what problems they currently encounter, and what mental models they bring to the interaction. This research phase involves several methods.
User interviews are structured conversations with people who represent the target audience. A UX designer conducting interviews is not asking "what features do you want?" — a question that reliably produces a list of feature requests disconnected from actual behaviour. Instead, they ask about context: "walk me through the last time you had to do X," "what felt frustrating about that experience," "what did you try before settling on this approach." The goal is to understand the underlying need, not the surface request.
Observational research (contextual inquiry) involves watching users in their actual environment — at their desk, on their phone during a commute, in the physical setting where the product gets used. What people say they do and what they actually do differ significantly, and observation captures the gap.
Competitive analysis examines how similar products have approached the same design problems, identifying patterns that users may already expect and gaps that represent design opportunities.
Analytics review — examining quantitative data on how users currently behave in an existing product — grounds the qualitative research in actual usage patterns.
Synthesis and Problem Definition
Research produces raw material: notes, recordings, patterns, anomalies. The synthesis phase converts this into design inputs. This means identifying the key insights, grouping related findings, and articulating the specific problems the design needs to solve.
This work often produces artefacts like journey maps (visualising a user's experience across multiple touchpoints), affinity diagrams (clustering related findings), and problem statements or "how might we" questions that frame the design challenge.
Wireframing
With a clear problem definition, the designer begins exploring solutions structurally — before any visual styling. Wireframes are intentionally rough, using grey boxes and placeholder text to focus attention on layout, hierarchy, and flow rather than colour or typography. This roughness is deliberate: it signals to stakeholders that this is an exploration, not a finished design, which makes feedback more honest and productive.
Wireframes are typically created in Figma, though some designers use Balsamiq for particularly low-fidelity work or start with sketches on paper. The key is communicating structure and logic quickly enough to iterate without sinking time into visual polish that may need to be discarded.
Prototyping and Interaction Design
Once the structure is agreed on, the designer builds interactive prototypes — versions of the design that can be clicked or tapped to simulate the user experience. High-fidelity prototypes in Figma use actual visual design (colours, typography, components from the design system) and interaction animations that approximate the finished product.
Prototyping is valuable because it surfaces problems that static wireframes do not: confusion about what is interactive, unexpected flows, errors in multi-step processes. A prototype can be tested with users before any engineering resources are committed, dramatically reducing the cost of discovering design problems.
Usability Testing
UX designers conduct moderated or unmoderated usability tests to evaluate whether their designs work for actual users. In a moderated test, the designer (or a researcher) observes a participant attempt specific tasks with the prototype, noting where they succeed, where they hesitate, and where they fail. The researcher does not guide or assist — observing natural behaviour is the point.
Tools like Maze or UserTesting automate unmoderated testing at scale, allowing many users to attempt tasks and recording where they succeed or drop off. This provides quantitative data on top of qualitative observation.
Testing results feed directly back into design iteration. The cycle of design-test-refine is the core loop of UX work.
Handoff to Engineering
Once a design is tested and approved, the designer prepares engineering handoff documentation — detailed specifications in Figma (using Dev Mode or equivalent) that specify component dimensions, spacing, typography, colours, interaction states, and responsive behaviour across screen sizes. The quality of handoff documentation significantly affects how accurately engineers implement the design and how many clarification conversations are needed during development.
Senior UX designers stay involved through the engineering build phase, reviewing implementations against the design intent and flagging discrepancies before they reach production.
Tools of the Trade
Figma is the industry-standard tool for wireframing, prototyping, and design system management. It is collaborative and browser-based, meaning multiple team members can work on the same file simultaneously. Figma's acquisition by Adobe (later blocked by regulators) underlined its dominance — most UX jobs now list Figma proficiency as a requirement.
Maze enables automated usability testing of Figma prototypes, collecting task completion rates, time-on-task, and heatmaps from large numbers of remote participants without requiring a researcher to be present.
UserTesting provides access to a panel of test participants and records their interactions with prototypes or live products, including screen, voice, and face recording.
Miro and FigJam are whiteboard tools used for collaborative workshops, journey mapping, and affinity diagramming — particularly useful for distributed teams.
Optimal Workshop specialises in information architecture testing tools: card sorting, tree testing, and first-click analysis to evaluate navigation structures.
Salary Ranges by Level
United States (Glassdoor, LinkedIn Salary, levels.fyi, 2024)
| Level | Annual Compensation (USD) |
|---|---|
| Entry-level UX Designer | $65,000 - $90,000 |
| Mid-level UX Designer | $90,000 - $130,000 |
| Senior UX Designer | $130,000 - $175,000 |
| Lead / Staff UX Designer | $170,000 - $230,000 |
| UX Manager / Director | $180,000 - $280,000+ |
At large technology companies, total compensation including equity can exceed these base figures significantly at senior levels.
United Kingdom: Entry-level GBP 28,000-42,000. Senior UX designers in London earn GBP 70,000-95,000.
Germany: Mid-level EUR 55,000-75,000. Senior roles EUR 75,000-100,000 at larger tech companies.
Freelance rates vary significantly: $50-100 per hour for early-career work, $120-200+ per hour for specialists with strong portfolios and proven client outcomes.
Portfolio Tips for UX Designers
A UX portfolio is the primary evaluation tool for hiring managers, and the most common mistake is confusing it with a gallery of polished visuals. What evaluators want to see is problem-solving thinking: What was the user problem? What research informed the approach? What did you test and iterate on? What was the outcome?
Show the process, not just the output. A portfolio case study that includes only final screen designs tells a hiring manager very little. One that walks through the research, the wireframe alternatives considered, the usability test findings, and the resulting iterations demonstrates the thinking behind the visual — which is what the job actually requires.
Quantify outcomes where possible. "Redesigned onboarding flow, reducing drop-off rate by 23%" is dramatically more compelling than "redesigned onboarding flow." Even estimated or directional data is better than no data.
Three strong case studies beat ten thin ones. Depth demonstrates rigour; breadth alone demonstrates exposure.
Do not wait for employer projects. Side projects — redesigning an existing app you find frustrating, contributing to open-source civic technology, volunteering UX support for a nonprofit — are legitimate portfolio material when framed with a clear problem statement and methodology.
UX Designer vs UI Designer vs Product Designer
These three titles are used inconsistently across the industry, which creates confusion for practitioners and hiring managers alike.
UX designer emphasises the research, strategy, and problem-definition end of the work. UX roles in large companies may be almost entirely research-focused, with dedicated visual designers handling the interface layer.
UI designer (user interface designer) focuses on the visual and interactive layer — the specific visual design of components, the colour system, typography, iconography, and micro-interactions. At smaller companies, this is often the same person as the UX designer; at larger companies, it may be a separate specialisation.
Product designer is the most common title in technology companies for someone doing the full scope of work — research, wireframing, visual design, and prototyping. The "product designer" title reflects the expectation that this person is a full partner in the product development process, not a specialist brought in only for visual work.
In practice, most working designers at technology companies operate as product designers regardless of title, with the UX/UI distinction being more meaningful in industries where large design teams have enough scale to specialise.
How to Start a UX Career
Bootcamps and self-study: Numerous reputable bootcamps (General Assembly, Springboard, CareerFoundry, Google's UX Design Certificate on Coursera) provide structured curricula and portfolio projects. The certificate matters less than the portfolio you build through the programme.
Degree programmes: Degrees in interaction design, human-computer interaction (HCI), graphic design, psychology, or computer science provide relevant foundations. HCI programmes at Carnegie Mellon, Georgia Tech, and UCL are particularly well-regarded. A degree is not required to work in UX but provides stronger foundations for research-heavy roles.
Transition from adjacent roles: Graphic designers, front-end developers, and product managers frequently transition into UX. The jump is more natural than it seems — the skills are adjacent and companies value the cross-domain perspective.
Practical Takeaways
The most impactful thing a UX designer can do is establish and maintain a direct relationship with real users throughout a project. Designs that skip research or substitute assumed knowledge for actual user observation reliably produce products that engineers build correctly but users do not want. The research disciplines of the role — interviewing, observing, testing — are what prevent expensive mistakes during engineering.
If you are building a portfolio to enter the field, resist the temptation to make everything look polished. A case study showing a messy, real discovery process is more credible to experienced hiring managers than a case study with nothing but high-fidelity screens and no visible thinking.
References
- Norman, D. "The Design of Everyday Things." Basic Books, revised edition, 2013.
- Bureau of Labor Statistics. "Occupational Outlook Handbook: Web and Digital Interface Designers." BLS.gov, 2023-24 edition.
- Krug, S. "Don't Make Me Think, Revisited." New Riders, 3rd edition, 2014.
- Gothelf, J., & Seiden, J. "Lean UX." O'Reilly Media, 3rd edition, 2021.
- Figma. "State of Design Report." Figma, Inc., 2023.
- Nielsen, J., & Landauer, T. K. "A Mathematical Model of the Finding of Usability Problems." Proceedings of ACM CHI, 1993.
- Portigal, S. "Interviewing Users." Rosenfeld Media, 2nd edition, 2023.
- Glassdoor. "UX Designer Salary Data." Glassdoor.com, 2024.
- LinkedIn Economic Graph. "Fastest Growing Design Jobs." LinkedIn, 2023.
- Buxton, B. "Sketching User Experiences." Morgan Kaufmann, 2007.
- Rubin, J., & Chisnell, D. "Handbook of Usability Testing." Wiley, 2nd edition, 2008.
- Pernice, K. "UX Leadership: Creating High-Performing Teams in the Digital Age." Nielsen Norman Group, 2022.
Frequently Asked Questions
What does a UX designer do on a typical day?
A UX designer's day typically involves user research, creating wireframes, running usability tests, iterating on prototypes in Figma, and collaborating with product managers and engineers. The specific balance of research versus design output depends on the company's size and the designer's seniority.
What is the difference between UX design and UI design?
UX (user experience) design focuses on the overall structure, flow, and usability of a product — how it works. UI (user interface) design focuses on the visual details — colour, typography, and component aesthetics — that make the product look a certain way. Many designers do both, and the roles often overlap at smaller companies.
What tools do UX designers use?
Figma is the dominant tool for wireframing, prototyping, and design systems. Research tools include Maze, UserTesting, Lookback, and Optimal Workshop. Teams also use Miro or FigJam for collaborative workshops. Older workflows sometimes still involve Sketch or Adobe XD.
How much does a UX designer earn?
Entry-level UX designers in the US earn \(65,000-\)90,000. Mid-level designers earn \(90,000-\)130,000. Senior designers at large tech companies can earn \(150,000-\)200,000+ in total compensation. Freelance rates vary widely, from \(50 to \)200+ per hour depending on specialisation and client type.
Do you need a design degree to become a UX designer?
No. Many working UX designers entered the field through bootcamps, self-study, or transitions from adjacent fields like graphic design, psychology, or software engineering. What matters most to employers is a strong portfolio demonstrating research thinking and problem-solving, not the credential behind it.