UX Designer vs UI Designer vs Product Designer: What Each Actually Does (And What They Get Paid)

Published on BirJob.com · March 2026 · by Ismat

Three Listings, One Company, Zero Clarity

About a year ago, I was browsing job postings on a well-known fintech company's careers page — won't name them, but you'd recognize the logo — and I noticed something that made me stop scrolling. They had three open design roles posted on the same day. "UX Designer." "UI Designer." "Product Designer." I read all three descriptions carefully. I read them again. Then I opened them side by side in three browser tabs and did a line-by-line comparison.

The UX Designer posting mentioned "creating wireframes, conducting user research, and collaborating with engineering." The UI Designer posting mentioned "creating high-fidelity mockups, maintaining the design system, and collaborating with engineering." The Product Designer posting mentioned "conducting user research, creating wireframes and high-fidelity mockups, maintaining the design system, and collaborating with engineering." That last one was literally the first two combined, with the word "strategy" sprinkled in.

I sent screenshots to a designer friend in Baku. She laughed and said: "Welcome to the design industry's longest-running identity crisis." And she was right. The confusion between these three titles isn't a minor annoyance — it actively harms people's careers. I've talked to designers who spent two years building UX research skills only to realize the "UX Designer" role they were targeting actually wanted someone who could push pixels in Figma all day. I've seen UI designers get rejected from "Product Designer" roles because they couldn't articulate a product strategy, even though they'd been doing product-level work under a different title for years.

So let's actually untangle this. Not the theoretical, academic version — the real one. What each role does on a Tuesday afternoon, what tools they live in, what they get paid, and which one you should aim for depending on where you are right now.

The Numbers First

Before philosophy, let's talk money and market size. Design roles have exploded over the past decade, and the salary data tells an interesting story about how companies value each title differently — even when the work overlaps.

• Glassdoor reports the average UX Designer salary in the United States at approximately $108,000 per year, with a typical range of $82,000–$143,000 depending on location, experience, and company size.
• The combined "UI/UX Designer" title — which is its own category on most salary sites — averages around $86,000 according to Glassdoor. That's notably lower. The slash in "UI/UX" often signals a smaller company that wants one person to do both jobs, which ironically depresses the salary rather than increasing it.
• Product Designers command the highest average: $120,000–$135,000 per Glassdoor, with top-tier companies (Meta, Google, Airbnb) paying $160,000–$250,000+ in total compensation when you include stock and bonuses, per Levels.fyi.
• The U.S. Bureau of Labor Statistics groups many design roles under "Web Developers and Digital Designers," projecting 16% growth through 2032 — much faster than average. That's roughly 34,700 new positions.
• The Interaction Design Foundation notes that the global UX design market was valued at over $5 billion in 2023 and continues to grow as companies increasingly treat design as a competitive advantage rather than a cost center.
• In emerging markets like Azerbaijan, Turkey, and Eastern Europe, design salaries are naturally lower but rising. A UX designer in Baku might earn $800–$2,000/month, while the same role in Istanbul pays $1,500–$3,500/month. remote work for Western companies can multiply those numbers 3–5x.

The takeaway: the "Product Designer" title consistently pays more than "UX Designer," which pays more than "UI/UX Designer." Whether this reflects actual differences in skill or just title inflation is something we'll dig into.

What a UX Designer Actually Does on a Tuesday

Let's kill the abstract definitions and talk about what a UX designer's week actually looks like. I've talked to dozens of designers about this, and the reality is both more mundane and more interesting than the job descriptions suggest.

A UX designer's core work revolves around understanding users and translating that understanding into design decisions. The "experience" in "User Experience" is the operative word. Here's a realistic week:

Monday: Review analytics from last week's feature launch. Bounce rate on the new checkout flow is 12% higher than the old one. Write up hypotheses about why. Schedule three user interviews for Wednesday.

Tuesday: Morning standup with the product team. Spend two hours creating a user flow diagram for the next feature. Afternoon: build low-fidelity wireframes in Figma — boxes, lines, placeholder text. No colors, no polish. The point is structure, not aesthetics.

