"Sell me this pen" is still the most famous of all sales role play interview scenarios, and it's a good illustration of what goes wrong with the rest. There's nothing to discover, so it rewards a practiced pitch. And the buyer is whoever happens to be interviewing that day, so it can't compare two candidates anyway. This piece is for recruiters and sales hiring managers who run role plays across SDR, AE and account manager reqs. You'll get a buyer card format that holds the buyer still, eight scenarios built on it, one written out in full, and a scorecard weighted by role.
My bias, since I'm about to argue for standardizing the buyer. Skillvee is a 60-minute "day at work" simulation that replaces the recruiter phone screen and the first interview round. The candidate solves a real challenge, talks to AI teammates to get the information they need, and defends their decisions on a call, while the screen is recorded. It measures how someone works: communication, collaboration, agency, AI leverage, problem solving, quality of output and time management. Our sales simulation runs an AI buyer that plays the same arc for every candidate, so I'm not neutral about the problem below.
Why most sales role play interview examples don't compare candidates
The hiring manager playing the buyer gets easier as the day goes on and as they start to like someone, which I've argued at length in the sales hiring assessment tools piece. Nobody's cheating. Playing one skeptical buyer five times while judging is just hard.
The scenario lists that rank for this topic don't fix that, because most of the ones I've read were written for training reps. A training scenario can flex to fit the rep. A hiring scenario has to hold still, since the whole point is that two candidates faced the same thing.
The fixed-buyer card
Every scenario below uses the same card. The person playing the buyer reads it before each candidate, and the card, not their mood, decides what they say.
- Buyer: name, title, company, and one line of situation.
- Candidate brief: what the rep sells and what they get to read, and nothing that gives away the hidden pain. The cards below assume you sell B2B software; swap in your product.
- Hidden pain: the real problem the buyer won't volunteer.
- Key question: the kind of question that earns the hidden pain. Asking about the current process and what it costs usually counts. Pitching features doesn't.
- Scripted objection: one pushback, and the minute it arrives.
- Win condition: what a strong call ends with, normally a specific next meeting with a named person.
Eight sales role play scenarios for interviews
| # | Scenario | Role | Hidden pain | Key question | Scripted objection |
|---|---|---|---|---|---|
| 1 | The happy incumbent | AE | Their current vendor's renewal price jumped and nobody has told the CFO yet | Asking what's changed with the current tool this year | Minute 8: "Honestly, we're pretty happy with what we have." |
| 2 | The budget freeze | AE | The freeze has one exception: anything that cuts headcount cost this quarter | Asking what the company is prioritizing right now | Minute 6: "There's no budget until next year." |
| 3 | The delegate | AE | The contact was told to "look into options" and can't sign anything | Asking who else is involved and how they'd decide | Minute 10: "Just send me pricing and I'll pass it along." |
| 4 | The gatekeeper | SDR | The exec's team missed its Q2 pipeline target, and the assistant is building the board slide about it | Asking what's on the exec's plate this quarter | Minute 2: "She doesn't take cold calls." |
| 5 | The inbound tire-kicker | SDR | Downloaded a guide for a project that got approved last week | Asking why now | Minute 4: "I'm just researching, not buying anything." |
| 6 | The new boss | Account manager | The sponsor left, and the new VP is reviewing every tool's cost | Asking about changes on their side since the last review | Minute 7: "We'll probably renew, just send the paperwork." |
| 7 | The expansion nobody asked for | Account manager | A second team is using a spreadsheet workaround the account manager doesn't know about | Asking how other teams handle the same work | Minute 9: "We don't need more seats." |
| 8 | The technical ambush | AE or sales engineer | The buyer's security team blocks any vendor without a current third-party security audit | Asking what their security review requires | Minute 5: "Has this passed a security review somewhere like us?" (the brief doesn't say) |
Scenario 8 is the one I'd add to every AE loop. The honest answer is "I don't know, let me find out, and what does your review need?", and you learn a lot from whether the candidate says it or bluffs. SDR cards (4 and 5) run five to eight minutes, not twenty, and the win condition is fifteen minutes on the right person's calendar.
Scenario 1, written out in full
Buyer: Morgan Lee, Head of Revenue Operations at a 200-person logistics software company. Uses a competitor's forecasting tool, rolled out two years ago.
Candidate brief: "Morgan took a first call with your SDR and agreed to 20 minutes. They use a competitor for forecasting. Your goal: find out whether there's a real reason to change, and leave with a next step." Ten minutes to prepare.
Hidden pain: the incumbent's renewal quote came in much higher than last year. Morgan hasn't raised it with the CFO yet, because the rollout was Morgan's project.
Key question: any question about what's changed with the current tool, how the renewal is looking, or what the CFO thinks of it. If the candidate asks only about features, Morgan talks about features.
Scripted objection: at minute 8, "Honestly, we're pretty happy with what we have." Say it the same way to every candidate. If the pain has already come out, Morgan says it with less conviction. If it hasn't, Morgan means it.
Win condition: a second call with Morgan and the CFO before the renewal date, with the candidate offering to bring a cost comparison.
A candidate who pitches forecasting accuracy for twenty minutes can run a polished call and never learn the renewal price moved. Without the card you'd score that call on polish.
Scenario 5, the SDR version
The name describes how Alex comes across, not what's true.
Buyer: Alex Kim, Operations Manager at a 60-person accounting firm. Downloaded your guide on month-end close two days ago.
Candidate brief: "Alex downloaded our month-end close guide. Call them and book a 15-minute meeting with an account executive if there's a reason to." Three minutes to prepare.
Hidden pain: the firm's partners approved a project last week to cut month-end close from ten days to five, and Alex owns it.
Key question: "What made you look at this now?" or anything close. If the candidate launches into the product, Alex stays vague.
Scripted objection: at minute 4, "I'm just researching, not buying anything."
Win condition: a 15-minute slot with an AE this week, with Alex bringing the project's timeline.
The sales interview scorecard
These five dimensions follow the five-point account read from the pillar piece. Score each 1 to 4, with a quote or a moment from the call next to every number.
| Dimension | 1 | 4 |
|---|---|---|
| Preparation | Summarized the brief back | Came in with written guesses about the pain and questions to test each one |
| Discovery | Pitched until the buyer ran out of patience; hidden pain never came out | Earned the hidden pain with questions about the operation and its cost, then dug into it |
| Objection handling | Argued or discounted inside thirty seconds | Got curious, asked what was behind it, and tied the answer to the pain |
| Next step | "I'll send over some info" | A dated meeting with a named person, ideally including the decision maker |
| Written follow-up | Generic recap; could be for any call | Uses the buyer's own words, matches what was actually agreed |
Weight the dimensions by role before the first candidate:
| Dimension | SDR | AE | Account manager |
|---|---|---|---|
| Preparation | 15% | 15% | 15% |
| Discovery | 35% | 20% | 30% |
| Objection handling | 10% | 25% | 20% |
| Next step | 30% | 15% | 15% |
| Written follow-up | 10% | 25% | 20% |
Those weights are my starting point, not research, and they assume SDRs who book by phone. If yours mostly work in writing, use the written-outreach version from the pillar piece and move weight onto the follow-up. Whatever you change, change it before you meet anyone, so the hiring manager's favorite doesn't get to decide which dimension counted.
How to run it
Send the brief ten minutes before the call (three for SDR cards) and let the candidate take notes. Run twenty minutes of conversation, or five to eight for an SDR card. Ask for the follow-up email within an hour. Record the call if the candidate agrees. Scoring discovery from memory is where drift gets back in.
If more than one person plays the buyer, have both score the first two candidates independently and compare. Where they disagree by more than a point, the card's too loose. Tighten the key question or the objection.
Where this gets hard
A good card takes an hour to write, and the first draft usually leaks. If the brief hints at the renewal price, discovery becomes reading comprehension. Test each card on a colleague first.
Holding the buyer still is also tiring. By the fourth candidate you'll want to help, and the card is what stops you.
And none of this scales to hundreds of applicants. It belongs where you'd otherwise spend a sales manager's hour. Inside Skillvee, the sales simulation runs this shape end to end: a prep brief, a discovery call with an AI buyer who only gives up the real problem when asked well, and a written follow-up read against the call. If you're hiring for customer success too, the same idea applied to accounts is in the CSM interview case study. And if you want to see what running it across your req list costs, the pricing page has the plans.