Inside Sales and SDR Interview Questions

"I know what the day looks like. It's a lot of dials, a lot of voicemails, and most people saying no or nothing at all. I've done a version of it already, calling alumni for donations at my college, and what I found was that I liked the puzzle of the first ten seconds. If I got the opener right, people stayed on. I also like that the job is measurable. At the end of the week I can see exactly what I did and what came of it, and I'd rather be judged on that than on how busy I looked. Longer term I want to close deals, and I think the best closers are people who learned to open conversations first."

"From your case studies and the job posts your customers put out, it looks like your buyer is usually a head of finance or a finance operations manager at a company with a few hundred people. Their pain is month-end close. Too many spreadsheets, too many approvals chased by email, and late nights at the end of every month. So I wouldn't open by talking about features. I'd open with something like, 'Most finance leads I speak to tell me month-end close still means chasing approvals in email. Is that true for you, or have you already fixed it?' It names a pain they probably feel, and it's easy to answer. If they say it's fixed, I've learned something too."

"I studied business, and alongside it I worked in a call centre handling billing calls for a phone company. That taught me to stay steady on call number sixty the same as call number one, and to deal with people who start the call annoyed. In my last year I also ran sponsorship outreach for a student event, where I cold emailed and called about forty local businesses. Most ignored us, a few said yes, and I learned that the follow-up usually got the reply, not the first email. So I've done volume, I've done cold, and I've done rejection. What I haven't done is sell a business product properly, and that's what I want this role to teach me."

"I'd like to become an account executive in a couple of years. But I don't see this role as a waiting room. I think the way to earn that move is to be consistently good here, hitting target month after month, and building the skills a closer needs before I have the title. So I'd ask to sit in on the account executives' meetings I book, to learn what happens after the handoff. I'd ask them what made my best meetings good. And I'd try to understand deals end to end, why they close and why they stall. If I'm doing all that and my numbers are solid, I'd hope the move is an easy decision for my manager rather than something I have to ask for."

"In my second month, I went almost two weeks without booking a meeting. I was making my calls, but every conversation ended in 'not interested'. The first few days I just pushed harder, which didn't help. Then I listened back to ten of my recorded calls, and it was obvious. I was pitching in the first sentence, so people had a reason to say no before they'd said anything about themselves. I rewrote my opener to ask one question about their current process instead. I also started logging each no with the reason, so it felt like data rather than a personal verdict. The next week I booked three meetings. The lesson I kept is that a bad run is a signal to check the call, not just to add more dials."

"My manager listened to one of my calls and said, 'You asked a great question and then answered it yourself before they could.' That stung, because I thought the call had gone well. But when I listened back, she was right. I was nervous about silence, so I filled every pause. I started doing one simple thing: after a question, I'd count to three in my head before I said anything. It felt awkward for a week. But prospects started telling me much more, and my notes after calls got a lot richer, which the account executives noticed too. Now I actually ask for call reviews, because someone else hears things I can't hear myself."

"Honestly, I like it. I'd rather know exactly where I stand than guess. When I'm near the top, it keeps me honest, and when I'm near the bottom, it tells me something needs to change, and fast. What I've seen go wrong on those teams is people guarding their best openers or email templates like secrets. I don't think that helps anyone, because the whole team is feeding the same account executives. So I'd happily share what's working for me, and I'd go straight to whoever is top of the board and ask to listen to their calls. The board shows the number. It doesn't show how someone got there, so asking is how you find out."

"There was an operations director at a logistics firm who'd ignored four emails. I noticed on their careers page they were hiring several dispatchers at once, which usually means they're growing fast and their scheduling is under strain. So I called at about eight in the morning, before the day got busy, and opened with that: 'I saw you're hiring dispatchers across three sites, which usually means scheduling gets messy. How are you handling that right now?' He actually laughed and said it was a mess. I asked two more questions, then asked for twenty minutes with our account executive later that week, and gave him two specific times. He picked one. What I'd repeat is finding a trigger that shows they probably have the problem right now, and making the ask specific."

