Most people who want to get into UI/UX design start by collecting tutorials. They finish a Figma course, then redesign the Spotify app because a video told them to and wait for something to happen. Nothing does.
The demand for designers is real and you don't need a degree to get hired. People get stuck on the order. They spend a year sharpening skills nobody asked them to prove and skip the few things a hiring manager actually checks. I've read a lot of junior portfolios, and the people who break in fast tend to ignore the standard advice. Here's the order I'd give a friend who asked where to start.
Start as a product designer, not a "UI/UX designer"
"UI/UX designer" is mostly a job-board filter. The real roles split up:
- Product designer. Owns a feature from the problem through the shipped screen. The generalist, and the most common opening.
- UX researcher. Runs interviews and studies. Usually wants a research background.
- UI or visual designer. Focuses on the surface: layout, type, color, components.
- Design systems designer. Builds the components every other designer reuses.
For a first job, aim at product design. It has the most listings, and small companies hire generalists because they can't staff five specialists. Pick that one track and point everything at it. You can niche down later, once you know which part of the work you'd do for free.
Build three case studies, not a gallery
A hiring manager gives your portfolio about a minute before deciding whether to keep reading. They aren't counting your screens, they're trying to work out how you think and whether you can explain a decision out loud.
Three deep case studies beat ten pretty ones. Each one walks through a single project and covers:
- The problem, and who actually had it.
- Your constraints. A deadline, no budget, an existing codebase, a stakeholder who wanted it loud.
- What you did, kept separate from what your team did.
- What changed after it shipped. A number is ideal. A real quote from a user is almost as good.
Kill the unsolicited app redesigns, or give them a real reason to exist. A line that says "I redesigned Instagram" tells a hiring manager nothing. One that says "I reworked the Instagram comment thread for a VoiceOver user who kept getting lost in it, and tested the change with her" tells them most of what they want to know. The second version names a real constraint and a real person, and that is what gets you the interview.
No work experience yet? Build your own project.
Pick a small tool you actually want to exist and vibe code it into something that runs, not another static mockup. You don't have to draw every screen from scratch. Start on a real foundation with a tool like SaaS Design (which you use directly in Claude or Codex), which drops a full, production-ready design system into the project from one prompt. Then restyle it and customize it as needed with your own touches.
Write the result up as a case study, including which design decisions you kept and which ones you overrode and why. It pulls double weight, because shipping something real with AI is the exact fluency hiring teams have started screening for.
Learn Figma until it bores you
Figma runs this industry, and it isn't close. Sketch faded years ago, and Adobe shelved XD after its deal to buy Figma fell apart. Learn it deeply enough that the tool stops getting in the way and you're just thinking about the design in front of you.
The parts that actually get you hired:
- Auto layout, until you can make a responsive component without fighting it.
- Components, variants, and properties, so your files read like a system instead of a stack of frames.
- Prototyping, enough to click through a real flow.
- File hygiene: named layers and a structure another person can open without getting lost.
Then pick up enough HTML and CSS to be useful, not enough to become an engineer. Understanding how flexbox actually behaves changes the way you design, and it makes you the designer engineers want to work with. That matters more than it sounds, because engineers refer the people they trust.
Get real reps before anyone pays you
The first job is the one everyone struggles with, because the listings all ask for experience you don't have yet. So you go make some that counts. Find a real problem with a real person attached to it:
- A local business with a broken site. Walk in, offer to fix one page, and talk to their customers while you're there.
- A nonprofit that needs a working donation flow. They rarely have a designer and they'll let you ship.
- An open-source app with rough UI. File issues, propose changes, and do the work where people can see it.
- The job you already have. Redesign the internal tool your team complains about and write up what improved.
A couple of those, done properly and written up, beat a bootcamp certificate. You're proving something small and specific: that you talked to a real user and made a call you can defend to a stranger.
Make your work findable
A lot of design roles fill through referrals before the public posting does much. The goal is to be the name that comes to mind, and you get there by working in public.
Post the case studies somewhere public. Then write up one decision you made and why, in a few hundred words. When you comment on other designers' work, say something more useful than "love this." And be around where designers gather: a couple of Slack or Discord communities, LinkedIn if you can stand it, the comments under good design writing, the odd local meetup.
It feels slow for a while. Then a senior designer reshares one post and your inbox looks different. One good thread can outrun two hundred cold applications.
When you do apply cold, skip the boards everyone floods. Smaller, startup-leaning sites like Wellfound get far fewer applicants per role. Get your portfolio live before you start there, because Wellfound lets you add a website URL to your profile, and a real link to your work carries more weight than a cover letter ever will.
What interviews actually test
A design interview isn't a quiz. It usually opens with a portfolio walkthrough, and many teams add an app critique or a take-home exercise. They're working out whether they want you in the room when something breaks.
In the walkthrough, don't tour everything. Pick one project and live in the messy middle of it: the thing you tried that flopped, and the call you reversed when a deadline forced a worse-but-shippable choice. Being honest about your own bad decisions reads better than a perfect story nobody believes.
For a take-home, scope it down and finish. A small, done solution that explains its own assumptions beats an ambitious half-built one. Write your assumptions into the file so they can follow your thinking.
How much do UI/UX designers make?
In a major US market, a product designer makes roughly $90,000 to $153,000, and senior designers clear $200,000 once equity and bonuses count. The number swings hard by city and company size, so anchor to one real market. Glassdoor's early-2026 data for New York put the average product designer there around $116,000, with the middle of the range from about $90,000 to $153,000 and seniors near $217,000. Most metros run lower, so scale those figures to your own city.
Don't take a recruiter's number at face value. Pull the current figure for your city and title on Glassdoor and Levels.fyi before you say anything out loud. When they ask what you're expecting, give a range and set the bottom to a number you'd genuinely accept, because the bottom is usually where the offer lands.
How do you use AI in UI/UX design?
You use it to generate a fast first pass, then fix what's wrong with your own judgment. A designer who can prompt a tool for a draft and then make it good gets through far more work than someone mocking every screen by hand. Job posts have started listing AI fluency right next to Figma, and the people who can show it are skipping a rung on the way in.
Learn the new tools the way you once learned Figma. Figma has its own AI features now, and prompt-to-UI tools like v0 will turn a sentence into a working screen.
Common questions
Do you need a degree to become a UI/UX designer?
No. Most hiring managers care about your portfolio and how you think, not a diploma. A few strong case studies and a real grasp of the work matter far more than a credential.
How do you build a UI/UX portfolio with no experience?
Build a real project of your own. Pick a small tool you want to exist, design and ship it (you can vibe code the front end and start from a ready-made design system like SaaS Design), then write it up as a case study that shows the problem, your decisions, and what changed.
How much do UI/UX designers make?
In a major US market a product designer makes roughly $90,000 to $153,000, and senior designers clear $200,000 once equity and bonuses count. Glassdoor put the New York average around $116,000 in early 2026. Smaller metros pay less.
What tools do UI/UX designers use?
Figma is the industry standard for UI design and prototyping. It helps to know a little HTML and CSS, and increasingly to be fluent with AI tools like Figma's AI features, prompt-to-UI tools such as v0, and AI design systems.
How do you use AI in UI/UX design?
Use it to generate a fast first pass, then fix what is wrong with your own judgment. The valuable skill is directing the tool and knowing why a generic result is generic and what to change.
How long does it take to become a UI/UX designer?
Most people who focus on real projects rather than endless courses can put together a hireable portfolio in a few months. The bottleneck is shipping real work and writing it up, not collecting tutorials.
What to do this week (choose at least two)
- Rebuild one screen from an app you use in Figma, with auto layout, until it survives being resized.
- Email one local business or nonprofit and offer to fix a single page for free.
- Start a project for your portfolio. If you have nothing from work yet, create your own and build it.
- Write up whatever you make, rough edges and all, and put it somewhere public.
Even two of these will put you ahead of most people who've spent a year "studying UI/UX" without shipping anything.