2 min lesson
The demo-back round (Cursor-specific)
Explain the order in "The demo-back round (Cursor-specific)", then say how you would verify the result.
Step 1 of 2
This is the round that filters marketers who talk about products from marketers who actually use them. Every GTM hire at Cursor demos the product back during the process - you walk the panel through Cursor as if pitching or teaching it to a developer.
It is not a quiz on features. It is a sample of your core job: turning a complex AI + developer workflow into a narrative that lands with a skeptical technical audience. The panel is watching whether you reach for the value or the click sequence.
Build a tight 5-10 minute live demo around one real workflow you've done yourself. Agent on a multi-file refactor, Tab in a real edit loop or codebase Q&A to get oriented in an unfamiliar repo all work. Pick the one you can narrate without thinking about the keyboard.
- 1Open with the job-to-be-done. Name the developer's real problem first: “You've inherited a 200k-line repo and you need to make a cross-cutting change without breaking three other things.”
- 2Show the aha, not the menu. Drive the one moment where the value lands - the agent making a correct multi-file edit, Tab completing the change you were already reaching for. Let it breathe.
- 3Narrate value over clicks. Say why each step matters to the developer, not what button you pressed. The panel can see the screen; they're listening for the framing.
- 4Address the skeptic's objection out loud. “A developer will ask: can I trust this diff? Here's how I verify it before accepting” - naming the doubt is more credible than hiding it.
- 5Close on the so-what. One sentence on why this changes the developer's day, not a feature recap.
Rehearse it end to end and prepare a backup workflow in case your first one misbehaves live. Practice recovering gracefully - fumbling your own tools under light pressure reads as someone who doesn't really build with them.