"I'd be honest and short. Something like, 'Sure, I'm calling from a company that helps warehouse teams cut the time they spend on stock counts. I was hoping to have a quick word with whoever looks after warehouse operations. Is that still Daniel?' If they say he's busy, I'd ask for help instead of pushing: 'No problem. When's a good time to catch him, or is there a direct line or someone else who handles this?' Receptionists often know exactly who deals with what, so treating them well pays off. And I'd write down their name so next time I can say hello properly. What I won't do is pretend he's expecting my call. That gets you put through once and blocked forever."

"I keep it short and honest. First, who I am: 'Hi Maria, it's Alex from Acme Software.' Then I'm upfront that it's a cold call, because pretending otherwise puts people on guard: 'This is a cold call, so I'll be quick.' Then one line of relevance, based on what I know about her role: 'I work with operations managers at mid-sized manufacturers, and a lot of them tell me they're still tracking machine downtime by hand.' Then I hand it over with a question: 'Is that the case for you, or have you already sorted that?' The whole thing takes about fifteen seconds. The goal isn't to sell anything. It's to get her talking about her situation."

"I'd open: 'Hi Sam, it's Jordan from Acme Scheduling. This is a cold call, so I'll be quick. Operations heads with shift teams often tell me building the weekly rota eats a day of someone's time. Is that true for you?' If you say yes, I'd dig in: 'Who builds it today, and what happens when someone calls in sick?' Say you tell me supervisors phone around for cover at six in the morning. I'd ask, 'How often does that happen?' Once I've heard the problem in your words, I'd stop asking and make the ask: 'I won't pitch you on the phone, but that's what our customers were dealing with before they switched. Would twenty minutes with my colleague be worth it, to see how it would work for your sites? I've got Tuesday at eleven or Wednesday at three.' If you pick one, I'd confirm your email and send the invite with a short agenda while we're still on the call."

"Yes, but not a pitch. Most voicemails don't get a call back, so I use them to make my email more likely to be opened. I'd keep it to about fifteen seconds: 'Hi Maria, it's Alex from Acme Software. I'm calling about how your team tracks machine downtime. I'll send you a short email in a minute with the subject line "downtime tracking". If it's relevant, just reply there. My number is on it too.' That way, when the email lands, she already knows my name and why I'm writing. I'd say my name and number slowly and clearly. And I wouldn't leave one on every call, maybe the first and one later in the sequence, otherwise it starts to feel like pressure."

"One month last year, I finished at about two thirds of my meeting target. When I looked at my numbers, my dials were fine and my connects were fine, but my connects weren't turning into meetings. So the problem was the conversation, not the effort. I also saw that most of my list that month was a new segment, smaller companies, and I'd been using the same talk track I used for larger ones. It didn't fit. I sat with my manager, rewrote my questions for smaller teams where the owner often does the buying, and asked a teammate who covered that segment to let me listen to a few of her calls. The following month I hit target. I'd rather miss and know exactly why than hit it by accident."

"At my last company, two of us called the same prospect in the same week because neither of us had logged our activity properly. The prospect was annoyed and told us, fairly, that it looked disorganised. After that I made a rule for myself: every call and email gets logged before I move to the next one, with a one-line note and the next step and date. I also spent a Friday afternoon cleaning my territory, merging duplicate contacts and marking people who'd left their companies. When I mentioned it at our team meeting, my manager asked me to show others how I set up my views. It's boring work, but the CRM is how the team knows who's talking to whom."

"I'd track it like a funnel. At the top, activity: calls, emails and social touches each day. Then how many calls actually connect to a person, and how many turn into a real conversation. Then meetings booked, meetings that actually happen, and meetings the account executive accepts as a real opportunity. If I had to pick one, it'd be qualified meetings held, because that's what the business actually needs from me. But the others tell me where to fix things. If my dials are fine and connects are low, it's probably the list or the time I'm calling. If connects are fine but meetings are low, it's my conversation. Activity numbers are the ones I control day to day, so I watch them too."

