How to Get a UX Design Job

Getting your first UX design job is harder than getting your second or third, and most advice about the job search is wrong. It tells you to "network" and "put yourself out there." That's not wrong — but it's not specific enough to be useful.

Here's what actually moves the needle.

What hiring managers look for

Before you optimize your portfolio, understand what you're optimizing for.

Hiring managers at most companies are evaluating two things:

1. Can this person think through a design problem? They want evidence of process — that you identify the right problem, consider different approaches, make trade-offs deliberately, and respond to constraints. Visually polished work without process is a yellow flag.

2. Will this person communicate well and function on the team? Design is a collaborative job. How you explain your decisions, how you respond to critique, and whether you can work with engineers and product managers matters as much as the work itself.

What most junior designers get wrong: they optimize for visual quality at the expense of showing process. A portfolio of beautiful screens with no explanation of why decisions were made is less compelling than a messy portfolio that shows clear thinking.

Portfolio structure

Three to four case studies is the right number. More than four dilutes attention. Fewer than three is too thin.

Each case study should follow this structure:

The problem: What user need or business problem were you solving? Be specific. "Users couldn't find relevant products" is a problem. "Our app" is not.

Your role and constraints: What were you responsible for? What were you working with — existing codebase, a short timeline, limited research access?

Your process: What did you do? Research methods you used (and why), how you moved from research to concepts, how you narrowed down options, what feedback you incorporated and why. Screenshots of sketches, wireframes, and iterations are good here.

The solution: Your final designs. Show screens in context — device mockups, realistic content. Explain the key design decisions: why this layout, why this hierarchy, why this specific interaction.

Outcomes: What happened after you shipped? User metrics, business metrics, qualitative feedback. If you can't get metrics from a past employer, share what you measured and what you'd measure next.

What you'd do differently: This shows self-awareness. Every real designer can articulate what they'd change with hindsight.

Try Figma Free

Writing case studies

Most portfolio case studies are too long, too vague, or both. Rules:

• Lead with the outcome, not the process. "I redesigned the checkout flow, reducing drop-off by 23%" is more compelling as an opening than "In this project, I was tasked with..."
• Show your thinking with specificity. "I chose a bottom navigation pattern because user interviews revealed that 80% of tasks started from search or recent items — both needed thumb-accessible positions" is much stronger than "I chose this because it felt more intuitive."
• Use visuals at every step. Don't describe your wireframes — show them. Annotate what the key decisions were.
• Keep written sections to 200–400 words per section. Hiring managers skim. Make your work readable at skim speed.

Use Notion for building your case studies — it's easy to update, doesn't require coding, and lets you embed Figma files directly. Write the text, embed prototypes, add images.

Resume tips

Your resume matters less than your portfolio for UX roles, but it still needs to be right.

• One page for early-career designers
• List outcomes alongside responsibilities: "Designed checkout redesign that reduced cart abandonment by 18%" beats "Responsible for checkout redesign"
• Include your portfolio link prominently — top of the page, not buried at the bottom
• Skills section: list tools (Figma, Maze, etc.) and methods (user interviews, usability testing, design systems), not generic buzzwords

Interview preparation

Most UX interview processes include:

Portfolio presentation: You walk through 1–2 case studies in 30–45 minutes. Practice this out loud, alone or with a friend. Time yourself. The biggest mistake is running out of time before you reach the outcomes. Know where to cut.

Design challenge: A take-home or live prompt — "design an onboarding experience for [type of user]." Interviewers care about your process, not your Figma speed. Talk through your thinking. Ask clarifying questions. You're allowed to say "I'd normally research this, but in the interest of time, I'll make some assumptions."

Stakeholder and collaboration questions: "Tell me about a time you disagreed with a PM about a design decision." Prepare 3–5 stories using the STAR format (Situation, Task, Action, Result). Have a story about receiving and incorporating difficult feedback, navigating constraints, and collaborating cross-functionally.

What to do without experience

The catch-22 of entry-level design: jobs want experience, but you need a job to get experience.

Practical paths around it:

Speculative projects: Redesign a real product with documented process. Clearly label it as unsolicited. A good speculative case study demonstrating clear thinking competes with professional work.

Volunteer and freelance: Non-profits, local businesses, and early-stage startups often need design help and can't afford experienced designers. You get real briefs, real constraints, and something to discuss in interviews.

Contract and internships: Many companies hire design interns or contractors. These often convert to full-time roles. A contract role is a long interview.

Adjacent roles: Joining a company in a related role (research coordinator, product support, marketing) and moving into design internally is underrated. You understand the product deeply and have built relationships.

Try Notion Free

The job search itself

Most job offers come from referrals, not cold applications. The order of effectiveness:

1. Direct referrals: Someone who works at the company passes your portfolio to the hiring manager
2. Reaching out to designers at target companies: A warm introduction is better than a cold application
3. LinkedIn cold applications: Volume-based, low response rate, but necessary
4. Job boards: LinkedIn, Indeed, Wellfound (for startups), and Dribbble Jobs

Track your applications in a Notion database. Log the company, role, date applied, and status. Follow up after two weeks if you haven't heard back. Treat it like a project.

The most important thing you can do while job searching: keep building. Design something new every week. Your portfolio should look visibly more capable at month three than at month one.