The SDR Interview Roleplay: How to Prep for the Cold Call They'll Make You Do Live

Almost every serious SDR process I have seen in the last few years ends with the same thing. Two decent conversations, a bit of resume talk, and then the hiring manager says: "Okay, last part. I'm going to be a VP of Sales. You're calling me cold. Go whenever you're ready."

And most candidates lose the job right there.

Not because they were nervous. Nerves are expected and forgiven. They lose it because the second the manager says "go," they start pitching. They deliver the value proposition they memorised off the careers page, they string three benefits together, and thirty seconds later the manager says "alright, good, let's stop there" in the tone you use when you have already made up your mind.

I have been on both sides of this. I have sold inside AWS and Dell, I have built and exited four businesses, and I have listened to a lot of people try to open a call. The gap between a candidate who passes the roleplay and one who does not has almost nothing to do with polish. It is about whether you behave like someone having a conversation or someone reciting one.

Here is what the person on the other side is actually grading, and how to prepare for it in a week.

Why they make you do this at all

A hiring manager cannot tell from an interview whether you will pick up the phone on a Tuesday afternoon when the first eleven dials went nowhere. That is the real thing they are buying, and it is unknowable in advance. So they use the roleplay as a proxy.

The proxy tells them three things. Can you be coached — meaning, do you have a discernible approach that could be adjusted, or is it mush. Do you flinch when someone is short with you. And can you ask a stranger for something without apologising for existing.

Notice that "did you say the right words" is not on that list. Nobody expects a candidate to know their product. The manager knows the script they hand new hires on day one is going to overwrite whatever you say in that room. What cannot be overwritten in onboarding is your temperament under mild social pressure.

Which means the roleplay is not a knowledge test. It is a behaviour test. Prepare for it accordingly.

What they are actually grading

The first fifteen seconds

Call it fifteen seconds. However long it takes you to say who you are and why you are calling. This is the single most diagnostic part of the whole exercise, because it is the part where nervous candidates hide.

Hiding looks like speed. It looks like a rising tone at the end of every sentence. It looks like "Hi, is this a bad time?" — which invites the answer you do not want — or the fake-familiar "Hey! How's it going?" that every buyer has learned to recognise as a cold call within two syllables.

What a good opener sounds like is slower than you think and more honest than you think:

"Hey Mark, it's Tim calling from Northgate. You don't know me — this is a cold call. Can I have thirty seconds and then you can tell me to get lost?"

That is not clever. It is not supposed to be. It works in a roleplay for the same reason it works on a real call: it tells the truth about what is happening, it hands the other person control, and it sounds like a person rather than a paragraph.

The permission-based opener is not the only one that works. You can open with a reason for the call tied to something specific about them. You can open with a straight statement of the problem you solve. What matters is that you have chosen one deliberately and you can explain why you chose it if the manager asks. "I use this one because it lowers the temperature and I would rather get a fast no than a slow one" is a better answer than any opener delivered without a reason behind it.

One more thing about those fifteen seconds. Say your name and your company slowly, and then stop talking for a beat. Candidates who barrel straight from their name into their pitch without a breath are telling the manager they are scared of silence. You will spend your entire SDR career sitting in silences you did not create. Show them you can handle a small one.

Whether you ask a question before you explain anything

This is the one that separates the top candidate from the rest of the pile, and it is the one most people get wrong.

After your opener, the manager will grunt something like "go on" or "you've got thirty seconds." The instinct is to fill that space with the pitch. Do not. Give them one sentence of context — the problem, not the product — and then ask something.

"Sure. We work with sales leaders who've got reps hitting activity numbers but not booking enough meetings off it. Before I assume that's you at all — how's your team's meeting volume tracking against where you need it?"

Two things just happened. You gave them a hook, and you handed the conversation back. A hiring manager listening to that hears a rep who will discover rather than spray. That is worth more than a perfect value prop, because the value prop is in the onboarding deck and discovery instinct is not.

