Sales Executive Interview Questions

"My first taste of it was running the stall for our college fest sponsorships. I had to call local businesses who'd never heard of us, and most said no, but the ones who said yes did it because I'd worked out what they wanted, which was students walking past their shop. I liked that the result was clear: either you got the sponsor or you didn't. After that I took a part-time role selling phone plans in a store, and I was consistently near the top of the board. I'd pick sales over a fixed routine because I like being judged on what I actually deliver. I know there'll be bad weeks and a lot of no's. That part doesn't scare me, it's just the job."

"From your website, your case studies and a few reviews, it looks like most of your buyers are owners or operations heads at mid-sized manufacturers. They're buying because they're losing time and stock to messy inventory tracking, not because they love software. That's the kind of buyer I've sold to before. At my last company I sold packaging supplies to factories, so I know how a plant manager thinks: they want to hear about downtime and reliability, and they hate being sold to by someone who's never seen a shop floor. I want to sell your products because they solve a real, expensive problem for people I already know how to talk to."

"I'm happy to share when someone genuinely helped. I'd rather have a smaller share of a deal we won than all of a deal we lost. At my last company, a senior colleague joined a negotiation with me because the customer wanted someone with more years in the room. She made a real difference, so we split the credit and I didn't think twice. It also meant she was glad to help me again the next time. I'm competitive, and I like being near the top of the board, but I'd rather get there by selling more than by guarding every lead. If the split rules are clear upfront, it rarely turns into an argument."

"I do my best work with a manager who's clear about the target, gives me honest feedback, and actually listens to my calls or comes out on visits now and then, because that's where I learn the most. My best manager used to go through one lost deal with me each month, not to blame me but to find the pattern. What works less well for me is being checked on every hour without any coaching behind it. In return, I keep my CRM up to date so my manager never has to chase me for where things stand, and I ask for feedback rather than waiting for it. I think that makes me easy to manage."

"I was measured on three things: new revenue each quarter, the number of new accounts I opened, and a weekly activity target for meetings. Over the last two years I hit my revenue target in six of eight quarters, and I beat it by a good margin in two of those. The two I missed were back to back, when a large customer delayed a rollout and I'd leaned on that one deal too much. What I changed after that was simple: I never let one deal be more than a small slice of my forecast again, and I kept more early-stage deals in play. I'm happy to walk you through any of those numbers in detail."

"About a year in, I went five weeks without closing anything. My first instinct was to just make more calls, but I sat down with my CRM and looked at where deals were dying. Most of them were getting stuck after the proposal. I realised I was sending proposals too early, before I really understood the problem, so they read like price lists. I changed two things. I added a second discovery conversation before any proposal, and I started booking a call to walk through the proposal instead of emailing it. I also asked my manager to listen to two of my calls. Within the next month I closed three deals, and my proposal-to-close rate stayed better after that."

"I'd ask, but honestly. I'd call and say something like, 'You mentioned signing next month. Is there something that has to happen first, or is it just timing?' Sometimes it's only a signature waiting for someone to get back from leave, and sending the paperwork to whoever can sign sooner solves it. If signing earlier genuinely helps them, like getting an installation slot before their busy season, I'd point that out. What I wouldn't do is make up a price rise or throw in a discount just so my month looks better. They'd work it out, and I'd have taught them to wait for month end every time. If next month really is right for them, I'd tell my manager straight, move it in the forecast, and put my energy into deals that can close this month."

"First, I'd give myself a couple of minutes in the car and not pretend it didn't sting. Then I'd look quickly at whether the three nos had anything in common. If all three said they're locked into a contract, that's useful, so I'd note the end dates in the CRM and plan to call back before then. If it's just a bad run, I let it go, because the next customer had nothing to do with it. Then I'd spend the rest of the time on the meeting ahead: reread my notes, remind myself what they told me last time and what I want to leave with, like a date for a trial. If I walk in still thinking about the last three, I'll rush to the pitch and sound desperate, and buyers pick that up straight away."

"The first thing I'd make sure of is that the customer doesn't get two reps calling them with different stories, because that looks bad for all of us. Then I'd check the CRM, since that's the record of who owns the account and who's been talking to them. I'd speak to my colleague privately, assume there may be a misunderstanding, and ask what happened. Sometimes they got an inbound call and didn't check ownership. If we can agree, great. If we can't, I'd take it to our manager with the records and let them decide. Even if I felt wronged, I wouldn't let it turn into a feud, because I'll be working with that person for a long time."

"I was working a deal with a chain of clinics. The operations manager loved our product, we'd done a demo and a trial, and I'd already put it in my forecast. Then the finance director stepped in and chose a cheaper option. Looking back, my mistake was that I'd only ever talked to one person. I never asked who else had a say or what finance cared about, so I never made the case on cost savings. When I asked for feedback, the finance director told me nobody had shown her the numbers. Since then, in every deal I ask early who else is involved in the decision, and I try to meet the person who signs the cheque before I call a deal likely."

