A sales development rep has one job that is easy to describe and hard to do: turn names on a list into qualified meetings on someone else's calendar. The work is daily and repetitive, and it rewards people who stay curious on the two hundredth call. A good SDR researches before they dial, writes emails a buyer would actually read, handles the first objection without arguing, and logs everything so the account executive walks into the meeting knowing why it exists. These SDR interview questions are written to surface that mix of rhythm and judgment.
They suit owners hiring their first outbound rep, sales leaders adding a seat to an existing team, and multi-location groups that want one person booking meetings for several offices. Each question includes a model answer and a note on how strong and weak answers differ.
Choose eight to ten questions across the four groups. If your SDR will mostly call, weight the second group. If they will mostly work inbound leads and email, weight the first and third. Ask every candidate the same core set so you can compare them on one scorecard, which you will find further down.
Run at least one live role-play. An SDR who describes a great cold call and an SDR who can actually make one are often different people. Five minutes on the phone with you playing a busy buyer tells you more than twenty minutes of stories. Then close with the paid exercise, which tests research, writing and judgment on your real market.
Model answer: I start with the profile of our best current customers: industry, size, location, the tools they use. I sort the list against that and pull the top fifty that match closest. Then I look for a reason to reach out now, such as a new location, a hiring push or a leadership change. Accounts with a strong fit and a fresh trigger go first.
Strong vs weak: Strong candidates mention fit and timing together. Weak ones start at the top of the spreadsheet and work down.
Model answer: For top accounts, five minutes: their website, a recent post or news item, and the contact's role. For the next tier, one minute and a relevant detail about the industry. I batch research in the morning so I am not switching between reading and dialing all day.
Strong vs weak: Look for tiers and a time limit. Candidates who research every account for twenty minutes will book few meetings; those who never research will book bad ones.
Model answer: I identify the person who feels the problem we solve and the person who signs. At a fifty-person company that may be one person. I check LinkedIn and the company site, verify the email in our data tool, and if I am unsure I call the front desk and ask who handles the area. I would rather ask than guess.
Strong vs weak: Strong answers separate the user of the problem from the buyer. Weak answers target the most senior title on the page every time.
Model answer: I flag the record so nobody else wastes time on it, try a second source, and if the contact has left the company I find out who replaced them. A departed contact is often a good reason to reach the new person.
Strong vs weak: Strong candidates clean data as they go. Weak ones skip the record and move on, leaving it broken for the next rep.
Model answer: I would listen to recorded calls, read the last ten closed deals and the last ten lost ones, and ask the account executive for the three questions they always ask. Then I would write a one-page cheat sheet: who buys, why, what they usually object to, and the best proof points.
Strong vs weak: A strong answer goes to real calls and real deals. A weak one relies on the website and a slide deck.
Model answer: Speed comes first with inbound. I reply quickly, by phone if they left a number, and I reference what they downloaded or asked. With cold accounts I need a reason to interrupt them. With inbound they already gave me one, so the goal is a fast, useful conversation and a meeting.
Strong vs weak: Strong candidates talk about response time and context. Weak ones put inbound leads into the same long cold sequence.
Model answer: Specifics, for example a list of dental offices that kept saying they had someone for that. The candidate noticed every yes came from groups with three or more locations, narrowed the list to those, and changed the opening line to talk about running several offices.
Strong vs weak: Strong candidates read the results and change the targeting. Weak ones simply sent more of the same.
Model answer: Something short that states who they are, why the call, and asks permission. For example: "Hi Maria, it is Dan with [company]. You were not expecting my call. I work with operations leads at multi-location clinics on scheduling no-shows. Can I take thirty seconds to explain why I called, and you can tell me if it is worth talking?"
Strong vs weak: Strong openers are honest and give the buyer control. Weak ones open with "How are you today?" or a two-minute pitch.
Model answer: I agree, then ask one question so the email is worth reading: "Happy to. So I send the right thing, are you handling scheduling in-house today or with a tool?" Often that question starts the real conversation. If not, I send a short, specific email the same hour and reference the call.
Strong vs weak: Strong candidates turn the brush-off into a question. Weak ones hang up and send a generic brochure.
Model answer: Under one hundred words, a subject line that looks like a colleague wrote it, an opening about the buyer rather than us, one clear problem, one proof point and a simple ask. For example: "Saw you opened a fourth location in October. Most groups at that size tell us scheduling gets harder before it gets easier."
Strong vs weak: Strong candidates write tight, specific copy on the spot. Weak ones start with "I hope this email finds you well" and list features.
Model answer: I mix channels: a call and email on day one, a LinkedIn note on day three, a second email with a new angle, another call, then a short breakup note. Usually six to eight touches over about three weeks. Every touch should add something new, a question, a proof point or a resource. If I have nothing new to say, the sequence is too long.
Strong vs weak: Look for varied channels and a reason for each touch. Weak answers repeat "just bumping this up" five times.
Model answer: I respect it and get curious: "Makes sense, most of the groups we work with did too. What made you choose them, and is there anything you wish they did better?" If the answer is "nothing", I ask whether I can check in at their renewal date and log it.
Strong vs weak: Strong candidates ask questions and capture timing. Weak ones either argue or give up immediately.
Model answer: Keep it under twenty seconds, say my name and number twice, reference the email I am about to send, and give one reason to call back. Then I send the email right away so the two touches connect.
Strong vs weak: Strong answers link voicemail and email. Weak ones either never leave voicemails or leave a full pitch.
Model answer: I treat rejections as data and keep my numbers in view. I take a short break after a rough block, review one recorded call to find something to fix, and set small goals like five conversations before lunch. The work is a volume game with a quality bar, and one bad hour does not change the week.
Strong vs weak: Strong candidates have a routine for resilience. Weak ones talk only about "staying positive" with no method.
Model answer: It depends on what the team agrees, but usually: the company fits our profile, the person has the problem or owns it, there is some timing, and they understand what the meeting is for. I would rather book four meetings that are real than ten that are curiosity calls.
Strong vs weak: Strong candidates describe a clear bar and ask what yours is. Weak ones count any yes as a meeting.
Model answer: Two or three, woven into conversation: "How are you handling this today?", "What happens if it stays the same for another six months?", and "Who else would want to see this?" I listen more than I talk and write down their words for the AE.
Strong vs weak: Look for open questions and note-taking. Weak answers recite a framework acronym with no sense of how it sounds on a call.
Model answer: Who they are, why they took the meeting in their own words, what they use today, any timing or budget hints, who else is involved and anything to avoid. Short enough to read in two minutes. I also confirm the meeting with the prospect the day before.
Strong vs weak: Strong candidates write a useful brief and reduce no-shows. Weak ones book the slot and leave the AE guessing.
Model answer: I ask the AE what was missing and adjust my qualification. If I see a pattern, like a certain company size that never fits, I tell my manager and remove it from my lists.
Strong vs weak: Strong candidates welcome the feedback. Weak ones blame the AE for not closing.
Model answer: I call within a few minutes of the missed start, then send a friendly note with two new times. If they no-show twice, I ask directly whether this is still a priority. I track my show rate because a meeting nobody attends does not help anyone.
Strong vs weak: Strong candidates own their show rate. Weak ones say no-shows are the AE's problem.
Model answer: I would compare the deals that closed with the ones that did not. Maybe I am booking users who cannot buy, or companies too small for our price. I would sit in on two of the AE's calls to hear what happens after my handoff, then adjust.
Strong vs weak: Strong candidates investigate the whole funnel. Weak ones say closing is not their job.
Model answer: When they are clearly outside our profile, have no way to buy in the next year, or are not the right person and will not point me to who is. Disqualifying quickly keeps my time for accounts that can move, and I log why so the account can come back later if things change.
Strong vs weak: Strong candidates disqualify with a reason and a date to revisit. Weak ones keep every lead open forever.
Model answer: Accounts touched, conversations, positive replies, meetings booked, meetings held and how many became real opportunities. Activity tells me whether I am working; the later numbers tell me whether the work is good.
Strong vs weak: Strong candidates track the whole chain down to opportunities. Weak ones only count dials and emails.
Model answer: I log as I go, not at the end of the day. Every call gets an outcome and a next step before I dial the next number. I spend ten minutes on Friday cleaning anything I missed. If it is not in the CRM, it did not happen.
Strong vs weak: Look for habits tied to each call. Weak answers admit to catching up "when there is time".
Model answer: Something concrete, such as noticing calls before 9 a.m. connected far more often for their buyers, and moving the calling block accordingly. Or seeing one email template got almost no replies and rewriting it.
Strong vs weak: Strong candidates connect data to a specific change. Weak ones describe working harder.
Model answer: Names and actions, for example HubSpot or Salesforce for records and tasks, Outreach or Salesloft for sequences, a dialer, LinkedIn Sales Navigator for lists, and a data tool like ZoomInfo. The useful detail is what they built: saved lists, templates, reports.
Strong vs weak: Strong candidates describe workflows. Weak ones list logos they have logged into once.
Model answer: Call reviews every week with specific feedback, a clear target and a chance to try something new and report back. I like hearing a recording of my own call even when it is painful.
Strong vs weak: Strong candidates ask for feedback on real calls. Weak ones want coaching only on "the big picture".
Model answer: Many good SDRs want to become account executives, and that is a healthy answer if they can say what they are learning toward it, such as running discovery or handling pricing questions. Others want to lead SDRs. Either is fine. Be wary of no answer at all.
Strong vs weak: Strong candidates have a direction and a plan for getting there. Weak ones see the role as a stopgap.
Pay the candidate for two to three hours. Give them a short description of your ideal customer, three anonymized customer stories and a list of fifty real-looking target accounts. Ask them to return:
Then run a five-minute live cold call role-play using one of their own accounts, with you playing a skeptical buyer. Score research, writing, call handling and judgment separately.
Score each area from 1 to 4 after the interview and the exercise. A hire should score at least 3 in every row, with no row at 1.
If you would rather meet strong candidates than run this process yourself, Ryz can place a dedicated sales development rep on your team. Your SDR works in your CRM, your email domains and your sequences, keeps your US business hours, and writes and speaks fluent English. Ryz recruiters screen every candidate, and you meet a named shortlist before anyone starts. Most start in under two weeks. Tell us the role and we'll send a plan and a price, or book a call. Writing the role first? Use our sales development rep job description template.
Three is usually enough: a short phone screen (which doubles as a test of their phone presence), a structured interview with a live role-play, and a paid exercise with a debrief. Have the account executive who will receive their meetings join one round.
You can, if you have someone to coach them every week. Look for evidence of resilience and clear writing from other jobs, such as customer service or recruiting. If nobody has time to coach, hire someone who has already done outbound.
Both book meetings. SDRs usually work warm leads and a defined target list; BDRs usually open new markets, segments and partners from cold. See our BDR interview questions for that role.
Role-play it. Give the candidate a short brief, play a busy buyer, and raise one or two common objections. Notice whether they stay calm, ask questions and ask for the meeting.
It depends on your market and how much material you give them. A rep who gets real call recordings, past wins and a clear qualification bar in week one ramps much faster than one who starts with a slide deck.
Questions we didn't answer? Email info@ryzlabs.com.