Procurement Interview Questions

"I started in a finance support role processing supplier invoices, so I saw the end of the process first. I kept noticing the same problems: prices that didn't match the order, suppliers nobody had compared, contracts that renewed on their own. I asked to move into the buying team, and my first real project was re-tendering office facilities services. We tightened the scope, brought in two new bidders and ended up with better service levels at a lower cost. That was the moment I got hooked, because I could see a direct line from my work to the budget and to how well people could do their jobs. What keeps me here is that mix of numbers, negotiation and people. I'd like my next role to give me ownership of a full category, from strategy to supplier reviews."

"From what I can see you run a fleet of delivery vehicles and several warehouses, so I'd expect fuel, vehicle leasing and maintenance, packaging, and temporary labour to be the big lines, with IT and facilities behind them. What would worry me first is fuel and packaging, because both follow commodity prices you can't control, so the question is how much of that is covered by index clauses or hedged in some way. Temporary labour worries me for a different reason: it's often bought locally by site managers, so it can turn into scattered spend with inconsistent rates and compliance checks. I'd be curious how close that is to your real picture, and which category the team thinks has the most room to improve."

"Most of my experience is in indirect spend. I've handled IT hardware, office supplies and marketing print, and I supported a senior buyer on a facilities management tender. For IT hardware and office supplies, I owned the day-to-day: raising purchase orders against our framework agreements, chasing deliveries and dealing with invoice queries. For marketing print I ran the quotes myself, usually three suppliers per job, and I built a simple rate card so the team stopped asking for fresh quotes on every small job. On the facilities tender I wrote parts of the RFP, scored the responses with the panel and helped prepare the negotiation pack. I haven't owned direct materials yet, and that's one of the reasons this role interests me."

"It starts with a need. Someone raises a purchase requisition saying what they want, how many and which cost centre pays. That goes through approval, usually based on value and budget. Then procurement either uses an existing contract or catalogue, or sources a supplier if there isn't one. Once the supplier is chosen, we issue a purchase order, which is the formal commitment with price, quantity, delivery date and terms. When the goods or service arrive, someone records a goods receipt. The supplier sends an invoice, and accounts payable matches it to the order and the receipt. If they agree within tolerance, the invoice is approved and paid on the agreed terms. Each step is there for a reason: approval controls spend, the order fixes the price, and the match stops us paying for things we never got."

"A three-way match compares three documents: the purchase order, the goods receipt and the supplier's invoice. If the quantities and prices agree within the tolerance we've set, the invoice can be paid. When it fails, I first work out which document is wrong. If the invoice shows a higher price than the order, I check whether the price really changed and was agreed. If it wasn't, the supplier issues a credit note or a corrected invoice. If the quantity is off, maybe only part of the delivery was received, so we pay for what arrived. Sometimes the receipt was simply never entered, which is an internal fix. What I avoid is just raising the order value to make the numbers match, because that hides the problem and defeats the control."

"Maverick spend is buying that goes around the agreed route: using a supplier we have no contract with, ignoring the preferred supplier, or ordering first and raising the purchase order afterwards. It matters because we lose the negotiated prices, the contract protection and visibility of what we spend. It usually happens for understandable reasons. The process is slow, people don't know a contract exists, or there's no contract for what they need. So I start with the data to find the worst areas, then fix the cause. That might be a catalogue for common items, a faster approval path for low-value buys, or a new agreement where people keep going off-contract. Once the easy route exists, I tighten the rules, like a no purchase order, no pay policy, and report compliance by department."

"A standard purchase order is for a one-off purchase where I know the item, quantity, price and delivery date, like buying ten office chairs. A blanket order suits repeated small purchases from one supplier over a period, like maintenance consumables. I set a value limit and a validity period, and invoices are booked against it without a new order each time, which saves a lot of admin. A contract or agreement with releases is for when we've negotiated prices and terms for a period, maybe with a target quantity or value, and then raise release orders against it as we need stock. That keeps every order at the agreed price and lets us track consumption against the commitment. The names really do change between systems. In some, a blanket agreement is exactly that priced contract, and the releases are the orders. So on day one I'd check how they're set up here."

