Sales Engineer Interview Questions

"I studied mechanical engineering and started in a plant maintenance team, so I was the customer for a lot of salespeople. Most of them could recite a brochure, but the one I trusted asked about our duty cycle and our breakdown history before he offered anything. That stuck with me. When a sales engineer job came up at a pump maker, I took it. What I enjoy is that I still use the engineering every day, reading a spec or sizing a product, but I also see the result, an order and a customer whose line runs better. In my second year I moved two maintenance-heavy plants onto a better-matched model and they became my steadiest repeat customers."

"From your catalogue and your case studies, most of your business is control panels and switchgear for mid-sized factories, plus a growing line of drives. Your buyers look like food processing, packaging and water treatment plants, where the electrical engineer picks the spec and purchase negotiates the price. I spent two years selling cable and accessories into those same kinds of plants, so I already know how their projects run, who signs off and what they worry about, which is downtime and safety. What draws me is that panels and drives are a bigger, more technical sale than cable. I'd be working with engineers on the design, not just quoting a rate per metre."

"I looked hard at both. A design job would keep me at a desk on one part of one product, and I found in my internship that I'm happiest when I'm talking to people and moving between problems. In my final-year project we had to buy sensors from three suppliers, and I ended up being the one who compared their datasheets and dealt with their reps. I understand this role means travel, targets and a lot of no before a yes, and that I'll need to learn the product properly before anyone listens to me. I'd rather build that technical base facing customers than learn it in isolation."

"I'm genuinely fine with it. Customers buy from people they've met, and I learn far more on a shop floor than at a desk. The risk with travel is that quotes and follow-ups slip, so I keep a routine. I plan the week on Friday by area, update my notes after every visit while I'm still in the car park, and keep one morning a week for offers and pending replies. When I'm travelling, I tell customers when they'll hear back and stick to it. In my last job there was a week with visits in three towns plus a tender deadline, and I kept the tender work to evenings so I could still make every visit and submit on time."

"A dairy plant sent an enquiry for a standard cast iron pump to move a cleaning solution. The flow and head were fine, but when I asked what the solution was, it turned out to be the acid step of their cleaning cycle, and cast iron gets eaten away by acid over time. I called their project engineer rather than purchase, asked for the chemical details and temperature, and sent a short note comparing the two materials for that duty. I quoted both options, with the stainless one clearly recommended. It cost more, and purchase pushed back, but the engineer backed it because I'd shown him the reason in writing. The pump is still running, and that plant now sends me enquiries before they write the spec."

"I wouldn't mark it compliant. If the customer tests it at inspection or in use, we either get rejected at delivery or we've shipped something we said it wasn't, and the damage lasts much longer than one lost bid. I'd go back to my manager with options instead of just a no. First, check whether the shortfall matters for their actual duty, and if the tender allows pre-bid queries, ask the customer about it. Second, list it honestly as a deviation, with a short technical reason why it won't affect performance. Third, see if a different model or an add-on meets the figure fully. Most evaluators accept a well-explained minor deviation. What they don't forgive is finding out later."

"I read the whole thing once before quoting anything, because the traps are rarely in the technical section. I note the deadline, the bid format, qualifying criteria like past supply records or certificates, any approved vendor or make list, and whether the technical and commercial bids go in separately. Then I build a clause-by-clause compliance sheet: complied, deviation with a reason, or needs clarification. Anything unclear goes to the customer as a pre-bid query before the cut-off. Next I pick the model, get our application engineer to check sizing and the special requirements, and gather datasheets, drawings, test certificates and type approvals. Finally, someone else reviews it against the checklist before submission, because a missing signed page can knock out a good bid."

"I start with the bill of materials from engineering, priced at current rates, then add labour and testing time. Next come the costs people forget: special packing, freight to site, transit insurance, installation and commissioning if we're doing it, and a provision for warranty. Then I look at the terms. Long credit costs us money, so it has to be reflected, and if delivery is months away and the product is heavy in copper or steel, I'd either add a buffer or include a price variation clause. On top of that goes our target margin. Finally I check the number against what the market will bear and what I'm allowed to discount, so I know my opening price and my floor before I send it."

