A UX designer decides how a product works: the flows, the structure, what happens at each step and whether people can complete their task. A UI designer decides how it looks and feels on screen: layout, type, colour, components and states. In small teams one person usually does both, and that combined role is often called a product designer.
Hire UX first when people struggle to use the product. Hire UI first when the product works but looks inconsistent or untrustworthy. Most startups need one person who can do both.
| UX designer | UI designer | |
|---|---|---|
| Focus | How it works | How it looks and feels |
| Questions | What does the user need next? | Is this clear, consistent and on brand? |
| Deliverables | Research, flows, wireframes, prototypes | Mockups, components, design system, states |
| Tested with | Usability tests, analytics | Visual review, accessibility checks |
| Typical tools | Figma, research and analytics tools | Figma, design system libraries |
| Common mistake | Great flows, weak visual trust | Beautiful screens, broken flows |
| Hand-off | Flows and prototypes | Specs, tokens and components |
| In small teams | Usually the same person | Usually the same person |
At Accern, a no-code NLP platform for finance, 95% of users never used the product themselves; the customer success team built use cases for them. Jargon like taxonomy, NLP and data store confused people. Fixing that was UX work: research through the customer success team, personas, flows and plain language. Retention went up 200% and support tasks dropped 82%.
Nielsen Norman Group's definition is a good anchor: user experience covers every aspect of the user's interaction with the company, its services and its products.
UI is where trust is earned at a glance. Consistent components, clear hierarchy, readable data, sensible empty states. At ViewStats one design system covered web, mobile, marketing and a Chrome extension, with tokens, tables, data viz and forms. Without that, every new feature would have looked like a different product.
Look at the evidence in a portfolio. A strong UX candidate shows the problem, the research, the flows they tried and what changed after launch. A strong UI candidate shows a consistent system: components, states, spacing, data display and how it scales across screens.
Ask them to walk through one decision. A UX designer should explain why the flow changed; a UI designer should explain why a component looks and behaves the way it does. A product designer should be able to do both in one story.
Be careful with job titles. Many companies use UI/UX designer, product designer and UX designer interchangeably. Read what the person actually owned in each project.
I do both, which is normal for a product designer. My product designer vs UX designer post covers where ownership changes, and my onboarding UX case shows UX and UI working together on one problem.
If you can only hire one person, hire someone who can show both a flow they fixed and a system they built.
Neither is better; they solve different problems. UX makes the product usable, UI makes it clear and trustworthy. Good products need both.
Yes. In startups and small teams it is the norm, and that role is often called a product designer.
They are hard in different ways. UX is harder to measure and argue for; UI is harder to make consistent at scale.
No, but understanding how components are built helps a lot, and more designers now ship code with AI tools.
UX makes the product work; UI makes it clear and trustworthy. Small teams need one person who can do both well, and larger teams benefit from specialists in each.
Need a product designer or design engineer for your product? I work remotely with teams worldwide, from research to shipped code.