Skip to lesson
Exit
Study Design & Method Fit1 / 4

1 min lesson

Recruiting expert developers

Tell someone how to act on this idea: "In dev-tools research, the study design is easy and recruiting is the bottleneck."

Step 1 of 4

In dev-tools research, the study design is easy and recruiting is the bottleneck. Treat recruiting as a first-class design problem or your beautiful plan dies waiting for participants.

Cursor's users are professional developers: time-poor, skeptical of being “researched,” and immune to a $25 gift card. They don't answer panel screeners and they can smell a generic study. Your sourcing and screening choices shape the validity of everything downstream, so they belong in the plan, not in an afterthought.

Learn more

Advanced table

No single source is unbiased

Source
In-product intercept
Strength
Catches users mid-task, real context, fast
Built-in bias
Skews to active, engaged users; misses the churned and the lurkers
Source
Power-user / opt-in list
Strength
High-signal, articulate, willing
Built-in bias
Over-represents enthusiasts; their needs aren't the median developer's
Source
Community / Discord
Strength
Reachable, passionate, fast to respond
Built-in bias
Vocal-minority effect; loud opinions aren't prevalence
Source
Sales / CS intros
Strength
Access to enterprise and decision-makers
Built-in bias
Filtered through the account relationship; may be on best behavior
Source
External research panel
Strength
Can hit specific stacks/roles you can't reach internally
Built-in bias
Professional participants; verify they're real working developers

No single source is unbiased; pick the source whose bias is harmless for your question or sample across several.