There’s a persistent idea in hiring that the ideal designer is a unicorn — someone who can do UX research, UI systems, product strategy, motion, and ship production code before lunch. It sounds efficient. It’s usually a trap.
UX, UI, and Product overlap, but they are not the same craft. Treating them as one role flattens the work and makes it harder to hire for what a team actually needs.
What “unicorn” usually means
In practice, “unicorn” is a wishlist disguised as a job title. Teams want research rigor, visual polish, and product judgment — often without the headcount to support each discipline. The result is vague expectations and diluted outcomes.
- UX focuses on flows, friction, and whether people can complete the job.
- UI focuses on hierarchy, craft, and how the product feels moment to moment.
- Product focuses on prioritization, tradeoffs, and what should exist at all.
Generalists are valuable. Unrealistic hybrids are not a hiring strategy.
Hire for the bottleneck
Early teams often need a strong generalist who can move across surfaces. Later teams need sharper specialists. The mistake is pretending one person can permanently replace three complementary skills at a high level.
If your product feels confusing, invest in UX. If it feels cheap, invest in UI. If you’re shipping the wrong things well, invest in Product. Clarity about the bottleneck beats a mythical job description every time.
A healthier bar
Look for people with a primary craft and adjacent fluency. Someone who can lead UI and speak product. Someone who can lead research and collaborate tightly with engineering. Overlap is healthy. Fantasy role definitions are not.
You don’t need a unicorn. You need the right mix of depth for the stage you’re in — and honest scope for the people you hire.