What does a UX/UI designer actually do (and what it pays)
Updated on July 30, 20266 min read
Picture an app that lets you book a dentist appointment. UX design decides how many taps it takes to find an open slot and confirm; UI design decides what that "confirm" button looks like, where it sits, and whether you notice it at all. A UX/UI designer owns both of those decisions, and that split is the fastest way to understand a job that sounds vague until you see it in action.
If you've asked what a UX/UI designer actually does, whether the work pays well in the United States, and how someone gets in without an art school pedigree, this walks through all three.
What UX and UI mean in plain terms
UX stands for user experience. It's about how a product feels to use: is it logical, quick, and frustration-free? UI stands for user interface. It's the visual and interactive layer: buttons, colors, typography, spacing, icons, and the states each element moves through when you tap or hover.
They overlap, but they answer different questions. UX asks "can someone get this done without giving up?" UI asks "does this screen look clear and trustworthy while they do it?" A checkout flow can have gorgeous UI and still lose users because the UX buries the shipping cost until the final step. The reverse happens too: a smart flow wrapped in cramped, inconsistent visuals reads as amateur, and people bounce.
Most US job listings bundle the two into one "UX/UI designer" or "product designer" role, especially at startups and mid-size companies. Larger tech employers in places like San Francisco, Austin, and New York sometimes split them into separate UX researcher and UI/visual designer titles.
What a UX/UI designer does day to day
The stereotype is someone pushing pixels in a design tool all day. The real week is broader.
A designer usually starts by understanding the problem. That means talking to users, reading support tickets, watching session recordings, or interviewing the sales team about why deals stall. From there they map the flow: the sequence of screens and decisions someone moves through to finish a task.
Then comes wireframing: rough, low-fidelity layouts that focus on structure, not color. Once the structure holds up, they build high-fidelity mockups and interactive prototypes that behave like the real thing. Those prototypes get tested with actual people, revised, and handed to engineers with specs for spacing, colors, and behavior.
Here's a concrete example. Say a food-delivery app gets complaints that people can't find their past orders. The designer digs into the data, finds the reorder button is hidden two menus deep, sketches a version that puts recent orders on the home screen, prototypes it, tests it with eight users, and ships a fix that cuts reorder time in half. That whole loop — research, design, test, refine — is the job.
Collaboration eats a real chunk of the week too. Designers sit with product managers to prioritize, with engineers to check what's buildable, and with marketing on brand consistency. The best ones write clearly and defend decisions with evidence, not taste.
The tools you'll actually use
Figma dominates US design teams right now. It's collaborative, browser-based, and where most job postings expect you to work. You'll also run into FigJam or Miro for whiteboarding, Maze or UserTesting for research, and design systems like Material Design as a shared vocabulary. You don't need all of them on day one, but Figma fluency is close to non-negotiable.
Is UX/UI design well paid in the United States?
Short answer: yes, competitively, and it scales with experience. Pay depends heavily on location, company size, and whether you land at a product company or an agency. Salaries in metros like San Francisco, Seattle, and New York run higher than the national picture, and they usually come with a higher cost of living to match.
Here's how the levels tend to stack up in relative terms:
| Level | Typical experience | Where pay tends to land |
|---|---|---|
| Junior / entry-level | 0–2 years | Solid starting salary, above many other entry roles |
| Mid-level | 2–5 years | A meaningful step up, often into six figures in tech hubs |
| Senior | 5+ years | Strong six figures at established product companies |
| Lead / design manager | 7+ years | Highest band, includes team leadership and strategy |
Two things move the needle most. First, portfolio quality: hiring managers care far more about the projects you can show than the years on your résumé. Second, specialization. Designers who can also run research or understand front-end constraints tend to command more, because they reduce the back-and-forth with other teams.
How people break into UX/UI design without a design degree
This is the part career changers care about, and the honest answer is that most working designers did not study design in college. They came from marketing, teaching, retail, psychology, or engineering, and they built the skills deliberately.
The entry path has three parts that matter more than any credential. You need to understand design fundamentals: hierarchy, contrast, spacing, typography. You need tool fluency, mainly Figma. And you need a portfolio of two to four case studies that show your thinking, not just your final screens. A case study that explains the problem, your research, your options, and why you chose one wins interviews.
Self-teaching works for disciplined people, but it's slow and easy to stall on. A structured program compresses the timeline and gives you feedback, which is the thing YouTube can't. Our UX/UI design bootcamp is built around shipping real portfolio projects with mentor review, so you leave with work you can actually show, not just certificates. If you'd rather set your own pace around a job, the self-paced UX/UI design track covers the same ground on your schedule.
What a realistic first year looks like
Expect the first few months to feel like learning a new language. You'll redo the same wireframe five times and slowly stop hating it. By month four or five, if you're consistent, you'll have a couple of case studies worth showing. The job search itself takes patience: entry-level design is competitive, and a sharp portfolio plus a clear story about why you switched fields beats a scattershot application every time.
Networking matters more than people expect. Local design meetups, Figma community events, and portfolio reviews in your city put you in front of people who hire. A lot of first design jobs come through a warm introduction, not a job board.
Is it the right fit for you?
You'll probably enjoy this work if you like solving puzzles, care about how everyday things could work better, and don't mind having your ideas challenged. You'll struggle if you want a purely artistic job with no constraints: design lives inside deadlines, budgets, and engineering limits, and that friction is where the craft actually happens.
The role also keeps changing as tools speed up the repetitive parts. That raises the value of the human skills: framing the right problem, running honest research, and explaining a decision so a whole team gets behind it.
UX/UI design pays well, has real career runway, and welcomes people without a traditional design background more than almost any other tech role. The move that separates thinkers from applicants is building a portfolio that proves you can solve a problem end to end. If you're ready to get started, Code Labs Academy's UX/UI design bootcamp gives you real projects, mentor feedback, and something worth showing before you ever send an application.
