How to Pass the Mock Cold Call in an SDR Interview

Most SDR candidates prepare for the wrong part of the interview. They rehearse their answer to "tell me about yourself." They memorise the company's funding round. They practise a story about a time they overcame adversity. Then they get to the mock cold call, freeze for four seconds, deliver a pitch nobody asked for, and never hear back.

The roleplay is the interview. Everything before it is a filter to see whether you're worth ten minutes of roleplay. Once you're in it, the hiring manager is not really listening to your words. They are checking four boxes, and none of them are the ones you think.

What the hiring manager is actually scoring

I have been on both sides of a phone that mattered, and I can tell you the scoring is cruder than candidates imagine. A hiring manager is running a mock cold call to answer one question: if I hand this person a list on Monday, will I have to sit next to them for three months before they book anything?

That question breaks into four sub-questions.

Do you have a structure at all

Not a good structure. Any structure. The single most common failure I see is a candidate who opens fine, gets a response they didn't script for, and then wanders. The call turns into a monologue about the product, then a nervous question, then more product, then "so, yeah."

A hiring manager can teach you a better opener in a week. They cannot teach you to think in a shape while a stranger is being short with you. So they listen for shape. Did this person open, give a reason for calling, ask something, and try to close? If the answer is yes, you're already ahead of most of the pipeline, even if every individual line was mediocre.

Can you take one objection without collapsing

The interviewer will push back. That is guaranteed. What they're measuring is not whether you had a clever comeback ready. It's whether your voice changed.

Watch a nervous candidate get "I'm not interested" and you can hear the collapse in real time. The pace speeds up. The pitch goes up a semitone. They start apologising: "Oh, sorry, I totally understand, I know you're busy, I just thought maybe..." That's the sound of someone who will hang up on themselves at dial forty on a Tuesday afternoon. The hiring manager has heard that sound before and knows exactly what it costs them.

You don't need to be smooth. You need to stay flat. Same pace, same volume, same energy, one line of response, then a question. That's it.

Do you ask for the meeting

This one is almost comical. A huge share of candidates run a decent roleplay and then never actually ask for anything. They finish with "so would that be something you'd be interested in learning more about?" and wait.

Ask for a specific time. Say the day. Say the length. If you don't ask for the meeting in the mock call, the hiring manager writes one word in their notes and it isn't a good one.

Are you coachable while the exercise is still running

This is the hidden one, and it's the one that separates two candidates who both ran a fine call.

Good interviewers break character halfway through. They'll say something like "pause — try that opener again, but don't ask permission." What they're testing is not whether the second attempt is better. It's whether you can take a correction, apply it immediately, and keep going without getting rattled or defensive.

The wrong response is to explain yourself. "Right, yeah, I usually don't do that, I was just thinking because you said..." The right response is three words: "Got it. Again." Then do it differently. Visibly differently. If they told you to drop the permission opener, drop it entirely — don't soften it, don't split the difference. A candidate who changes behaviour inside thirty seconds of feedback is worth hiring almost regardless of how they started.

A 60-second frame that works for any product

You will not know their product well enough to improvise. Don't try. Use a frame that holds up whether you're selling observability software, freight brokerage, or payroll services, and fill it with whatever you learned from the careers page.

Four parts. Roughly sixty seconds if the prospect says nothing, which they won't.

One: name yourself and be honest about the call

"Hi [name], it's Tim from [company]. I'll be straight with you — this is a cold call. Can I have thirty seconds and then you can tell me to go away?"

That's it. No "how are you today." No "did I catch you at a bad time," which is a question engineered to produce the word yes. Naming the call for what it is does two things: it disarms, and it signals to the hiring manager that you are not scared of the thing you're doing. Reps who are ashamed of cold calling perform shame down the phone.

Some managers hate the permission opener. If they tell you to cut it, cut it and open with the reason instead. That's the coachability box getting ticked.

Two: give a reason for calling that is about them

The reason should be a sentence about a problem someone in their seat has, not a sentence about your product.

