How to Prepare for an Account Executive Discovery Call Role Play

You've passed the recruiter screen, nailed the hiring manager's behavioral questions, and now you are facing the ultimate test. It is time for the account executive discovery call role play. For a lot of sales professionals, this is easily the most intimidating part of the entire interview process. Talking about past quota attainment, pipeline management, or your biggest closed-won deals is one thing. Demonstrating your sales acumen live, under intense pressure, while your potential future boss acts like a difficult prospect? That is an entirely different beast.
This simulation exists for one simple reason: to see if you can actually do the job. Interviewers are not looking for a flawless product pitch. In fact, pitching too early is the single most common reason candidates fail this round completely. They want to see your structured thinking. They are watching for your ability to uncover deep business pain, your active listening skills, your emotional intelligence when faced with objections, and your overall command of the conversation. If you want to master this interview, you will need a strategic approach, a heavy reliance on proven sales frameworks, and a solid grasp of buyer psychology.
What is an account executive discovery call role play?
In a typical setup, you will receive a prompt or a brief a few days before the interview. This brief outlines your exact scenario. It tells you the company you are selling for (sometimes the company you are interviewing with, sometimes a fictional product), the product you represent, and the specific persona you will be speaking to. For example, you might be told you are selling a revenue intelligence platform to a Chief Revenue Officer, or a cybersecurity tool to a Chief Information Security Officer.
You will also get a few basic details about their current situation—maybe they recently missed their quarterly targets, or they just acquired a new company and are struggling with tech stack integration. From there, you get 15 to 30 minutes to conduct a mock call with the interviewer, who stays in character as the prospect the entire time.
Do not get confused about your primary objective here. You aren't trying to close a deal on the spot. Your actual goal is to qualify the prospect, uncover their underlying business challenges, understand their buying process, and tie their pain to a high-level capability of your product. Most importantly, you need to secure a logical next step. Usually, that means scheduling a deeper, more tailored product demonstration that involves a wider group of stakeholders.
Step 1: Deconstructing the interview prompt
Preparation starts the minute you receive the prompt. Do not just read it once and plan to wing the conversation. You need to forensically break down the scenario and build a call hypothesis. A call hypothesis is your educated guess about what is keeping this specific persona up at night, based on the limited information provided in the brief.
To build a strong foundation before the call even begins, map out these three specific elements:
- The Persona's Core Metrics: How is this person evaluated? If you are talking to a VP of Sales, they care about quota attainment, win rates, and sales cycle length. If you are talking to a VP of Customer Success, they care about net revenue retention (NRR), churn rates, and time-to-value. Write down the top three metrics this person likely loses sleep over.
- The Status Quo Trap: What are they likely doing today? If the prompt says they are struggling with lead routing, assume they are using a manual spreadsheet process or an outdated legacy system. Formulate questions that expose the inefficiency of this status quo.
- Your Thesis Statement: Write down one sentence that defines why they need your product right now. For example: 'Because they are expanding into the EMEA market, their current manual compliance tracking will cause a major audit failure, meaning they need our automated compliance platform to scale safely.'
Setting the stage: The anatomy of a perfect upfront contract
Before you even ask your first discovery question, you absolutely have to take control of the meeting. The best account executives pull this off by establishing an upfront contract. This is a verbal agreement made at the very beginning of a meeting. It outlines the agenda, the primary goal of the call, and what the potential outcomes will be. Setting this contract shows the interviewer that you are a peer, an expert, and a true professional who respects their time.

