Sales Executive Interview Questions for Experienced Candidates

“I've spent the last six years selling office equipment and service contracts to mid-sized businesses. For the first two years I sold mostly to office managers, small one-off orders that closed in a week or two. As I got better at it, I moved onto multi-site contracts where the buyer was usually a finance head or an operations director, and a deal took two to four months with three or four people involved. For the last two years I've owned a territory of around sixty active accounts, and I've been the person my manager hands the bigger renewals to. I also started training new joiners on demos. So the sale I know best is a considered purchase with a committee, a contract and a long relationship after it, which I think is close to what you're hiring for.”

“When a senior colleague left, I took over his forty accounts with two days' notice, and his CRM notes were thin. In the first week I sorted the accounts by revenue and by renewal date, so I knew which ones could hurt me soonest. I called the top ten personally, introduced myself, and asked one question: is there anything you were promised that's still open? Three of them had been promised things that weren't written down anywhere, including a free service visit and a price hold. I honoured the ones that were reasonable and was honest with one customer about a promise we couldn't keep. In the first three months I kept every account that was up for renewal, and I also found two that had quietly stopped ordering. After that I pushed for a handover template on our team, so the next person wouldn't start blind.”

“Two years ago my annual target rose by about a third, while my territory stayed the same. My first reaction was that it wasn't possible, so before arguing I broke it down. I looked at what my existing accounts could realistically add, what renewals were due, and how much new business that left. The gap was new customers, roughly two more new customers a month than I'd ever won. I told my manager that honestly in January, not in October, and asked for two things: a list of lapsed accounts from before my time, and some marketing leads in my area. I spent the first quarter reactivating old accounts, which was faster than cold prospecting. I finished the year just under target, the closest anyone on the team got. The lesson was that raising the concern early, with a plan attached, got me support instead of a lecture.”

“Honestly, I'm stronger at growing existing customers. Over the last two years, most of my number came from accounts I already had, through extra sites, add-on services and renewals at a higher level. I'm good at getting to know how a customer runs and spotting where we can help next. New business is where I've had to work harder. I used to let prospecting slip when my accounts were busy, so last year I blocked two mornings a week for it no matter what, and I opened eleven new accounts, which was the most I've ever done. It's still not my natural strength, but it's a habit now rather than something I do when things are quiet. If this role is mostly new logos, I'd want to talk about how the targets split.”

“One of my accounts started as a single small order of printing supplies from an office manager at a logistics firm. Instead of just taking reorders, I asked if I could see how they worked. I found out they had four depots, each buying separately from different suppliers at different prices, and their finance team had no idea what they were spending. I put together a simple comparison for the finance head showing what one contract across all four sites would look like, with one invoice and fixed prices. It took about five months and a trial at one depot, but they moved all four sites to us. Over two years it became one of my three biggest accounts. The lesson I took was that the person placing the order is rarely the person who feels the problem, so I always ask who else is affected.”

“I'd ask for a short meeting in their first couple of weeks, and I'd go mostly to listen. What are they being asked to deliver, and what did they like about the competitor? I wouldn't criticise the other supplier. Then I'd come back with a clear summary of what we've actually delivered for the account, in numbers they care about, like downtime or cost per order, and I'd offer a review of the current setup with fresh eyes, including anything we could improve. At the same time, I'd make sure the other people who use our product day to day know about the change and are happy to speak up. Honestly, if I only had one contact at my biggest account, that was already a mistake. I'd also tell my manager early, so the account plan and forecast reflect the new risk.”

“I'd treat it as a strong year with a weak base. First I'd protect the two big accounts: review their contracts, renewal dates and how many contacts we have in each, and make sure there's a clear plan with each customer for the year, because losing either one would sink the territory. Then I'd look at the next tier down, maybe ten accounts that buy something but could buy more, and pick the five with the most room, based on their size and what they buy elsewhere. I'd also set a steady weekly target for new prospects, even though the big accounts will keep pulling my time. I'd track one simple number each quarter, how much of my revenue comes from the top two, and aim to bring it down gradually while still growing overall. I'd share that plan with my manager so the goal is agreed, not just mine.”