"The reason I'm calling is that I work with heads of ops at companies your size, and the thing that keeps coming up is invoices sitting in three different systems, so nobody can tell you what's actually outstanding at month end."

Notice there's no product in that. There's a role, a context, and a specific, ugly, operational detail. Specificity is the entire game here. "Companies struggle with efficiency" tells the interviewer you know nothing. "Invoices sitting in three systems" tells them you can at least construct a hypothesis, which is a skill they can build on.

If you genuinely don't know the product's problem space, ask before the roleplay starts. "Before we run this — who am I calling and what's the pain we usually lead with?" That is not cheating. That is what a rep does before a call block, and asking it scores you points.

Three: ask one real diagnostic question

More on this below, because it's the strongest move you have.

Four: ask for the meeting with a time in it

"Look, I don't know if this is a fit. Worth twenty minutes to find out? I've got Thursday at ten or Friday after lunch."

Two options. A stated length. A clear admission that you might be wrong, which lowers the stakes for the person saying yes. Then stop talking. The silence after the ask belongs to them, and the number of candidates who fill it by re-pitching is astonishing.

The strongest move in the exercise: ask something you actually want to know

Here is the thing that will separate you from everyone else who interviewed that week.

After your reason for calling, do not continue. Ask a diagnostic question — one real question about how they currently do the thing, and then shut up and listen to the answer.

"How are you handling that at the moment — is it one person pulling it together manually, or have you got something in place?"

"When you closed the books last month, how long did it actually take?"

"Who owns that right now? Is it you, or has it landed on finance?"

Three things happen when you do this. First, you stop pitching, which means you stop being annoying. Second, you get information you can use in your ask, so the close stops sounding generic. Third — and this is the part that gets you hired — the hiring manager realises you are running a conversation rather than reciting one.

The test of a real diagnostic question is simple: could you predict the answer? If you could, it's a rhetorical setup for your pitch and the prospect can smell it. "Would it be useful to save time on reporting?" is not a question, it's a trap, and everyone knows it. "How long did last month's close take?" has an answer you don't know, which means you have to listen to it.

Then — critically — use the answer. If they say "three weeks, and finance hates me for it," your close is "three weeks and an angry finance team is exactly why I called. Twenty minutes Thursday?" That single callback, taking something they said and putting it in your ask, does more for your score than any clever line you could have prepared.

Most candidates run out of road here because they've never practised the middle of a call. The opener gets rehearsed a hundred times. The bit where someone answers your question and you have to respond to a human being gets rehearsed never. If you want a template for how a call sounds when the person on the other end is a sales leader who dials for a living and will grade your structure while you talk, our cold call script for VPs of sales and SDR managers is written for exactly that audience — which is, conveniently, the audience interviewing you.

The three objections you will definitely get

Interviewers do not get creative. You'll get some version of these three, usually in this order.

"I'm not interested"

The temptation is to argue. Don't. You've been talking for eleven seconds; there's nothing to be interested in yet, and they both know it.

"Totally fair, you don't know me. Can I give you the one sentence and then you can decide? If it's a no it's a no."

Then give one sentence. An actual sentence, not a paragraph. If they say no again, you go to the graceful exit, which I'll come to.

What's being scored: did you stay level, and did you keep the frame? You're not begging. You're offering a fast, cheap way for them to reject you properly, which is a much easier thing to agree to than a meeting.

"Send me an email"

This is the one candidates fold on instantly. "Sure! What's your email?" — and the roleplay is effectively over, because everyone in the room knows that email is going nowhere.

"Happy to. So I don't send you something useless — is the bigger issue the reporting side or the reconciliation side?"

You agreed, so you're not fighting. But you attached a question to the agreement, and now the call is alive again. If they answer, you're back in a conversation and you can go for the meeting from there. If they insist on just the email, take it, then say: "I'll send it in the next ten minutes. If it lands wrong, tell me and I'll leave you alone. If it lands right, can I grab twenty minutes next week?"