Wednesday: Conduct three 30-minute user interviews via Zoom. Watch real people try to use the prototype. Take notes on where they hesitate, where they click the wrong thing, where they say "I expected this to do something else." This is the heart of UX work, and it's the part most job descriptions underemphasize.

Thursday: Synthesize interview findings. Create an affinity map (sticky notes grouped by theme, physical or digital). Present findings to the product manager and engineering lead. Argue about scope.

Friday: Iterate on wireframes based on research findings. Hand off updated flows to the UI designer (if there is one) or start adding visual polish yourself (if there isn't).

The core toolkit includes user interviews, surveys, usability testing, journey mapping, persona development, wireframing, and information architecture. Notice what's not on that list: making things look pretty. A UX designer who spends most of their time picking colors and tweaking border-radius values is doing UI work, regardless of what their title says.

According to the UX Design Institute, the most critical skill for a UX designer is empathy — the ability to set aside your own assumptions and genuinely understand how someone else experiences a product. This sounds soft and fluffy. It is not. It's brutally hard, and most people are terrible at it. The designers who are genuinely good at user research are worth their weight in gold, because they prevent companies from building features nobody wants.

What a UI Designer Actually Does on a Tuesday

If UX is about structure and understanding, UI is about surface and precision. A UI designer makes things look right, feel right, and behave consistently.

Monday: Review the wireframes the UX designer handed off. Start translating low-fidelity boxes into high-fidelity screens. Choose typography, spacing, color palette. Ensure everything aligns with the existing design system.

Tuesday: Spend three hours refining the button states for a new component: default, hover, pressed, disabled, loading. Each state needs to look distinct but cohesive. Add the component to the design system library in Figma with proper auto-layout, variants, and naming conventions. This is meticulous work that requires an obsessive eye for detail.

Wednesday: Design the responsive versions. The desktop layout works, but what happens at tablet breakpoints? What happens when the screen is 375px wide? Where does the navigation go? How does the table reflow? Debate with engineering about whether a particular animation is feasible within the sprint timeline.

Thursday: Create a micro-interaction prototype — a button that expands into a form with a smooth transition. Export specs and assets for the development team. Write annotation notes: "This padding is 16px, not 12px. Yes, it matters."

Friday: QA the last sprint's implementation. Open the staging build, compare it pixel-by-pixel to the designs. File tickets: "The shadow is wrong. The font weight should be 500, not 600. The loading spinner is 2px too far to the left." Engineers love this. (They don't love this.)

The core toolkit: visual design, typography, color theory, design systems, component libraries, motion design, responsive design, accessibility standards (WCAG), and design-to-development handoff. A great UI designer understands CSS even if they never write it. They know what's easy to build and what will take a developer three days of headache.

The Interaction Design Foundation describes UI design as "the process designers use to build interfaces in software, focusing on looks and style." That's accurate but incomplete. Modern UI design is as much about systems thinking as aesthetics. Building and maintaining a design system with hundreds of components, tokens, and variants is an engineering discipline wearing a design hat.

What a Product Designer Actually Does on a Tuesday

Here's where it gets interesting. A Product Designer does UX work and UI work and also sits at the strategy table. The title emerged in the early 2010s, largely popularized by companies like Facebook (now Meta) and Airbnb, who wanted a single designer embedded in a product team who could own the entire design process end-to-end.

Monday: Attend the product team's quarterly planning meeting. Review OKRs. The team needs to increase activation rate by 15% this quarter. Propose three design-led experiments based on funnel analysis. Argue with the PM about which one to prioritize. Win one, lose two.

Tuesday: Conduct a competitive audit. How do Stripe, Square, and Adyen handle onboarding? Screenshot everything. Identify patterns. Write a brief analysis document. Share with the team on Slack.

Wednesday: Run a design sprint workshop with engineering and PM. Sketch eight possible solutions on paper in 10 minutes (Crazy 8s). Dot-vote. Combine the best ideas into a single concept. Build a rough prototype by end of day.

