SDR Mock Cold Call Interview: Scripts, Role Play Framework, and Prep Plan

The SDR mock cold call interview is where a lot of candidates lose momentum late in the hiring process. The resume was good enough. The recruiter screen went well. The hiring manager liked the story. Then the candidate gets a short role-play prompt, rushes into a pitch, talks too much, misses the objection, and forgets to ask for the meeting.

That is fixable.

Hiring teams do not expect an entry-level SDR or BDR candidate to sound like a polished enterprise seller. They are looking for a few practical signals: you can prepare quickly, open a call clearly, earn a conversation, ask a useful question, handle resistance without panicking, and close for a reasonable next step. The best candidates treat the mock cold call like a sales audition, not a theater performance.

Use this guide to prepare for the actual exercise. If you want the deeper phone practice system, pair it with The Cold Calling + Mock Call Playbook. If your broader interview loop is the bottleneck, add The Tech Sales Interview Playbook.

What Interviewers Assess

Interviewers are usually scoring the mock call against a simple question: would this person be coachable enough to put on the phone after training?

They are rarely judging only the words you use. They are watching the way you think under pressure.

1. 1Preparation - Did you understand the company, buyer, likely pain, and goal of the call?
2. 2Confidence - Do you sound calm enough for a prospect to stay on the line?
3. 3Structure - Is there a clear opener, reason, question, objection response, and close?
4. 4Relevance - Can you connect the product to a believable buyer problem?
5. 5Listening - Do you pause and respond to what the prospect actually says?
6. 6Coachability - Can you self-assess and improve after feedback?

The hidden score is judgment. A candidate who gives a short, relevant, buyer-centered call usually beats a candidate who memorizes a long script and tries to force it through every objection.

The Standard Scenario

You'll typically be given:

• A fictitious company and product
• A target persona (VP Sales, Head of Marketing, etc.)
• 5-10 minutes to prepare
• 3-5 minutes to execute the call
• One or two objections from the interviewer
• A debrief question after the call

Sometimes they tell you the product in advance. Sometimes you sell their actual product. Sometimes the interviewer acts like a busy executive who is not rude, but clearly wants you off the phone.

Do not overcomplicate the objective. In most SDR interview role plays, your goal is not to close a deal. Your goal is to earn a next meeting.

That means your call should be short, specific, and controlled. You are trying to prove you can create enough curiosity for a prospect to say, "Fine, send me something" or "Sure, put time on the calendar."

Mini Keyword Map for Your Prep

If you are preparing for this interview, think in terms of the language hiring managers use:

• SDR mock cold call interview: the live phone role-play in an SDR or BDR hiring process.
• Mock cold call script: the opener, reason for calling, problem question, objection response, and close.
• SDR interview role play: the broader sales simulation, which may include cold calls, discovery, objection handling, or follow-up.
• Tech sales interview role play: the same exercise inside SaaS, cybersecurity, fintech, HR tech, martech, data, or other B2B software companies.

Those phrases matter because they reflect the actual search intent: candidates are not looking for theory. They need a script, a practice plan, and a way to avoid freezing during the live exercise.

Preparation Strategy

Before the interview:

• Research the company's buyer, market, and core problem
• Write a one-sentence reason the buyer would care
• Practice your opener out loud until it sounds natural
• Record three practice calls and listen for rambling
• Prepare responses to the five most common objections
• Practice a clean calendar ask

During prep time:

• Identify the core value prop
• Draft a one-sentence pitch
• Anticipate the top three objections
• Plan your opening and close
• Write one discovery question that fits the buyer

The biggest mistake is practicing only in your head. Cold calls are an audio skill. You need to hear your pacing, filler words, tone, and pauses.

The Framework to Use in the Mock Call

1. 1Opener: Permission-based pattern interrupt
2. 2Reason: One sentence explaining why you are calling
3. 3Problem question: A question that starts a real conversation
4. 4Handle: A calm response to the first objection
5. 5Close: A specific ask for the next meeting

Here is the simple version:

"Hi [Name], this is [Your Name] with [Company]. I know I am catching you out of the blue. Do you have 30 seconds for me to explain why I called, and you can tell me if it is worth a real conversation?"

If they say yes:

"The reason I reached out is that we help [buyer type] with [specific problem], especially when [trigger or situation]. I am curious, how are you handling [problem area] today?"

If they answer, ask one follow-up before pitching. If they object, acknowledge it and keep the conversation moving.

The interviewer is not expecting magic. They want to hear a call that has a beginning, middle, and end.

Mock Cold Call Script Example

Use this as a practice script, not a word-for-word line you force into every interview.

Rep: "Hi Jordan, this is Malik with PipelineDesk. I know this is a cold call. Do you have 30 seconds for me to tell you why I called, and you can decide if it is relevant?"

Prospect: "Fine, go ahead."

Rep: "Appreciate it. I saw your team is hiring six SDRs this quarter. We help revenue leaders see which outbound sequences are creating qualified meetings before the quarter is already missed. How are you tracking call, email, and LinkedIn performance across the team today?"

Prospect: "We already have a CRM."

Rep: "That makes sense. Most teams we speak with do. Usually the gap is not whether activity is logged. It is whether managers can spot which messaging is working early enough to coach the team. Are you mostly relying on dashboard reporting, or are managers reviewing rep-level sequence quality too?"

Prospect: "Mostly dashboards."

Rep: "Got it. That is exactly where a short conversation may be useful. Would it be unreasonable to compare notes for 15 minutes next week and see whether there is a gap worth solving?"

