Product Designer
Frequently asked questions about hiring for the Product Designer role, plus the mistakes that most often derail it.
Common hiring mistakes for this role
Hiring on visual portfolio instead of discovery depth
A designer with flawless Dribbble shots that only show the finished UI is not automatically productive at an SMB. Polished pixel work delivers little signal about the ability to frame a problem, talk to users and decide under uncertainty. In the portfolio review, weight the process (hypotheses, tests, iterations, measured impact) more heavily than pixel polish. Profiles with one or two deeply explained case studies beat profiles with ten pixel shots.
Confusing UX Designer and Product Designer
The titles UX Designer, UI Designer, Interaction Designer and Product Designer are used inconsistently in the German market. A Product Designer at an SMB typically covers discovery, interaction, visual and handover to frontend; a pure UX researcher or pure UI designer covers only part of that. Describe the real scope in the ad (share of discovery, interaction, visual, system maintenance) and check in the portfolio review that the profile covers all areas. Otherwise you pay for one role and get half of it.
Demanding multi-day take-home assignments
A design assignment of 8 or more hours actually takes 20-24 hours (with emotional investment in visual polish), demotivates the best profiles (who have other options in parallel) and delivers no better signal than a well-constructed 2-3 hour task. You want to measure the quality of the reasoning and the discovery, not the completeness of a finished UI. Cap the expected time explicitly and accept low-fidelity solutions (wireframe plus rationale) instead of polished mocks.
Hiring a senior designer from a corporate for an early-stage SMB
A designer with 8 years at a corporate (SAP, mature Zalando, mature Delivery Hero) learned to work in an already-set frame: roadmap from the top, a dedicated research function, a maintenance slot for the design system, engineering within reach, metrics instrumented. At an early-stage SMB (under 30 people, PMF not yet stable) none of these conditions hold. The profile arrives expecting structure, struggles to decide in the chaos and loses motivation within 3-6 months. Look instead for a profile that has already lived through a PMF phase; it will be able to navigate uncertainty.
Underestimating cross-functional communication
A Product Designer at an SMB talks almost daily with PMs, engineers, sometimes directly with management, sales or customers. Anyone strong visually but weak cross-functionally produces friction: misread briefs, opaque handovers, conflicts with frontend, defensive critique sessions. Assess communication explicitly in the interview (situational questions with PM and engineering angles, real-time critique of a mockup, explaining a design decision in everyday language).