How to Get a UX/Product Design Internship (No Experience)

It's fall recruiting, you're pulling your Wave-1 materials together, and every UX listing seems to want years of experience you don't have. Here is the reframe that changes the game: in design, the portfolio is the application. Nobody screens your resume first, they open your case studies. So the whole fight is two or three case studies that show how you think, and you can build that material without anyone hiring you. This post is the break-in playbook, and it sits under the general no-experience guide, which is the parent for turning proof into offers.

What UX and product design internships actually screen for (it's the portfolio, not the resume)

In design, the work is the qualification. A hiring designer opens your portfolio link, skims two case studies, and decides in a couple of minutes whether to talk to you. Your resume is a formality they check after. That is the opposite of most fields, and it is good news, because a portfolio is something you control completely.

The baseline they expect is narrow: fluency in Figma, free for individuals and free with the full Professional feature set for verified students, plus a case study that reads as a narrative rather than a wall of screens. Tool fluency is the floor. Everyone applying can push pixels, so what separates you is whether your case study explains a decision.

And the degree myth needs killing. A design degree is preferred at some teams and required at almost none. Non-design majors break in on portfolio strength constantly, because the portfolio answers the only question that matters: can this person frame a problem and reason toward a solution?

The one rule that gets you screened in: show your process, not just screens

Here is the single rule that decides more design outcomes than talent: show your process, not just your screens. An interviewer already knows what a wireframe looks like. What they cannot see from a gallery of polished mockups is the thing they are hiring for, which is your reasoning.

A process-driven case study documents the decision trail:

• The problem and the user. Who is this for, and what were they struggling with?
• The constraints. Time, platform, a design system, a real client's non-negotiables.
• Two or three iterations. Show the version that didn't work and why you moved off it.
• Decisions and why. "I moved the primary action up because the earlier draft buried it below the fold."
• The trade-offs you cut. What you left out on purpose. This is the most senior-sounding part of any case study.
• What you'd change. Honest reflection reads as maturity, not weakness.

Contrast two portfolios. One is six beautiful final shots with a one-line caption each. The other is three screens plus the messy middle: the wrong first draft, the reason you scrapped it, the constraint that forced your hand. The second wins every time, because it proves a mind at work. Aim for two or three strong case studies, not six thin ones. Every case study you post is a promise you can defend it live, so post nothing you can't walk through end to end.

How to get real project material when no one has hired you

The guardrail comes first and never moves: use real users and real constraints, and label everything honestly. Never invent research findings, user counts, or engagement metrics. A fabricated number unravels in one interview question, and it is a lie to the team you want to join. If a caption shows a figure, present it as an illustrative goal ("target: cut checkout from 5 steps to 3"), not a claim about a result you didn't measure.

Within that rule, you have three legitimate routes. For build mechanics and scoping, which project to build and how to present it goes deep on producing the artifact.

A redesign with a documented rationale

Pick a real app or site with a genuine flaw, redesign the flow, and document why at every step. The value is the paragraph explaining what was broken, who it hurt, and how your version fixes it. A redesign done as a documented argument reads as design work. Done as a fresh coat of paint, it reads as decoration.

Real product work for a club, nonprofit, or campus org

The strongest route, because it ships to actual users. Every student org and small nonprofit has a broken sign-up flow, an unreadable event page, or an app idea with no designer. Offer to do it. You get real constraints, a stakeholder who says no to things, and real people using the result.

A scoped self-brief

When you want a specific skill in your portfolio, write yourself a tight brief with invented-but-labeled constraints: "onboarding flow for a habit-tracker aimed at first-years, mobile-only, three screens max." Label the constraints as your own scope so nothing reads as a false claim. Designing to a fixed brief is exactly what the job feels like.

Package it: the portfolio that recruiters can actually open

The best case study is worthless if the reviewer can't open it on their phone in ten seconds. Packaging is its own skill, and the full portfolio guide is the deeper how-to, so here is only the design-specific layer.

Lead with your strongest case study, always, because reviewers rarely reach the bottom of the page. Caption each project in three beats: the problem, what you did, the outcome. Host it somewhere public that loads fast, and confirm it works on mobile. Then run the test almost nobody runs: open your live portfolio in an incognito window on your phone and click every single link. A broken case-study link is a silent rejection.

Where UX internships get posted (the sourcing stack)

Design cohorts are smaller than the software engineering intake at the same company, so sourcing is about watching the right lists on a routine, not blasting hundreds of applications. Roughly in order of signal:

• Handshake and your university portal, with smaller applicant pools and school-specific recruiting.
• Community internship trackers, open repos that surface a req close to the day it drops.
• Design job boards and communities, where roles that never hit the giant boards get listed.
• Cold outreach to studios and nonprofits, which often have unposted need and answer a specific email.
• Career fairs, where product and design teams show up in person.

Our guide to where to find internships ties the whole stack into a routine you run on repeat.

When to apply (fall rolling review, Wave 1)

Reqs generally open across roughly August into the fall, they are reviewed on a rolling basis as they arrive, and design cohorts are small, so spots fill fast. A strong application in the first wave meets a fuller set of slots and fresher reviewers. The same portfolio three weeks later competes for what's left.

Which means a September applicant is early, not late. Apply the day a window drops rather than waiting for a deadline. Open dates shift year to year, so treat any window as a typical range and confirm it on each company's careers page. The full wave breakdown lives in when to apply for internships, and because you'll juggle windows across a dozen teams, a simple system to track your applications keeps you from missing one.

The interview funnel: portfolio walkthrough + design exercise

The design loop looks nothing like a coding loop. Here is the map, round by round.

The portfolio walkthrough

You present one or two case studies live, usually somewhere in the range of twenty to forty minutes, then get grilled on your decisions. This is why every case study is a promise: the interviewer stops you at a screen and asks "why this and not that?" Walk the problem, the constraint, the iterations, and the trade-off you cut, the same story your case study already tells. If you posted work you can't explain, this is where it shows.

The design exercise / app-critique / whiteboard round

A timed, collaborative problem, sometimes a fresh prompt to sketch, sometimes a critique of an existing app. Read this clearly: you are graded on how you think out loud, handle ambiguity, and take feedback, not on a polished artifact. The structure that scores: clarify the user and the goal before you draw anything, reason aloud, invite feedback and build on it, and do not jump straight to features. Taking a critique gracefully is half the grade, so our guide to handling criticism in an interview is worth a read first.

The behavioral round

Expect "why design," "tell me about a project you're proud of," and "how do you handle critique." Your best case study is also your best STAR story, because it already has a problem, a decision, and an outcome baked in. Structure it with our STAR method guide. If a team hands you a take-home instead of, or on top of, the live rounds, here is how to nail it without over-building.

What to do this week

1. Pick one project route and start it. A documented redesign, real work for a campus org, or a scoped self-brief. One, not three.
2. Rewrite one case study to show process. Add the wrong first draft, the constraint, and the trade-off you cut. Delete two mockups if you have to.
3. Run the incognito test. Open your live portfolio on your phone and click every link. Fix the dead one before a recruiter finds it.
4. Build a target list sorted by what's open now, and apply the day a window drops.

To keep names in front of you while you build, browse internships and add the design and product teams that keep showing up. If you're weighing product management too, our PM internship playbook runs the same field guide for that path.

Frequently asked questions

Can you get a UX or product design internship with no experience?

Yes. The substitute is two or three case studies that show your process: problem, constraints, iterations, decisions and why, and the trade-offs you cut. You can build that material through a documented redesign, real work for a club or nonprofit, or a scoped self-brief, without anyone hiring you first.

Do you need a degree for a UX design internship?

Usually not. A design degree is preferred at some teams and required at almost none. Non-design majors break in constantly on portfolio strength, because the portfolio, not the diploma, answers whether you can frame a problem and reason toward a solution.

How do I build a UX portfolio with no experience?

Three legitimate routes: a redesign with a documented rationale, real product work for a club or nonprofit that ships to users, or a scoped self-brief with clearly labeled constraints. The rule that never bends: use real constraints, label everything honestly, and never invent research findings, user counts, or metrics.

What is a UX design exercise or whiteboard challenge?

A timed, collaborative problem graded on how you think out loud, handle ambiguity, and take feedback, not on a polished artifact. Clarify the user and the goal first, reason aloud, invite feedback, and don't jump straight to features before you've defined who you're solving for.

In design, the work is the qualification, so the whole break-in comes down to two or three case studies that show how you think and that you can defend live. Start one project route this week, rewrite a case study to show its process, and apply the day a window drops. September is early, not late.