Hiring a product designer at seed, and when not to

Note: The first design hire is one of the easiest to get wrong at seed. Here is what the role actually needs to be, how to interview for it, and the cases where you should not hire at all.
We sell a design subscription, so treat the following with the scepticism it deserves. It is still true: sometimes the right answer at seed is to hire someone, and a partner who will not tell you that is not being useful.
The trouble is that the first design hire is one of the easiest roles to get wrong, because most founders have never managed a designer and the job title covers about six different jobs.
What the role actually is at seed
At seed you are not hiring someone to make screens. You are hiring someone who can decide what to build next, talk to users without a researcher, design the thing, work with engineers to get it shipped, and hold the brand together while doing it. That is a generalist with real product judgement, and there are far fewer of them than there are people with the title.
The most common mistake is hiring for the portfolio you liked rather than the work you have. Beautiful case studies from a large company usually mean someone who worked inside a mature design system with a researcher, a content designer and a product manager beside them. Take those away and the work often changes shape.
When hiring is the right call
- Design work is constant rather than occasional, and it is on one product you own.
- You have eighteen months or more of runway, so the ramp is affordable.
- A founder can give the role real time, because a designer with no direction at seed will produce work nobody asked for.
- The product is the company. If design quality is the difference between winning and losing, that capability belongs inside.
- You can genuinely attract someone senior. Equity, the problem, and the people are what you are selling, and if none of those are compelling yet, be honest about it.
When it is not
- Design is currently your bottleneck. A hire does not solve a bottleneck for five to six months once you count search, notice period and ramp.
- The need is spread across product, brand, website and pitch material. One person will not cover all of that to a senior standard, and hiring for the average leaves you weak everywhere.
- The work is genuinely lumpy, heavy before a raise or a launch and quiet after.
- You cannot manage the role. An unmanaged senior designer is an expensive way to get work you did not want.
- Runway is under a year. Fixed headcount against a short runway is a decision you may have to unwind in the worst possible month.
We have set out the full loaded comparison, including on-costs, recruitment and ramp, in a separate piece on what product design costs. The short version is that the salary is the smallest part of the number.
Writing the role
Most seed design job specs are a list of tools and a wish for a unicorn. Two changes make a real difference. Name the actual problem rather than the responsibilities, because senior designers pick companies by the problem. And be specific about the breadth, so someone can tell whether the role is product design with a bit of brand, or brand with a bit of product. Those attract different people, and the mismatch is where a bad hire starts.
Say what the first ninety days look like too. It is the fastest way to filter out people who want a bigger machine around them than you have.
Interviewing for it
Portfolios show taste. They do not show judgement, and judgement is what you are buying. A few things that work better:
- Ask them to walk through a project where the first direction was wrong. What they noticed, and what they did about it.
- Give them a real, current problem from your product and talk it through together for an hour. You are watching how they think, not collecting a solution.
- Ask what they would need from you to do the job well. Good senior people have a clear answer and it usually involves access to users.
- Ask about something they shipped that failed, and whether they know why. Anyone who has only shipped successes has either been lucky or is not counting.
- Do not set a large unpaid take-home. The best people will decline and you will have filtered for availability rather than quality.
If you cannot hire yet
The gap between needing senior design and being able to hire it is where most seed teams actually live. The options are the usual three: a freelancer for a defined piece of work, an agency for a project with a clear end, or a subscription for continuous senior work across surfaces without fixed headcount. Each trades something, and we have compared them honestly elsewhere.
The thing worth avoiding is the middle path where nobody owns design, everyone contributes a little, and the product slowly becomes six products. That costs more to undo than any of the three options cost to start.
That is the exact gap Anyday was built for. Senior designers embedded with your team across product, brand and web, output from the first week, no recruitment or ramp, and you can pause when the runway needs it. And if after reading the above you think you should hire, we will tell you so.
- At seed you are hiring product judgement and range, not someone to make screens.
- Hire when the need is constant, on one product, you have runway, and a founder can manage it.
- Do not hire to fix a bottleneck. The role is five to six months from spec to real output.
- Interview for judgement: a wrong first direction, a real current problem, and something that failed.


