I want to help you pick one. More than 8% of the people who apply to MentorCruise are evaluating design roles. The question I hear from almost all of them isn't "what's the difference between UX and UI?" They already know. The question is which one they should actually apply for.
I've watched hundreds of career transitions through MentorCruise. The successful ones follow a pattern: they start with internal clarity (what do I actually want?), move to skill mapping (what gaps exist?), and only then go external - networking, applications, job boards. Most people start with step three and wonder why they're stuck. This article covers steps one and two for the UX vs UI decision.
TL;DR
- UX hires on research process and synthesis documentation. UI hires on visual execution and component systems. These are almost completely different hiring bars - building toward the wrong one wastes months.
- UX designer salary ranges in the US generally run from around $85,000 to $130,000. UI designer salary ranges run from around $65,000 to $110,000. The gap reflects hiring difficulty, not discipline prestige.
- Wrong-fit signal for UX: if conducting research, documenting your reasoning, and synthesizing findings sounds like punishment, it will show up immediately in portfolio reviews.
- Wrong-fit signal for UI: if visual choices feel arbitrary and you can't explain why one layout is cleaner than another, a Figma tutorial won't fix that gap.
- Most career changers lose months pursuing both tracks simultaneously. Committing to one is faster - and a mentor who has hired for both roles can tell you in one session which bar your background is closer to clearing.
Is UX or UI design right for you?
It's not a pros-and-cons comparison. The question isn't which discipline is more interesting in the abstract - it's which hiring bar you can reach faster, given your current background and how you naturally work.
Two filters determine the answer. First: process versus visual. Do you naturally think in user flows, research questions, and reasoning chains - or in layouts, visual systems, and how things look at every state and breakpoint? Second: what's actually available in your job market? Design roles represent more than 8% of the people who come to MentorCruise, and the decision fork we see most often isn't ideological. One applicant put it directly: they were based in a market where UX research roles were very limited, so they were considering UX design instead. That's not settling. That's pragmatic path selection - picking the track with more openings in your region.
The comparison most articles bury in prose is worth putting in a table:
| Dimension | UX design | UI design |
|---|---|---|
| Portfolio focus | End-to-end research process and case studies | Visual execution and component systems |
| Top hiring criterion (2026) | Research process documentation | Polished visual execution |
| Interview format | Portfolio walk-through and research critique | Portfolio walk-through and design exercise |
| Primary tools | Figma, Maze, Dovetail, Miro, Otter | Figma, design tokens, component libraries |
| US salary range | \~$85K-$130K | \~$65K-$110K |
One negative-fit signal I want to name plainly, because it saves time: if you hate looking at data, conducting interviews, and documenting your reasoning, UX research work will feel like punishment - and it shows up immediately in portfolio reviews. UX hiring managers are not looking for people who can do research. They're looking for people who want to. That's a real filter, not a soft observation.
What UX and UI designers actually do
Both are design roles, but the work is more different than the titles suggest. UX is research-and-reasoning work that happens mostly in documents and conversation. UI is visual-and-systems work that happens mostly inside Figma. The job that sounds more like your default way of thinking is probably the right starting point.
What a UX designer does day-to-day
UX design is mostly research. You plan studies, recruit participants, conduct sessions, synthesize findings into artifacts like journey maps or affinity diagrams, and then translate all of that into design rationale your team can act on. The Figma file is the last thing you open, not the first.
On a given week, a mid-level UX designer might recruit participants, run moderated sessions, synthesize findings into a journey map, and present to the product team - all before the design tool opens. The output is documentation as much as design. A 2026 benchmarks report from CodeLabs Academy found that 54.5% of hiring managers cite research process as their top portfolio criterion for UX roles. Not the wireframes. The research.
US salary ranges for UX designers generally run from around $85,000 to $130,000 depending on seniority and location.
What a UI designer does day-to-day
UI design is mostly visual systems work. You build components, document variants, maintain design tokens, and make sure the product looks consistent across every state and breakpoint. It's closer to visual craft than research - and the Figma file is the thing you live in.
A UI designer's week might involve building a new component, documenting its states and tokens, reviewing a developer's implementation, and iterating based on engineering feedback. The same 2026 benchmarks report from CodeLabs Academy flags that UI portfolios are evaluated on polished execution and component systems - not just final screens.
UI designer salary ranges in the US generally run from around $65,000 to $110,000.
How to transition into UX or UI design
The transition path is different for each track - and the mistake I see most often is people treating them the same. The first thing a UX hire needs is a research case study. The first thing a UI hire needs is a component system. If you're building toward the wrong one, you'll know it by the time you're applying.
How to transition into UX design (from non-tech)
Don't start with Figma. Start with research. Find a project - volunteer, freelance, internal at your current company - where you can talk to real users, document your process, and build a case study around it. The design tool is the easy part; the case study structure is what UX hiring managers actually review.
The transition sequence that works:
- Learn the research skills before the design tools. User interviews, moderated sessions, affinity mapping, journey mapping - these are the outputs hiring managers look at first.
- Find a real project with real users, not a redesign exercise of an app you already use. The case study needs actual participants and actual findings.
- Document everything: the research plan, the participants (even anonymized), the synthesis artifacts, the design rationale. "I did user research" is not a portfolio.
- Build the case study around the process, not the output. The final screens matter less than the thinking that produced them.
Milestone checkpoint: your portfolio passes the first recruiter filter when it contains at least one end-to-end case study including a written research plan, synthesis artifacts (affinity diagram, journey map, or equivalent), and design rationale. Pass or fail test: a recruiter can follow your thinking from problem to solution without asking "but where is the research?"
A mentor who has reviewed UX portfolios from the hiring side can tell you in one session exactly what's missing. Dan Ford spent 15 years in tech recruiting before becoming a career coach. He's seen thousands of resumes and conducted hundreds of interviews, and his MentorCruise mentees get the insider perspective on what a research-documented case study actually looks like to a hiring manager.
If you're in the early stages, a UX research mentor can help you identify which research methods to document first.
If you've already decided UX is your path, our UX and Product Designer career guide goes deeper on the full transition roadmap.
How to transition into UI design (from non-tech)
UI hiring is about systems, not screens. Anyone can drag-and-drop in Figma. The portfolios that get callbacks contain component libraries with documented variants, design tokens, and a visible understanding of how design decisions translate to engineering constraints. That's what you're building toward - not a collection of app mockups.
The transition sequence that works:
- Visual design fundamentals first: color theory, typography, grid systems. These are the foundation that separates principled design decisions from arbitrary ones.
- Build Figma proficiency alongside a real project. Don't learn the tool in isolation - use it to build something with real constraints.
- Produce one component system as your portfolio anchor. Document the logic, not just the look. Why is this spacing value 8px? What happens to this button in its disabled state? How do the tokens cascade through the system?
- Seek engineering collaboration to understand implementation constraints. UI designers who understand how developers use component specs are more hireable than those who don't.
Milestone checkpoint: your portfolio passes the hiring bar when it contains at least one component system or design system contribution with documented token structure and variant states - not just isolated screens. Pass or fail test: a hiring manager can see how you think in systems, not just how you execute individual frames.
One more negative-fit signal worth naming: if you can't articulate why one layout feels cleaner than another - or if visual choices feel arbitrary rather than principled - a Figma tutorial won't fix that. UI hiring is partly about taste, and taste takes longer to develop than tool proficiency. That's not a reason not to pursue it; it's a reason to get mentor feedback on your visual instincts early, before spending months on the wrong projects.
A Figma mentor can review your component work and tell you whether it's at the level design teams actually use. A UI design mentor who has hired UI designers can give you the spec-quality bar before you apply.
Common roadblocks (and how to get past them)
The most expensive mistake I see is people building the wrong portfolio for the track they chose. Both waste months. Getting a mentor to review your portfolio direction before you invest in it is the fastest fix.
Three roadblocks come up consistently for non-tech career changers entering design.
-
Building the wrong portfolio for the track. I've seen both failure modes consistently in portfolio reviews - the UX applicant submits beautiful final screens without research documentation; the UI applicant submits research writeups without component systems. Both fail the first recruiter filter. The fix is to get someone who has hired for the specific role you're targeting to review your portfolio direction before you spend three months building it in the wrong direction.
-
Treating certifications as interchangeable. The Google UX Design Certificate (available on Coursera) is a UX qualification. It does not transfer to the UI hiring bar.
-
Underestimating geography and job-market supply. The right track depends partly on what's actually available in your market. Some regions have far more UI roles than UX research roles. A mentor who has hired in similar markets can advise on which track has more openings in your region - and that advice can change the entire direction of your portfolio work. This is not a minor consideration.
AI tools in design are useful accelerants for specific milestones - wireframe generation, component suggestions, pattern exploration. But they don't replace what actually determines hireability. For UX, that's research synthesis and documented reasoning. For UI, that's taste and system thinking. Both require human judgment at review moments - and that's where mentor feedback is sharpest.
Tools, mentors, and next steps
The tools are the easy part. Figma is the standard for both tracks. The research tools for UX - Maze for testing, Otter for transcription, Miro or FigJam for synthesis - can be learned alongside a real project. What takes longer to learn is what "good" looks like in the track you picked. That's what a mentor accelerates.
For UX designers, the core toolkit covers:
- Figma for wireframing and prototyping
- Maze for usability testing
- Otter.ai for session transcription
- Miro or FigJam for synthesis and affinity mapping
- Notion or Confluence for research documentation
For UI designers, the core toolkit covers:
- Figma as the primary design environment
- Style Dictionary or Tokens Studio for design tokens management
- Storybook for component documentation and handoff to engineering
If you're moving into UX or UI design, the highest-leverage thing you can do is get a mentor who has reviewed portfolios from the other side of the hiring table. The difference between a portfolio that gets you interviews and one that doesn't is usually one or two specific gaps - and it takes a few minutes with the right person to name them. Find a UX mentor. We have a 7-day free trial and a full money-back guarantee.
FAQs
Is UX or UI design harder to break into?
Both are competitive, but the barriers are different. UX hiring requires documented research work - a portfolio without end-to-end case studies won't clear the first filter. UI hiring requires polished visual execution and system thinking. Neither is "easier" overall, but if your background leans toward empathy and reasoning, UX is closer to your existing skill set. If it leans toward visual taste and tool proficiency, UI is closer.
How long does it take to get a first UX or UI job from scratch?
Most career changers take 12-18 months to get to a portfolio strong enough to interview for mid-market roles, assuming consistent part-time work. The outliers who move faster have usually done two things: committed to one track early, and gotten mentor feedback on their portfolio before applying rather than after the first round of rejections.
Do I need a degree to become a UX or UI designer?
No. Neither track has a degree requirement at most companies. What hiring managers look at is the portfolio - research process documentation for UX, visual execution and component systems for UI. A certificate from Google, Interaction Design Foundation, or a reputable bootcamp can help signal foundational knowledge, but the portfolio is the gate.
What's the difference between UX design and UX research?
UX design includes both research and design - you plan studies, synthesize findings, and produce wireframes or prototypes. UX research is a more specialized track focused entirely on the research and synthesis stages, usually at larger companies that can afford separate roles. For a career changer entering at the generalist level, "UX designer" is typically the right title to target.
Can I switch from UI design to UX design later?
Yes, and it's more common than the reverse. UI designers who want to move into UX typically need to add a documented research practice - one well-executed case study that shows research planning, participant recruitment, and synthesis alongside the visual work. The visual skill doesn't go to waste; UX teams value designers who can produce wireframes alongside their research.
Is it worth getting the Google UX Certificate?
It depends on what you already know - and here "it depends" actually has a useful answer. For someone with no design exposure, the Google UX Certificate provides a structured foundation and teaches the core research and design vocabulary. Hiring managers recognize it as a signal of intent and foundational knowledge, but it won't replace portfolio work. Treat it as the starting point, not the destination - and pair it with a mentor who can tell you when you're ready to apply.