“Two years ago I called a strong quarter and came in well short, because three of the deals I'd counted slipped into the next quarter. Looking back, all three had the same problem: my contact loved the product, but I'd never spoken to the person who actually signed off the budget. I was forecasting on enthusiasm, not on a buying decision. After that, I set myself a simple rule. A deal only goes into my commit if I've met the person who signs, I know their approval steps, and there's a date they've agreed to, not one I've guessed. It made my forecast smaller for a while, and my manager wasn't thrilled at first. But over the next four quarters I landed within a couple of deals of my call every time, and that trust mattered more than a big number.”

“I'd tell my manager straight that I don't think it belongs in commit yet, and explain why in facts, not feelings. For example, the customer hasn't agreed a signing date, or their finance approval is still open. I'd rather say that now than have them pass the number up the line and then have it fall through at the end of the month, because that hurts both of us. But I wouldn't just say no and walk off. I'd put it in as a best case, tell them what I'm doing this week to find out for sure, like getting a meeting with the person who signs, and agree a day by which we'll know. If there's another deal in my pipeline that's more solid, I'd offer that instead. If they still overrule me, it's their call, but my honest view would be on record.”

“At my last company I was renewing a three-year service contract with a manufacturer, and their purchasing lead opened by asking for a big cut, saying a rival had offered less. I'd agreed with my manager beforehand exactly how far I could go, and I'd listed things that were cheap for us but valuable to them: faster response times, a spare unit on site, a free training day. I didn't move on price in the first meeting. I asked what the rival's offer actually included, and it turned out their response time was much slower. In the end I gave a small price reduction, but only in exchange for a longer term and adding their second site. We kept the account, the contract grew overall, and my margin was only slightly lower. What I'd change is getting the plant manager, who valued our service, into the room earlier.”

“I wouldn't agree to the discount, because a promise I'm not allowed to make can come back and hurt the customer relationship more than losing a day. First I'd ask why it has to be today. Often it's a negotiation tactic, or their budget closes this week, and those need different answers. I'd tell them honestly that I want to make this work, the extra discount needs approval from above me, and I'll have an answer by a specific time. Meanwhile I'd try anyone else with authority, like my manager's manager or the sales director, with a short summary of the deal and why I think it's worth it. I'd also look at what I can offer within my own limits, maybe better payment terms or an extra service, in exchange for the longer contract. If I lose the deal because I wouldn't overstep, I can live with that.”

“I had a hospital group as one of my largest accounts, and I found out almost by accident that they'd invited a competitor to pitch for the renewal. Looking back, the signs were there: orders had dropped a little for three months, my contact kept postponing our review, and two complaints had gone to support without anyone telling me. I'd got comfortable because the account had always renewed. I asked for an honest meeting, took our service manager with me, and asked what we'd got wrong. It was slow repairs at one site. We fixed the engineer schedule there, offered a monthly service report, and I started visiting every month instead of every quarter. They renewed, but for one year instead of three, which was fair. Now I track order trends and support tickets for every key account, not just my own calendar.”

“Last year our material costs went up and the company raised prices across the range. I had about fifty accounts, so I sorted them into three groups: long, happy customers, customers who'd complained about price before, and a handful who were talking to rivals. I spoke to the riskiest group first, in person, before the letter went out. I explained the reason plainly, gave them the new prices with plenty of notice, and for the bigger ones offered to lock the new price for a year if they renewed early. A few asked to see cheaper product options, and I showed them honestly. I kept all but two accounts, and one of those came back within six months. The mistake I made was leaving the happy group to the letter alone. Two of them told me they'd have liked a call too.”

“A rep who joined our team last year was booking lots of meetings but closing very few. I sat in on three of his calls and saw the pattern straight away: he started presenting within the first two minutes and never really asked the customer what was going wrong for them. So instead of telling him, I ran two calls myself while he watched, and afterwards we counted how many questions I'd asked before showing anything. Then we role-played his next few meetings, and I gave him one thing to fix at a time, starting with asking three questions before opening his laptop. I didn't join his calls after that, but we reviewed each one briefly. Within two months his close rate had roughly doubled. The hardest part for me was not jumping in when I could see a meeting going badly.”

“Our team kept losing deals late because we'd never confirmed how the customer actually made a purchase decision. I started writing a one-page summary for every serious deal, sent to the customer after the second meeting: what problem they'd told me about, who would sign, the steps to approve it, and a target date. The customer corrected anything I'd got wrong. Over one quarter, deals where I'd sent it closed noticeably more often and slipped less. I shared a couple of real examples at a team meeting, without making a big pitch, and offered to help anyone write their first one. Two colleagues tried it, saw the same effect, and within a few months my manager made it part of our deal reviews. I didn't mind giving it away. When everyone's forecast gets more accurate, the whole team's targets become more sensible.”

