A product designer onsite interview usually has four parts: a portfolio presentation, a design challenge on a whiteboard or in a design tool, a cross-functional round with a product manager or engineer, and a behavioral interview. To prepare, build a 45-minute portfolio talk around two or three projects, practice a repeatable approach to the design challenge, and have stories ready about working with PMs and engineers.
Formats vary by company. Some replace the live challenge with a take-home exercise, and smaller companies may combine rounds. Ask your recruiter for the agenda and who you will meet. For a bank of individual questions, see our UX designer interview questions guide; this page covers how the onsite is structured and how to prepare for each part.
What happens in a product designer onsite interview?
A designer onsite is commonly four to five sessions of 45 to 60 minutes. The portfolio presentation is often first, so the rest of the panel can refer back to it.
| Round | Typical length | Who attends | What it tests |
|---|---|---|---|
| Portfolio presentation | 45–60 min | Several designers, often a PM or design manager | Process, decision-making, impact, storytelling |
| Design challenge | 45–60 min | One or two designers | Problem framing, user focus, structured thinking under time pressure |
| Cross-functional round | 45 min | A PM, engineer or researcher | Collaboration, trade-offs, handling disagreement |
| Behavioral / design manager | 45 min | The hiring manager | Ownership, feedback, growth, team fit |
| App or product critique (some companies) | 30–45 min | A designer | Design vocabulary and reasoning |
For the logistics of the whole day, see our hub on how to prepare for an onsite interview.
How do I structure a 45-minute portfolio presentation?
Present two projects in depth rather than five briefly. Reviewers want to understand how you think, and that takes time per project. Keep about 15 minutes for questions, because the questions are where much of the scoring happens. Here is a structure we use as an example.
- Introduction (2–3 minutes). Who you are, the kind of problems you like and what you will show.
- Project one (12–15 minutes). The problem and why it mattered to the business, your role and team, research and what it showed, two or three key decisions with the options you rejected, the final design and the measured outcome.
- Project two (10–12 minutes). Choose a contrasting project: a different user, platform or kind of constraint.
- Reflection (2 minutes). What you would do differently and what you learned.
- Questions (15 minutes). Expect "why did you choose that?", "what did engineering push back on?" and "how did you measure success?"
Be precise about your role. If a researcher ran the study or another designer built the visual system, say so. Panels commonly probe this, and a vague answer costs more trust than an honest "I owned the flows; our researcher ran the interviews."
What do reviewers score in a designer onsite?
Rubrics differ by company, but most designer panels look for the same broad signals. Use this as a self-check before the day.
| Signal | What it looks like in your answers | Common gap |
|---|---|---|
| Problem framing | You state the user, the goal and the constraint before showing screens | Opening with final mockups |
| Process and rigor | Research, options explored, testing and iteration | A process that looks textbook but did not change the design |
| Decision-making | You explain trade-offs and why you chose one path | "The team decided" with no view of your own |
| Craft | Clear hierarchy, consistent patterns, attention to edge cases and accessibility | Only happy-path screens |
| Impact | Outcomes such as task success, conversion or support tickets | No measure of whether it worked |
| Collaboration | How you worked with PM, engineering and research | Treating engineers as an obstacle |
For critique rounds, it helps to have shared vocabulary. Jakob Nielsen's 10 usability heuristics (Nielsen Norman Group, first published in 1994) are a common reference, such as visibility of system status and error prevention. Use them to explain your reasoning, not as a checklist to recite.
The design challenge: a sample walkthrough we wrote
The design challenge tests how you think in a short, ambiguous session. Talk through your reasoning, ask questions and leave time to show a solution. If yours is on a board, our guide to the whiteboard interview has layout tips. Here is an example walkthrough we wrote for the prompt "Design a way for gym members to book classes."
- Clarify (5 minutes). "Is this mobile or web? Is the goal to fill classes or to reduce no-shows? Who else uses it: instructors, front desk?" Suppose the interviewer says mobile, and the gym's problem is that popular classes fill instantly while 20% of booked spots go unused.
- Users and goals (5 minutes). Regular members who want a reliable spot, occasional members who want flexibility, and staff who want full classes. Focus on regular members, since they drive most bookings.
- Key journey (10 minutes). Find class, check availability, book, get a reminder, attend or cancel. The pain points are at "book" (slots gone) and "cancel" (no easy way, so people simply do not show up).
- Ideas (10 minutes). A waitlist that auto-fills cancellations, a one-tap cancel in the reminder, and a gentle no-show policy. Choose the waitlist plus one-tap cancel, because together they solve both pain points.
- Sketch (10–15 minutes). Class list with clear availability states, a booking confirmation, and a reminder notification with "Can't make it? Release your spot."
- Measure and edge cases (5 minutes). Success: lower no-show rate and higher class fill rate. Edge cases: waitlist offers sent at night, members on several waitlists, accessibility of the availability states for people with color vision deficiency.
Notice that the walkthrough states a choice at every step. Interviewers commonly score whether you make and explain decisions, not how many screens you draw.
Cross-functional and behavioral rounds
In the cross-functional round, a PM or engineer wants to know what you are like to build with. Expect questions such as:
- "Tell me about a time engineering said your design was too expensive to build. What did you do?"
- "How do you decide what goes into the first version?"
- "How do you hand off designs, and what happens after?"
- "Describe a time data contradicted your design instinct."
The behavioral round with the design manager covers feedback, ownership and growth. Prepare stories in the STAR format about receiving tough critique, disagreeing with a PM, and a project that did not go to plan. End each session with a question for that interviewer; our questions to ask the interviewer list has options for design managers and peers.
If you also interview for product roles, compare our product manager onsite interview questions, since PM and design loops share a lot of the cross-functional ground.
How to practice for a product designer onsite
- Present your portfolio talk aloud three times with a timer, once to someone outside design.
- Run two practice design challenges a week, each in 45 minutes, and review where you spent too long.
- Rehearse the spoken rounds with an AI interview practice tool. Mock Interview builds questions from your résumé and the job description and scores each spoken answer out of 10 with what to fix. It is free for 15 minutes a day with no account. Follow each employer's rules on AI and use it to prepare beforehand.
Rehearse the talking parts of your design loop
Practice behavioral and cross-functional answers in a free AI mock interview and get a score out of 10 with what to tighten. Nothing to install.
Try a free AI mock interviewFAQ
How many projects should I show in a designer onsite?
Two in depth is common for a 45 to 60 minute presentation, with a third ready in case you are asked. Depth on fewer projects usually beats a quick tour of many.
Should my portfolio presentation be the same as my website portfolio?
No. The presentation should tell the story of your decisions, with more process and fewer final screens than a website portfolio usually shows.
What if I do not finish the design challenge?
That is common. Interviewers care more about framing, prioritization and reasoning. Manage time so you can at least sketch a solution and say how you would measure it.
Is a take-home design exercise better than a live challenge?
Neither is better; they test different things. A take-home shows polish and depth, while a live challenge shows how you think in real time. Prepare for whichever your recruiter confirms.
How do I talk about projects under NDA?
Ask your former employer what you can share, then remove confidential details, blur sensitive screens and describe outcomes in relative terms. Say up front that some details are changed.