Your first designer should be a generalist.
The first designer at a startup does not get to focus. They do user research, interaction design, visual execution, and handoffs to engineering, sometimes in the same afternoon. Here is how to hire for that reality.
Most founders hire a specialist as their first designer because a specialist's portfolio is easier to evaluate. The result is a designer who does one thing well and none of the other things at all.
If you have ten minutes before a hiring review, read only this.
What the first product designer actually does.
At a small startup the first designer owns the entire design surface: flows, visual language, component decisions, research conversations with users, and the Figma files that engineering ships from. A specialist who only does visual polish or only does research is not the right shape for that job.
Planning a hire like this? Tell us the role and we will map the right approach within a week.
Book a consultation →The generalist vs specialist trade-off.
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.
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.