Thursday: Test the prototype with five users. Take notes. Iterate. Also: hop into a Figma file and actually design the final screens. Apply the design system. Get the visual details right. A product designer can't just hand off wireframes — they have to ship polished work.

Friday: Present the week's work to stakeholders. Explain not just what you designed, but why. Tie the design decisions back to user research and business metrics. This is the part that separates product designers from the other two titles: the ability to connect design to business outcomes.

The core toolkit includes everything from UX and UI, plus: product strategy, metrics analysis, A/B testing, stakeholder management, cross-functional collaboration, and business acumen. A product designer is expected to speak the language of engineers (feasibility), PMs (prioritization), and executives (revenue impact). It's the most demanding of the three roles, which is why it pays the most.

The Comparison Table

The Tools Landscape in 2026

The design tooling market has undergone a dramatic consolidation over the past five years, and it matters for your career which tools you invest in learning.

The short version: learn Figma. If you're a UX designer, add Miro and a usability testing tool. If you're a UI designer, go deep on Figma's component system, auto-layout, and variables. If you're a product designer, learn Figma plus an analytics tool (Amplitude, Mixpanel, or even Google Analytics).

"UX Is Not UI" — The Misconception That Won't Die

I need to address this directly because it's 2026 and we're still having this conversation.

The statement "UX is not UI" has been repeated so many times in LinkedIn posts, Medium articles, and bootcamp marketing materials that it's become a mantra. And like most mantras, it's both true and misleading.

It's true in the sense that user experience design and user interface design are genuinely different disciplines with different skill sets, as I've outlined above. You can be a brilliant UX researcher who can't design a visually appealing button. You can be a stunning visual designer who has never run a usability test.

It's misleading because in practice, at most companies, these skills are not cleanly separated. The Nielsen Norman Group, the most respected research organization in the UX field, acknowledges that "in many organizations, the distinction between UX and UI is blurred or nonexistent." A study by the UX Design Institute analyzed hundreds of job postings and found that the majority of "UX Designer" listings required strong visual design skills, while many "UI Designer" listings expected user research competency.

Here's the reality: only large, mature design organizations have the luxury of separating UX and UI into distinct roles. Google, Apple, Spotify, and Airbnb can afford to have dedicated UX researchers, UX designers, UI designers, motion designers, and content designers all working on the same product. A startup with 50 employees and one designer? That person is doing everything. And that person is usually called a "Product Designer" or "UI/UX Designer," depending on whether the company's hiring manager read a blog post about role titles before writing the job description.

The insistence on "UX is not UI" has had an unfortunate side effect: it has created a generation of designers who specialize too early. I've met UX designers who refuse to learn visual design because "that's UI work." I've met UI designers who've never talked to a user. Both are limiting their careers unnecessarily. The market wants versatility, especially below the senior level.

Career Paths: Two Routes to the Top

There are broadly two paths into senior design leadership, and understanding them will help you decide which title to aim for now.

Path A: The Research Track

Junior UX Researcher → UX Designer → Senior UX Designer → UX Lead → Head of UX Research → VP of Design (Research)

This path is for people who love understanding human behavior. You start by assisting with user interviews and survey analysis, grow into designing experiences informed by that research, and eventually lead teams that shape how an entire organization thinks about its users. At the top, you might manage a research operations team of 10–20 researchers and influence product strategy through data-driven insights.

Pros: Deep expertise is genuinely rare and highly valued. Companies will fight to retain a great UX researcher. The work is intellectually stimulating and rarely boring.

Cons: Fewer job openings at mid-career than generalist roles. Many companies don't have dedicated UX research positions — according to NN/g's UX Maturity Model, most organizations are at maturity levels 1–3 (out of 6), meaning they haven't invested in specialized research roles yet. You may find yourself being the "researcher who also designs" for much of your career.

Path B: The Craft-to-Strategy Track