Notice what this does:

• The opener asks permission without sounding timid.
• The reason is tied to a business trigger.
• The question invites the buyer to talk.
• The objection response does not argue.
• The close asks for a small next step.

How to Handle Common Objections

Most interviewers use predictable objections because they want to see whether you stay composed.

"Not interested"

Weak response: "Can I ask why?"

Better response:

"Totally fair. Usually when I hear that, it means either the timing is off or this is not a priority. Before I disappear, is improving [problem] something your team is focused on this quarter, or not really?"

This gives the prospect an easy way to answer without feeling trapped.

"We already use a competitor"

Weak response: "What do you use?"

Better response:

"That makes sense. Most teams have something in place. I am not calling because you have no tool. I am calling because teams often still struggle with [specific gap]. Is that a problem you are seeing, or is the current setup working well?"

You are not attacking the competitor. You are testing for an unresolved problem.

"Send me information"

Weak response: "Sure, what is your email?"

Better response:

"Happy to. To make sure I send something useful, are you more interested in [pain A] or [pain B]?"

If they answer, you can earn a next step:

"Got it. I will send the short version. If it looks relevant, would you be open to a 15-minute conversation Tuesday or Wednesday?"

"No budget"

Weak response: "What if it was cheaper?"

Better response:

"Understood. I am not asking you to buy anything today. Usually budget only matters if the problem is real enough. Is [problem] costing the team time or pipeline right now, or is it more of a future issue?"

This reframes the call around pain and timing.

"I am busy"

Weak response: "When is a better time?"

Better response:

"I figured I might be catching you in the middle of something. I can be brief. The only reason I called is [one-sentence reason]. Is that even on your radar, or should I let you go?"

This respects the objection while giving the buyer one more chance to engage.

The 10-Minute Prep Plan If They Give You a Prompt

When the interviewer gives you a prompt and a few minutes to prepare, do not try to learn everything. Build a call card.

1. 1Buyer: Who am I calling?
2. 2Likely pain: What problem would this person care about?
3. 3Trigger: Why might this be relevant now?
4. 4Reason: Why am I calling this specific person?
5. 5Question: What question can open the conversation?
6. 6Objections: What two objections are most likely?
7. 7Close: What meeting am I asking for?

Here is an example:

• Buyer: VP Sales
• Likely pain: SDR ramp and inconsistent outbound conversion
• Trigger: Hiring more SDRs this quarter
• Reason: New headcount makes coaching quality more important
• Question: "How are you measuring whether new reps are using the right talk tracks?"
• Objections: "We use Salesforce" and "send me info"
• Close: 15-minute meeting to compare outbound coaching workflows

That is enough. A clear call card beats a long page of notes.

How to Debrief After the Role Play

The debrief can save you even if the call was imperfect. Interviewers often ask:

• "How do you think that went?"
• "What would you do differently?"
• "What feedback do you have for yourself?"
• "Want to try that again?"

Do not say, "I think it went great" unless it truly did. That sounds unaware.

Use this structure:

1. 1Name one thing that worked.
2. 2Name one thing you would improve.
3. 3Explain the adjustment you would make.
4. 4Ask for feedback.

Example:

"I think the opener was clear and I got to the reason for the call quickly. I could have asked a better follow-up after the first objection instead of moving to the meeting ask so fast. If I ran it again, I would slow down and ask what their current process looks like before closing. How would you coach me on that?"

That answer proves coachability, self-awareness, and sales maturity.

Practice Drills Before the Interview

Run these drills for two or three days before the interview.

Opener reps

Say your opener 25 times until it sounds conversational. Change the company, buyer, and problem each time.

Objection reps

Pick five objections and respond to each in under 20 seconds. The goal is not a perfect answer. The goal is composure.

One-question discovery

Practice writing one strong question for different buyers:

• VP Sales
• SDR Manager
• Head of Marketing
• Founder
• RevOps leader

Close reps

Practice asking for the meeting without sounding apologetic:

"Would it be unreasonable to compare notes for 15 minutes next week?"

"Does Tuesday afternoon or Wednesday morning work better for a quick conversation?"

"If this is relevant, the next step would be a short working session. Is that worth putting on the calendar?"

Feedback reps

After every practice call, say what you would improve. This makes the real debrief feel normal.

Common Mistakes to Avoid

• Talking too much without pausing
• Sounding robotic or scripted
• Crumbling at the first objection
• Forgetting to actually ask for a meeting
• Getting defensive when pushed
• Pitching features before you understand the problem
• Treating "send me information" as a win
• Asking vague questions like "what keeps you up at night?"
• Using fake enthusiasm instead of clear business relevance
• Ending the call without confirming the next step

What a Strong Final Answer Sounds Like

If you have time for one final practice rep, use this structure:

"My goal in the mock call is not to over-pitch. I want to open clearly, earn permission, connect the call to a likely business problem, ask one useful question, handle resistance calmly, and close for a small next step. If I miss something, I want to show I can take feedback and improve quickly."

That is exactly how a hiring manager wants a new SDR to think.

The Bottom Line

You do not need a perfect mock cold call to pass the interview. You need a structured call, a relevant reason, a real question, a calm objection response, a specific close, and a coachable debrief.

If you are preparing this week, do not just read examples. Practice out loud. Record yourself. Run the call card. Handle the objections. Close for the meeting.

For a deeper script library, scoring rubric, and practice routine, use The Cold Calling + Mock Call Playbook. If you need help with the full interview loop around the role play, use The Tech Sales Interview Playbook.