"A good note lets someone else pick up the account without asking me anything. I'd write the outcome first, like 'Connected, 6-minute call, meeting booked for Wednesday.' Then what I learned: 'Builds the rota in spreadsheets, supervisors phone around for cover at 6am, happens two or three times a week. Head of HR would also have a say.' Then the next step, with an owner and a date: 'AE demo Wednesday at 3, I'll confirm Tuesday.' I'd also update the fields that matter, like the stage, the contact's role and the reason if they said no. No essays, and no vague notes like 'good call'. If I'm off sick tomorrow, the note should be enough for someone else to carry on."

"We had a large retailer on our list that nobody had ever got a reply from. The account executive and I sat down for half an hour and mapped the people we could find: the head of operations, two regional managers and someone in IT. We agreed I'd go after the regional managers with calls, because they're closer to the daily pain, while she wrote a short, senior-level note to the head of operations. One regional manager took my call and told me the stores were struggling with staff scheduling. I booked a meeting with her and our account executive, and she then pulled her boss into the second meeting. What I learned was to go in at more than one level at once, and to agree the message with the AE up front so the prospect hears one consistent story."

"Within about ten minutes of the start time, I'd send a short, friendly message: 'Looks like today got away from you, no problem. Would Thursday at ten or Friday at two work instead?' If there's a number, I'd call too. No guilt, just make it easy to rebook. I'd let the account executive know straight away so they're not waiting. Then I'd look at why it happened. Was the invite clear about what the meeting was for? Did I confirm the day before? Did they really agree, or did I push too hard? If it happens a lot, I'd tighten my process, like sending a short agenda in the invite and a confirmation message the morning before."

"I'd ask for fifteen minutes with the account executive and go through the last few rejected meetings one by one. What exactly was missing? Wrong person, no real problem, no timeline? It might be that I'm missing something, or that we just have a different picture of a good meeting. Then I'd suggest we write down together what a qualified meeting needs, maybe the right role, a problem they've said out loud, and some sense of timing, and I'd put a short summary of each point in my handover notes. After a couple of weeks, I'd check back. If we still disagree, I'd bring in our manager with the notes, not as a complaint but so the team has one agreed standard for everyone."

"When I moved from calling small shops to calling IT managers, I knew almost nothing about security software, and I had two weeks before I was on the phones. I didn't try to learn everything. I focused on three things: the problems our customers had before they bought, the words they used for those problems, and the two or three questions prospects asked most. I got those from reading call notes, listening to a dozen recorded calls and asking our sales engineer for an hour of his time. Then I practised my opener and my answers with a teammate. On calls, when someone asked something deeper, I said, 'Good question, that's exactly what our specialist will cover in the meeting,' which honestly helped me book them."

"I'd say yes right away, because arguing just ends the call. But I'd ask one question so the email isn't generic: 'Happy to. So I send something useful rather than a brochure, are you mostly handling scheduling in spreadsheets today, or do you already have a tool?' Often they answer, and now we're talking about their situation. If it sounds like a fit, I'd say, 'That's actually what our customers usually tell us before they switch. Would it be worth fifteen minutes next week?' If they still want the email, I'd confirm their address, say when they'll get it, and ask when I can call to follow up. Then I send it within the hour, short, and about what they told me."

"'Not interested' this early is usually a reflex, because they don't yet know what I'm calling about. So I'd acknowledge it and ask one thing: 'Totally fair, I did call out of the blue. Can I ask, is that because you've already got this covered, or it's just not a priority right now?' That's easy to answer, and either answer tells me something. If they've got it covered, I might ask what they use and how it's going. If it's timing, I'd ask when would be better. If they say no again, I'd thank them, wish them a good day and end the call. I'd log the reason too. Pushing past a second no just damages the company's name, and I'd rather call back in a few months to someone who remembers me as polite."

"First I'd lower the temperature. 'That's a fair question, and I'm sorry to catch you off guard.' Then I'd be honest about the source, for example a business contact database we use, or their company's website. If I don't know, I'd say so and offer to find out, never guess. I'd give my reason in one sentence and then hand them the choice: 'If it's not relevant, I'm happy to take you off our list right now.' If they ask to be removed, I remove them straight away and mark them as do not contact in the CRM, so nobody on the team calls again. Rules on cold calling and contact data are different from country to country, so I'd follow whatever our company policy says for that market. Keeping someone's trust matters more than one call."