"First I'd confirm the exact part, the quantity and when it has to be on site, and whether there's any alternative part or a spare elsewhere in the business. Then I'd get quick quotes, even by phone, from two or three suppliers who can deliver in time, and do basic checks, like whether they're a registered company and can invoice us properly. Most companies have an emergency purchase procedure, so I'd use it: get the right approver on the phone, raise the order the same day, and document why normal sourcing was skipped. Keeping the line running comes first, but not by paying on a personal card with no record. The day after, I'd look at why we had no supplier for a critical part, and either set up an agreement or ask planning to hold a spare."

"I choose based on how well we understand the need. An RFI, a request for information, is for learning. Say we want to automate invoice processing and don't know what's out there. The RFI asks suppliers about their capabilities and experience, and helps us build a shortlist and a sensible spec. An RFQ, a request for quotation, is for when the spec is fixed and the main question is price and delivery. Buying five hundred units of a standard laptop model is a good example. An RFP, a request for proposal, is for when we're asking suppliers to propose how they'd solve a problem, like outsourcing our cleaning across several sites. There, we score their approach, service levels, experience and price together. Often they run in sequence: RFI to shortlist, then RFP or RFQ to the shortlist."

"The tool I use most is the Kraljic matrix. You plot each category on two axes: how much it affects cost or profit, and how risky or hard the supply is. Low impact and low risk are routine items like stationery, so I simplify: catalogues, purchasing cards, less of my time. High impact but low risk is leverage spend, like standard packaging with many suppliers, where I use competition and tenders to push price. Low impact but high risk is a bottleneck, maybe a special part only one firm makes, so I focus on securing supply with stock or longer agreements, and look for alternatives. High impact and high risk is strategic, like a key raw material, and there I build a close long-term partnership. It stops me wasting effort tendering stationery while a bottleneck part goes unmanaged."

"First I separate single from sole sourcing. Sole means only one supplier can make it. Single means others exist but we chose one. Single sourcing makes sense when concentrating volume gets us real leverage, when switching costs are high because of tooling or product approvals, or when we need a deep partnership, like co-developing a part. The trade-off is risk: if they have a fire, a strike or a cash problem, we have no fallback. So I manage it actively. I watch their financial health and delivery trends, agree a buffer stock, ask to see their own sub-supplier risks, and make sure the contract covers continuity plans. Where I can, I keep a second supplier qualified, even with a small share of volume, so switching is weeks not months. Multiple sourcing costs leverage and effort, so I don't default to it either."

"The one I know best was a cleaning services tender for three office sites. I started with the facilities manager to agree the scope: frequencies, areas, and the service levels that really mattered to staff. We agreed scoring criteria and weights before going out. I searched the market, sent a short pre-qualification to check insurance and safety records, and invited five suppliers to an RFP. I ran a site visit so everyone got the same information, and answered questions in one shared log. The panel scored independently, then we met to agree scores. I negotiated with the top two on price and mobilisation, wrote the award recommendation, got approval and signed the contract. I also gave each unsuccessful bidder short feedback, which several of them appreciated."

"Total cost of ownership is everything the purchase costs us over its whole life, not just the price on the quote. That includes delivery and installation, training, running costs like energy and consumables, maintenance and spare parts, downtime when it fails, and what happens at the end, whether that's disposal cost or resale value. A good example is printers. One supplier offered machines noticeably cheaper up front, but their toner cost per page was much higher and the service contract only covered parts, not labour. Once I modelled five years of our actual print volume, the more expensive machine came out clearly cheaper overall. Presenting it that way also made the decision easy for finance, because they could see the comparison year by year instead of just the purchase price."

"I'd start by agreeing that finance is partly right. Cost reduction is when we pay less than last year for the same thing, so the budget line actually goes down. Cost avoidance is when we stop a cost that would otherwise have happened, like a supplier asking for a big increase and us holding them to a much smaller one. That's real value, but the budget doesn't fall, it just doesn't rise as much. The fix is to agree the baseline and the rules with finance before each project, not after. Then I report the two separately, and I track reductions against actual volumes bought, not the volumes we forecast. I'd also invite finance to sign off the big ones. Once they helped set the method, the argument goes away and procurement's numbers get trusted."

"In my last role, we were spending heavily on courier services, and every department booked its own. Before touching price, I sat with the heaviest users and pulled three months of shipment data. Most parcels went same-day premium, but when I asked, only a small share truly needed it; people chose it because it was the default. So I made standard next-day the default, kept same-day available with a short reason, and moved everyone onto one consolidated contract. That volume let us negotiate better rates too. To check quality, I tracked on-time delivery and complaints for two months after the switch. Delivery performance stayed the same and nobody raised a complaint, and the spend dropped clearly. What made it work was changing the spec people didn't need rather than cutting the service they did."