"The ones I use most are simple. A trial close along the way, like, 'If we could sort out the setup, does this look like the right fit?' That tells me where they stand. A summary close at the end, where I recap what they told me they need and how we meet it, then ask if they're ready to go ahead. And sometimes a choice between two real options, like starting with one team or all three. For me, the line is honesty. Asking clearly for the business is my job. But inventing a deadline, saying the price goes up tomorrow when it doesn't, or pushing after someone's said no clearly, that's pressure. It might win one deal, but it loses referrals and repeat business."

"I noticed a regional logistics company posting a lot of jobs for warehouse staff, which told me they were growing fast. I looked up their operations head, sent a short message about how two similar firms had cut their picking errors with our scanners, and asked for fifteen minutes. The first call was mostly questions. I learned that errors were costing them re-deliveries every week. I brought our technical lead to the second meeting to do a small trial in one warehouse. The trial showed a clear drop in errors, so the business case wrote itself. They signed for one site, then rolled out to three more that year. I'm proud of it because it started from a job advert, not a warm lead."

"First I'd look at who buys from us in other territories and what they have in common, their industry, size and the problem we solve for them. That becomes my ideal customer. Then I'd build a list of fifty or so companies in my area that match, using business directories, trade associations, local news about expansions, and anyone my colleagues elsewhere know there. I'd rank them by how good a fit they look. From week two, I'd work a daily rhythm of calls, short messages and a few walk-in visits, and log everything. I'd also go to a local trade event if there's one. My goal for the month is a handful of real conversations and one or two early customers I can use as references."

"A restaurant owner told me she was happy with her current supplier and didn't want to switch. I thanked her, asked what she liked about them, and asked if I could check in every couple of months. In between, I sent her a note when we launched a product line that fit her menu, and once I dropped off samples when I was nearby, with no pitch. About five months later her supplier had a string of late deliveries before a busy weekend. She called me because I was the one she remembered. We started with a small trial order and she moved most of her business to us within a few months. What changed wasn't my pitch. It was that I was still there when her problem showed up."

"Early in my career I told a customer we could deliver a custom version of our product in four weeks. I'd assumed that from an older deal and never checked with operations. It turned out to be ten weeks. I found out two days after they'd signed. I called the customer the same day rather than hoping it would sort itself out, told them plainly that I'd got it wrong, and gave them the real date. Then I worked with operations to ship the standard version in the meantime so they weren't left empty-handed. They weren't happy, but they stayed, and they told me later that the phone call was why. Since then I never commit to a date or a feature without checking with the team that delivers it."

"First I'd listen and let them get it all out, and I'd tell them I'm glad they called me directly. Then I'd ask what they expected it to do and what it's actually doing, so I can see where the gap is. Often it's a setup issue, and I can get our support or technical team on a call with them that week. If the gap is because of something I said during the sale, I'd own that plainly. Either way, I'd agree a clear next step and a date, and I'd call them myself afterwards to check it's fixed. A customer who gets taken care of after a problem often ends up more loyal than one who never had one, and they're the people who give referrals."

"I had a prospect who wanted our software, but only if we built three custom features and gave them payment terms far longer than we ever offered. It would have been a decent-sized deal in a month I needed it. But when I dug in, their main need was something our product doesn't do well, and our support team would have spent months on workarounds. I went to my manager with the numbers and my view that we'd likely lose them within a year and carry the cost of it. We agreed to decline. I told the prospect honestly that we weren't the right fit for that need and suggested what kind of tool would suit them better. They respected that, and they've since referred another company to me that was a good fit."

"Before I tell you anything about this pen, can I ask when you last signed something that mattered? This morning, a contract with a client, okay. What did you sign it with? Whatever was lying on the desk. And did it work first time? It skipped, right. So here's what I'd say: this one writes smoothly the moment it touches paper, it's refillable, so when it runs low you swap the ink in seconds instead of hunting for a pen that works, and it looks like it belongs to someone who signs serious deals. You said you've got more contracts coming this quarter. Shall I leave this one with you so it's ready for the next one?"

"I think of it in a few stages. First is prospecting, finding people who might need what we sell, and qualifying them, checking they have the need, a budget and the power to decide. Then discovery, where I ask questions to really understand their problem. Only after that do I present or demo, and I shape it around what they told me. Next come objections and negotiation, where I answer concerns and agree terms. Then the close, which is simply asking for the business. After signing, I make sure the handover is smooth, check in once they're up and running, and look for chances to grow the account or ask for a referral. Most lost deals I've seen skipped discovery."

"In my first few months selling office printers, a facilities manager asked whether our machines could print straight from their document system without going through a computer. I wasn't sure, and I could feel the pull to just say yes. Instead I said, 'I don't want to guess on that. Let me check with our technical team and get back to you by tomorrow.' I rang our support lead from the car park, found out it worked but needed an extra licence, and emailed her that afternoon with the exact answer and what it would cost. She told me most reps just say yes. After that I sat with support for an hour a week until I knew the common questions cold, and I kept a list of them. We won that deal the next month."

