The hire that decides whether design becomes strategic.
The first product designer is the hire that determines whether design becomes a strategic function or a service that makes things look nice.
For founders who have never managed a designer, the difficulty is doubled: you are hiring for a skill you cannot evaluate from experience, against portfolios that are all designed to be persuasive. This guide gives you a lens that does not require design expertise, covering why the first hire should be a generalist, what to look for when you cannot assess craft, and how to define the role before the search opens.
The first product designer is the hire that determines whether design becomes a strategic function or a service that makes things look nice.
If you have ten minutes before a hiring review, read only this.
Generalist first, always.
Your first designer does user research, interaction design, visual execution, and engineering handoff. A specialist who only does visual work, or only does research, cannot cover that breadth. Hire the generalist who can hold the full product surface, then hire specialists once the work is large enough to divide.
Because specialist portfolios are easier to evaluate. A visual designer's work looks impressive immediately. A generalist's best work often looks unremarkable, because the interface got simpler and the flow got shorter. Founders who cannot assess design gravitate to the portfolio that is easiest to admire, which is precisely the wrong selection criterion for this hire.
When the product surface is genuinely narrow and the design problem is genuinely one thing. A data-heavy internal tool with no consumer surface may need interaction depth more than range. But that is the exception, and it should be a deliberate decision rather than the outcome of an easier interview.
The generalist versus specialist trade-off covers this decision in more depth, including how the answer changes at the second and third design hire.
What to look for when you are not a designer.
You do not need to judge craft. You need to judge evidence, reasoning, and collaboration, all of which are assessable without design training.
The one question that works without design expertise
Pick any screen in their portfolio and ask what they removed to get there. Good designers answer immediately and specifically, because subtraction is most of the work. Weak answers describe what was added. This question requires no craft judgement from you and is difficult to rehearse.
For a deeper structure, the portfolio evaluation framework gives founders a three-question walkthrough for a single case study.
Hiring your first designer? Tell us the product and the stage. We will come back within one business day on whether you need a generalist, a specialist, or a contractor first.
Discuss a mandate →Define what design owns before you hire.
Before the search opens, decide what design actually owns. Does it own user research? The design system? Visual branding? Front-end components? A designer hired without scope clarity will either overreach into territory nobody agreed they held, or underperform against expectations nobody wrote down.
Write it down, then say it in the interview
Scope is also a recruiting argument. Senior generalists choose roles on the basis of ownership more than on package, because the alternative is a large company where the lane is narrow. If you can describe precisely what this person will own, you are competitive against employers paying more.
The evaluation process.
Four stages are enough for a first design hire, and each one is designed to be run by a founder who is not a designer.
Do not skip the engineer reference
It is the same principle as hiring a product manager: the people downstream of the work see what the interview cannot. Ask whether handoffs were clear, whether the designer stayed engaged after the mockup was delivered, and whether they adjusted when something proved expensive to build.
Our design hiring practice runs this evaluation for founders who cannot assess design directly, and the reference stage is where most of the differentiation appears.
Where a specialist partner changes the outcome.
Portfolios reward presentation, so design hiring is easy to get wrong. A design-literate search partner evaluates thinking, collaboration and shipped work before you see a candidate.
Team profile → The design team is profiled before recommending which role to open first.
Beyond the portfolio → Candidates are assessed on process, decisions under constraint and engineering collaboration.
Leadership searches → Head of Design and VP Design roles run as founder-led executive search.
Market reach → Product designer searches reach passive candidates at companies with real design cultures.
Discuss a mandate →Real mandates, real numbers.
Seven roles across data science, research, full stack engineering and UI/UX design. Each ran as its own specialist search with one hiring bar, rather than a single high-volume funnel.
Four senior seats across frontend engineering, data science, product management and Salesforce architecture, each needing a different mix of technical depth and product context.
Building a design team that ships good work?
If you are hiring a first designer, a design leader or a specialist, we can show you the market and the right sequence for your team before any commercial conversation.
A senior team member responds within one business day. No pitch deck, no obligation.