2 min lesson
Form your product theses
Use "Form your product theses" to tell the cases apart, then choose a response for each one.
Step 1 of 3
The “discuss ideas” round rewards a point of view, not a framework. Walk in with real opinions about Cursor's product, sequenced and pressure-tested and you've already separated yourself from candidates who recite a prioritization matrix.
Build your theses in three buckets: paper cuts you've personally hit, one bigger bet with a measurable hypothesis and a clear statement of what you would not build. Ground every one in the test that defines this role - does it become something developers use every day?
Learn more
Full explanation
Form your product theses
- 1Surface. Keep a running list from your own daily use and from public developer chatter; a paper cut you can name from memory is more credible than one you invented.
- 2Score. Rate each on how often it hits and how much trust it costs when it does - a daily annoyance that makes the tool feel wrong outranks a rare cosmetic glitch.
- 3Sequence. Ship the high-trust-per-effort fixes first to build momentum, batch related cuts and don't let a single hard one block the easy wins behind it.
- 4Close the loop. Note how you'd confirm the fix landed - a drop in the related support theme or a usage metric, not just a closed ticket.