Skip to lesson
Exit
Behavioral & Why Cursor1 / 2

2 min lesson

Build each story this way

Explain your answer to "Why is a well-told 'lost deal' story one of the strongest things you can bring to a Cursor values round and what makes it land versus fail?" Add one concrete detail from the lesson.

Step 1 of 2

Build each story this way

  1. 1Situation and Task, in two sentences. Enough to make the stakes legible. Skip the org chart.
  2. 2Action, in the first person. What you did, the decision you made, the tradeoff you chose. This is most of the airtime.
  3. 3Result, with a number. Deal size, cycle time, attainment against quota, net expansion or seats landed across the org.
  4. 4The honest coda. One sentence on what you'd do differently. On a truth-seeking team, this is what makes the rest believable.
Say it like this

“When I joined my last company I was the first rep in a brand-new region - no accounts, no pipeline, no playbook, just a number to hit. So I built the motion from scratch: I picked a dozen target accounts by engineering headcount and stack, wrote the outbound sequences myself and led with a hands-on technical proof-of-value instead of a pitch to earn a champion inside each one. From that champion I multi-threaded up to the VP Eng and built the business case around onboarding time, not a feature list. I ended up self-sourcing about 80% of my pipeline that year and closing 116% of quota, and two of those accounts became our regional reference customers. The one thing I'd change: I'd qualify the security review earlier - I under-weighted it on one deal and it slipped a full quarter.”

Interview move

Even when a win was a team effort, say “I.” Not to erase the SE or CS, but because the interviewer is grading your contribution. “I found the champion, I built the business case, I multi-threaded to the CTO” is the signal. “We worked it together” hides exactly what they need to hear.

Watch out

Vague stories read as low-rigor to an enterprise sales bar. “The customer was thrilled” with no number fails the screen. And a lost-deal story with no real loss is a tell - name what you actually misread, a stakeholder you didn't multi-thread or a security objection you under-weighted and the concrete change you made because of it.