Visual Designer / Graphic Designer → UI Designer → Product Designer → Senior Product Designer → Staff Product Designer → Design Manager → Head of Design / VP of Design

This is the more common path. You start with strong visual chops — maybe you came from graphic design, illustration, or even front-end development. You learn interaction design. You pick up enough research skills to be competent. You become a product designer who can own end-to-end design. Eventually, you either go deep as an individual contributor (Staff/Principal Designer) or switch to management.

Pros: Maximum career flexibility. Product designers are in demand at every company size. The path to management is clearer. You develop a broad skill set that makes you hard to replace.

Cons: Being a generalist means you're rarely the best at any one thing. You may feel like you're "pretty good" at research and "pretty good" at visual design but not exceptional at either. At staff/principal levels, companies often expect deep expertise in at least one area, and "I do a bit of everything" becomes insufficient.

The Design Bootcamp Saturation Problem

I'm going to say something unpopular: the UX/UI bootcamp pipeline is broken, and it's producing too many entry-level designers who aren't ready for the market.

Between 2018 and 2023, dozens of bootcamps — General Assembly, Springboard, Designlab, CareerFoundry, Google's UX Design Certificate on Coursera — collectively produced hundreds of thousands of "UX designers." The Google certificate alone has been completed by over 500,000 people. These programs range from 3 months to 12 months, and they teach the fundamentals: design thinking, wireframing, prototyping in Figma, basic user research.

The problem is that fundamentals aren't enough to get hired anymore. When I browse junior UX designer portfolios, I see the same three case studies over and over: a food delivery app redesign, a fitness tracker app, and a nonprofit website. The personas look identical. The journey maps follow the same template. The Figma mockups are competent but indistinguishable.

This isn't the bootcamp graduates' fault. They did what they were told. The issue is market saturation at the entry level combined with a contraction in junior design hiring. LinkedIn's 2025 data shows that while design hiring overall is growing, the growth is concentrated at mid and senior levels. Junior and entry-level design roles have become brutally competitive.

What actually works to break in? Here's what I've seen from designers who successfully transitioned:

• Solve a real problem, not a hypothetical one. Redesign an actual product you use daily. Even better: redesign something in your local market. If you're in Azerbaijan, redesign a local bank's app. Nobody else in the candidate pool has that case study.
• Learn front-end basics. HTML, CSS, and a little JavaScript. You don't need to become a developer, but designers who can build their own prototypes in code (or even contribute to front-end implementation) are dramatically more employable than those who only work in Figma.
• Specialize early if you can. "I'm a UX designer for fintech onboarding flows" is infinitely more interesting to a hiring manager at a fintech company than "I'm a UX designer."
• Contribute to open-source design. Projects like Open Source Design need help, and the contributions go on your portfolio with real user impact.

The "UI/UX Designer" Title: Help or Harm?

I want to call out the "UI/UX Designer" title specifically because it's the most common design job title in the world, and it's also the most confusing.

In the US and Western Europe, serious design organizations rarely use "UI/UX Designer." It's considered a red flag — a signal that the company doesn't understand design well enough to define the role properly. When a job posting says "UI/UX Designer," experienced designers often read it as: "We want one person to do two jobs for the price of one."

But in emerging markets — the Middle East, South Asia, Eastern Europe, Central Asia — "UI/UX Designer" is the default title. In Azerbaijan, almost every design role I see listed is "UI/UX Designer." In India, it's the same. This isn't because these markets are behind; it's because most companies in these regions genuinely need one person to handle both research and visual design. They don't have the headcount for specialization.

My advice: don't obsess over the title. Obsess over the work. If a job is titled "UI/UX Designer" but the actual work involves user research, wireframing, visual design, and design system maintenance, that's a product designer role by any other name. Take it. Do great work. Call yourself a Product Designer on LinkedIn if you want. Nobody will fact-check it against your contract.

Salary Deep Dive: What Moves the Needle

The salary ranges I mentioned earlier are averages, and averages hide a lot. Here's what actually determines whether you're on the high or low end:

