By Lee Flanagan
Why Hiring an SDR Matters — and Why Most Teams Get It Wrong
The Sales Development Representative role is deceptively brutal. It’s the entry point to enterprise sales, yet it demands a cocktail of resilience, process discipline, and emotional thickness that most candidates simply don’t possess. You’re looking at a role where 60% of new hires either quit or wash out within 18 months. That’s not a hiring failure — that’s the SDR economy. But the ones who stick? They become your best Account Executives, most coachable managers, and longest-retained sellers.
The problem isn’t spotting extroverts. Any recruiter can find someone who talks a lot. The real mistakes happen earlier. Hiring teams conflate confidence with coachability, mistake activity volume for strategic intent, or get seduced by pedigree over demonstrated grit. You’ll see candidates who can recite their CRM’s features but can’t describe a single rejection in detail. Others who’ll talk for twenty minutes about their “process” yet have never written a prospecting sequence that actually landed meetings. The worst ones? They’re waiting for inbound leads, not prospecting outbound — and they won’t tell you that until week three.
This guide covers 25 interview questions across 5 dimensions: Prospecting & Research, Messaging & Personalisation, Objection Handling & Resilience, Activity Discipline & Sequence Quality and Coachability & Feedback Application. Every question here probes intent, resilience, and craft — the three things that predict SDR success.
Core Competencies for a Great SDR Hire
The best SDR hires land on five non-negotiables: Goal-Oriented (quotas matter; they keep score), Ownership (no waiting for marketing; they own the pipeline), Attention to Detail (bad research torpedoes credibility), Relationship Building (prospecting is rapport-building at scale), and Empathy (understanding the buyer’s world, not just the pitch). Two more that separate the exceptional: Influence & Persuasion (moving objectors), and Resilience (surviving the no).
Prospecting & Research
What good looks like
A strong SDR builds target lists that match a defined ICP and persona rather than working from generic data dumps. They use tools like LinkedIn Sales Navigator, intent signals, and company research to identify accounts worth pursuing, and can explain why a specific prospect made the list on a given day.
Behavioural questions
- Tell me about an account you prospected into that you’re particularly proud of.
- How did that account end up on your list in the first place?
- What research did you do before you reached out? Walk me through the sources.
- What made you confident this was the right person to contact, rather than someone else at the company?
- What happened when you reached out, and how long did the full cycle take from first touch to booked meeting?
- Walk me through the last time you built a prospecting list from scratch.
- What was the brief you were working from? Who defined the ICP?
- What filters and signals did you use inside Sales Navigator or your data tool?
- How did you decide which accounts made the cut and which didn’t?
- How did that list actually perform once you started working it?
- Tell me about a time you researched a prospect and decided not to reach out.
- What did you find that made you disqualify them?
- How did you document that so you didn’t waste time on them again later?
- What did you do with the time you got back?
- How did you communicate that decision to your AE or manager, if at all?
- Describe a time your prospecting approach wasn’t working and you had to change it.
- What signal told you it wasn’t landing? Reply rates, meeting quality, something else?
- What did you actually change — the list, the persona, the signals you were filtering on?
- Whose input did you bring in before making the change?
- What was the before-and-after, ideally with numbers?
Situational scenario
You’ve been handed a territory of 400 mid-market accounts in the UK and Ireland. Your manager wants 30 booked meetings in your first 90 days and has given you Sales Navigator, an enrichment tool, and access to the team’s previous sequence library. You start on Monday.
Walk me through your first week.
Then introduce a constraint: “Half the accounts have been touched by previous SDRs in the last 12 months with no result. How does that change what you do on Monday?”
What to listen for
whether they prioritise account tiering before opening the sequencer, how they handle previously-worked accounts without just rebadging old messaging, whether their plan is grounded in observable signals rather than vague 'research', and whether they can articulate what 'good' looks like at the end of week one.
Messaging & Personalisation
What good looks like
A strong SDR writes opening messages that connect a specific trigger or insight about the prospect to a credible business reason to talk. They can explain the difference between superficial personalisation (mentioning a recent post) and relevant personalisation (tying that post to a problem the product solves), and they iterate on their copy based on response data.
Behavioural questions
- Walk me through the best cold email you’ve written in the last six months.
- What was the trigger or insight that prompted you to write it?
- How did you decide on the opening line versus the ask?
- How many drafts did it go through, and what changed between drafts?
- What was the response, and what did you learn from how the prospect replied?
- Tell me about a sequence you wrote or rewrote that improved performance.
- What was the baseline you were trying to beat? Reply rate, meeting rate, something else?
- Which step in the sequence did you change first, and why that one?
- How did you isolate whether it was the copy or something else driving the lift?
- What did the numbers look like before and after, and over how long a window?
- Describe a time a prospect replied negatively to one of your messages.
- What did the reply actually say?
- What did you go back and read in your original message after seeing the reply?
- What did you change in your template the next day?
- Did you reply to that prospect, and what did you say?
- Tell me about a time you used a LinkedIn touch as part of a sequence.
- What was the role of the LinkedIn step versus the email steps around it?
- What did the message actually say — give me the wording as close as you remember it.
- Why that wording for that persona?
- How did it perform compared to email-only sequences for the same persona?
Situational scenario
You’re prospecting Heads of Talent at Series B SaaS companies. You’ve noticed the company you’re targeting just posted ten new engineering roles in the last fortnight and the Head of Talent shared a LinkedIn post last week about how hard it is to hire senior backend engineers in this market. You’re selling a sourcing tool.
Draft the opening message out loud — talk me through it as you write it.
Then introduce a constraint: “Your manager has banned anyone on the team from referencing LinkedIn posts in cold emails because it's become a cliché in our space. Rewrite the opener.”
What to listen for
whether the original message connects the trigger to a specific business outcome rather than just name-dropping the post, whether they hold a clear point of view on what the prospect cares about, how they react when their first instinct is taken away, and whether the rewrite still earns a reply.
Objection Handling & Resilience
What good looks like
A strong SDR recognises common objection patterns — no budget, no time, wrong person, happy with current provider — and has a repeatable way of acknowledging the objection without collapsing the call. They recover quickly from rejection across a day’s call block and can describe specific language they use rather than generic ‘I stay positive’ answers.
Behavioural questions
- Tell me about the toughest live objection you’ve had on a cold call.
- What were the exact words the prospect used?
- What was running through your head in the three seconds after they said it?
- What did you actually say back? Give me the wording.
- Where did the conversation end up, and what did you take into the next call?
- Describe a day where your call block went badly.
- How many calls in did you realise it wasn’t going your way?
- What did you do mid-block — change something, push through, take a break?
- How did the rest of the day go after that point?
- What did you do that evening or the next morning that you wouldn’t have done otherwise?
- Tell me about a prospect who told you they were happy with their current provider.
- What did you ask them next?
- What did you learn about why they were ‘happy’?
- Did the conversation continue, and if so, what kept it alive?
- What did you do with that account afterwards — nurture, disqualify, pass on?
- Walk me through a time you got a ‘wrong person’ objection.
- How did you handle it in the moment?
- What did you do to find the right person without burning the contact you already had?
- How long did it take you to get back into that account at the right level?
- What’s your rule of thumb now when that objection comes up?
Situational scenario
You’ve made 40 dials this morning. Connect rate has been low, and the three connects you did get all ended with some version of “we’ve just signed with a competitor, take us off your list.” It’s 11:30am and you have two hours of call block left before your one-to-one with your manager.
What do you do next?
Then introduce a constraint: “Your manager pulls you aside before the one-to-one and says the team's meeting numbers for the week are behind and she needs you to add another hour of dials this afternoon. How do you respond?”
What to listen for
whether they have a tangible reset routine rather than just 'mindset' talk, whether they distinguish between effort-level problems and quality-level problems, how they handle a manager request that may or may not be the right call, and whether they bring evidence to that conversation.
Activity Discipline & Sequence Quality
What good looks like
A strong SDR runs a consistent daily and weekly rhythm inside their sequencer (Outreach, Salesloft, or similar), keeps their tasks current, and treats the sequencer as a system to be managed rather than a queue to be cleared. They balance volume targets with meeting quality and can explain how they decide what to do first when their task list is longer than the day allows.
Behavioural questions
- Walk me through a typical day from logging in to logging off.
- What’s the first thing you open, and why that?
- How do you structure call blocks versus admin and research time?
- How do you decide what to bump when something runs over?
- What does the last 30 minutes of your day usually look like?
- Tell me about a week where you hit your activity targets but the meeting quality was poor.
- How did you know the quality was poor? What was the signal?
- What did you find when you looked back at the accounts and personas that booked?
- What did you change the following week?
- What happened to your activity numbers when you made that change?
- Describe how you’ve managed your sequencer when your task list got out of control.
- How many tasks were overdue at the worst point?
- What did you do first — bulk actions, triage, something else?
- What rule did you put in place afterwards to stop it happening again?
- How long did the new rule stick before you had to adjust it?
- Tell me about a time you pushed back on a sequence template the team was using.
- What in the data made you sceptical of it?
- Who did you raise it with, and how did you frame the case?
- What did you propose as the alternative?
- What was the outcome, and what did you learn about how decisions get made on your team?
Situational scenario
It’s Wednesday morning. Your Outreach task list shows 180 due tasks across calls, emails, and LinkedIn steps. You have a quota of 15 booked meetings for the week and you’re sitting on 4. Your AE has just asked you to add five named accounts into your sequences today because she’s heard movement in those accounts.
How do you plan the day?
Then introduce a constraint: “You start your call block at 10am and by 11am you've cleared 20 dials with no connects. The AE is now asking when those five new accounts will be live. What do you do?”
What to listen for
whether they triage tasks by likely outcome rather than just clearing the queue top-to-bottom, how they handle a senior stakeholder request that competes with their own plan, whether they protect call block time, and whether they communicate trade-offs rather than silently absorbing them.
Coachability & Feedback Application
What good looks like
A strong SDR seeks out feedback on their calls and messaging rather than waiting for it, applies coaching points in a way that’s visible in their next attempt, and can name specific things they’ve changed in the last few months as a result of being coached. They distinguish between feedback they agree with, feedback they disagree with, and feedback they need more information on.
Behavioural questions
- Tell me about the most useful piece of coaching you’ve had in the last six months.
- Who gave it to you, and in what setting?
- What were the exact words or the specific point they made?
- What did you do differently on your very next call or email?
- How do you know that change stuck rather than fading after a fortnight?
- Describe a time you received feedback you disagreed with.
- What was the feedback, and why did you disagree?
- What did you do before pushing back, if anything?
- How did you raise your disagreement, and with whom?
- Where did you land — did you adopt it, adapt it, or leave it?
- Walk me through a recent call review with your manager.
- Which call did you bring, and why that one?
- What did your manager flag that you hadn’t noticed?
- What did you flag yourself before they got to it?
- What were your two or three action points coming out of the review?
- Tell me about a skill you’ve deliberately tried to improve in this role.
- What made you decide that was the skill to focus on?
- What did your practice or improvement routine actually look like week to week?
- How did you measure whether you were getting better?
- Where do you think you still need work on it?
Situational scenario
You’ve just finished a discovery-style cold call that you thought went really well — the prospect engaged for nine minutes and asked questions. Your manager listens back to the recording and tells you that you talked for 70% of the call, missed two clear buying signals, and that the meeting you booked is unlikely to hold.
What’s your reaction in the moment, and what do you do in the next 24 hours?
Then introduce a constraint: “The meeting does hold and the prospect ends up taking a demo. Does your manager's feedback still stand? What do you do with it?”
What to listen for
whether they separate the manager's observation from the outcome, whether they go back to the recording themselves rather than relying on the manager's summary, how they translate feedback into a specific behavioural change on the next call, and whether a good outcome causes them to discount the underlying coaching point.
Red Flags in SDR Interviews
Watch for these:
“I haven’t taken that many rejections.” Red flag. If someone’s been in the role six months and is genuinely averaging fewer than five rejections a week, they’re not prospecting hard enough — they’re either waiting for warm leads or fishing in a pond that’s too small. An SDR who hasn’t felt the sting of a no isn’t pushing.
“I describe our ICP as mid-market, B2B SaaS companies.” Vague. Real research produces specificity: “Companies that just scaled from Series A to Series B, hired a VP Sales in the last three months, and have Slack in their Salesforce stack.” The level of detail tells you if they’ve actually done the work.
“My sequencer has been running the same sequence for six months and it’s working great.” Danger. Static sequences die. The best SDRs are constantly testing, pivoting, and iterating. Stagnation reads as laziness.
“A message that didn’t work? I’m not sure — I’d have to check my notes.” They should remember. The failures stick with you. If someone can’t recall a single flopped message without digging, they’re not learning from each attempt.
“I’m waiting for Marketing to give me better leads.” Wrong energy. SDRs own their pipeline. If someone’s mindset is passive — waiting for hand-raises and marketing automation — they’ll never build a book of business. This is an entry-level role that demands hunter mentality.
Can’t name a single coach or give specifics on feedback they acted on. Coachability matters more than raw talent. Someone who’s never genuinely taken coaching won’t survive month two.
How to Structure an SDR Interview Loop
Most organisations botch this. Here’s what works:
Stage One: Recruiter Screen (20 minutes). Verify basics — availability, location, compensation expectations, commute. Listen for red flags: vagueness about past rejections, generic talk about “process”, or excuses about past roles. Don’t hire for polish here; hire for honesty and self-awareness.
Stage Two: Hiring Manager Conversation (45 minutes). Deep-dive behavioural. Cover two or three of the rejection/resilience questions above. Watch whether they own failures or blame circumstances. Ask about their actual process, not the process they think they should have.
Stage Three: Live Role-Play (30 minutes). Non-negotiable. Run a mock objection scenario — common ones are “We’re already talking to your competitors” or “We don’t have budget.” Watch not just what they say but how they listen, whether they ask questions, and whether they’re rehearsed or present. Most teams skip this or run it without a scorecard, which turns it into vibes-based hiring. Use a structured framework: engagement, questioning, handling objection, next step clarity.
Stage Four: Peer SDR or AE Conversation (30 minutes). Peer-to-peer reveals things managers don’t see. Your best AE will spot whether the candidate thinks like a seller or like a candidate trying to impress.
Stage Five: Skip-Level or Brief Executive Check (15 minutes). Not a deep interview — a values/energy fit. Often overlooked, but worth it. — structured scoring, consistent rubrics, and recording ensures you’re comparing apples to apples and catching patterns you’d miss in a purely conversational loop.
Ready to Standardise Your SDR Hiring?
Frequently asked questions
Should I ask about sales experience, or is this role for true entry-level?
Both. True entry-level (fresh from school) can work if they show grit and coachability. Prior sales or customer-facing roles are a plus, but don't overweight pedigree. A candidate with six months in retail plus clear resilience often outperforms a failed tech sales hire.
How important is domain knowledge — should they know our product space?
Not essential at interview. You're hiring for coachability and prospecting mechanics, not subject matter expertise. That said, curiosity matters — someone who's researched your market or your competitors in prep signals intent.
How do I probe for "real" grit vs. rehearsed resilience?
Ask for specifics. "Tell me about a tough month" is fine, but press: "How many dials per day?" "How many rejections?" "What did you actually change?" Rehearsed answers feel smooth. Real answers include pauses, self-criticism, and specifics.
What should I weigh the role-play differently — is it deal-breaker material?
Yes. A poor role-play can disqualify, especially if the candidate is defensive or checked-out. A good role-play is not a guarantee, but a bad one is a meaningful red flag. Someone who can't handle a single objection with presence won't survive month three.
Is it worth asking reference checks about rejection tolerance?
Absolutely. Ask former managers: "How did this person handle rejection?" "What was their worst week, and how did they bounce back?" References often reveal coachability far more honestly than the candidate will.