1 min lesson
Build each story this way
Answer "Why does the Result in an SDR's STAR story need a metric and why is one honest failure story worth keeping in the bank?" Use one lesson detail to support it.
Step 1 of 2
Build each story this way
- 1Situation and Task, in two sentences. Enough to make the stakes legible. Skip the org chart.
- 2Action, in the first person. What you did, the decision you made, the tradeoff you chose. This is most of the airtime.
- 3Result, with a number. Meetings booked, reply rate, quota attainment, conversion lift or accounts opened.
- 4The honest coda. One sentence on what you'd do differently. This is what makes the rest believable.
"We had a tier of mid-market accounts nobody worked because they'd been marked low-fit. I decided to prove one could open. I found the VP of Engineering quoted in a podcast about their scaling pain, dropped my templated opener and led with that exact problem plus one specific idea, then followed up twice with something new each time. It booked on the third touch and became a closed opp two quarters later. What I'd change: I almost ran the generic sequence first, and that account would have ignored me - trust the research earlier."
Learn more
Advanced table
Tag every story so you can deploy on demand
Tag every story so you can deploy on demand
- Story
- Cold-sourced the logo nobody worked
- Primary value
- Ownership
- Result you'll cite
- Booked from a cold list, became a closed opp
- Story
- The week I got crushed
- Primary value
- Resilience
- Result you'll cite
- Changed my opener, recovered the month
- Story
- Rewrote my pitch after coaching
- Primary value
- Coachability
- Result you'll cite
- Reply rate roughly doubled the next sprint
- Story
- Built the sequence from nothing
- Primary value
- Self-starter
- Result you'll cite
- First repeatable cadence the team adopted
- Story
- Hit quota in a brutal quarter
- Primary value
- Grit / activity
- Result you'll cite
- Top of the board on conversations-to-SQL
- Story
- The deal I lost on a thin reason
- Primary value
- Honesty
- Result you'll cite
- Named what I misread, fixed the qualifying
| Story | Primary value | Result you'll cite |
|---|---|---|
| Cold-sourced the logo nobody worked | Ownership | Booked from a cold list, became a closed opp |
| The week I got crushed | Resilience | Changed my opener, recovered the month |
| Rewrote my pitch after coaching | Coachability | Reply rate roughly doubled the next sprint |
| Built the sequence from nothing | Self-starter | First repeatable cadence the team adopted |
| Hit quota in a brutal quarter | Grit / activity | Top of the board on conversations-to-SQL |
| The deal I lost on a thin reason | Honesty | Named what I misread, fixed the qualifying |
Even when a result was a team effort, say "I." Not to erase teammates, but because the interviewer is grading your contribution. "I researched the persona, I wrote the email, I booked the meeting" is the signal. "We worked it together" hides exactly what they need to hear.
Vague stories read as invented. "I'm just really persistent" with no scene fails the screen. Make each story specific and metric-backed - a named persona, the actual opener you used, the number it produced.