Hiring a product designer when you don't have a design background is one of those situations where it's easy to get burned. You look at portfolios, everything looks polished, you pick the one whose work feels the most "premium," and six months later you realize they can't talk to users, can't ship under constraints, and spend three weeks perfecting a component no one asked for.
This guide is for founders and operators at small companies who need to make a smart design hire without a design expert on the team to help them. You can do this well. You just need a different framework.
Start with what you actually need
Before you write a single job post, get specific about the problem you're hiring to solve. "We need a designer" is too vague to hire well against.
Ask yourself:
- Are you pre-product or post-product? A designer hired to figure out what to build (0-to-1) needs completely different skills than one hired to improve a product that already has users.
- Do you need someone who can also do front-end? A product designer who can ship HTML/CSS or work directly in a design system is worth more to a small team — but they're harder to find and cost more.
- How much visual polish actually matters right now? If you're a B2B SaaS selling to operations managers, usability beats aesthetics. If you're consumer, brand and feel matter more.
- Will this person work alone or alongside engineers? Solo designers at small companies need to be comfortable making calls without a design manager above them.
Get this clarity before you post anything. It shapes every downstream decision.
What a product designer actually does (and doesn't do)
A lot of founders conflate roles that are genuinely different.
Product designer: Owns the full user experience — research, wireframes, high-fidelity mockups, prototypes, and working with engineers to ship. This is the role you probably want.
UI designer: Primarily focused on visual execution. Great at making things look good, less likely to be driving product thinking or doing user research.
UX researcher: Focused on discovery and validation — interviews, usability tests, surveys. Usually not shipping design files.
Graphic designer: Brand, marketing assets, print. Not the same as product.
For a company with fewer than 50 people, you almost always want a product designer — someone who can go from "here's a problem" to "here's a tested, shippable solution." The title you use in your job post matters because it filters who applies.
What to look for in a portfolio (even without design training)
Portfolios are where non-designers feel most lost. Everything looks good. Here's what to actually look at.
Look for process, not just output
Anyone can show you a beautiful final screen. You want to see how they got there. Look for case studies that show:
- What problem they started with
- What they learned from users or data
- What alternatives they considered
- Why they made the tradeoffs they did
- What happened after it shipped (did it work?)
If a portfolio is only final screens with no context, that's a yellow flag — especially for a senior or mid-level hire.
Look for shipped work
Mock projects and unsolicited redesigns are fine for junior designers building a portfolio, but for a hire who's going to be your only designer, you want evidence of real work that shipped under real constraints. Ask: "Is this live? Where can I see it?"
Look for range without chaos
A good product designer can work across flows, not just hero screens. Look for onboarding flows, empty states, error handling, mobile and desktop variants — the unglamorous parts of a product. If every piece in their portfolio is a hero shot, they might not have experience with the full surface area of a product.
The job description
Write your job post for the candidate you want, not the fantasy hire. If you load it with fifteen requirements and buzzwords, you'll get candidates who are good at applying for jobs, not candidates who are good at the job.
A strong product designer job post for a small company should include:
- A clear description of what the company does and where it's at (stage, team size, funding or revenue if you can share it)
- The specific problem this designer will own in the first 6 months
- Must-haves vs. nice-to-haves (keep must-haves short — three to five things)
- How design fits into your process (do engineers have autonomy? Is there a PM? Do you do user research?)
- Compensation range (post it — you'll get better applicants faster)
If you want help putting this together quickly, you can use our free job description generator to get a solid starting draft you can customize.
Salary: what does a product designer actually cost?
As of 2024, here's a rough market breakdown for a full-time product designer in the US:
- Junior (0–2 years): $70,000–$95,000
- Mid-level (2–5 years): $95,000–$135,000
- Senior (5+ years): $135,000–$180,000+
In lower cost-of-living markets or for fully remote roles with a national candidate pool, you can often find strong mid-level talent at the lower end of these ranges. In SF or NYC, expect to be at or above the top.
Contract or fractional designers are worth considering if you're not ready for a full-time hire. A good senior freelancer might charge $100–$150/hour, which sounds expensive but can be cost-effective for 10–20 hours/week versus a full-time salary plus benefits.
How to evaluate candidates without design expertise
You don't need to know design to run a good process. You need to ask the right questions.
The portfolio walkthrough
Ask the candidate to walk you through one project from their portfolio — ideally something they picked because it shows how they think. Then ask:
- What was the original problem?
- What did you try that didn't work?
- What constraints were you working under?
- What would you do differently now?
You're listening for clarity of thinking, honesty about tradeoffs, and whether they can connect design decisions to outcomes. A designer who can't explain their choices simply is a designer who may not have made deliberate choices.
A paid work sample (keep it small)
For finalists, give them a scoped problem from your actual product — something that would take 3–5 hours. Pay them for it ($150–$300 is reasonable). You're not looking for perfection. You're looking for:
- Did they ask clarifying questions before starting?
- Did they make assumptions explicit?
- Can they explain their thinking in the debrief?
Avoid unpaid "take-home projects" that take 10+ hours. It filters out the best candidates who have options.
Involve someone who uses the product
If you can, have a customer, a power user, or even a team member who represents your target user look at candidate work and give a gut reaction. This isn't a vote — it's signal.
Common mistakes founders make hiring designers
Hiring for taste instead of craft. You like how their portfolio looks. But do they understand your users? Can they solve problems systematically?
Skipping the process conversation. A designer who's only ever worked in a mature design org with dedicated researchers, PMs, and design systems will struggle in a 10-person startup where they have to do everything themselves.
Underleveling to save money. A junior designer without guidance will spin. If you can't mentor them, hire mid-level at minimum.
Not giving them access to users. Designers who can't talk to users make decisions in a vacuum. Make sure you're set up to support this — it's not just on them.
Where Penroll fits
Penroll is built for exactly this kind of hire — a small team, a specific role, and a founder who doesn't want to spend three weeks figuring out how to write a job post or screen a stack of resumes. You can generate a tailored product designer job post, get structured screening criteria, and move faster without needing an in-house recruiter. It's the hiring infrastructure small teams don't have — without the agency markup.