Sales Manager Interview Questions

"I spent four years selling to mid-sized manufacturers and was usually near the top of the team. What moved me toward management was that newer reps kept asking me to sit in on their calls, and I enjoyed that more than my own deals. My manager noticed and gave me two new hires to mentor. When I got the team lead role, the hardest part was stopping myself from jumping in and closing deals for people. It felt quick, but it meant they never learned. So I switched to preparing with them before calls and debriefing after. Today I measure myself on how many of my reps hit target, not on any deal I touched."

"From what I've read and from talking to one of your customers, you sell to operations heads at mid-sized companies, deals usually need three or four people to sign off, and the cycle is a few months, not a few days. That's very close to what I've managed for the last three years. What pulls me in is that you're growing the team fast. I've hired and onboarded seven reps in eighteen months, and I know how easy it is for a growing team to lose its discipline. I'd like to be the person who keeps the standards up while the team doubles. I'd still want to check my picture of your sales cycle with you, because I'm sure I've missed some detail."

"One of my reps was chasing the largest contract our team had seen, with a retail chain. The buyer liked us, but the deal stalled because their finance head had never met anyone from our side. I did three things. I helped the rep map everyone involved in the decision, which showed we'd never spoken to finance or IT. I set up a call between our finance director and theirs, which settled the payment terms question in one meeting. And I got pricing approval from my own boss in a day instead of the usual week. The rep ran every customer meeting and owned the relationship. It closed about three weeks later, and I made sure it was announced as her win."

"My best rep was well over target but kept almost nothing in the CRM, so her deals were invisible in the forecast, and her accounts would have been lost if she'd left. The rest of the team noticed and started asking why they had to update it. I spoke to her privately. I said her results were great, but I couldn't forecast what I couldn't see, and the team was watching. Then I asked what made it painful, and it turned out she was typing the same details in twice. We cut the fields she had to fill in, and she agreed to update everything by Friday each week. She did. If she hadn't, I'd have made it part of her review, because one exception quickly becomes the team's new rule."

"First I'd get the facts, because I want to know exactly what was promised and to which customers before I say anything. Then I'd ask the rep directly. If it's true, the customers come first. I'd work with our delivery team and my manager to decide, account by account, whether we can honour the promise or need to reset expectations honestly, ideally with me on that call. With the rep, it's a serious conversation, and depending on how deliberate it was, it may go to HR. I'd also ask myself whether the pressure I put on the number pushed them to it. If it did, I'd change how I'm running the team, not just deal with one person."

"I think they'd say I'm fair and that I'm in the detail with them. I know every rep's key deals, and I'll help prepare for a big meeting any time. They'd probably also say I'm straight with them. If a deal isn't real, I'll say so. The criticism I've heard is that I can be too involved. A couple of experienced reps told me in feedback that I checked on their deals more than I needed to. That was fair. So now I agree with each senior rep how much contact they want, and I stay out of their deals unless something triggers it, like a deal slipping or a big discount request. It's made my one-to-ones with them far more useful."

"We finished a little over target, and seven of my nine reps hit their own number, up from four the year before. I'd split the credit honestly. The market was kind to us in the second half, and one big renewal landed early, which helped. What I'd claim is the jump in how many reps hit target. I brought in a weekly pipeline review with clear rules for what counts as a real deal, and I spent two hours a week coaching calls with the reps in the middle of the pack. Those middle reps are where most of the extra wins came from, not the top two, who'd have hit target anyway."

"Every week I look at new pipeline created, because it tells me what next quarter will look like. I watch how many deals moved forward a stage and how many stalled. Then the results side: what closed, our win rate and our average deal size. I'd say raw activity, like the number of calls or emails, gets too much attention. It's useful for a new rep, or when someone clearly isn't working, but a rep can make a hundred calls to the wrong people. I'd rather know how many real conversations turned into a first meeting. The whole point of weekly numbers is to spot a problem early, while there's still time to fix it."

"Pipeline coverage is how much open pipeline you have for a period compared with the target you still need to close. People often quote three times as a rule of thumb, but the right number depends on your win rate. If historically about a quarter of the pipeline value we expect in a quarter actually closes, I need roughly four times the remaining target in pipeline, or I'm relying on luck. I work that out by value, not deal count, because a few big deals can skew it. I'd also check timing. Pipeline that won't close until next quarter doesn't help this one, so I only count deals expected to close in the period. And coverage is only as good as the pipeline is honest. If a lot of deals are old and stale, a big coverage number means nothing, so I clean the pipeline before I trust the ratio."

"I had a rep who'd missed target four months running. Before assuming anything, I looked at his numbers stage by stage. His activity was fine and he booked plenty of first meetings, but very few moved on to a proposal. When I sat in on calls, I saw he pitched before he understood the customer's problem. So we agreed a sixty-day plan in writing. He'd run discovery with a simple question list, I'd join two calls a week, and we'd track meetings to proposals every Friday. He improved in the first month, then slipped back. At the end of the plan, HR and I agreed it wasn't working, and we parted respectfully. Looking back, I wish I'd started that plan two months earlier instead of hoping it would fix itself."