"A good offer starts with the customer's enquiry reference, then the scope of supply and technical details with datasheets. Then the commercial terms: the price basis, meaning ex-works or delivered and who pays freight and insurance, taxes and duties shown clearly, delivery period, payment terms, warranty period and from when it starts, and how long the offer is valid. The clause people forget most is exclusions. If civil work, cabling or site unloading aren't ours, it must say so, or we end up doing them free. The second one is what starts the delivery clock, for example from receipt of a clear order, advance and drawing approval, not from the day they email a PO with open questions."

"I lost a compressor order for a textile mill to a cheaper competitor. At the time I blamed price. When I asked the buyer for feedback afterwards, he said the two offers looked the same on paper, so he took the lower one. That was on me. Our machine used noticeably less power at their load, but I'd put that in a datasheet at the back instead of showing them what it meant on their electricity bill. I had also only met purchase, never the utilities engineer who'd care about running cost. Now, on any equipment that runs long hours, I get to the user early and put a simple running-cost comparison on the first page of the offer."

"A cement plant had used one bearing and seal brand for over a decade. Their maintenance head said openly that nobody gets blamed for buying the usual brand. So I didn't ask for the whole account. I asked which position gave them the most trouble, and it was a fan that failed every few months because of dust. I proposed a trial on just that one fan, with our application engineer checking the fit and lubrication, and we agreed to log running hours and temperature together. It ran well past their usual failure point. That data, collected by their own team, did the selling. Over the next year they moved several other positions to us, and I never had to lead with a discount."

"First I'd ask for the detail behind the sheet, or at least the scope each bidder quoted, because three offers are rarely the same thing. I'd go through it line by line: materials, ratings, what's included like installation, spares and testing, the warranty period, delivery and payment terms. Very often the cheapest one has left out something the customer will pay for later. I'd send purchase a short, polite note showing where the offers differ, and I'd call the user engineer too, because they care about those differences more than purchase does. Then, if there's still a real gap on a like-for-like basis, I'd talk to my manager about what we can move, within our limits, and reply by the deadline they gave me."

"I break ownership cost into what they pay once and what they keep paying: purchase and installation, then energy, routine maintenance, spares and the cost of breakdowns. For something like a pump or compressor running most of the day, the electricity over its life is often the biggest cost, well above the price of the machine, so a small efficiency gain matters. I use their own numbers, their running hours, their power rate, what an hour of stopped production costs them, so it isn't my claim, it's their data. Then I put it on one page, our unit next to the cheaper one over, say, five years. Buyers are measured on price, so I also give it to the user engineer, who can argue for it inside."

"First I'd find out what's behind it. Sometimes the buyer has a budget ceiling, sometimes they just need to show their boss they got something. Then I'd look at what costs us little but helps them. If they pay a larger advance or pay faster, that's worth real money to us, so I can give something for it. A bigger quantity or a two-year rate contract justifies a better price. I could include a starter pack of spares, commissioning, or a longer warranty rather than lowering the unit price, which also protects the price for next time. Or we reduce scope, like dropping installation they can do themselves. Whatever I give, I ask for something back, so the discount isn't the only thing that moves."

"I'd sold two control panels to a packaging plant with a firm delivery date tied to their shutdown. Three weeks before, production told me one imported component was delayed. I told the customer the same day, rather than hoping it would sort itself out, and gave them a date I could stand behind. Then I sat with our planning and purchase teams to find options. We agreed to ship both panels on time with that one component fitted on site later, which our service engineer could do in an hour without another shutdown. The customer ran their shutdown as planned. Since then I check component availability with planning before I promise a delivery date, not after."

"First I'd let him vent, then ask for the facts: what exactly stopped, any alarm or error code, what they were running at the time, and photos or a short video. With a line down, two days isn't acceptable, so I'd call the service manager directly with that information. Often the technical team can diagnose a lot over a video call, or someone nearer can go sooner. I'd tell the plant head exactly what I'd done and when he'd hear from me next, and stick to that. If I could get there the same day, I would, even if I can't repair it myself, because being on site tells the customer we're taking it seriously. Afterwards I'd check whether the installation or setup caused it."

