The Generalist vs Specialist Trade-off
| Generalist | Specialist |
|---|
| Coverage | Research, interaction, visual execution, handoff | One dimension of design depth |
| Best stage | 0 to 10, pre-design-team | 5-person design team with division of labour |
| Portfolio signal | Wide work at varying depth | Deep work in one discipline |
| Risk | Depth gaps in specialist areas | Coverage gaps across the product |
| First designer? | Yes | No |
What to Look For
- Has shipped a product, not just designed one. Portfolio should show design decisions made in production, not just polished Figma files.
- Has worked without a large design team. A designer from a 30-person design org has optimised for one lane.
- Can explain why they made design decisions, not just what they made.
- Has worked closely with engineers, not thrown files over a fence.
The design hiring practice evaluates first-designer candidates on range of work and production evidence, not visual polish alone.
The Portfolio Trap
A visually stunning portfolio does not tell you whether the designer can do user research, handle engineering constraints, or make fast decisions in a small team. Ask for a case study of a shipped feature: what did they start with, what did they discover, what changed, and what shipped? That story tells you more than the portfolio.
Product designers in India who have worked at early-stage startups are often the strongest candidates for first-designer roles precisely because they have operated without infrastructure.
The first designer hire shapes the design practice for every hire after it. Getting a generalist who can build the foundation, the design system, the research habit, and the engineering relationship, is worth the extra time in the search. The design hiring practice has run this search at seed and Series A, and the instinct to hire a specialist first is the single most common mistake we see.
Making your first designer hire?
Send us the product and we will return a profile recommendation within a week.
Book a Consultation →