2 min lesson
The user is a professional developer
Give a plain answer to "Why does studying Cursor's developer user differ from consumer UXR and how should that change your research focus?" Then ground it in one lesson detail.
Step 1 of 2
Cursor's user is an expert developer working in an AI-native code editor. Studying that person is a different craft from consumer UXR and the interview will read you for whether you know the difference.
Cursor is a VS Code fork wired around proprietary models, so the surface is familiar to any engineer but the behavior is new. The people using it are technical, opinionated and time-poor. They are skeptical of fluffy research and they will notice immediately if your questions reveal you've never actually written code in the tool.
- Expertise
- They know their craft deeply - surface usability is table stakes, not the story.
- Recruiting
- Hard to reach and protective of their time; a no-show costs you a week.
- Skepticism
- They sniff out fluff fast; credibility is earned by speaking their language.
- What they value
- Speed, control, trust in AI output and staying in flow.
Translate “want, need and love” into this user's terms and it stops being abstract. Love here is rarely about a cleaner button. It's whether Tab predicts the edit they were about to make, whether they trust an agent's diff enough to accept it without reading every line and whether the tool keeps them in flow instead of pulling them out to babysit it.
Can they find the feature and complete the task?
First-run impressions and learnability dominate.
Does it fit a deep, idiosyncratic workflow under real pressure?
Edge cases, trust in AI output and long-run flow dominate.