"I had a rep who was steady but always finished just under target. Looking at her deals, she won almost as often as the top reps, but her deals were smaller. On calls, she'd name a price as soon as the buyer asked and never explored what else they needed. So for two months we worked on one thing: asking about the wider problem before quoting. We practised in role-plays on Mondays, and each week I listened to one of her recorded calls with her and picked one moment to improve. Her average deal size went up noticeably the next quarter, and she finished the year third on the team. The key was not trying to fix five things at once."

"Three weeks is early, so I wouldn't panic, but I wouldn't wait either. I'd sit down with them and look at what they've actually done. How many calls and emails, to which companies, and what they're saying. Usually it's one of three things: they're calling the wrong people, their opening line doesn't land, or they're doing too little because they're nervous. Then I'd spend a morning making calls next to them, and I'd let them hear me get turned down too. We'd agree a small target, like booking two meetings in the next two weeks, and check in for ten minutes at the end of each day. Most new reps just need a first win to get going."

"I keep deal reviews in the pipeline meeting, so one-to-ones don't turn into a second forecast call. I start with whatever they want to raise, because that's often where the real problem is. Then we look at one skill we're working on, tied to their numbers. If their deals stall after the first meeting, for example, we'd look at how they set next steps. I'll often play back a short part of a recorded call and ask what they'd do differently. We finish with one or two things they'll try this week, and I note them down so I can ask next time. I do them weekly for newer reps and every two weeks for experienced ones, and I try hard never to cancel them."

"I start by asking how they think it went, because reps often spot the problem themselves, and it sticks better when they do. Then I pick one thing they did well and one thing to change, and I point to the exact moment in the call. Something like: around twelve minutes in, when the buyer mentioned their budget review, you went straight to features, and I'd have asked what the review involves. Then we practise that moment for a couple of minutes. I don't give them a list of ten things, because they'll remember none of them. The next time I listen to one of their calls, I check for that one change first."

"I hired a rep who interviewed brilliantly. Confident, great stories, strong numbers from his last job. Within three months it was clear he'd been selling a well-known product with lots of leads coming in on their own, and he'd never had to find his own customers. Our job was mostly outbound, so he struggled badly. What I missed was that I listened to his results without asking how they were made. Now I ask every candidate where their leads came from and what their pipeline looked like at the start of a quarter. I run a short role-play where they have to open a cold call. And with the candidate's permission, I always speak to a former manager, not only the friendliest reference on the list."

"I look for four things: curiosity about the customer's problem, resilience after rejection, coachability, and a track record in a similar kind of sale. Confidence alone isn't on that list, because it's easy to fake in an interview. So I test. I ask them to walk me through a real deal from first contact to close, and I keep asking how, which shows whether they did the work or just rode along. I run a short role-play, give one piece of feedback, and run it again. Someone who takes the feedback and changes their approach is coachable. Someone who argues or repeats the same thing usually isn't. Then I check references with their former managers."

"I wouldn't hire ten people in month one. First I'd spend a few weeks learning the region: which industries and company sizes fit us best, who we're up against, and whether our usual pitch lands there. Then I'd hire two or three experienced reps who are comfortable building from nothing, and I'd go out on calls with them to hear what buyers actually say. Once we can see a pattern that repeats, like which kind of account books meetings and how long deals take, I'd write the hiring profile and onboarding plan and hire the next wave. From day one I'd set up the basics: a clean CRM, ramped targets and a weekly pipeline review. At six months I'd judge us on early signals, like pipeline built and first deals won, because a new region rarely has much revenue to show that soon."

"We finished one quarter well short, mostly because three large deals slipped in the last two weeks. I'd forecast all three as safe, so part of that was on me. I got the team together on the first Monday, said plainly that we'd missed and that my forecast had been too hopeful, and then we went through the three deals together without pointing fingers. The pattern was that in none of them did we know the customer's buying steps. So we changed one rule: a deal can't be called committed unless we know who signs and what steps are left. I also made sure every rep started the new quarter with meetings booked in week one, so there was some momentum. We hit target the next quarter, and our forecasts got much closer to reality."

"I'd thank them for coming to me rather than just resigning, and then ask what's really behind it. Often it isn't only pay. It could be a bigger territory, a path to leading a team, or simply feeling stuck. If there's something fair I can do, like a better account list or a clear route to a team lead role, I'd take it to my manager quickly. What I wouldn't do is make a promise I can't keep, or match an offer in a way that breaks our pay structure, because the team usually finds out. Whatever happens, I'd quietly make sure their key accounts are well documented and that those customers know more than one person here. If they still leave, I want them leaving on good terms."

"Some competition is healthy in sales, and I don't try to remove it. But I make sharing part of the routine. Every week one rep spends ten minutes on something that worked for them, like an email that got replies or how they handled a push-back on price. When I praise people in team meetings, I call out helping as well as closing, like the senior rep who spent an afternoon with a new hire. I also check that the pay plan and the leaderboard don't punish helping, for example by making sure anyone who genuinely assists on a deal gets some credit. And I share my own mistakes first, which makes it easier for everyone else to share theirs."

