Updated October 2026
A startup product designer interview works best in four stages: a founder screen, a portfolio deep dive, a fictional work sample, and a session with the engineers who will build the designs. Each stage tests something a polished portfolio can hide.
Our rule is to hire for the decisions in the portfolio, not the pixels. Most case studies are team output: a PM framed the problem and a lead designer set the style. The part you can credit to one person is what they chose, rejected and argued for, so every question below digs for that.
Our illustrative example: a Series A startup selling appointment booking software to physiotherapy clinics, hiring its first product designer. Its strongest candidate, Priya, built most of her portfolio at a large fintech.
The product designer interview plan
| Stage | Who | Length | What it tests |
|---|---|---|---|
| 1. Founder screen | Founder | 30 min | Appetite for being the only designer, stage fit, salary range |
| 2. Portfolio deep dive | Founder plus a PM or senior engineer | 60 min | What they decided versus what the team decided |
| 3. Work sample review | Founder plus one engineer | 60 min | Problem framing, trade-offs, explaining choices |
| 4. Build session | Two engineers | 45 min | Handoff quality, edge cases, cost awareness |
Ask every candidate to bring one screen that never shipped.
- The visual style and type choices
- The problem statement
- The polished final prototype
- The launch metrics
- Which options they rejected
- What research changed their mind
- What they cut to hit the date
- The argument they lost
Portfolio decisions
- Pick one project. Which decision in it was yours alone, and what were the alternatives?
- Show me something that didn't ship. Why not?
- Where did you disagree with your PM or founder, and who turned out to be right?
- What did you cut to hit the deadline? Would you cut it again?
- If I called the engineer on this project, what would they say was hard about working with you?
Strong answer: Specific rejected options and a clear line between their work and the team's.
Red flags: "We" for every decision, or no unshipped work to show.
Priya passed this section on her second project, a small internal tool, where she could name three layouts she had tested and dropped. Her famous fintech project was mostly the brand team's work, and she said so.
Working as the only designer
- Without a design manager, how do you know your work is good enough?
- A founder sends you a screen they sketched over the weekend. What do you do with it?
- How would you start a design system when nobody has set time aside for one?
- What is the smallest piece of process you would introduce in your first month?
- Tell me about design work you did outside your comfort zone, such as a sales deck or a pricing page.
Strong answer: Their own ways of getting critique, and treating the founder's sketch as evidence about a customer.
Red flags: Waiting for a brief, dismissing founder input, or a month-one plan built around a full design system.
"I would ask what problem the sketch solves, because it is usually the founder's answer to a customer conversation I missed. Then I would talk to that customer and come back with two options, the founder's and mine, plus what each costs to build."
Research and customer judgement
- Tell me about research that changed your mind about a design you liked.
- How would you get five conversations with our users, clinic reception staff, in your first two weeks?
- When have you shipped without research, and how did you check afterwards?
- How do you tell a usability problem from a feature request?
- What would you want to know before touching our booking flow?
Strong answer: Research that cost them a favourite idea, and a practical plan for reaching busy users.
Red flags: Research that always confirmed their view, or a plan needing a research team.
Building with engineers
- Walk me through a handoff. What's in it besides the screens?
- How do you design empty states, errors and loading?
- An engineer says your design will take three weeks, not three days. What next?
- When did you last change a design after seeing it built?
- What do you need to know about our front-end stack before designing for it?
Strong answer: Handoffs with edge cases written down, a cheaper version offered without being asked, and curiosity about the stack.
Red flags: Screens thrown over the wall, or treating build cost as engineering's problem.
Work sample: a fictional booking problem
Never ask for a free redesign of your real product. It is unpaid spec work, strong candidates refuse it, and those who agree lack your context. Use a fictional brief close to your problem.
For the clinic role: a fictional dental practice wants patients to rebook a cancelled appointment from a text message, with no app download. Give a one-page brief with two patient quotes. Ask for rough flows, one key screen and a note on what they would test first. Cap it at 3 hours.
Look for questions before pixels, edge cases such as a patient with two bookings, and a test plan they could run next week.
Scoring rubric
| Outcome | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Customer insight | No research examples | Research done for them | Runs research, findings used | Research changed the roadmap |
| Core flow quality | Screens without a problem | Clear flow, few trade-offs | Trade-offs named and tested | Measured improvement after launch |
| Design system | Never built components | Uses an existing system | Built a small system | Built one engineers adopted unprompted |
| Engineering partnership | Hands over screens only | Covers some edge cases | Full handoffs, cost-aware | Offers cheaper options early |
| Founder handover | Defers or dismisses founders | Takes direction well | Pushes back with evidence | Turns founder input into research |
These rows match the scorecard in our product designer job description template.
Where Funded.club fits
We run product design searches on a fixed fee agreed upfront, averaging 6 to 9% of salary. One dedicated recruiter screens portfolios against your scorecard, with first candidates within 7 days. See pricing.
Frequently asked questions
Should I pay candidates for a design exercise?
If you can. A small fixed payment respects the candidate's time. Either way, keep the brief fictional and under 3 hours.
How many portfolio projects should I review in depth?
Two. One deep conversation about a single project, including what didn't ship, tells you more than a tour of six.
Is a product designer interview different for a first design hire?
Yes. A first designer has no manager or system to lean on, so test working alone and handling founder input. Our guide on hiring your first product designer covers the full process.
Worth a brief chat about your next hire? Book a free call.
Hiring after a funding round?
First candidates in 7 days. Fixed-fee, no commission.