"I'd start by showing my leadership the market data early, not at year end, so there are no surprises. Then I'd look beyond unit price, because price is only one lever. Can we reduce demand, for example cutting waste or overuse? Can we change the specification to something just as good but cheaper? Can we consolidate volume across sites for better terms, or lock prices for longer before they rise further? There's also process cost and payment terms. At the same time, I'd agree with finance how to count holding prices below the market trend, which is cost avoidance, and report it separately from true reductions. If the target still isn't realistic, I'd say so with the evidence and propose a revised one, rather than dressing up numbers that won't show in the budget."

"For a critical component, I'd look at quality first: their certifications, defect history, and ideally a site audit and trial samples. Then delivery and capacity, meaning lead times, how much spare capacity they have and where they source from. Cost comes in as total cost, not just unit price. I'd also check financial stability, because a cheap supplier that goes under mid-contract is expensive, plus compliance areas like safety, data and labour standards. For weighting, I agree it with engineering and quality before any bids come in, so nobody can tilt the scores afterwards. For something critical, I'd typically weight quality and supply reliability well above price. For a routine item, price would carry much more weight. The key is that the weights reflect what it would cost us if this supplier failed."

"A packaging supplier missed two deliveries in a row, and one of our lines was about to stop. First I contained it: I called our secondary supplier, who could cover part of the volume at short notice, and worked with planning to re-sequence production. Then I met the supplier's account and operations managers. It turned out they'd lost a machine and hadn't told us, hoping to catch up. I asked for a written recovery plan with dates and daily updates until they were back on track, which they delivered. Afterwards I changed two things. I added an early-warning clause, so they must tell us within a set time if they can't meet an order, and I kept the backup supplier on a small regular share so they'd stay ready. The silence hurt more than the breakdown."

"I'd start with the data, so I'm sure of the trend: which orders were late, by how much, and what it cost us in expedites or lost production. I'd also check we're not part of the cause, like changing orders at short notice. Then I'd set up a review with the supplier, share the numbers, and ask them to explain the root cause. It could be capacity, a sub-supplier problem, or staff turnover. I'd ask for a written corrective action plan with dates, and agree weekly check-ins until the numbers recover. If it keeps slipping, I escalate: senior meetings on both sides, applying any service credits in the contract, and quietly qualifying an alternative. I wouldn't jump straight to switching, because changing a key supplier has its own risk, but I'd make sure we could if we had to."

"For me it comes down to being hard on the issue and fair to the people. I make expectations clear from the start, and I keep my side of the deal: paying on time, sharing forecasts, and warning them early if our plans change. That earns me the right to be firm when they miss something, and I always use data rather than emotion when I do. In negotiations I'm direct about what I need, but I don't play games like inventing fake competing bids, because suppliers talk and trust is hard to rebuild. I also ask them for ideas, since they often know how to take cost out of their own process if we change a spec or order pattern. The suppliers who see us as a good customer are the ones who help us first when things get tight."

"After price, the first thing I check is how price can change: is there an index clause, how often, and with what notice. Then payment terms and any minimum volume commitments, because those can quietly lock us in. For performance, I want clear service levels with a real remedy, like service credits or the right to exit if they keep missing. On risk, I look at the liability cap and indemnities with legal, plus insurance and, where relevant, data protection. Finally the exit: how long the term is, whether it renews automatically and how much notice we need to give, whether we can terminate for convenience, and what help we get to move to another supplier. Auto-renewal with a short notice window is one I always diary, because it's easy to miss."

"Early in my career I renewed a software subscription and didn't read the renewal clause closely. It rolled over automatically for another full year unless we gave ninety days' notice. By the time the business told me they wanted to switch, we were inside that window, so we paid for a year of a tool we barely used. I went back to the vendor and negotiated some of the value into training and a smaller licence count, which helped, but it was still a real loss. Since then I keep a contract register with every notice date, and I set reminders well before each one. I also push back on auto-renewal where I can, or ask for a shorter notice period. It was a small clause with a big cost, and I've never missed one since."

