Is a product designer the same as a UX designer?

Not exactly. A product designer covers most of what a UX designer does - research, flows, wireframes, prototypes - but also takes on business strategy, metrics, and visual/UI design. In many companies the two titles are used interchangeably, but at larger tech firms product designers tend to have a broader, more commercially oriented remit than UX designers.

Which pays more - UX, UI, or product design?

Product designers generally command the highest salaries, largely because the role carries more end-to-end ownership and business accountability. Senior UX designers at specialist or large-company roles are competitive. Dedicated UI design roles tend to sit slightly lower, though UI skills combined with UX or product work can be very well compensated. Differences are most pronounced at mid-to-large tech companies.

Should I learn UX or UI design first?

For most career-changers, starting with UX is the better foundation. UX teaches you how to think about users and structure a product before styling it. UI skills build naturally on top of that. If you already have a graphic design background, the reverse path - strengthening your UX and research skills - can also work well.

Can one person do all three?

Yes, and many practitioners do - especially at smaller companies and startups where a single designer covers research, interaction design, and visual design end-to-end. At larger organisations these disciplines are more likely to be split across specialist roles. The term 'full-stack designer' is sometimes used for people who span all three fluently.

Do you need a PhD to work in UX research?

Not to be a UX designer who also does research - that combination doesn't require a PhD, because the research is applied to an existing or planned product rather than open-ended discovery. Large research-led organisations such as Google, however, often look for UX researchers with a PhD specifically for narrow, deep research roles investigating genuinely new territory, not incremental improvements to a known product. If your interest is applying research to ship and improve real products, a PhD isn't the requirement; if your interest is research as its own discipline at that level, it increasingly is.

Should I aim to be a UX designer, a UI designer, or a product designer?

It depends on what you enjoy and where you want to work. If you like understanding people and defining problems more than visual craft, UX or UX research suits you. If you enjoy the visual system - colour, type, layout - UI is closer to your strengths. If you want to be the person connecting user needs to business outcomes across the whole project, product design is the closer fit. Many people end up doing all three at different points in their career, and switching between them is normal, not a sign of indecision.

UX Designer vs Product Designer vs UI Designer

UX designer vs product designer is one of the most common points of confusion for anyone entering the design field - and the difference matters when you're choosing a career path or reading job ads.

If you're researching a design career, you have almost certainly seen all three titles - UX designer, product designer, UI designer - used interchangeably, occasionally in the same job ad. These are related roles that share tools and overlap significantly, but they have distinct focuses, day-to-day responsibilities, and career trajectories. This post compares the roles themselves. For a deeper look at the underlying disciplines, see our companion post on product design vs UX design.

UX designer vs product designer vs UI designer: the role definitions

To compare the roles clearly, it helps to start with what each one actually involves day-to-day.

What does a UX designer do?

UX stands for user experience. A UX designer's job is to make products useful, usable, and satisfying for the people who use them. The focus is on the complete journey a person takes to achieve a goal - not just a single screen, but every step, decision point, and potential point of friction along the way.

A UX designer's work typically includes:

User research - interviews, surveys, usability tests, and field studies that surface what people actually need and where they struggle. Our guide to UX research methods covers the main approaches and when to use them.
Information architecture - how content and features are organised, labelled, and navigated.
User flows and journey maps - mapping the steps a person takes from entry point to goal completion.
Wireframing - low-fidelity structural layouts that focus on hierarchy and logic, not aesthetics.
Prototyping and testing - building rough interactive versions to validate ideas with real users before committing to build.

The north star for UX design is whether the product genuinely works for its users. A UX designer might spend weeks on a problem before a single visual decision is made. The discipline draws from psychology, cognitive science, and research methods as much as from design. See our deeper guide to what a UX designer actually does for a fuller picture.

What does a UI designer do?

UI stands for user interface. UI design is the craft of the visual and interactive surface - everything a user sees and directly touches. Where UX defines the structure and logic of an experience, UI defines its look, feel, and moment-to-moment interactivity.

A UI designer's work typically includes:

Visual design - colour, typography, spacing, layout, and visual hierarchy.
Interactive elements - buttons, form fields, toggles, menus, and their various states (default, hover, active, disabled, error).
Design systems and component libraries - reusable visual components and style rules that keep a product consistent at scale.
Microinteractions - the small animations and transitions that make an interface feel responsive and alive.
Accessibility - ensuring contrast ratios, font sizes, and interaction patterns work for users with a range of abilities.

A useful shorthand: UX decides what goes on the screen and why; UI decides exactly how it looks and responds. A beautifully styled interface built on a confusing flow is a UX failure. A logically sound flow rendered with broken visuals and poor contrast is a UI failure. Good products get both right.

For a deeper comparison of these two disciplines, our post on UX vs UI design covers the distinction in full.

What does a product designer do?

Product design is a broader remit that encompasses much of what UX and UI design involve, but extends further into business strategy, product thinking, and measurable outcomes.

A product designer still conducts research, maps flows, builds wireframes and prototypes, and owns the visual design of what ships. But they're also expected to:

Engage with product strategy - contributing to decisions about what to build and why, not just how to design what has been scoped.
Work with business metrics - understanding how a feature affects retention, conversion, engagement, or revenue, and letting that inform design decisions.
Collaborate cross-functionally - working closely with product managers, engineers, and data analysts from early problem-framing through to post-launch measurement.
Own end-to-end feature delivery - from initial problem definition through to shipped output and evaluation of whether it worked.

Where a UX designer might ask "is this flow usable?", a product designer is simultaneously asking "does this feature move the metric we care about?" and "are we solving the right problem at the right time?". The role carries more commercial accountability, which is part of why it tends to come with higher seniority and pay.

