How to Use Sales Roleplay in Interviews to See How Candidates Actually Sell

The only way to know how someone sells is to watch them sell. A guide to designing interview roleplays that produce real signal, what to score, what not to score, and the common mistakes that make roleplays useless.

The only way to know how someone sells is to watch them sell. An interview roleplay is the closest you can get before day one. Most companies run it wrong and turn it into a performance review instead of a capability test.

By Kayvon Kay | Revenue Architect, Founder of SalesFit.ai

Why the Roleplay Is the Most Underutilized Interview Stage

After two decades and 101 sales teams, I still see companies skip the roleplay or run it so poorly that it provides no useful data. The most common objection is that it "makes candidates nervous" and does not reflect how they would perform on the job once they know the product. That objection is backwards. Yes, they will perform better once they know the product. But the behavioral wiring you are evaluating in a roleplay does not change with product knowledge. How they listen, how they recover when a prospect pushes back, whether they have the instinct to check for understanding, whether they attempt to advance the conversation at the right moments, all of that is wiring, not training. You are not testing product knowledge. You are testing selling behavior.

The other objection I hear is that top performers are confident enough to perform well in roleplays, which means you are just filtering for confidence, not capability. That is only true if you design the roleplay to reward confidence. A well-designed roleplay specifically tests the moments where confidence breaks down: when the buyer says something unexpected, when the price objection comes, when the candidate realizes the prospect is not actually the decision-maker. Those are the moments that reveal genuine skill. Confident-but-shallow candidates hit those moments and improvise badly. Deep sellers slow down, think, and handle them well.

The candidates who are strongest in structured questions and weakest in the roleplay are usually the most revealing hires you almost made. The story was excellent. The moment-to-moment behavior under pressure was not. You would have found that out in month two. Better to find it in the interview.

How to Design the Scenario

The scenario should be realistic and close to your actual sales environment. If you sell mid-market software to operations leaders, the buyer persona should be an operations leader at a mid-market company, not a fictional enterprise procurement committee with eighteen competing priorities. Unrealistic scenarios produce unrealistic performances, and unrealistic performances tell you nothing about what this person will do when they are actually in front of your prospects.

The scenario brief should give the candidate three things: a buyer name and title, one or two sentences about the buyer's current situation, and one or two sentences about the relevant pain point. That is it. You are not handing them a detailed discovery summary. You are giving them a starting point and watching what they do with limited information. How they handle limited information is one of the most important things you can evaluate.

Here is an example brief for a B2B software company: "You are calling on Marcus, VP of Operations at a 300-person logistics company. The company recently switched to a new WMS and the implementation has been rocky. Marcus is your first meeting, and you were introduced through a mutual connection. He has 20 minutes." That is enough. A strong candidate will ask good discovery questions. A weak candidate will pitch immediately. You will know within three minutes which one you have.

Avoid gotcha scenarios. A scenario where the buyer is deliberately hostile, irrational, or impersonating a real prospect you lost is testing stress reaction, not sales capability. You want mild but realistic friction, not extreme pressure. The objections should be the objections your actual buyers use: "We're happy with our current vendor," "This isn't the right time," "Your price is too high compared to X." These are the objections your reps will face daily. Watching how the candidate handles them tells you exactly what you need to know.

What to Score and What to Ignore

Scoring the roleplay requires a rubric. If you are evaluating purely on gut feel, the most confident performer will almost always win, regardless of actual skill. The rubric should have five dimensions, each scored on a 1 to 4 scale before the debrief begins.

Structure: Does the candidate establish rapport, state a clear objective for the call, and move through a logical sequence, or do they meander from topic to topic? Structure is a trainable skill, but candidates with no instinct for it often struggle even after training.

Discovery quality: Does the candidate ask questions that reveal the buyer's real situation, priorities, and decision-making process, or do they spend most of the call pitching at a phantom pain point they assumed from the brief? The best discovery questions are specific, open-ended, and build on each other. They do not sound like a CRM intake form.

Objection handling: When the objection comes, does the candidate acknowledge it, understand it, and address the underlying concern, or do they immediately defend and argue? Candidates who argue with objections will alienate your prospects. Candidates who acknowledge, explore, and reframe will extend conversations that would otherwise end.

Active listening: Does the candidate actually use what the buyer tells them, or do they stick to their prepared script regardless of what the buyer says? The clearest test: after the buyer shares something specific about their situation, does the candidate reference it later in the call? If not, they were not listening. They were waiting to talk.