"I wouldn't say yes on the spot to win it. First I'd ask the customer what's driving the date. Sometimes only one unit is needed urgently, or they need drawings early for their civil work more than they need the product. Then I'd check with planning: is anything in stock or in finished goods, is there a similar unit in production for a customer who could wait and would agree to swap, can a standard model replace a special one for now? I'd go back with an honest answer, for example one unit in three weeks from stock and the rest at the normal time, or a firm date if that's the best we can do. A date I can keep is worth more than a promise that turns into a penalty and an angry customer."

"First I check the customer's order against my offer line by line, because orders often slip in different terms, and I clear any mismatch before we accept it. Then I hand it over to our order team with everything they need. If drawings or datasheets need customer approval, I chase that, since delivery usually runs from approval. I keep the customer updated on manufacturing, set up any inspection they want to witness at our works, and make sure dispatch papers are right. Before delivery I confirm the site is actually ready, because a machine sitting in a crate isn't commissioned. Then I coordinate our service team for installation and commissioning, a proper handover and operator training, and I make sure they know how to reach us under warranty."

"I try to make their jobs easier, because every promise I make depends on them. That means handing over orders with everything clear, the right specs, approved drawings and agreed terms, so production isn't chasing me for details. I check with planning before I promise a date, and I don't escalate over their heads unless I've spoken to them first. When a customer is happy with an installation, I forward the message to the service engineer and his manager, because they rarely hear the good news. With accounts, I help chase payments instead of treating collections as their problem. In return, when I have a real emergency, people are much more willing to help."

"One dealer's sales of our motors had been flat for a year while the rest of the region grew. Instead of just raising his target, I spent a day at his shop. Two things came out. His counter staff didn't know our range, so they sold the brand they understood, and he kept almost no stock of our faster-moving sizes, so walk-in buyers went elsewhere. We agreed a small standard stock list, I ran two short product sessions for his staff, and I took one of them with me on a few factory visits. Within two quarters he was back in line with the region. If nothing had changed, I'd have discussed adding a second dealer with my manager."

"I'd get the facts before reacting. Maybe the customer's purchase team sent the enquiry to the dealer too, which happens. I'd call the dealer, not to accuse him, but to understand what he quoted and on what terms. Then I'd go to my manager with the company's account rules, because most firms decide which accounts are handled directly and which through dealers. The worst thing for us is two different prices from the same brand, so we'd agree internally who handles this account and at what price, and give the customer one clear offer. If the dealer is the better route for service, I'd happily let him close it and take the credit my company's policy allows."

"When I choose a dealer, I look at who they already sell to and whether that overlaps with our target customers, whether they have staff who can talk technically, their financial health and payment record, and which competing brands they carry, because that decides how much attention we'd get. Once they're on board, we agree a yearly target, a basic stock list, credit terms and the area they cover. Then the real work is making them want to sell us: I train their staff, go on joint visits to their key customers, pass them leads that suit them, and make sure any schemes are clear and paid on time. I review numbers with them monthly, face to face, not just by email."

"In my first few months, a maintenance engineer asked whether our gearbox could run in a room that got very hot in summer and what that would do to its rating. I knew there was some derating but not the numbers. I told him I didn't want to guess on something that affected his equipment life, wrote the question down with his room temperature and duty, and promised an answer within two days. I asked our application engineer that afternoon, and sent the customer a proper reply with the corrected size the next morning. He told me later that was why he trusted our quote over the others. I also made a short sheet of the questions I'd been asked, so I'd be ready next time."

"I'd start with the load, not the motor. What's the conveyor carrying, at what speed, and does it start fully loaded? A loaded conveyor needs good starting torque, so that affects the choice. Then the duty: does it run continuously or start and stop many times an hour, because frequent starts heat the motor. Next the supply voltage and frequency, and how they'll start it. Star-delta and soft starters cut the starting torque, which matters on a loaded belt, while a drive can give good torque from low speed and vary the speed too. Then the site: ambient temperature and altitude can mean derating, dust or wash-down decides the protection level, and a hazardous area needs a certified motor. Finally mounting and frame size to match what's there, and the efficiency class local rules require."

