Hiring your first UX researcher: when a startup needs one

hiring-your-first-ux-researcher:-when-a-startup-needs-one

Updated November 2026

Hire a dedicated UX researcher when product decisions start stalling, or get settled by whoever argues hardest, because your designers and product managers are too busy shipping to talk to users. That point usually comes once you have several designers and PMs spread across teams, or when you move into a new customer segment or market. Before then, a product designer with research habits covers it, and the first researcher you hire should be a generalist who mixes methods.

The signal is stalled decisions, not headcount

Our guide to hiring your first product designer explains why a designer who can run interviews comes before a researcher. This page picks up later, when that arrangement starts to creak. The trigger is the moment research becomes the thing everyone agrees matters and nobody has time to do.

An illustrative example runs through this page. Ravi is VP of product at a Series B property-management SaaS company with four product designers and five PMs across three teams. The company is about to sell to large portfolio landlords as well as small letting agents, and roadmap meetings have turned into debates.

Signs you need a researcher (three or more is a good prompt)
☐ Roadmap arguments get settled by quoting one sales call.
☐ Designers skip discovery to hit sprint dates, then rework after launch.
☐ Two teams interview the same customers in the same month and never share notes.
☐ You are entering a segment or market where the team has no instinct for the user.
☐ Churn reasons and support tickets pile up and nobody turns them into findings.

Ravi ticked four of the five. The one that convinced his CEO was the new segment, because nobody on the team had ever run a large rental portfolio.

Researcher, research ops or more research time

Three options solve different problems, and all three get called "doing more research".

OptionWhat it solvesFits whenWatch out for
Protected research time for designersTeam-level questionsDiscovery is skipped under sprint pressureThe time vanishes in the first busy month
Research operations hire or contractorFinding participants, consent, toolsDesigners run good studies but lose days finding peopleNobody owns cross-team questions
Generalist UX researcherCross-team questions, new segmentsBig questions belong to no single teamBecoming a usability testing desk

For a first hire, choose a mixed-methods generalist who is at ease with interviews, field visits, usability tests and a simple survey, who picks the method to suit the question. A quantitative specialist or a one-method expert makes a better second hire, once you know where the gaps are.

Ravi had considered research ops first. His designers could reach customers easily enough, so an ops hire would have fixed a problem he did not have.

What the first 90 days should produce

Days 1 to 30
A backlog with the PMs
List the open decisions each team faces and rank them by the cost of getting them wrong.
Days 31 to 60
Repeatable recruitment
A reliable way to reach customers, prospects and churned users, agreed with sales and success.
Days 61 to 90
One changed decision
A study whose findings move something on the roadmap, presented in the planning meeting.

The backlog is the step founders skip. Without it, the researcher spends month one taking requests from whoever asks first, and month two as the usability testing team. A shared list of decisions, owned with the PMs, puts research inside planning.

Finding participants is the hidden work. In B2B software, customers belong to account managers who are protective of them, so agree with your sales and customer success leads upfront how the researcher may contact accounts and how often. At Ravi's company the head of customer success set up a rotation so no landlord was asked twice in a quarter.

The 90-day test is a decision that changed, or got made faster, because of a study. Ravi's first researcher, Noor, ran field visits with six portfolio landlords and learned they cared far more about reporting to property owners than about the tenant app the roadmap had put first. The tenant app moved back a quarter, and a two-month debate ended in one meeting.

How to assess a UX researcher

Write the job scorecard first, with outcomes that name decisions the role will inform rather than reports it will produce.

Ask for a portfolio walk-through of one study that changed a decision, and let the candidate choose it. Then ask who disagreed with the findings and what happened next, which shows whether they can move people more senior than them.

Weak walk-through
Explains the method in detail and the outcome is "we shared a report". Every study is a usability test of a finished design. Findings arrive as a long list with no priority.
Strong walk-through
Starts with the decision the study had to inform. Explains why they chose that method over a cheaper one. Says what changed, what was ignored and why, and how they got PMs into the sessions.

Then set a short research plan exercise of a couple of hours at most. Give a real question from your backlog, such as whether larger landlords would pay for owner reporting, and ask for a one-page plan setting out who to study, how to recruit them, what to leave out and how long it takes. Review it live with a PM and a designer.

Red flags: work that ends in long reports nobody reads, a portfolio made only of usability tests, and a candidate who has never had to find their own participants. At a startup, nobody else will find them.

The first researcher should report to whoever owns the roadmap across teams, usually a head of product or design, as our guide to hiring a head of product describes. Placed inside one team, they end up working only for that team.

Where Funded.club fits

We are a fixed-fee recruiting partner for funded startups and fast-growing teams across North America, Europe and APAC, and since 2019 we have helped 500+ startups from Seed to Series D. One dedicated recruiter runs each search end to end, including support through offer, with first screened candidates within 7 days.

The fee is agreed upfront, averaging 6 to 9% of salary against the 20 to 25% typical of contingency recruiters. For an illustrative UX researcher on $125,000, it is $11,500, with part paid as an advance and the balance when the candidate accepts. All bands are on our pricing page.

Frequently asked questions

Should a startup's first design hire be a UX researcher?

Usually not. A product designer with research habits can run interviews and turn the findings into shipped work, which a small team needs more. A dedicated researcher makes sense later, when several designers and PMs are working across teams.

How many designers should we have before hiring a UX researcher?

There is no fixed number. The better signal is whether product decisions are stalling or being made on opinion because nobody has time to talk to users. A new segment or market can justify one earlier.

What should a first UX researcher deliver in 90 days?

A research backlog agreed with the PMs, a repeatable way to recruit participants, and at least one study that changed or sped up a roadmap decision. If all you have after 90 days is reports, the role needs resetting.

Worth a brief chat about your next hire? Book a free call.

Hiring after a funding round?

First candidates in 7 days. Fixed-fee, no commission.

See pricing Book a free call Try the Growth Planner