Advancement: Does the candidate attempt to move the conversation forward at an appropriate moment, or do they let the call end without a clear next step? A close attempt does not need to be aggressive. It can be as simple as "Based on what you've shared, does it make sense to walk through how this would work for your specific environment?" The instinct to advance the conversation is what you are looking for. Candidates who never attempt advancement are expecting the buyer to drive the deal. That is a reliable predictor of stalled pipelines.

What you should ignore: nervousness in the first two minutes (this will not reflect on-the-job performance), production quality of their delivery, whether their approach exactly matches your current playbook, and whether they use the exact same language your top reps use. You are hiring for behavioral wiring, not playbook compliance. Playbook compliance can be trained. Wiring cannot.

How to Debrief the Candidate Afterward

The debrief is as valuable as the roleplay itself and is almost universally skipped. After the roleplay ends, take three minutes and ask the candidate: "How do you think that went?" and then be quiet. What they say first reveals their self-awareness. Do they immediately identify the thing they would do differently? Do they defend every choice? Do they give you a diplomatic non-answer?

The best candidates will identify the specific moment where the call could have gone better without being prompted. "I think I moved too quickly past the price objection. I should have asked more questions before trying to justify the value." That level of self-diagnosis is predictive of coaching responsiveness, which is one of the most important traits for long-term sales performance. It means when a manager or a top rep shows them a better approach, they will incorporate it rather than defending their current behavior.

Follow the candidate's self-assessment with one specific observation from the scorecard. Not a judgment, just a data point. "I noticed that when Marcus mentioned the implementation issues with the WMS, you moved to pitch mode rather than asking a follow-up question. What was your thinking there?" Now you have a real conversation about their decision-making in the moment, and that conversation tells you more about their learning style and self-awareness than the roleplay itself did.

The debrief is also where you evaluate how they receive feedback. Someone who defends every choice without genuine curiosity will behave the same way when their manager gives them feedback on a live deal. Someone who asks good questions and genuinely considers the alternative approach will be a pleasure to develop.

What the Roleplay Reveals That the Interview Cannot

Structured interview questions reveal how someone thinks about selling. The roleplay reveals how they act when selling. Those two things diverge more often than most hiring managers expect. The candidate who described a sophisticated multi-stakeholder approach in the interview and then pitched through a 20-minute call without asking a single discovery question is showing you their real selling behavior, not the version they prepared in advance.

The specific things the roleplay surfaces that no question can: how they handle the first moment of friction, whether they pace themselves or rush toward a close, how they navigate ambiguity in the buyer's stated priorities, whether they listen well enough to adapt mid-call, and what their natural energy and tonality are when they are not performing for an audience. All of those are behavioral patterns that will play out on every single call they make for you.

The roleplay also reveals role fit in a way that no assessment or question can replicate. A candidate who is naturally wired for enterprise consultative selling will struggle visibly with a transactional 20-minute pitch call. They will want to go deeper, ask more questions, avoid the rushed close. That is not a weakness in isolation. It is a misalignment with the role. Seeing that in the interview saves you from a mismatch hire that produces a frustrated rep and an underperforming territory.

For a complete framework on the four-stage interview process that uses the roleplay alongside structured questions and assessment data, see the pillar guide on interviewing sales candidates without getting played. To understand the red flags that often surface first in roleplays, see our breakdown of sales interview red flags that predict bad hires.

The Common Mistakes That Make Roleplays Useless

The first mistake: making the scenario too easy. If the buyer persona has no real objection and no competing priority and is enthusiastic about hearing more, you are not testing anything. Every candidate will perform well. The scenario needs realistic friction, not extreme difficulty, but real friction. A buyer with a current vendor they are mostly satisfied with, a budget concern, and a timeline pressure is realistic. That is what your reps are dealing with every day.

The second mistake: not debriefing. The roleplay without a debrief is a performance with no learning loop. Half of the value is in watching the candidate process what they just did. Skip the debrief and you have cut your signal in half.

The third mistake: scoring only the close. A close attempt in the last two minutes of a 20-minute roleplay says almost nothing about sales capability if the preceding 18 minutes were a mess. Score the whole call. Discovery quality and listening discipline predict long-term performance better than close attempts do. Candidates who are good at the close but weak at discovery will produce early pipeline that stalls out before month three.

The fourth mistake: running the roleplay before the structured interview. The structured interview should come first so you are not contaminating the roleplay with impressions formed during it. Run the questions, score them, form your hypothesis about the candidate, then test the hypothesis with the roleplay. When the roleplay confirms your hypothesis, you have confidence. When it contradicts your hypothesis, you have something interesting to explore in the debrief.

Related Articles

How to Interview Sales Candidates Without Getting Played by the Best Interviewers in the Room

The Best Sales Interview Questions That Actually Predict Quota Attainment

The Sales Interview Scorecard Template That Removes Gut Feel From Hiring