How to hire a product designer

A product designer owns how your product works and feels for the people who use it, from defining the problem to shipping the screens. This playbook covers when to hire one, which type you need, what it costs, where to find candidates, a four-step interview plan with a portfolio review and a fair design exercise, questions, evaluation and pay.

When to hire your first product designer

Design is one of the first non-engineering roles most startups add, but it is easy to hire too early or too late. Our post on the three signs you are ready to hire a product designer goes deeper; here is the short version.

Hire a full-time designer when:

• No one on the team can do design well, and that gap is blocking your product from getting to market or being something customers choose to use.
• Design needs are ongoing. If there are a few months of continuous product work ahead, a full-time hire is more efficient than managing a series of contractors.
• Usability is how you compete. If your category is full of painful products, a simple and trustworthy experience can be a real advantage.

Wait, or use a freelancer or agency, when:

• You need a brand identity, a logo or a marketing site, and the work has a clear end.
• The product is still changing so fast that screens would be thrown away.
• You are not sure the role needs a full-time person. A contract or retainer arrangement can bridge you to a decision.

If you are weighing a PM first, see the product manager playbook. In small teams a strong designer and a strong PM often overlap, so you may need only one at first.

Types of product designers

Job titles in design are loose, so decide on the skills before you write the posting.

Be honest about what the first designer will spend their time on. A candidate who is wonderful at brand illustration may struggle in a product built around dense data tables, and the reverse is also true.

What to look for in a product designer

• Problem framing. They define who the user is and what is wrong before they open a design tool.
• User understanding. They use research or data, even informal, and can say what users need.
• Craft. Hierarchy, spacing, typography and consistency, with polish that does not slow shipping.
• Collaboration. They bring engineers and PMs in early and take critique well.
• Communication. They tell a clear story about their work and handle questions calmly.
• Ownership and speed. They ship, learn and iterate, and are comfortable with ambiguity and no design system.

Write these down before the first interview. They become the criteria you evaluate candidates against below.

Red flags to probe. Case studies with final screens only, no clear account of which decisions were theirs, blame placed on engineers or users for what went wrong, and no questions about your product or users. Each is a reason to ask more, not an automatic no.

What it costs to hire a product designer

Hiring a product designer has three costs: the recruiting fee if you use outside help, your team’s time across a four-stage process including the portfolio review and exercise, and the pay package itself. For pay, see the compensation section below and our compensation strategy guide. For the recruiting fee, Dover’s Marketplace publishes what companies actually paid for design hires:

Recruiters on Dover set their own pricing, and you can engage them without a long-term contract.

Where to find product designers

The strongest designers are often not looking, so use more than one source.

• Referrals from your engineers, advisors and other founders. Designers know who is good.
• Portfolio communities and design events, where people share their work publicly. You can often see how someone thinks before you reach out.
• Direct outreach. Look at the public portfolios of designers whose work fits your product, and write short, specific messages about the problem they would solve. See how to source candidates.
• Job boards, with a description that is clear about the product, the type of designer and the problems they will solve. See where to post jobs and find candidates.
• Design schools and bootcamps for junior designers.
• A vetted recruiter. Recruiters on Dover’s Marketplace who hire product designers can run the outreach while you stay in the interviews.

Ask for a portfolio link or a case study right in the application so you can screen on work, not resumes.

In Dover’s ATS, post the job to 50+ job boards from one place, post to Dover Startup Jobs if you are a venture-backed startup, and see which source produces hires in Reporting & Analytics. See Managing job boards.

A four-step interview plan for product designers

Plan on about four and a half hours of candidate time including the exercise, and adjust to your stage. For the principles behind it, see our guide to interview process best practices.

For the screen, our guide to phone screens has a script. For the final loop, give each person a different competency so questions do not repeat, include one conversation that is not evaluative so the candidate can ask honest questions, and let them meet the engineers and PM they would work with.

How to review a designer’s portfolio

Start before the interview, with ten minutes on each portfolio. Then use the live walkthrough to test whether the candidate really did the work.

What to look for:

• A clear problem. Each case study should say who the user was, what was wrong and why it mattered.
• The candidate’s role. Look for “I” statements: what they personally researched, decided and designed, and who they worked with.
• Process and tradeoffs. Good case studies show options considered, constraints and why they chose what they chose.
• Evidence from users. Research, testing, feedback or data, even if informal.
• Outcomes. What changed after launch, and what they learned, including what did not work.
• Craft. Layout, hierarchy, spacing, typography and consistency. At a startup, polish and speed both matter.
• Range and fit. Work on products with some similarity to yours, such as complex workflows, B2B, mobile or consumer.

Red flags:

• Final screens only, with no problem, process or outcome.
• Cannot explain which decisions were theirs.
• Every project looks the same, with no sign of adapting to the problem.
• Blames engineers, PMs or users when asked about things that went wrong.
• Cannot explain why a design choice was made, or can only justify it as “it looked better”.
• Speculative redesigns of big-name products as the whole portfolio, with no real constraints or shipped work.
• No questions about your product, users or team.

Portfolio walkthrough prompts. Ask the candidate to pick one project they are proudest of and present it for 15 minutes, then ask:

• What was the problem, and how did you know it was the right one to solve?
• What was your role, and who else was involved?
• What did you try that did not work?
• What did you cut, and why?
• How did you work with engineering to get this built?
• What would you do differently now?

The design exercise: how to run it fairly

An exercise can be very useful, but a bad one wastes candidates’ time and attracts only people with free evenings. Keep it fair.

Rules for a fair exercise:

1. Time-box it. Keep a take-home to two to three hours, or run it live in 45 to 60 minutes. Say so in the invitation.
2. Pay for anything longer. If the exercise takes more than a few hours or the candidate produces polished work, pay for their time.
3. Use a made-up problem, not your roadmap. Never ask for free work on a real problem you will then build.
4. Do not ask for pixel-perfect visuals. Ask for thinking: who the user is, the key flow, sketches or wireframes, and the tradeoffs.
5. Explain how it will be judged. Share the evaluation criteria in advance.
6. Discuss it live. The conversation about the work is more important than the artifact.
7. Offer accommodations. Allow candidates to use their own tools, and give a way to submit in a format they can manage.

Sample live exercise (45 to 60 minutes):

Imagine a [product type, for example a scheduling tool for clinics] has a problem: [a specific problem, for example, new users abandon setup at the calendar-connection step]. You have a fictional user, [name and short description]. Talk us through how you would approach it. We will give you data points if you ask. Sketch the key flow on a whiteboard or in your preferred tool. At the end, tell us what you would test first and how you would know it worked.

Sample take-home (2 to 3 hours):

Choose one of these prompts:

1. Redesign the onboarding of an app you use regularly, to help a new user get to value faster.
2. Design the settings page for [a fictional product with several account types].
3. Critique a screen we provide, and propose three changes in order of priority.

Submit a short document (a few screens plus notes) that explains the user, the problem, your approach and the tradeoffs. We care about your thinking more than polish.

What good looks like: the candidate defines the user and the problem before drawing, asks clarifying questions, explores more than one direction, picks one and explains why, and names what they would test.

In Dover, build this plan on the job’s Interview Plan tab. Use a single-part stage for the screen and the portfolio review, a multipart stage for the final loop, and an assessment stage for a take-home exercise. Assign each a feedback form and an email template, and send candidates a scheduling link from their profile. See Setting up your interview plan.

Product designer interview questions

Choose two or three per area, and ask the same questions to every candidate for the same stage.

Design process and problem solving

• Walk me through your process, from a vague problem to a shipped solution.
• Tell me about a time the problem you were asked to solve turned out to be the wrong one.
• How do you decide when a design is good enough to ship?
• How do you work when you have a deadline and little user data?

User research and data

• How do you learn about users when you have no research budget?
• Tell me about a research insight that changed a design.
• What metrics would you use to judge a redesign?
• How do you handle feedback from a customer or an executive that you disagree with?

Craft and systems

• Show me a screen you think is well designed and explain why.
• How do you decide when to create a new component and when to reuse one?
• Tell me about a design system you built or contributed to.
• How do you think about accessibility in your work?

Collaboration and communication

• Describe how you work with engineers. When do you bring them in?
• Tell me about a disagreement with a PM or engineer and how it was resolved.
• How do you give and receive critique?
• How do you present work to non-designers, like founders or sales leaders?

Startup fit

• How would you work in a team with no existing design system or design leader?
• What would you do in your first 30 days here?
• Tell me about a time you had to move quickly with imperfect information.
• What would you want to own, and what would you want help with?

Reference checks for product designers

Do them for finalists, after the design exercise and before the offer. Portfolios show the result, and references show how the person got there.

• Ask a former manager or PM what the candidate personally owned on the projects in their portfolio.
• Ask an engineer who worked with them how early they were brought in and how handoff went.
• Ask how they handled critique and disagreement, and how they responded when a design did not work.
• Ask whether the manager would rehire them and in what kind of role.
• If you can, speak to someone the candidate did not list, such as a peer who worked closely with them.
• Compare the stories to the portfolio walkthrough. Gaps matter more than flattering adjectives.

Ask candidates for permission before you contact a current employer.

How to evaluate product designer candidates

