The Core Problem
"UX Designer", "Product Designer", "UX Researcher" — anyone working in UX knows the confusion. Job ads mix these titles freely, often describing nearly identical roles. This article unpacks the most common titles and what they actually mean in practice.
UX Designer
The classic title. A UX designer typically owns the full user experience process: research, information architecture, interaction design, and often visual design. In enterprise contexts, this role tends to be broad — a generalist who can cover multiple phases of a project.
Product Designer
Increasingly common in tech companies, especially those influenced by Silicon Valley culture. A product designer typically works more closely with product management and engineering, often with a stronger emphasis on visual and interaction design than on research. The term implies strategic ownership of a product area.
UX Researcher
A specialist role focused exclusively on research: user interviews, usability testing, contextual inquiry, survey design, and data analysis. In smaller organisations, research is often combined with design; in larger ones, dedicated researchers are increasingly common.
UX Strategist
A senior role that bridges UX and business strategy. The UX strategist connects user needs, business goals, and technical constraints — often working at the organisational level rather than on individual features.
What Actually Matters
Job titles matter less than skills, methods, and mindset. The key questions to ask about any UX role:
- Does the role have access to users for research?
- Is there an expectation of both research and design output?
- How close is the collaboration with product management?
- What does "done" look like — research report, wireframe, or shipped feature?
"Don't hire a job title. Hire a skill set and a mindset."
At UBCG, we always start by mapping the real expectations behind a title before advising clients on team structures or evaluating candidates. The label is the beginning of the conversation, not the end.
