Topic 2 — UX vs. UI vs. Product Designer

Goal: Untangle the overlapping design titles you'll see in job ads.

Lesson 2.1 — The UX Designer: the architect

Two weeks into her new life as a designer, Tessa has a job board open and a knot in her stomach. "UX Designer." "UI Designer." "Product Designer." "Interaction Designer." She spent eight years styling retail floors and never once doubted what her job was called. Now the titles blur together and she can't tell which ones she's even allowed to apply for. That knot is the whole reason this topic exists.

Start with the one that surprises career-changers most, because it isn't about making things pretty at all.

A UX Designer owns the experience and structure of a product. They research who the user is, map how that person moves from "I want to book a trip" to "trip booked," decide what belongs on each screen and in what order, then test whether real people can get through it. Their daily worry is flow and logic — does this make sense, can someone finish the task, where do they get stuck — not the exact shade of blue on a button.

Think back to the house Tessa used to imagine for her retail clients. The UX designer is the architect, deciding how many rooms there are, where the kitchen sits relative to the dining room, whether you have to walk through a bedroom to reach the bathroom. Get the layout wrong and no amount of beautiful paint saves the house.

At Wanderwell, the 40-person travel-booking startup where Tessa just landed an apprenticeship, her mentor Marcus puts it plainly when she asks what UX even means.

"UX is everything the user feels before they notice a single color. If they got lost, that was me. If they got there, that was me too."

So when Tessa reads a posting heavy on words like research, user flows, wireframes, journey maps, usability testing, she's looking at the architect's side of the work — the experience, the bones, the logic of the thing.

Lesson 2.2 — The UI Designer: the interior designer

Here's where Tessa's eight years finally pay off.