What I Actually Think

I've spent a lot of words being balanced. Let me be direct about what I believe.

The "Product Designer" title has won. Not because it's the most precise term — it's actually quite vague — but because it most accurately describes what modern companies need: someone who can research, design, and think strategically about a product, all in one role. The trend toward Product Designer as the default title has been accelerating since 2020, and I don't see it reversing.

Pure "UX Designer" roles are shrinking outside of large organizations. If you're a specialist UX researcher, you need to target companies with mature design orgs (100+ designers). If you're at a smaller company, you'll be expected to also do visual design whether your title says "UX" or not.

The "UI Designer" title is the one most at risk from AI tools. I know this is a hot take, and I say it with empathy. AI tools like Midjourney, DALL-E, and generative design features in Figma are getting very good at producing visual variations. They can't replace the systems thinking and judgment of a senior UI designer, but they can dramatically reduce the need for junior UI-focused roles. Visual execution is becoming commoditized. Design thinking is not.

If you're starting your design career in 2026, aim for "Product Designer." Build strong research skills and strong visual skills. Don't pick one. The market will reward your versatility. If you must specialize, specialize in a domain (fintech, healthcare, B2B SaaS) rather than in a skill type (research vs. visual).

If you're in an emerging market like Azerbaijan, Turkey, or Georgia, the best move is to build a strong English-language portfolio and target remote Product Designer roles at Western companies. The salary arbitrage is enormous. A mid-level Product Designer making $80,000/year remotely for a US startup has a better quality of life in Baku than someone making $150,000 in San Francisco. This isn't a secret, and more designers are figuring it out every year.

Decision Framework

Use this to figure out which title to pursue:

Choose UX Designer if:

• You're fascinated by human psychology and behavior
• You enjoy conducting interviews and analyzing qualitative data
• You'd rather map out a user flow than pick a color palette
• You're comfortable with ambiguity and open-ended research questions
• You're targeting a company with 50+ designers where specialization is valued

Choose UI Designer if:

• You have a strong visual design background (graphic design, illustration, art direction)
• You're obsessed with craft — typography, spacing, color, micro-interactions
• You want to build and maintain design systems
• You enjoy the intersection of design and engineering
• You're aiming for a Creative Director or Design System Lead role long-term

Choose Product Designer if:

• You want maximum career flexibility and earning potential
• You enjoy both research and visual design (even if you're not the best at either)
• You like working cross-functionally with PMs, engineers, and stakeholders
• You want to influence product strategy, not just execute on someone else's vision
• You're at a startup or mid-size company where you'll be the only designer on your team

Sources

• Glassdoor — UX Designer Salary
• Glassdoor — UI/UX Designer Salary
• Glassdoor — Product Designer Salary
• Levels.fyi — Product Designer Compensation
• U.S. Bureau of Labor Statistics — Web Developers and Digital Designers
• Interaction Design Foundation — UX Design
• Interaction Design Foundation — UI Design
• UX Design Institute — What Does a UX Designer Do?
• UX Design Institute — UX Designer Job Descriptions
• Nielsen Norman Group — UX vs UI
• Nielsen Norman Group — UX Maturity Model
• UX Tools — Design Tools Survey
• Adobe — XD End of Support
• Google UX Design Certificate — Coursera
• LinkedIn — Jobs on the Rise 2025
• Open Source Design

I'm Ismat, and I build BirJob — Azerbaijan's job aggregator that scrapes 90+ career pages so you don't have to. If you're a designer looking for your next role in Baku or remote, we've got you covered.

You might also like

• AI Engineer vs ML Engineer: What Actually Changed and Why It Matters
• The Analytics Role Confusion: Business Analyst, Data Analyst, BI Analyst — What's the Actual Difference?
• DevOps vs SRE vs Platform Engineer: The Infrastructure Title Mess, Explained
• Product Manager vs Project Manager vs Program Manager: A Guide for People Who Can't Tell Them Apart