The question has to be a real one. "Does that resonate?" is not a question, it is a request for permission to keep talking, and every experienced buyer treats it as such. "Would you be interested in learning more about how we help teams like yours?" is worse. Ask something they would actually have an opinion about: how they are handling it today, what they tried last, who owns it internally, whether it is even on the list this quarter.

If you want to see what this looks like when the buyer is a sales leader specifically — which they will be in most SDR roleplays, because the hiring manager is playing themselves — the way I break down calling VPs of Sales and SDR managers who cold call for a living is a good model for the register to use. You cannot run a trick on someone who runs the same trick for a living. Be straight with them.

How you handle the brush-off

They will throw one. It is the whole reason the exercise exists. And they will throw it early, usually before you have finished your second sentence, because they want to see what you do when the script you rehearsed no longer applies.

The failure mode is not a bad rebuttal. The failure mode is the flinch — the "oh, okay, no problem, sorry to bother you, have a great day." Managers hear that and mentally close the file. The second failure mode is the opposite: arguing. Talking over the objection, or the cheerful "I totally understand, and that's exactly why I'm calling!" which is the sound of a rep who is not listening.

What you want in the middle is acknowledge, then one honest attempt, then a clean exit if it does not land. Attempt. Singular. Pushing twice on a brush-off in an interview roleplay reads as desperate, not persistent.

Have answers ready for these three, because in my experience they cover nearly everything a manager will throw at you.

"I'm not interested." Delivered flat, usually about eight seconds in, before you have said anything they could possibly not be interested in. The move is to name that gently.

"That's fair, you've got no idea what I do yet. Let me give you the one line and if it's not relevant I'll never call you again. Sound alright?"

"Send me an email." The polite kill. Do not just say yes — an email that arrives with no context is a deleted email, and the manager knows it.

"Happy to. So I don't send you something useless — is the meetings problem the one worth reading about, or is it something else at the top of your list right now?"

If they hold firm, take the email and take the win. "Great — what's the best address? And I'll follow up Thursday morning, is that alright?" You got a next step and you did not grovel.

"Now's not a good time." The easiest of the three and the one people fumble most, because they hear rejection instead of a scheduling problem.

"Of course, I called you out of nowhere. Two options — I can take twenty seconds now and you decide if it's worth more, or I'll call back Thursday at eight. Which is less annoying?"

What all three have in common: you acknowledge the thing they said, in their words, before you do anything else. And you make the next move small. Nobody agrees to a big ask from a stranger on a phone.

Whether you ask for the meeting

An astonishing number of candidates never do it. They have a decent opener, they ask a reasonable question, the manager gives them a bit of rope, and then the roleplay just sort of dissolves into conversation until someone says "okay, good."

Ask. Specifically, with a time in it.

"Look, I'm not going to solve this on a cold call. Worth twenty minutes Thursday at nine so I can show you what the other teams are doing about it? If it's not useful you've lost twenty minutes and I'll go away."

Direct, time-boxed, with a stated downside. "Would you be open to a quick chat sometime next week?" is not an ask, it is a hope. Say the day. Say the time. If they say Thursday doesn't work, offer another one — that is not pushing, that is scheduling, and the manager will read it as such.

And if they say no? Ask for something smaller. Permission to call back next quarter. The name of the person who actually owns it. A rep who leaves with something is a rep who will leave with something at 4pm on a bad Friday.

How to prep in a week

A week is plenty. What follows is what I would do.

Days one and two: learn their buyer, not their product

Every candidate reads the product page. Almost none of them work out who buys it and what that person's job feels like.

Go find the company's case studies and read the job titles in them. Go on LinkedIn and find three people who hold that title at companies the vendor would target. Read what those people post about. You are looking for the vocabulary — what they call the problem when they talk to each other, which is almost never what the vendor calls it on the website.

