Most founders ask founding designer candidates about their process.
Wrong question.
After 10 years building design teams at Meta, BCG, and fast-growing startups, I've sat in on a lot of design interviews. Founders ask the same things every time. Walk me through your process. How do you handle feedback from engineers? What does your Figma workflow look like?
All reasonable. None of them the most important question in the room.
There's one question I always tell founders to ask instead:
"What's the biggest user problem you're not solving?"
It sounds simple. But the answer separates two completely different types of designer.
Production designer vs. product partner
A production designer answers with a tool, a constraint, or a timeline. "We didn't have bandwidth to tackle onboarding." "The design system didn't support it." "We shipped what we could scope in the sprint."
A product partner answers with a user insight. They'll describe a specific person, a specific friction point, and a specific gap between what the product does and what the user actually needs. And they'll probably follow it up with a question back to you.
That distinction is everything when you're hiring your first designer.
At the early stage, you don't need someone who executes briefs. You need someone who sees around corners. Someone who challenges your assumptions about what the product should do, advocates for the user when everyone else is staring at the roadmap, and treats design as a business lever, not a deliverable.
Why the portfolio only tells half the story
Portfolios are polished. They show you the work that made it through, cleaned up and presented in the best possible light. They don't show you how a designer thinks about what didn't get built, what trade-offs they pushed back on, or whether they were genuinely curious about the people using the product.
That one question gets at all of it.
The portfolio tells you what they've made. The question tells you how they think.
What to listen for
When you ask it, pay attention to a few things:
Do they think in users or outputs? The strongest candidates describe a real person with a real problem. Weaker candidates describe a feature gap or a design debt item.
Do they show curiosity or acceptance? A great founding designer is bothered by unsolved problems. They've thought about them. They have a point of view. If the answer comes too easily and too cleanly, that's worth noting.
Do they turn it back to you? The best candidates use the question as an opening. They want to know what you think the biggest unsolved problem is. That instinct to collaborate and align, rather than just answer, is exactly what you want in a creative partner.
The broader principle
Hiring a founding designer is different from hiring any other designer. You're not hiring someone to join a system. You're hiring someone to build one.
That requires a specific kind of person. Comfortable with ambiguity. Fast without being sloppy. Able to hold the user's perspective while translating it into something engineers can build and founders can sell.
One question won't tell you everything. But it'll tell you more than the portfolio review, more than the process walkthrough, and more than the Figma skills test.
Ask it in every founding designer interview. Then just listen.
Carl Wheatley is the founder of X2Talent, a boutique recruiting firm placing founding designers, product designers, and the engineers who work closest with them. A former designer himself, he spent 10 years building design teams at Meta, BCG Digital Ventures, and fast-growing startups, and now works with companies across the SF Bay Area and NYC.
Hiring your first founding designer? Get in touch.
Looking for a new role? Join my designer network so I have your up-to-date info when the right opportunity comes up.