A UI Designer owns the visual surface — the part you see and touch on screen. Color. Typography (the fonts and how they're sized and spaced). Spacing. Icons. Buttons. The UI designer takes the structure the UX work laid down and makes each screen attractive, consistent, and clear: the right blue, the readable headline, the button that obviously looks tappable, the spacing that lets the eye rest.

Back to the house. If UX is the architect, UI is the interior designer — choosing the materials, colors, and finishes so the place looks and feels wonderful. The architect made the room exist in the right place; the interior designer makes you want to be in it.

This clicked for Tessa instantly. Arranging a retail space — what catches the eye first, how color pulls a customer toward the back wall, how spacing keeps a display from feeling cramped — is UI work in a different medium. She already has the eye; what's new is the toolset, not the instinct.

A quick way to feel the line: imagine an app where you reach your balance in two taps, but every screen is a wall of grey text in a tiny font. The flow works — UX is solid — and the UI is failing you. Now imagine a gorgeous, lovingly styled app where you simply cannot find the "transfer money" button. Beautiful UI, broken UX. You need both, and they fail independently.

When a posting leans on visual design, design systems, typography, color, polish, pixel-perfect, you're reading the interior designer's side of the craft.

Lesson 2.3 — When one person does both: "UX/UI Designer" and "Product Designer"

So which one is Tessa? She keeps trying to pick a side, and Marcus keeps telling her to stop.

Here's the open secret. In theory UX and UI are two specialties. In practice, especially at smaller companies, one person does both — which is exactly why the combined title "UX/UI Designer" is so common. At a 40-person startup like Wanderwell there's no budget for an architect and a separate interior designer for every screen. Tessa is expected to research the flow, structure the screens, and make them beautiful. That's the most common, most accessible entry-level shape of the job, and it's why this course teaches both together.

Then there's the title quietly conquering the field: "Product Designer."

A Product Designer is largely that same combined UX-plus-UI role with a broader, more strategic flavor. Beyond researching users and styling screens, they weigh business goals and product strategy — asking not only "can the user do this?" but "should we even build this, and does it move the business?" They sit shoulder to shoulder with the product manager. At Wanderwell that's Priya, the PM who decides what gets built; a Product Designer is the person who pushes back with "users won't book faster this way, and here's the data" rather than just executing whatever lands in their lap.

Since roughly 2020, "Product Designer" has become the default design title at most modern tech companies, absorbing the old separate "UX Designer" and "UI Designer" labels into one end-to-end role. At plenty of places it means the same job as "UX/UI Designer"; at others it signals a touch more seniority and strategy. There's no fixed rule — the running theme of this whole topic.

Lesson 2.4 — The neighbors: roles to recognize, not fear

The job board runs well past UX, UI, and Product Designer. A handful of neighboring titles keep showing up, and Tessa needs to recognize each one well enough to know whether it's her job, an adjacent one, or someone else's entirely.

• UX Researcher — studies users full-time: interviews, surveys, usability studies, then hands the findings to the design team. At Wanderwell this is Hannah, who runs the larger studies and shares user interviews so the designers don't start from zero. But Hannah is a luxury of a company that's growing. UX Researcher is common only at larger companies; at smaller ones, designers do their own research — so Tessa should still learn it.
• Interaction Designer / Motion Designer — focuses on how things move and respond: the animation when a card flips, the way a button presses in, the transition between screens. A specialty within the experience side.
• Graphic Designer — works on brand and marketing: logos, ad campaigns, social posts, the brand out in the world. Skills overlap with UI, and it's one of the most common backgrounds people pivot from. But it is not product design — no flows, no screens you operate, no user tasks.
• Frontend Engineer — builds the design in code. At Wanderwell that's Dev, who turns Tessa's screens into a working app and flags when something she drew isn't feasible. The relationship is a handoff: designers hand their work to engineers, and designers don't code. Understanding basic constraints helps you design things Dev can actually build, but writing the code is his job.

Knowing the neighbors mostly spares Tessa from misreading a posting. A "Graphic Designer" role at a marketing agency is not the product-design job she's training for, however pretty the work looks; a "Frontend Engineer" posting wants someone who writes code, full stop. Recognizing each one keeps her from knocking on the wrong door.

Lesson 2.5 — Company size, and the one rule that saves you

So why are these titles such a mess? Same answer as almost everywhere in tech: company size.

At a large company, the roles split into specialists — a separate UX team, a separate visual team, dedicated researchers like Hannah, sometimes even content designers who only write the words on screen. You'd be hired to go deep on one slice.

At a startup like Wanderwell, one generalist — usually titled "Product Designer" or "UX/UI Designer" — covers the whole spectrum. Research, structure, visuals, prototype, hand off to Dev, repeat. Tessa is the architect and the interior designer and her own researcher, all before lunch.

The work stays roughly constant; the titles stretch and shrink to fit whatever the org needs them to mean. The same word — "Product Designer" — can describe a narrow specialist at one company and an everything-role at another. Knowing where a company sits tells you what the job will actually involve, which leads to the single habit that saves you in a job search:

Read the job description, never the title alone. The same word means different scopes at different employers.

A "UX Designer" ad that's all Figma, visual polish, design system, components is really a UI-leaning job wearing a UX label. A "Product Designer" ad heavy on roadmap, metrics, business outcomes wants the strategic end. Read a few ads this way and you stop applying blind and start saying, credibly, exactly where you fit.

And underneath all of it sits the reassuring part. The core craft is shared across every one of these titles: empathy for users plus visual skill. Learn UX and UI side by side, the way this course teaches them, and you're equipped for the most common and most accessible roles in the field, whatever the company decides to call them.

Worked example — One job board, four postings

Tessa sits down on a Sunday with four real postings open in four tabs. Marcus told her to decode each one before applying. Watch her do it.

Tab one — "UI Designer, mid-size fintech." All typography, color systems, component libraries, pixel-perfect screens. No research, no user flows. The interior-designer slice at a company big enough to split the roles. She could do it, but it's narrow — only the surface, never the structure. A maybe.

Tab two — "UX/UI Designer, 30-person startup." Interview users, map flows, wireframe, design high-fidelity screens, hand off to engineering. The generalist role: architect and interior designer in one person, doing her own research because there's no Hannah on staff. Dead center for her training. She stars it.

Tab three — "Product Designer, growth-stage travel app." The same do-it-all work as tab two, plus partnering with the PM on strategy, owning outcomes, influencing the roadmap. Same combined craft, broader and more strategic — the Priya-collaborator end. A stretch for a first job, but recognizable. She stars it and plans to lean on her business sense in the cover letter.

Tab four — "Graphic Designer, marketing team." Logos, ad creative, social campaigns, brand guidelines. Beautiful work, overlapping visual skills — and not product design. No flows, no screens you operate, no user tasks. She recognizes the neighbor and closes the tab.

Four postings. Four scopes hiding behind three or four overlapping words. Being able to look at any ad and name what it actually wants — and whether it's you — is exactly the skill this topic was built to give you.