"I'd say what's happened rather than pretend it's meant to do that. Something like, 'That's not what it should be doing, give me a minute.' If a quick restart fixes it, fine. If not, I wouldn't keep fiddling with it while they watch. I always carry a backup, like a second unit or a short recorded demo, so I'd switch to that. Then I'd use the time to ask more about how they'd use it day to day, which is often the most valuable part of a meeting anyway. Before leaving, I'd agree when I'll come back with the cause. Then I'd get the answer from our technical team and go back with it, and a working demo if they want one. How you handle a failure shows the buyer how you'll handle their problems later."

"A feature is what the product has. An outcome is what the customer gets from it. Take a delivery van with a bigger load space. If I say 'it has a larger cargo area', that's a feature, and the buyer has to work out why it matters. If I say 'your drivers can do their full route in one run instead of coming back to reload at lunch, so each van covers more deliveries a day', that's an outcome. And the outcome changes with the buyer. For a small florist it might be fewer trips. For a fleet manager it's fewer vans. I try to lead with the outcome that buyer told me they care about, and use the feature as the proof."

"Thanks for telling me, I'd rather know than guess. They're a decent company, so I won't knock them. Can I ask what's included in their quote? Things like delivery, installation, how long the warranty runs and who you call when something breaks? Earlier you told me the biggest pain with your last supplier was waiting a week for repairs. Our price includes an engineer on site within two working days, and that's in the contract, not just a promise. If their quote covers the same, then the prices really are close and I'd like to know what would make this an easy choice for you. If it doesn't, it's worth working out what a week of downtime costs you before comparing the headline numbers."

"I use the same simple approach every time. First I listen fully and acknowledge it, without jumping in. Something like, 'That's a fair point, a lot of people ask that.' Then I ask a question to understand it, because the first objection is often not the real one. 'Too expensive' might really mean 'I can't see the value yet' or 'I'd have to justify it to my boss'. Once I know the real concern, I answer that specific thing, ideally with an example from a similar customer. And then I check: 'Does that answer it, or is there something else on your mind?' If there's nothing else, that's usually a good moment to talk about next steps."

"I understand, it's a real investment, and I'd be worried if you weren't thinking about cost. Can I ask, when you say too expensive, is that compared with a budget you've got in mind, another quote, or is it more that you're not sure it'll pay for itself? Okay, so it's whether it pays back. Earlier you said your team spends around two days a month fixing billing errors by hand. If this takes most of that away, how long do you think it would take to cover its cost? That's how I'd look at it too. Would it help if I put those numbers on one page for you and your finance lead to look at together?"

"That's completely fair, I know timing matters. Can I ask what's happening this quarter that makes it a bad time? A system migration, okay, that makes sense. Just so I understand, the billing problem you mentioned, does that keep costing you while the migration's going on? It does. So one option is we don't start anything now, but we do the planning work together so you're ready to go the day the migration ends. If you'd rather leave it completely, that's fine too. Could we put a call in the diary for the first week of next quarter, and I'll send you a short summary beforehand so we're not starting from scratch?"

"First I'd call both of them back straight away to rebook, while they still feel a bit bad about cancelling, because that's when people are most willing to commit to a new time. Then I'd look at who else I know in that area. I usually keep a short list of nearby customers and prospects for exactly this reason. I'd drop in on an existing customer to see how things are going, and maybe walk into one or two businesses I've been meaning to approach. Any time left goes on follow-up emails and getting my notes into the CRM. A cancelled meeting shouldn't mean a wasted afternoon."

"I plan on Friday afternoon for the week ahead. I start with my pipeline and ask which deals actually need me in the room to move forward, like a demo, walking through a proposal, or meeting a new decision-maker. Those get booked first. Then I group everything by area, so Monday might be one side of my patch and Tuesday the industrial estate, because hours in traffic are hours not selling. Around each booked meeting I add a nearby customer to check in with and a couple of prospects I can call on. I'd rather have four good meetings in a day than eight rushed ones. And I keep one morning clear for proposals, follow-up emails and updating the CRM, otherwise the admin eats my evenings and the follow-ups slip."

"For me, the CRM is my memory. I might be talking to forty prospects, and I can't remember who mentioned their budget or who's waiting on a sample. After every call or meeting I log a short summary of what we discussed, anything they said about need, budget or who decides, the agreed next step with a date, and I update the deal stage and expected value so the forecast is honest. I do it straight away, in the car or right after the call, because by Friday the details are gone. It also matters for the team. If I'm off sick or leave, someone else can pick up the deal without the customer having to repeat everything, and my manager can plan without asking me for updates."

"I'd work backwards from my own history. Say one in three of my proposals closes, one in two meetings leads to a proposal, and one in five real conversations gets a meeting. For ten customers I'd need thirty proposals, which means sixty meetings, which means around three hundred conversations. Over a thirteen-week quarter, that's about twenty-three conversations and just under five meetings a week. But deals take time to close, so if my cycle is six weeks, most of that has to happen early in the quarter, not spread evenly. Then I check whether it's realistic. If it isn't, improving one stage often beats just working harder, like better qualification so more meetings turn into proposals. And I count what's already in my pipeline, because those deals cut what I need to start from scratch."