UX Designer vs UI Designer: What's the Difference and Which One Should You Hire?

★ Deliverables

What each role actually hands you

The clearest way to separate the two is to look at what lands in your shared drive at the end of a sprint. A UX designer gives you research notes and interview summaries, a map of the current experience with the drop-off points marked, user flows, information architecture (what lives where in the navigation), low fidelity wireframes, and often a usability test script plus the recordings and findings that came out of it. None of it is pretty. All of it is decisions: this step comes before that one, this field can be removed, this screen needs a confirmation state because people get confused there.

A UI designer gives you a type scale, a color system with contrast checked against accessibility standards, spacing rules, a component library in Figma with variants and states (default, hover, focus, disabled, loading, error, empty), high fidelity screens for every breakpoint you support, icon sets, motion and transition specs, and a handoff file that a front-end engineer can build from without guessing. Where UX says "the user needs to compare three plans here," UI says "here is the comparison table, at 1440px, 768px and 375px, with the recommended plan marked and the disabled state for a plan you already own."

★ Side by side

UX designer vs UI designer at a glance

For context on those numbers: the median US freelance rate for UI and UX work sits somewhere around $72 to $82 an hour, which is where most solid mid-level designers land. A combined product designer who genuinely does both well typically runs $95 to $150 an hour. That premium is usually cheaper than two specialists, because you stop paying for the handoff meetings between them. Our flat 10% project fee sits on top of whatever rate you agree, with no markup buried in the hourly.

★ The overlap

Where the two roles really blur

The neat split above holds at the extremes and falls apart in the middle. Interaction design is the contested zone: what happens when you tap the button, how errors are surfaced, whether a form saves as you type or on submit, how long a loading state waits before showing a skeleton. Some UX designers own all of that. Some UI designers own it because it lives in the component. Empty states are another one. Deciding that a new user sees an onboarding prompt rather than a blank table is a UX call, but writing the prompt and designing the illustration is UI work, and the two decisions are made in the same hour by the same person on most real projects.

Content and microcopy sit in the same grey area. So does accessibility: color contrast is clearly UI, keyboard focus order is clearly UX, and screen reader labelling belongs to whoever is paying attention. Titles vary by company too. A "product designer" usually does both. A "UX/UI designer" often means a UI designer who has read about research. A "UX researcher" does no visual design at all. Read the portfolio, not the title.

★ One hire or two

When a product designer who does both is the right hire

One person covering both is the right answer more often than the internet suggests. Hire a single product designer when you are pre-launch or early, when the whole design scope is under roughly 200 hours, when there is no existing design system to inherit, and when decisions need to move fast because you are still changing the product weekly. Splitting the work in that situation adds coordination cost to a project that does not have enough surface area to justify it. If you are scoping a first version, our guide on what it costs to build an MVP breaks down where design usually lands in the budget.

Split the roles when the problem is genuinely deep on one side. Serious research programmes (recruiting participants, running moderated sessions, synthesising across dozens of interviews) need a specialist, and so does a design system that four squads will build against for the next two years. Regulated products, complex data tools and anything with a real accessibility audit ahead of it also warrant two heads. The tell is simple: if either half of the work would fill a person full time for a month, hire two people.

★ Portfolio review

How to spot real UX work in a portfolio

Plenty of portfolios use UX vocabulary over what is really visual design. The case study opens with "we started with user research," shows one persona nobody could have got wrong, then jumps straight to eight gorgeous screens on a floating phone mockup. That is a UI portfolio wearing a UX jacket. Here is what genuine UX evidence looks like.

• A specific problem stated with a number attached, not "users found it confusing" but "62% dropped at step three of checkout."
• Options that were considered and rejected, with the reason. Real UX work leaves a trail of discarded directions.
• Ugly artefacts: whiteboard photos, sticky note clusters, raw flow diagrams, a spreadsheet of interview quotes.
• Constraints named out loud. Engineering said no to X, legal required Y, so the design went this way instead.
• A result that is not just "the client loved it," and honesty about what did not move.

The fastest live test is one question on a call: "walk me through something you designed that tested badly, and what you changed." A researcher answers immediately and in detail. Someone who has only ever polished screens tends to reach for a story about a difficult stakeholder instead. For a full process you can reuse on any role, see how to vet a freelancer properly, and if the job is brand and marketing assets rather than product, our notes on hiring a graphic designer cover a different set of signals.

★ Sequencing

How to sequence UX and UI on a real project

The order that works on most builds looks like this. Weeks one and two: UX discovery, stakeholder interviews, a look at whatever analytics and support tickets already exist, and an agreed problem statement. Weeks two to four: flows and wireframes, tested with five to eight people, revised twice. Around week four: UI takes the approved wireframes and builds the visual system, starting with the two or three screens that carry the most weight rather than all of them. Weeks five to seven: the rest of the screens, states and responsive layouts, with the UX designer still available to answer structural questions that surface during visual work. Then handoff to web developers or mobile app developers, with design available for build questions.

Two rules keep this from turning into a waterfall. Do not wait for every wireframe before starting visual work; get one full flow through UI early so you find the places the structure breaks under real content. And keep the UX designer on a few hours a week through the UI phase rather than ending their contract at handoff. That overlap is cheap and it prevents the most common failure, which is a visual designer quietly resolving a structural ambiguity in whatever way is easiest to draw.

Whichever order you choose, write the brief before you post the role. Ours on writing a freelance job brief has the structure, and how SuperGig works explains the 48 hour shortlist and milestone escrow that sit around it.

★ Getting it wrong

What happens when you hire the wrong one first

Hiring UI first is the expensive mistake, and it is the one most teams make because visual work feels like progress. You get a beautiful set of screens for a flow nobody validated. Engineering builds it. Three months later the funnel still leaks at the same step, and now fixing the structure means throwing away built code as well as design files. The rework typically costs more than the original design engagement did, because the visual system was built around a screen sequence that has to change.

Hiring UX first when you only needed UI is the cheaper mistake, but it still stings. You spend three weeks and $8,000 on research that confirms what your support inbox already told you, then discover the actual issue was that the pricing page looked like it was built in 2014. If your flows are stable and the complaint is credibility rather than confusion, start with visual work and skip discovery.

Either way, decide up front how you will know the redesign worked, and be specific: task completion rate, time to first successful action, drop-off at a named step. If conversion is the metric, it is worth separating the design change from the message, because a new layout and a new argument shipped together tell you nothing about which one moved the number. You can audit the copy, layout and calls to action on the page before and after, then compare against the design metrics to see which side of the work actually produced the lift.

When you are ready to bring someone in, hire a freelance UX designer for structure and research, or browse freelance designers across product, brand and visual work if you are still deciding which half you need.

★ FAQ

UX vs UI: quick answers