UX Researcher
Frequently asked questions about hiring for the UX Researcher role, plus the mistakes that most often derail it.
Common hiring mistakes for this role
UX research is a comparatively young function in the German SMB market; the most common hiring mistakes arise from an unclear role definition and from confusion with adjacent disciplines.
Confusing UX research and market research
Market research answers questions about the brand, the market and buying behavior; UX research answers questions about the use of a concrete product or feature. The methods overlap in part (interviews, surveys), but the questions and success metrics do not. A classic market researcher without product application typically struggles with pace (UX research works in sprint cycles, not quarterly studies) and with the direct connection to design decisions. Describe the product-discovery focus explicitly in the posting and check in the portfolio that the studies led to product decisions.
Hiring pure usability-test profiles
A researcher who has run exclusively moderated usability tests covers only part of the function. At an SMB with a single researcher, discovery interviews, lightweight surveys, analytics synthesis and occasionally diary studies are also expected. Check the method breadth explicitly in the portfolio (at least 3 different methods) and in the method review (the justification of the method choice per study).
Hiring a senior researcher from a large company for an early-stage SMB
A researcher with 8 years at a large company (SAP, a mature Zalando, a mature Delivery Hero) has learned to work within an already established frame: a dedicated ResearchOps team, an own recruiting pool, an established repository, clear collaboration with several designers and PMs. At an early-stage SMB (under 30 people, PMF not yet stable) none of these conditions is met. The profile arrives expecting structure, struggles with recruiting on their own, building a repository from zero and deciding in chaos, and loses motivation in 3-6 months. Look instead for a profile that has already lived through a build-up phase; they will be able to navigate through uncertainty.
Underestimating stakeholder impact in the interview
A researcher at an SMB talks almost daily with PMs, designers, engineers, sometimes directly with management. Anyone who is methodically strong but weak in stakeholder impact produces studies that disappear into the repository: correct findings that never lead to product decisions. Assess stakeholder impact explicitly in the interview (situational questions with a PM and engineering reference, the explanation of a research recommendation in everyday language, concrete examples of studies with a documented follow-up decision).