"No, I wouldn't book it. If they clearly don't fit, the account executive loses an hour, the prospect has a bad experience, and next time I book a meeting, the AE trusts it a little less. That trust is worth more than one month's number. What I'd do instead is tell my manager honestly that I'm one short and why. I'd also ask myself why I'm one short on the last day, because the real fix is earlier in the month. If the prospect is a possible fit later, say they'll have a budget next year, I'd note that in the CRM and set a reminder. And on a lot of teams a meeting only counts once the account executive accepts it, so a bad one often doesn't even help the number."

"I need enough to be confident the meeting won't waste anyone's time. First, fit: is this the kind of company we help, and am I talking to the right person or someone who can get me there? Second, a real problem, and I want them to say it in their own words. 'Yes, scheduling is a nightmare' counts. Me saying it and them agreeing politely doesn't. Third, some sense of timing and who else would be involved in a decision. I don't ask those as a checklist. I work them into the conversation, like 'If you did look at fixing this, who else would want a say?' Some teams use a framework like BANT, but I'd use whatever our team agrees. What matters is the account executive walks in knowing why they're there."

"I link the ask to what they just told me, so it doesn't feel random: 'You mentioned your supervisors lose most mornings to finding cover. That's exactly what my colleague can show you how to fix. Would twenty minutes be worth it?' Then I offer two specific times rather than 'when are you free?', because choosing is easier than thinking. If they agree, I send the invite while we're still on the phone and ask them to accept it. The invite has a short agenda in their words and the name of the person they're meeting. The day before, I send a quick confirmation. I'd also ask, 'Is there anyone else who should be in that meeting?' That often brings in the real decision maker."

"With inbound, the biggest thing is speed. Someone who filled in a form is thinking about the problem right now, and the longer I wait, the colder they get, so I'd call within minutes if I could. I'd open with what they did: 'I saw you downloaded our guide on shift scheduling. What made you look at that?' Then I still qualify, because interest isn't the same as fit. A student writing a paper downloads guides too. With outbound, they didn't ask for me, so I have to earn the first thirty seconds with relevance and an honest opener before I get to ask anything. Inbound is more about finding out what they need. Outbound is more about showing them they might need something."

"I'd keep it to about four or five sentences, readable on a phone. The subject line is short and plain, like 'dispatch hiring', so it looks like a real note, not an ad. The first line is about them: 'Saw you're hiring dispatchers across three sites.' Then the problem: 'When teams grow that fast, scheduling usually turns into a morning of phone calls.' Then one line of proof, like the kind of company we helped and what changed for them, without exaggeration. Then a small ask: 'Is that something you're dealing with?' rather than 'Can we book an hour?' An easy question gets more replies, and a reply starts a conversation. And no attachments on a first email. Spam filters are wary of them, and most people won't open a file from a stranger anyway."

"I'd pick two or three people in the account, usually the person who feels the problem daily and the leader above them. Over two to three weeks I'd mix channels. Day one, a call and a short email. A couple of days later, I'd view their profile and connect on a professional network with a short note, not a pitch. Then another call, and an email with a different angle, maybe a relevant example from a similar company. Every touch should give them a new reason to reply, not just 'bumping this up'. I'd vary the times of day I call. And I'd finish with a short, polite closing email saying I'll leave it for now. That last one often gets a reply. Then I log it and set a reminder to try again in a few months."

"For most prospects, I give it two or three minutes, because the job is still conversations, and an hour of research per person means almost no calls. In that time I'm looking for three things. Their role, so I know which problem they probably own. A trigger, like hiring for a certain team, a new office or a new leader, because that tells me why now. And one likely pain I can put into a single opening line. For my top ten or twenty accounts, I'd go deeper, reading recent news, mapping who else is on the team and finding a reason for each person. The test is simple: if the research doesn't change what I say in the first ten seconds, I've done too much of it."