That's a conditional close, and hiring managers love hearing one because it means you understand that an email is not an outcome.

"We already have someone for that" / "We're all set"

The wrong move is to attack the incumbent. "Oh, them — yeah, we hear a lot of complaints." You look cheap, and if the interviewer is playing a real buyer they'll punish you for it.

"Good, I'd be surprised if you didn't. Most of the teams I talk to have something in place — the reason they still take the call is usually [specific gap]. Is that a live issue for you or have you got it covered?"

You validated them, you normalised the call, and you gave them one specific thing to react to. Then a question. Always end on a question.

Notice the pattern across all three: one line of acknowledgement, one line of substance, one question. Never more. The moment your objection handling runs to four sentences you've become a monologue again, and the interviewer's pen goes down.

When the interviewer plays it hostile

Some will. You'll get the manager who answers with a flat "what," interrupts your second sentence, and says "is this a sales call" in a tone that suggests they'd like you removed from the internet.

This is not personal and it is not really about your call. They are checking your floor. Every rep has a good day; they want to know what you sound like on a bad one.

Three rules. Match their pace down, not up — if they're clipped, get clipped. Long, warm, apologetic sentences into a hostile prospect sound like weakness, and they extend the misery. Second, do not apologise more than once. "Fair enough" is a complete response. Third, keep asking for the meeting. Hostility is not a no. A no is a no.

And know how to leave. If it's genuinely dead, exit cleanly and confidently, because how you handle a lost call is being scored too: "No problem, I'll get out of your way. If the [specific problem] ever becomes a priority, I'll be the guy who called about it. Have a good one." Short. No grovelling. No "sorry to have bothered you." You did not bother anyone; you did your job.

If the roleplay is for a non-software role, the same principles hold but the tone shifts hard. Calling a plant manager who's standing on a factory floor is a different physics problem to calling a CRO, and the manufacturing cold call script is worth reading if that's the industry you're interviewing into — brevity matters even more, and warmth matters less.

How to ask for feedback so that it scores points

When the roleplay ends, do not ask "how did I do?" It's a question about you and it invites a polite non-answer.

Ask for one specific thing:

"What's the one thing you'd change about that call if I were on your team on Monday?"

Then — and this is the part that matters — when they tell you, don't defend it. Write it down. Say it back. "So, cut the permission opener and get to the reason faster. Got it." And then, if there's time: "Can we run the first fifteen seconds again with that change?"

That last request is the strongest thing you can say in an SDR interview. You have volunteered to be corrected in public and then immediately demonstrated the correction. Every manager who has ever coached a rep knows how rare that is. Most people, given feedback, spend the next thirty seconds explaining why they did the thing rather than doing it differently.

One more move for the end: ask what separates their best rep from their average one. You'll learn something real about the team, and you'll get an answer you can reference in your follow-up email that afternoon.

What to do in the week before

Read the company's careers page and their case studies, and write down three sentences describing a problem their customers have — in the customer's language, not the marketing team's. That's your reason for calling. Write five diagnostic questions whose answers you cannot predict. Write your close with two named time slots in it.

Then say all of it out loud. Not in your head. Out loud, standing up, into a phone. The gap between how a script reads and how it sounds is where most candidates lose the job. And practise the middle — the part after the objection, where you have to respond to something you didn't script. If the role involves calling into an installed base or following up on inbound, run the same drill against a warm call structure, because the framing changes completely when the person half-knows who you are.

If you want reps on this before the interview rather than during it, that's the exact reason I built DrillCall — you get an AI prospect that pushes back, stays in character, and doesn't get bored on the twentieth attempt, which is roughly how many attempts it takes before your objection handling stops sounding like recitation. What I'd do with a week's notice is run the same sixty-second frame twenty times against the objections above until the shape is automatic, then walk into the interview and let the structure carry you.

The hiring manager is not looking for a finished rep. They're looking for someone with a shape, a spine, and the ability to change what they're doing when told. Give them those three things and the mock call is yours.