1 min lesson
One Cursor friction you'd research
Name the parts in "One Cursor friction you'd research" and give the practical job of each one.
Step 1 of 3
One Cursor friction you'd researchthis is the authenticity proof
Have a real friction you've personally hit, stated as a researchable hypothesis with a method. This single answer does more to prove you use Cursor than anything else in the loop.
Worked example
- Friction
- Developers hesitate to let the Agent edit a shared production repo unsupervised
- Hypothesis
- Trust is gated by visibility of blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition., not by raw model accuracy
- Quick test
- 5 moderated sessions on multi-file edits + revert-rate telemetry split by repo stakes
- Decision it informs
- Whether to invest in a richer diff-preview before pushing auto-apply
Specific, falsifiable, tied to a roadmap call. That's the answer that lands.
Learn more
Full explanation
Three senior questions back
Three senior questions backasked questions reveal level
- "What research has actually changed a roadmap decision here in the last quarter and what made it land?"
- "Where does the team currently trust intuition over research and is that the right call?"
- "As the research function grows, what's the first ritual or piece of infrastructure you'd want built - and would I own that?"
Watch out
The fatal tell is a why-Cursor answer with no first-hand product detail. "I love AI tools and your mission is inspiring" is what someone says who hasn't installed it. Anchor on a concrete moment of your own usage - a specific feature, a specific friction - or the authenticity read fails no matter how strong your craft is.