2 min lesson
Speak the developer's language, show the product
Make the call in this situation: "Rewrite the report-shaped finding 'Users had trouble with the settings page' into a decision-shaped headline you could put at the top of a one-pager." Explain what supports it.
Step 1 of 3
Speak the developer's language, show the productcredibility is in the details
- Use the user's own words and the product's real surfaces - say "⌘K", "the Agent tab", "Tab completions", not "the input affordance."
- Show the real product moment: a clip of the actual editor mid-task beats a paraphrase every time.
- Quote verbatim. "It rewrote a file I didn't ask it to touch" carries weight a tidy summary drains away.
When the portfolio interviewer asks how you presented a study, do not say "I made a deck." Say "I sent a five-line Slack post with the call and the data, because the team was mid-sprint and needed to decide that day - the deck would have been read by no one." Choosing the lightweight artifact on purpose signals you understand Cursor's pace.
Reaching for a 40-slide deck by default reads as big-co habit at a flat startup. It is not that decks are banned; it is that the artifact should be chosen for the decision. Defaulting to the heaviest format is the tell that you over-process.