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.
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.
Why founders hire the specialist anyway
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 a specialist is the right call
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.
- Shipped product evidence: can you find the feature in a live product and use it yourself? Portfolio cases that exist only as Figma concepts are a warning, not a disqualification, but the ratio matters.
- Process rather than output: ask what they started with, what changed during the project, and what they would do differently. Designers who shipped can answer specifically; designers who presented cannot.
- Engineering collaboration: ask how the design changed when engineering pushed back. A designer who has never been pushed back on has never shipped anything with real constraints.
- Comfort without infrastructure: a designer from a thirty-person design org has operated in one lane with a research team and a design system. Your first designer has no lanes and no system.
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.
| Decide before the search | Typical answer at seed to Series A | Why it matters |
|---|---|---|
| Does design own research? | Yes, lightweight and continuous | Otherwise nobody talks to users and design becomes decoration |
| Does design own the design system? | Yes, but built minimally and late | Premature systems consume the first three months |
| Does design own brand and marketing surfaces? | Sometimes, and it must be explicit | This is the most common source of scope conflict |
| Does design write front-end code? | Optional, and never assumed | Assuming it silently narrows your candidate pool |
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.
- Portfolio review: one case study deep-dive rather than a tour of everything, using the removal question and the what-changed question.
- Live design exercise, optional for senior candidates: a small, real problem from your product, timeboxed and paid if it runs long.
- Engineer reference checks: collaboration quality and handoff clarity, asked of engineers who built their designs.
- Founder conversation: mutual fit, scope, and what design will mean at this company in twelve months.
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.
Cannot assess design yourself?
We run portfolio review and engineer references for founders hiring design for the first time. Tell us the role and we will scope it.
Start with the brief →