A flawless upfront contract contains four elements: Time check, Agenda, Prospect's goal, and Outcome. You confirm the hard stop, state what you want to cover, ask what they want to ensure gets covered, and explicitly state that the goal is to decide on a next step.
The hidden scorecard: What interviewers actually grade
Sales leaders use this simulation to evaluate the specific competencies that separate elite performers from average reps. Behind the scenes, they have a scorecard they are grading you against. If you want to score high across these areas, avoid the temptation to treat this like a casual chat. You need a concrete, actionable strategy.
- Call Control: Can you guide the conversation, politely interrupt when the prospect rambles, and keep the agenda on track?
- Business Acumen: Do you understand how a business actually makes money, saves money, or mitigates risk? Can you speak the language of the C-suite?
- Active Listening: Do you listen to understand, or just listen to respond? When the prospect drops a hint about a problem, do you drill down into it, or do you just move on to your next scripted question?
- Objection Handling: When the prospect pushes back on price or priority, do you fold, get defensive, or smoothly reframe the conversation?
- Next Steps: Can you confidently ask for the meeting and secure a firm calendar invite?
Using the SPIN framework to uncover and amplify pain
To reliably pass a sales role play interview, you need a proven framework backing you up. The most effective framework for discovery questioning is SPIN. SPIN helps you guide the prospect from realizing they have a minor operational issue to understanding that this issue is actually a massive business problem requiring an immediate fix. It stops you from asking random, disjointed questions and creates a highly logical conversational flow.
Here is how you apply SPIN practically during your role play, using a hypothetical scenario where you are selling customer support software:
- Situation: Establish the current reality. Do not ask things you could have Googled. Ask: 'I noticed your support team grew by 20% last quarter. How are you currently routing those tier-two technical tickets?'
- Problem: Identify the friction. Ask: 'A lot of leaders using legacy routing tell me that high-priority tickets end up sitting in the general queue. How often is your team missing their 1-hour SLA?'
- Implication: This is where average reps fail and great reps win. Make the problem hurt. Ask: 'When a tier-two ticket misses that SLA and a frustrated user takes to social media, how is that impacting your overall Net Promoter Score and your upcoming renewal conversations?'
- Need-Payoff: Guide them to the solution without pitching. Ask: 'If we could automate that routing so your specialized engineers get the ticket within 60 seconds, what impact would that have on your team's ability to hit your quarterly retention goals?'
Weaving MEDDIC into a 30-minute conversation
While SPIN helps you build a solid business case and emotional urgency, MEDDIC ensures you are actually talking to the right person and that a deal can realistically happen. In a quick 30-minute role play, you definitely will not uncover every single letter of MEDDIC. If you try, you will sound like a police interrogator. Instead, you have to demonstrate that you know how to drop these qualification questions into the conversation naturally.
Focus on the three most critical MEDDIC elements for a first call: Metrics, Decision Process, and Identify Pain. You have already handled pain with your SPIN questions. Now, you need to quantify it and figure out how they buy.
- Metrics: Tie the pain to a number. 'You mentioned the manual data entry is slowing down your reps. Do you have a sense of how many hours per week each rep is losing to this?'
- Decision Process: Understand the mechanics of their buying committee. 'Typically, when you evaluate a platform to overhaul your CRM data, who else internally needs to weigh in on that workflow?'
- Champion: Test if they have the juice to drive a deal. 'If we can prove that this saves your team 10 hours a week, how would you go about building the business case for your CFO to get this funded?'
Call control: How to manage the talkative or difficult prospect
Interviewers love to test your call control. They might intentionally give you long, rambling answers that eat up the clock, or they might give you frustratingly short, one-word answers. You have to adapt on the fly. If they are rambling, you need to use the 'polite interruption' technique. Wait for them to take a breath, use their name, and validate what they just said before redirecting.
For example: 'John, pause right there. What you just said about your Q3 pipeline gap is incredibly important, and I want to make sure I fully understand it. You mentioned the gap is primarily in the mid-market segment. Why do you think that segment specifically is lagging?' This shows active listening while firmly taking the steering wheel back.
If they are giving you one-word answers, use tactical mirroring. Repeat the last three words of their sentence back to them with an upward, questioning inflection. If they say, 'Our current process is just too slow.' You respond: 'Too slow?' Then, stay completely silent. The awkward silence will force them to elaborate and give you the details you need.
Handling common role play objections with the AIO method
Interviewers will intentionally throw curveballs your way just to test your resilience and emotional intelligence. They want to see if you panic, get super defensive, or smoothly handle the objection and pivot right back to discovery. A great framework to lean on here is Acknowledge, Isolate, and Overcome (AIO).
Here is how you handle the three most common role-play objections using concrete scripts:
- The Budget Objection ('We have zero budget for new software right now.'): Acknowledge: 'I completely understand, and frankly, I wouldn't expect you to have budget carved out for something you haven't even evaluated yet.' Isolate: 'Aside from the budget timing, is solving this SLA breach issue a priority for your team this quarter?' Overcome: 'Since it is a priority, let's set budget aside for a moment. Let's do the demo to see if this even solves your problem. If it does, we can build the ROI case together for when funds do open up.'
- The Competitor Objection ('We already use Competitor X.'): Acknowledge: 'Competitor X makes a great platform, we have a lot of respect for them.' Isolate: 'Usually, when I talk to VPs using Competitor X, they love the reporting dashboard, but they struggle heavily with the API integrations. How has your experience been with integrating your legacy tools?' Overcome: 'Since you are feeling that integration friction, it might make sense for us to show you how our open API architecture handles that specific workflow.'
- The Brush-Off ('Just send me an email with pricing.'): Acknowledge: 'I am happy to send over some materials.' Isolate: 'The challenge is that our pricing is entirely based on your specific user volume and module needs.' Overcome: 'To make sure I do not send you a generic deck that wastes your time, do you have two minutes right now to walk me through how many reps would actually need access?'
The trap of the feature dump and other fatal mistakes
Even seasoned account executives bomb role play interviews. The artificial environment makes them nervous, which usually causes them to fall back on terrible habits. Just being aware of these common pitfalls is the first step to avoiding them entirely.
The most fatal mistake is the 'show up and throw up' feature dump. When the prospect mentions a pain point, nervous reps immediately launch into a monologue about their software's features. Remember the 80/20 rule: you should be listening 80% of the time and talking 20% of the time. When you do talk, it should be to ask a layered question, not to pitch.
Another major mistake is ignoring the clock. If you have 30 minutes, and you are still asking basic situation questions at minute 25, you have failed the time management portion of the scorecard. Put a clock visible on your screen and mentally segment the call: 2 minutes for rapport and upfront contract, 20 minutes for SPIN/MEDDIC discovery, 3 minutes for high-level value mapping, and 5 minutes to close.
Winning the round: How to secure concrete next steps
A fantastic discovery call that ends without a clear, scheduled next step is ultimately a failed discovery call. Time management is absolutely critical here. Always keep an eye on the clock and leave three to five minutes at the end of the role play. Use this time to summarize the conversation, confirm the value, and confidently propose your next step.
Do not ask weak closing questions like, 'So, would you maybe want to see a demo sometime?' You need to prescribe the next step as a trusted advisor. Summarize the pain you uncovered, attach it to the business impact, and tell them what happens next.
A strong close sounds exactly like this: 'John, based on what you shared today about your pipeline bottlenecks and the impact it is having on your Q3 revenue targets, I am highly confident our platform can help. The logical next step is to schedule a tailored demonstration where I can show you exactly how we solve that specific deliverability issue. Do you have your calendar handy to find 45 minutes for next Tuesday?'
By combining a highly structured framework like MEDDIC and SPIN, demonstrating deep active listening, handling objections with grace, and executing a confident close, you will prove your worth to the hiring manager. You will show them that you are a top-tier account executive who is ready to hit the ground running, manage complex sales cycles, and absolutely crush your quota.
Frequently asked questions
How long should a discovery call role play last?
Most discovery call role plays are scheduled for 15 to 30 minutes. It is your responsibility to manage the time effectively. Always keep an eye on the clock and ensure you leave the final 3 to 5 minutes to summarize the pain points and secure a firm next step.
Should I pitch the product during a discovery call?
Keep pitching to an absolute minimum. A solid rule of thumb is to spend 80% of your time asking targeted questions and actively listening. Spend only 20% mapping their pain to high-level solutions. Do not fall into the trap of doing a massive feature dump.
What if I do not know the answer to a technical question the interviewer asks?
Be honest and transparent. Do not make up an answer. Just say, 'That is a great, highly technical question. I want to make sure I give you the exact right answer, so let me take that back to my sales engineering team and I will follow up with you on that specific point via email.' This shows maturity and honesty.
How do I recover if the role play goes completely off track?
Pause, acknowledge the detour, and confidently reset the agenda. You can say something like, 'I feel like we might have gone down a bit of a rabbit hole there. To bring us back to your main goal of increasing Q4 revenue, you mentioned earlier that...'
Can I bring notes into my role play interview?
Yes, absolutely. Bringing structured notes, your upfront contract, and a list of key SPIN and MEDDIC questions shows the interviewer that you are highly prepared. Just be sure to use them as a reference guide, rather than a script you read from monotonously.
Related comparisons
See AcePrompt in action
Watch how AcePrompt supports a real technical round - structured answers, tuned to your resume, in real time.
Nail your next sales role play with AcePrompt's real-time interview guidance.
Get started