"Sell me this pen."
That's not a role-play. It's a party trick. And it tells you absolutely nothing about whether someone can run a discovery call with a skeptical VP who has three competing vendors in their inbox.
A sales role-play interview can be the highest-signal stage in your hiring process — or it can be pure theater. The difference comes down to three things: Is the scenario realistic? Is there a rubric? Does the evaluator know what to listen for?
Here's how to design role-plays that actually predict on-the-job performance, with scenarios for both SDR and AE hiring.
→ Download the sales role-play scenario pack
Why Most Sales Role-Play Interviews Fail
Three problems kill most role-plays before they start:
The scenario is fake. "You're selling software to a CEO of a Fortune 500 company who has unlimited budget." Nobody has unlimited budget. Nobody buys software in a vacuum. When the scenario doesn't feel real, the candidate performs in a way that doesn't feel real either. You learn nothing.
There's no rubric. The interviewer watches the role-play, then says "they were pretty good" or "something felt off." Without defined scoring criteria, you're back to gut feel — which is the thing the role-play was supposed to replace.
The evaluator plays wrong. Some interviewers play the prospect as an impenetrable wall ("I'm not interested." "Still not interested." "I said I'm not interested."). Others fold immediately and agree to everything. Neither generates useful signal. The evaluator's job is to create realistic friction — the kind the candidate will face in the actual role.
Fix these three things and the role-play becomes your most valuable interview stage.
The Design Principles of a Predictive Sales Role-Play
Mirror the real job
If you're hiring an SDR who will make 60 cold calls a day, the role-play should be a cold call. If you're hiring an enterprise AE who runs 45-minute discovery meetings with procurement involved, the role-play should be a discovery meeting with complex stakeholder dynamics.
Match the scenario to the motion. Match the difficulty to the role level. Match the buyer persona to your actual ICP.
Keep it short
Ten to twenty minutes of role-play is enough. Longer than that and you're testing endurance, not skill. Follow the role-play with five to ten minutes of debrief — "What were you trying to do there? What would you do differently?"
The debrief often reveals more than the role-play itself. A candidate who performed mediocrely but diagnoses exactly what went wrong shows coachability. A candidate who performed well but can't articulate their approach might be running on instinct that won't transfer.
Brief the candidate
Don't ambush people. Give them 5 minutes and a one-paragraph scenario brief: who the prospect is, what the company does, why they might be interested, and what the candidate's objective is.
The goal isn't to test improv skills. It's to test selling skills under realistic conditions. Real sellers get context before a call.
Brief the evaluator harder
The evaluator needs more preparation than the candidate. Write out:
- Two or three objections to raise naturally during the conversation
- One piece of information to share only if asked (reward good discovery)
- The prospect's actual pain and urgency level
- When to push back and when to let the conversation flow
Bad evaluators ruin good role-plays. Calibrate your evaluators before using them.
Sales Role-Play Scenarios for SDR Hiring
Scenario 1: The Cold Call — Incumbent Vendor
Brief to candidate: You're calling Sarah, VP Sales at a 300-person fintech company. She's hired 8 reps in the past year and currently uses a manual interview process with unstructured panels. Your job: earn a 15-minute meeting.
Evaluator notes: You're busy but not hostile. You're mildly curious but say "we handle this fine internally" as your default. Share that you had a bad hire last quarter only if the candidate asks a good question about hiring outcomes. You'll agree to a meeting if the candidate gives you a specific, relevant reason.
What this tests: Opening, relevance, objection handling on "we already have a process," ability to earn the next step without pitching.
Scenario 2: The Warm Follow-Up — Went Dark After Demo
Brief to candidate: You had a good first call with James, Director of Sales Ops, two weeks ago. He said he'd loop in the VP. Since then — silence. You're calling to re-engage.
Evaluator notes: You got busy. The VP hasn't been briefed yet. You're still interested but not urgent. If pressed, admit that a competing vendor reached out and you're evaluating them too.
What this tests: Re-engagement technique, competitive response, urgency creation without desperation.
Scenario 3: The Gatekeeper
Brief to candidate: You're calling into the main line trying to reach Dana, Head of Talent. You get her EA, who is polite but protective.
Evaluator notes: Ask what it's regarding. If the candidate says "sales call" or sounds like a vendor, decline. If they're specific about relevance and respectful, offer to relay a message or suggest a better time.
What this tests: Gatekeeper navigation, professional tone, creative problem-solving.
Sales Role-Play Scenarios for AE Hiring
Scenario 4: Discovery Meeting — New Business
Brief to candidate: You have a 30-minute discovery meeting with Alex, VP Sales at a 400-person B2B software company. They're scaling from 15 to 30 reps this year and agreed to the meeting after seeing a peer's referral. Run the discovery.
Evaluator notes: You have real pain — two bad hires this quarter that cost you pipeline. But you're cautious. You've been burned by tools that promised to fix hiring and didn't. Share pain openly if asked well. Push back if the candidate jumps to demo too early. Ask "So what makes you different?" at some point.
What this tests: Discovery structure, question depth, patience, competitive positioning, ability to quantify pain.
Scenario 5: Competitive Deal — Objection Heavy
Brief to candidate: You're in the second meeting with Pat, Head of Revenue Operations. They've also seen a demo from a competitor. They like what they've seen from both vendors and want to understand the difference.
Evaluator notes: Lead with "I liked the competitor's demo — it was pretty slick." Mention their pricing is 20% lower. If the candidate tries to trash-talk, stay neutral. If they differentiate on value, engage more. Your real concern is implementation effort and whether your ATS integrates cleanly.
What this tests: Competitive composure, value-based differentiation, ability to uncover the real decision criteria behind the stated ones.
Scenario 6: The Stalled Deal — Mutual Action Plan
Brief to candidate: You've had three strong calls with Jordan, Director of Sales. Jordan loves the product. But the VP hasn't been brought in, procurement hasn't been engaged, and the timeline keeps slipping. This call is about getting the deal back on track.
Evaluator notes: You genuinely want to move forward but you're swamped and the VP is hard to pin down. If the candidate offers to help you build an internal case or structure the VP conversation, engage enthusiastically. If they just push for "can we get on the VP's calendar," stay vague.
What this tests: Deal management, mutual action plan creation, ability to coach a champion without being pushy.
What to Score in a Sales Role-Play Interview
Use this rubric for every role-play. Score each dimension 1–5 with the scorecard template.
| Dimension | 1 (Poor) | 3 (Adequate) | 5 (Exceptional) |
|---|---|---|---|
| Opening / Agenda | No structure, dives into pitch | Sets basic agenda, reasonably organized | Earns permission, confirms time, sets clear expectations |
| Discovery quality | Asks zero or surface questions | Follows a framework, covers basics | Asks layered questions that reveal unstated needs and priorities |
| Objection recovery | Folds or argues | Acknowledges and pivots with a reasonable response | Turns the objection into deeper discovery |
| Conversation control | Prospect leads the entire call | Maintains some structure | Guides conversation naturally while letting prospect talk |
| Value mapping | Generic pitch, no connection to prospect's situation | Connects some features to stated needs | Maps solution to specific pain, quantifies impact |
| Next step | No ask, or vague "let's stay in touch" | Asks for a meeting but doesn't nail logistics | Secures a specific, committed next step with clear purpose |
How to Brief Evaluators and Keep the Process Fair
Fairness matters. If one candidate gets a hostile evaluator who says "not interested" to everything, and the next gets someone who engages warmly, you're not comparing candidates — you're comparing evaluators.
Calibration steps:
-
Write the evaluator script. Not word-for-word, but the objections they'll raise, the information they'll share, and the general tone. Every candidate should face the same difficulty level.
-
Practice once. Before using a new scenario in real interviews, have two team members run it. Time it. Adjust the difficulty. Make sure it's possible to succeed but not easy.
-
Same evaluator when possible. If you're interviewing 5 AE candidates, have the same person play the prospect for all 5. Consistency is more important than variety.
-
Score independently before discussion. Each evaluator submits their rubric scores before the debrief meeting. This prevents anchoring.
Common Role-Play Mistakes That Destroy Signal
Playing yourself, not the persona. If you're a VP Sales evaluating an SDR candidate, don't play the prospect like a VP Sales would — play the prospect as written. Your job is to simulate reality, not to test whether they can sell to you specifically.
Interrupting to teach. Some interviewers can't help coaching during the role-play. "Actually, a better approach there would be..." Save it for the debrief. The role-play is observation. The debrief is coaching.
Going too long. If the role-play has clearly generated enough signal at minute 12, stop. Don't keep going to fill 20 minutes. Time is signal too — some candidates peak early and degrade.
Scoring personality, not skill. Charismatic candidates feel good. Quiet, methodical candidates feel boring. The rubric exists to override that feeling. Score the behaviors, not the vibe.
When to Use Chat vs. Voice vs. Video Role-Play
The assessment mode should match the selling channel.
| Role | Primary Channel | Best Assessment Mode |
|---|---|---|
| SDR (phone-first) | Cold calls | Voice role-play |
| SDR (email-first) | Cold email + sequences | Chat assessment |
| AE (mid-market) | Video demos + calls | Video assessment |
| AE (enterprise) | In-person + video | Video role-play or live panel |
| Sales Manager | Coaching conversations | Live scenario (in-person preferred) |
Mismatch kills signal. Testing a phone-first SDR on a written assessment tells you about their writing. Testing an AE who runs video demos on a phone-only call misses executive presence and presentation skill.
For a deeper comparison: Chat vs. Voice vs. Video — Which Sales Assessment Fits Your Hiring Motion?
Download the Sales Role-Play Scenario Pack
Stop running "sell me this pen" and start running scenarios that predict actual performance.
The pack includes:
- 10 ready-to-use scenarios (SDR and AE) with candidate briefs and evaluator scripts
- Scoring rubric with 1–5 anchors for each dimension
- Evaluator calibration guide
- Debrief template with coaching-focused follow-up questions
→ Start Free — run AI-scored role-play assessments at scale
FAQ
How do you run a sales role-play interview?
Use a realistic scenario, a fixed prompt, a defined rubric, and a short debrief so every candidate is evaluated on the same signal.
What should you score in a sales role-play?
Score discovery quality, objection recovery, conversation control, value mapping, and the credibility of the next step.
How long should a sales role-play interview be?
Ten to twenty minutes of role-play plus five to ten minutes of debrief is usually enough to get useful signal.
Should SDR and AE role-plays be different?
Yes. SDR role-plays should emphasize opening, objection recovery, and call control, while AE role-plays should emphasize discovery, stakeholder context, and close planning.