"IP stands for ingress protection. It's a two-digit code. The first digit is about solids, so how well it keeps out fingers, tools and dust, and a 6 means it's dust-tight. The second digit is about water, and a 5 means it's protected against water jets from a nozzle, like a hose-down. So IP65 is dust-tight and fine with jets of water, but it isn't rated to be dunked. That's a 7, and a 7 on its own doesn't promise jet protection, which is why some products carry both codes. To pick one, I ask where it'll sit: a clean control room needs far less than a dusty crusher area or a food plant that's washed down every shift. Going higher than needed usually costs more, so I match it to the real site."

"With a damper, the motor always runs at full speed and the damper just adds resistance, so they pay for air they then choke off. A drive slows the fan instead. On fans and centrifugal pumps, flow follows speed, pressure follows speed squared and power roughly follows speed cubed, so in theory running at four-fifths speed needs only about half the power. Real savings are smaller than the theory, and they depend on how many hours it runs below full flow. If the fan runs flat out all day, a drive saves very little and adds its own small losses. So I'd ask for their flow pattern and running hours, measure the present power draw, and show the payback from their numbers. I'd also check the existing motor is fit for drive use and flag the harmonics a drive puts on their supply."

"If someone could be hurt right then, I'd warn them straight away and not touch anything myself, because it's not my equipment and I don't know its state. Otherwise, I'd mention it to my host once we were away from the shop floor, plainly and without judgement, something like, I noticed the cover's off that panel near the press, I thought you'd want to know. If they have a safety officer, I'd suggest they tell them. I'd make a note in my visit report too. What I wouldn't do is ignore it to avoid spoiling the meeting, or use it to sell something. Customers usually respect a supplier who notices and speaks up, and if something happened later I couldn't live with having stayed quiet."

"Before I go, I read what I can about the plant, what they make and roughly what equipment they'd use, check our records for any past enquiries, and confirm who I'm meeting and what they want to discuss. I carry my own safety shoes and whatever the site needs, and I expect a safety briefing at the gate. On site, I ask to see the process where our product would sit, because I learn more in ten minutes on the shop floor than an hour in a meeting room. I try to meet both the maintenance or project engineer and someone from purchase. Afterwards I write a short visit report the same day and send the customer whatever I promised within a day or two."

"I'd welcome the order but not ignore the overdue. First I'd check with accounts exactly what's outstanding and whether there's a dispute behind it, like a missing document or a short delivery, because that's often why a payment is stuck and I can fix it. Then I'd talk to the customer's accounts or purchase head honestly: I want to process your new order, and to do that I need the old invoices cleared or a clear plan with dates. Depending on company rules, that might mean part payment now, an advance on the new order, or a credit approval from my manager. An order that never gets paid isn't a sale, so I treat collections as part of my target."

"My stages are enquiry, qualified, offer submitted, negotiation, order, then invoicing and collection, because an order isn't done until it's paid. Each week I track new enquiries, offers sent, orders booked against target, the value of offers still open and how old they are, and overdue payments. The number that tells me most is the hit rate, how many offers turn into orders. If I win one in four and my target needs a certain value of orders, I know roughly how much I need to be quoting. If the hit rate drops, either I'm quoting jobs I can't win or something's wrong with price or product fit, and I look into it before the month is gone."

"In the first month I'd learn the product properly, spend time with the service and application team, and go through any old enquiries, lost offers and past customers in our records, because they already know our name. I'd meet both dealers early to understand who they sell to and where they're weak. In the second month I'd map the territory: industrial areas, the bigger plants, trade association lists, and rank them by how likely they are to use our products. I'd plan visits by cluster so I'm not criss-crossing the district. By the third month I'd want a steady weekly visit routine, a few offers out and ideally some small first orders, and I'd review with my manager what's working before the next quarter."