Evaluate each candidate against the same criteria right after the interview, before you compare notes with other interviewers. Write what you saw and heard, not a number.

Decide in advance which criteria are must-haves. For a first designer, weigh problem solving, user understanding and speed more heavily than specialist polish. A weak showing on a criterion the role needs is a no, whatever else they do well.

Interview feedback form

Give every interviewer the same short form.

1. Overall recommendation: strong yes, yes, no, strong no.
2. For each criterion assigned to you, one or two lines of evidence: what the candidate said or showed.
3. The strongest signal from this interview.
4. The biggest concern, and whether onboarding could address it.
5. What we should probe in the next round.

Ask interviewers to submit their feedback before they read anyone else’s. Compare notes in a short debrief, not in a chat thread.

In Dover, create this as a feedback form in Settings → Feedback Forms and assign it to each stage, so every interviewer answers the same questions. On Premium, the AI Notetaker can capture the conversation and fill in the form. See Interview feedback forms.

Product designer compensation and closing the offer

How to think about designer pay

Decide your approach before you post the role, so you can state it in the first conversation. For market data, see our compensation strategy guide; this section covers the decisions, not figures.

• Level. Decide whether you need a senior designer who works alone or a mid-level designer who needs a lead. Pay follows scope, not title.
• Base salary and equity. Equity is often part of a startup offer. Explain the number of shares, the vesting schedule and what they are worth in plain terms.
• Tools and resources. Software, research budget and engineering support are part of the package designers weigh.
• Pay transparency. Many locations require a pay range in the posting. See compensation requirements for job postings.

Close a designer

Good designers choose teams that value design, so let finalists talk with the engineers and PM they would work with. Be clear about influence: who decides on product direction, how design feedback is handled and whether design reports to a founder. Tell them what tools, research access and engineering support they will have. Move quickly after the final round, because strong designers are usually talking to several companies. Then follow the steps in how to make an offer.

Common mistakes when hiring product designers

• Hiring a visual designer for a product job. Beautiful brand work does not show that someone can design a dense workflow.
• Judging on final screens. Polished mockups hide who did the thinking, so test the process with a walkthrough and exercise.
• Asking for free work on your real problem. It is unfair to candidates and attracts only people with spare time.
• Setting an exercise that takes a weekend. Time-box it, or pay for it.
• Skipping the engineer and PM conversation. A designer who cannot work with them will struggle whatever their portfolio looks like.
• Giving no clarity on influence. Strong designers want to know who decides, and vague answers lose them.
• Moving slowly. Strong designers are interviewing elsewhere, so decide within a day or two of the final round.

Get help hiring a product designer

Hiring your first designer is a hard search for a small team: the strongest candidates are rarely applying, and you need someone who knows what good design work looks like. Dover’s Marketplace connects you with vetted independent and fractional recruiters who have made design hires, and you can engage them without a long-term contract. They run sourcing, screening and scheduling, and every candidate stays in your own free ATS.

• Browse recruiters who hire product designers and see what past design hires cost.
• Run the process in Dover’s free ATS with interview plans, feedback forms and offers.

Frequently asked questions

When should a startup hire its first product designer?

Hire when design work is continuous, no one on the team can do it well, and weak UX is holding back the product or your sales. If you only need a brand, a logo or a one-off website, a freelancer or agency is usually the better fit.

What is the difference between a product designer and a UI/UX designer?

A UI/UX designer focuses on the interface and the flows inside it. A product designer covers the same craft and also owns problem definition, research and how the design fits the product strategy and business goals. For a first design hire at a startup, you usually want the product designer.

Should I pay candidates for a design exercise?

Pay for anything beyond a couple of hours, or time-box it to two to three hours and use a made-up problem. Never use your real product problem as a free test, and do not ask for polished visual work.

What are red flags in a designer's portfolio?

Look out for case studies that show only final screens, no clear problem statement, no explanation of the candidate's own role, and no outcome or learning. Work that cannot be explained under questioning is a bigger red flag than work that looks plain.

How much does it cost to hire a product designer?

It depends on how you hire. A traditional recruiting agency typically charges 15 to 25% of first-year salary, while Dover's Marketplace publishes the all-in cost of each design hire, shown in the live table on this page. Add your team's interview time and the pay package.

Where do you find product designers to hire?

Start with referrals from your engineers, advisors and other founders, then design communities, outbound outreach and job boards. Because the strongest designers are often not looking, a vetted recruiter can run the outreach for you.

How many interview rounds should a designer go through?

Four stages is typical for a startup: a screen, a portfolio review, a design exercise and a final loop with the people they would work with. More than that slows you down and loses candidates to faster offers.