Our post on product design vs UX design goes deeper on how the two roles relate and where the lines blur in practice.

How the three roles overlap

The honest answer is: considerably. All three disciplines often use the same tools (Figma is the industry standard across all three), all three involve understanding users, and all three contribute to the same end goal of a working product. The overlaps are real, not cosmetic.

In practice, many practitioners do all three - especially at startups and smaller companies where a single designer covers research, interaction design, and visual polish end-to-end. At larger organisations, the roles are more likely to be split across specialists: a UX researcher, an interaction designer, a visual/UI designer, and a product designer who coordinates between them.

How job titles vary by company

This is where things get genuinely confusing, because the same job can carry different titles depending on the company, its size, and its design maturity.

A few patterns that hold broadly:

Large tech companies (think companies with hundreds of designers) tend to use both titles and mean different things by them. "Product designer" usually implies a more senior, commercially embedded role. "UX designer" may refer to a more specialist, research-heavy or interaction-design-heavy role. UX researchers, content designers, and interaction designers often sit alongside both as separate disciplines.
Mid-size product companies and scale-ups often use "product designer" as the default title for anyone doing design work. "UX designer" titles are less common here, even when the actual work is similar.
Agencies and consultancies are more likely to use "UX designer" and to value deep specialisation in research, strategy, and information architecture.
Startups routinely use all three titles to describe broadly the same generalist design role. Read the job description, not just the title.

The practical implication: don't choose a career path based on a title. Look at the actual responsibilities in job ads for roles that interest you, and develop the skills that appear consistently.

UX research: the one role that can want a PhD

This is the distinction most "UX vs UI" explainers miss, and it's the most useful part of Natalia's answer.

"In UX, it's just UX, and UX can be UX research if you're interested just in research, and that's fine. And quite often, you have, for example, who has a PhD degree, they're researchers. It's their knowledge, and they can be researchers, and they focus on that. And if we speak about Google, or something like Google, they're looking UX researchers and they're looking somebody with PhD level because it's a very narrow field."

Why the difference? It comes down to what kind of research you're doing.

"A UX designer, it's a UX research plus design and it's not required PhD level because you're doing research not about like a future and you don't try to like a big, like a huge innovation like a Google tried to do. You're more focusing on the product, what exists. You're focusing on the target group. You're focusing on what we can do better or what we can improve."

So: if you're a UX designer applying research to a real, existing (or planned) product - talking to your actual users, testing what you have, improving what's already there - you don't need a PhD. That's the large majority of UX research jobs. A PhD becomes relevant specifically for a narrow category of deep, open-ended research roles at organisations pushing into genuinely new territory, where the research itself is the innovation, not a support function for a shipping product.

If you've been putting off a career change into UX because you assumed "UX research" meant "I'd need a doctorate," that assumption is usually wrong. It's only true for one specific, narrow slice of the field.

Comparison at a glance

	UX Design	UI Design	Product Design
Core focus	Usability, user journeys, research	Visual and interactive surface	End-to-end product quality + business impact
Key outputs	Research findings, wireframes, prototypes, flows	Visual designs, components, design systems	Feature designs, strategy input, metrics-informed decisions
Primary collaborators	Researchers, content designers, engineers	UX designers, brand teams, engineers	PMs, engineers, data analysts, leadership
Typical tools	Figma, Maze, Dovetail, Miro	Figma, design system tools	Figma, analytics platforms, roadmap tools
Scope	User-centred	Interface-centred	User + business
Common in	Agencies, large companies	Studios, large product teams	Startups, scale-ups, large tech

Salary and career path

All three paths lead to well-compensated careers, with product design typically commanding the highest salaries at senior levels, reflecting the broader scope and business accountability of the role. Dedicated UI design roles tend to sit slightly lower on average, though this varies considerably by sector and company size. For verified salary figures across all three roles, see our guide to UX designer salaries in the UK.

Across all three, there's a consistent pattern: specialists who can demonstrate impact on real products - with portfolio evidence - progress faster than generalists with theoretical knowledge. The ability to conduct and interpret user research is increasingly valued across all three roles, not just in UX.

Career progression in all three disciplines typically follows a path from junior/mid designer, to senior designer, to lead or principal designer, with some practitioners moving into design management and others deepening their craft specialism. Product design tends to open the most direct routes toward principal IC roles at tech companies and toward design leadership.

Which should you pursue?

The right answer depends on what draws you to design work.

Pursue UX design if you're most energised by understanding people - what they need, why they behave as they do, where they struggle - and you want to solve those problems through structure and logic before anything is styled. The UX design process gives you a practical framework for that kind of structured, evidence-based work. UX is the strongest foundation for most career-changers and gives you transferable skills regardless of which direction you specialise later.

Pursue UI design if you have a strong visual instinct and are drawn to the craft of how things look and feel at the interface level. A background in graphic design, illustration, or visual communication translates well here. UI as a sole specialism is more often found at larger companies and studios.

Aim for product design if you want the broadest remit, are comfortable with ambiguity, and are interested in how design intersects with business strategy and metrics. This is often where experienced UX or UI designers land after a few years, rather than an entry-level starting point.

For most people entering the field from a non-design background, starting with UX is the clearest path. It teaches you how to think about users, structure products, and justify decisions with evidence - all skills that carry into UI and product design naturally as your experience grows. Our step-by-step guide to how to become a UX designer walks through the practical route from career-changer to first role.

If you're ready to build those foundations properly, UX Academy (myuxacademy.com) runs live online UX courses in the UK, taught by working practitioners. Cohorts start on 14 October 2026 and 12 January 2027. You can explore the Beginner UX (AI) Design course or book a free 15-minute call with an advisor to get a feel for how we teach before committing.