Then write one paragraph, by hand, describing a single specific buyer. Not "VPs of Sales at mid-market SaaS companies." Something like: "Mark, VP Sales at a hundred-person software company, five AEs and three SDRs, board just raised the number, his pipeline coverage is thin and he knows the SDR team is the constraint but he is not sure whether it is the people or the process." That paragraph is what you are going to talk to. If you are interviewing at a SaaS company, my breakdown of dialling CROs, VPs of Sales and RevOps leaders will get you most of the way to a persona you can rehearse against.

If the company sells into an industry you have never touched, do the same work in that industry's language. The gap between a good and bad call to a general superintendent is entirely about vocabulary and timing, which is why the construction and trades version of this reads nothing like the SaaS one. Turning up to a roleplay with the wrong dialect is the fastest way to look like you did not prepare.

Day three: write it, then cut it in half

Write your opener, your one-sentence problem statement, your first question, your three brush-off responses and your ask. On one page. It should be one page and it should be mostly white space.

Then read it out loud and cut every word that exists to make you feel safe. "I just wanted to reach out and see if you might possibly have a moment." All of that is padding. "Just," "quick," "hopefully," "I was wondering if" — gone. Read what is left out loud again. If it still sounds like writing rather than talking, it is still too long.

Days four and five: rehearse out loud, standing up, recorded

Silent rehearsal in your head does nothing. Your head does not have a voice that shakes.

Stand up. Record it on your phone. Do the full sequence — opener, question, brush-off, ask — start to finish, without stopping to fix anything. Then listen back once. You will hate it. Everyone does. Pick the single worst moment, fix that one thing, and run it again. One fix per rep.

Do about ten of these across two days and vary the brush-off each time so you are not memorising a sequence. What you are building is not a script, it is the ability to keep going after being interrupted. Interrupt yourself deliberately. Say the opener, then out loud in the buyer's voice say "not interested," then respond. That switch — from your line to their line and back — is the muscle the roleplay tests.

If you can get a friend to play the buyer, tell them to be curt rather than hostile. Cartoon hostility is easy to prepare for and nothing like what you will get. What you will get is bored, and bored is harder.

Day six: the last rehearsal is a bad one

Do one run where you deliberately fumble the opener, then recover. Trip over your own name, pause, and say "sorry, let me start that again — Mark, it's Tim from Northgate."

Because you will fumble in the room, and the recovery is genuinely part of the grade. A candidate who stumbles and keeps going has shown the manager something a flawless candidate never gets the chance to. Practising the recovery means you will not treat the fumble as the end of the world.

The question to ask at the end

When the roleplay stops, most candidates exhale and wait to be told how they did. Do not do that. Say this:

"Before you give me feedback — can I tell you what I thought I got wrong? I think I moved to the ask too early and I should have asked one more question about how they're handling it today. What did you see?"

That one move does more for you than the roleplay itself. You have just demonstrated that you listen to your own calls, that you can name a specific weakness without flinching, and that you will be cheap to coach. Managers spend their week trying to get reps to hear what is wrong with their own calls. A candidate who arrives already doing it is a candidate who reaches quota sooner.

Be specific and be honest. A vague "I feel like I rambled" reads as fishing for reassurance. Name a moment. Then shut up and take the feedback without defending anything, and if it is good feedback, ask if you can try that section again. Almost every manager will say yes, and almost every candidate who asks improves visibly on the second run, which is the exact thing the manager wanted to find out.

What I would do next

If your interview is next week, the highest-leverage hour you can spend is not more reading. It is getting a buyer's voice in your ear that pushes back in ways you did not script. That is the whole reason I built DrillCall — so a rep can run the same call twenty times against a persona that brushes them off differently each time, before the call that counts. If you have a roleplay booked, load in the buyer you wrote on day one and run it until the brush-off stops surprising you.

And whatever you do, do not walk in with a memorised pitch. Walk in with an opener you believe, one good question, an answer for the three brush-offs, and the nerve to name a day and a time. That is the whole job. They are just checking whether you can do it once.