"BATNA stands for best alternative to a negotiated agreement. It's simply what I'll do if this negotiation fails. It matters because it sets my walk-away point: I shouldn't accept a deal worse than my best alternative. Before a negotiation I build it on purpose. I'll get quotes from at least one other qualified supplier, check if a different spec or material would work, see whether we could do part of it in-house, or whether we can wait. I also try to guess the supplier's BATNA: how badly do they need our volume, do they have spare capacity, are we a reference customer for them. The stronger my alternative and the weaker theirs, the firmer I can be. Without that prep, I'm negotiating on hope."

"At my last company we bought specialised lab software from the only vendor that integrated with our instruments, and our spend was tiny for them. At renewal they proposed a sharp price rise and a three-year lock-in. Pushing on price alone wasn't going to work, so I asked what they cared about. It turned out they wanted reference customers in our sector and predictable renewals. I offered a case study, a joint webinar and a two-year term, which gave them what they valued. In return we held the price flat for the first year with a capped increase in the second, and added a service level on support response, which had been our real pain. It taught me that when you can't compete on volume, you find out what the other side needs and trade for it."

"First I'd check the contract. If prices are fixed for the term, or need longer notice than a month, that's my starting point. Then I'd test the claim. I'd ask them to show the cost breakdown: how much of their price is that raw material, and how much it has actually moved. I'd compare that with a published price index for the material. If the material is a third of their cost and it went up by a quarter, their total cost only rose by about a twelfth, so that's the most I could justify, not a quarter. Then I'd respond with the number I can justify, and look for trades, like phasing it in, locking the price for longer, or exchanging it for better payment terms. Going forward, I'd agree an index-linked clause so the price can go down as well as up, and nobody has to argue from scratch."

"Our head of marketing wanted to award a large events contract to an agency she'd used at her previous company, without going to market. My worry was price and the fact that nobody had compared alternatives. Instead of saying no, I asked what she valued about them, and it was speed and creative quality. So I proposed a quick competitive process built around exactly those criteria, with her on the scoring panel. Her preferred agency took part alongside two others. In the end they scored well on creativity but another agency matched them and was clearly better on cost and contract terms. Because she'd set the criteria herself, she agreed with the result. We still use her agency for smaller creative work, and she now comes to procurement early rather than at the end."

"I'd first ask what's driving it, because there's usually a real budget pressure behind it. Then I'd show the decision in their language. I'd turn the quality gap into cost: likely defects, rework, failed deliveries, extra management time, and what happens if they fail mid-contract. Often the cheapest bid isn't the cheapest outcome. I'd also point out that we agreed the criteria and weights before bidding, and in a formal tender, awarding against our own published scoring can be challenged by the other bidders. That said, I'd offer options. We can negotiate harder with the best-value bidder to close part of the price gap, or look at scope we can trim. If leadership still chooses the low bid, I'd document the decision and the risks, and build strong service levels and exit rights into the contract."

"I'd start by listening. I'd ask a few of the teams who complain most to walk me through a recent purchase, and look at the cycle time data, so I know where the real delays are rather than guessing. Usually it's low-value buying that's over-controlled: the same approvals for a small order as for a big contract. So I'd make the routine stuff fast with catalogues, pre-approved suppliers or purchasing cards, and save the full process for the spend that carries real risk. Then I'd try to get involved earlier, at the planning stage, so procurement helps shape the need instead of arriving at the end with objections. And I'd share results in their language: faster delivery, better service, budget freed up for their projects. People stop seeing you as a blocker when you visibly help them get what they need."

"I'd decline, politely and in writing. While a tender is open, accepting hospitality from a bidder looks like influence even if it isn't, and it could make the whole award open to challenge. I'd thank them, say that our policy doesn't allow it during a live process, and keep it friendly, because they may well be a good supplier. Then I'd record the offer in the gifts and hospitality register and mention it to my manager, so there's a clear record that it was offered and refused. I wouldn't treat the supplier any differently in the scoring because of it. Outside of a tender, small hospitality can sometimes be fine within policy and declared, but a major event during an evaluation is exactly the case the policy is written for."

"First I'd make sure the information is accurate, for example by checking the company registration details, because it's a serious thing to raise. If it's true, the conflict isn't wrong in itself; what matters is that it's declared and managed. I'd ideally start by speaking to my manager directly and privately, since they may already have declared it. If they haven't, or I'm not comfortable raising it with them, I'd go to the next level or to compliance, which most policies allow for exactly this reason. The outcome should be that my manager steps away from any scoring or approval on this tender, and that it's all documented. The bidder stays in the process and is judged purely on merit. Keeping quiet isn't an option, because if it came out later, the award could be overturned."