"My reps said marketing's leads were junk, and marketing said my reps weren't calling them. Both were partly right. I sat down with the marketing manager and we pulled every lead from one month. About a third had never been called within two days, which was on us. But many of the rest were students and tiny firms we don't sell to, which was on the campaign. We agreed a written definition of a qualified lead, a rule that reps call every one within one working day, and a monthly look at what turned into pipeline. The arguing stopped because we were both looking at the same list. Within two months, far more of those leads were turning into real meetings."

"First I'd sit with both reps that day and find out exactly what changed. Is it a delay in signing, a budget freeze, or have we lost it? Then I'd look across the rest of the pipeline for deals that could realistically close early, not ones I'd just hope for. Tomorrow I'd give my director a revised number in three parts: what I'm confident in, what's at risk and why, and the specific actions to win some of it back. I'd rather tell them now that we'll probably land short than surprise them on the last day. What I wouldn't do is push reps into heavy discounts just to drag deals forward. That hurts next quarter and teaches customers to wait for the end of the month."

"I wouldn't just say I don't believe it. I'd ask questions. When did we last speak to the person who signs, not just our friendly contact? What has the customer actually done recently, like sending the contract to their legal team or booking a start date? What steps are left, and does each one have a date? If the answers are vague, the deal goes into best case, not committed, and I'd tell the rep that's not a judgement on them, it's about what we can prove. Then we'd agree one action this week to test it, like asking the buyer to confirm the signing date in writing. If they won't, that tells us a lot."

"I ask reps to update the CRM the day before, so we never spend the meeting reading numbers out loud. Then I split it in two. A short team part, where we look at what's new, what moved stage and what slipped, and then one-to-ones on the bigger deals. For each deal I ask the same few things: why does the customer need to act now, who signs, what's the next step and when is it. If a deal has no next step with a date, it doesn't count as live. I also watch the overall shape. Is there enough early pipeline for next quarter, or is everyone just chasing this month? Every deal we discuss ends with one action, and we check it the following week."

"I build it from the bottom up, then check it from the top down. Each rep puts their deals into commit, best case or pipeline, and I've written rules for each. Commit, for example, means we know who signs, the price is agreed, and the customer has confirmed a date. Then I sanity-check the total against history. If we usually win about one in three deals at proposal stage, and a rep is committing everything at that stage, something's off. I add my own judgement for each rep, because some are always hopeful and some always cautious. Finally, I track how close my call was to the actual result every month. A good forecast isn't always exactly right, but it's close, and it doesn't swing wildly from week to week."

"I'd start with one-to-ones, because in a group the loudest voice sets the mood. I'd ask each rep why they think their target is unfair and what number they'd see as fair. Then I'd check it against their territory's past sales, the pipeline they have right now, and how long deals take to close. Sometimes the complaint is right, like a rep who lost two big accounts to another team but kept the same target. That one I'd take to my manager with the data. Other times the target is tough but reachable, and then my job is to show them how, with a plan for the pipeline they'd need. Either way, I'd tell each of them what I found, even if it isn't what they hoped to hear."

"I'd accept that it's a business decision and not argue it in front of the team. Then I'd do the maths. If each rep brings in a certain amount of new business a year, losing one leaves a clear gap, and I'd show my manager what it would take to fill it: more pipeline per rep, a better win rate, or bigger deals. Next I'd reassign the open accounts by potential, so the best ones go to reps who have room, and I'd cut low-value work like internal reports that eat into selling time. Then I'd go back with a clear ask, maybe more marketing leads or some help from a pre-sales person, and say honestly what I think is achievable. Quietly accepting it and then missing helps nobody."

"I wouldn't just divide it equally. I'd look at each territory's potential: how many good-fit accounts are in it, what it sold last year, and how much repeat business is already there. A rep with a mature patch of loyal customers should carry more than someone building from scratch. New hires get a ramp, a lower target for their first few months, because in a longer sales cycle nobody closes much in their first quarter. I'd also set the rep targets so they add up to a little more than the team target, because in practice someone will leave, get sick or have a bad year. Then I'd walk each rep through how their number was built, so it feels reasoned, not just handed down."

"I'd start with the data, not the map. I'd list every account in the region, mark the current customers, and estimate each one's potential, using things like company size and what they already buy from us or from competitors. Then I'd group them so each territory has roughly equal potential and a workload one person can actually cover, including travel time if it's field sales. Sometimes it's better to split by industry or company size than by area, if buyers in one industry want someone who knows their world. I'd try not to move customers away from reps who have strong relationships with them unless there's a good reason. And I'd review the split after two quarters, because the first design always needs adjusting."

"I'd start with what the business needs this year, because reps will do exactly what the plan pays for. If we need new customers, new customers should pay more than renewals. The plan should have a sensible fixed and variable split, with the commission rate rising once someone passes target, so top performers keep selling instead of saving deals for next quarter. I'd avoid capping earnings, because a cap tells your best people to stop. I'd keep it to two or three measures at most, so any rep can work out their own pay on the back of an envelope. And I'd think through how it could be gamed. For example, if we pay on signing and the customer never pays, we need a way to claw that commission back. Finance and HR would sign it off with me."