“It depends on how serious the mistake is. If it's a small thing, like talking too long or missing a chance to ask a question, I'd let it go. They learn more from finding it themselves, and we can talk about it in the car. But if they're about to promise a delivery date we can't hit, or quote a price that's wrong, I'd step in, because the customer's trust matters more than anyone's pride. I'd do it lightly, something like, let me just add to that, and then give the right detail, so it sounds like teamwork and not a correction. Straight after the meeting I'd explain why I jumped in and ask what they'd do next time. Before any joint meeting, I also agree with the rep who leads which part, so we're not talking over each other.”

“Near the end of a year when our region was short, a senior manager asked me to book an order a customer hadn't signed yet, with the idea we'd sort out the paperwork in January. The customer had said yes verbally, but hadn't approved the budget. I told him I couldn't book it without a signed order, because if the budget fell through we'd be reversing revenue and I'd have told the customer something that wasn't true. Instead, I offered to call the customer's finance head that day and ask if they could sign before year end. They couldn't, so the deal went into January. I missed my annual bonus threshold by a small amount, and the conversation with that manager was cold for a while. But when the customer did sign in January, a bigger order than planned, he mentioned it in my review.”

“First I'd find out why they haven't paid. Sometimes it's a disputed invoice or a missing purchase order number, and that's easy to fix. Sometimes it's a cash problem, which is more serious. I'd call my contact and be direct but friendly: we want to take this order, and here's what's in the way. Then I'd sit down with finance, not argue with them, and see what they'd accept, for example part of the overdue amount now, a clear plan for the rest, or the new order on advance payment. I wouldn't promise the customer anything until finance agreed. In a similar case at my last job, the delay was a wrong address on our invoices. Once we fixed it they paid within a week and the new order went through. Selling to someone who can't pay isn't a sale.”

“I was selling a fleet tracking system to a distribution company, and three people had a say. The operations head wanted better routes, the finance head only cared about the total cost, and the IT manager was worried about yet another system to support. My first meeting was with all three, and it went nowhere because each of them was arguing their own point. So I met each of them one to one. For finance, I worked out the fuel savings from a trial on five vans. For IT, I got our technical lead to show them how little setup it needed. Then I went back to the operations head with both of those answers in hand, and he brought them together. They signed for a first phase of forty vans. Looking back, I should have met each person separately from the start.”

“First I find out why they want it, because the reason often points to a simpler fix. A customer asking for much longer payment terms might really have a budget that only releases at quarter end, and splitting the invoice solves that. If it's still non-standard, I write a short case for whoever approves it: what the deal is worth over its life, what the risk is, and what we get back, like a longer contract or a bigger first order. I send it to finance or operations as soon as the request comes up, not the day before the customer wants to sign, and I ask them what would make it a yes. I also tell the customer honestly that it needs approval and when they'll hear back. At my last company that habit meant most of my special requests were answered within a few days, because the approvers trusted I'd done the thinking.”

“I check a few things, and every one has to come from the customer, not from my hopes. First, a real problem they've said out loud, and what it's costing them to leave it. Second, I know who signs, and ideally I've met them, and I know the approval steps, like whether it goes to a board or through purchasing. Third, there's budget, or at least a clear route to it. Fourth, there's a date they're working towards for their own reasons, like a new site opening. And finally, there's a next meeting booked. If a deal has been sitting with no next step for a few weeks, I treat it as stalled, however friendly the contact is. I review my pipeline like this every week, and I'd rather remove a deal and add it back later than let it pad my numbers.”

“I look at a few things every Friday. First, how many new first meetings I booked, because that's what my pipeline looks like in two or three months. Second, which deals actually moved forward that week, like a proposal sent or a decision maker met, and which ones haven't moved at all. Stuck deals tell me more than new ones. Third, I compare my qualified pipeline to what I still need this quarter. From my own history I know I close about one in three qualified deals, so I want roughly three times my remaining target in there. If any of those slip, I change what I do the next week, usually more prospecting time or chasing the stuck deals for a clear yes or no. The month-end result just confirms what these numbers already told me.”