Supply Chain Questions to Ask an Interviewer
Supply chain questions to ask an interviewer when the role is in planning, procurement or logistics, chosen to show how the operation really runs and the parts of the job nobody put in the posting. They are grouped by the role itself, planning, buying and logistics, systems and data, what it is like to work there, and the close. Anyone picking questions to ask in a logistics interview, or going into a buying interview for a purchasing or sourcing job, will find most of theirs in the third group.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The role
What does this role own end to end, and where does it hand off?
Why ask it
A supply chain title can mean planning, buying, logistics or some mix of the three, and the mix differs from one company to the next. The handoffs are where the weekly arguments happen, so ask about them by name: who releases the order, who books the freight, who answers the customer.
What is the hardest problem the supply chain team is dealing with right now?
Why ask it
Ask this early, because the answer is often the reason the job exists. A named problem, such as late inbound from one region or stock sitting in the wrong warehouses, gives you something to speak to for the rest of the interview. If you are told nothing much is wrong, ask what took up most of last month.
Which KPIs would I be judged on in this role, and how often are they reviewed?
Why ask it
A planner held to forecast accuracy, a buyer held to savings and a logistics lead held to cost per shipment are doing three different jobs. Check that the number is one the role can move. Being scored on on-time delivery with no say over carriers or production is a hard place to sit.
What does an ordinary week look like in this job, and what does a bad one look like?
Why ask it
The ordinary week gives you the rhythm: the planning cycle, the supplier calls, the month-end close. The bad week shows how often the day is taken over by a late truck or a line about to stop, and whether that is rare or every Tuesday.
Why is this role open, and what did the last person find hardest?
Why ask it
A new role and a replacement are different jobs: one has no baseline to be measured against, and the other comes with a predecessor's backlog and habits. If someone left, ask what has changed about the workload or the tools since. 'Nothing' is an answer too.
Where does supply chain report: into operations, into finance, or to its own head on the leadership team?
Why ask it
The reporting line predicts the priorities. Under finance the pressure tends to fall on inventory and cost, under operations on keeping the lines running, and under a commercial lead on availability. None is wrong, but each makes for a different job.
How many SKUs, suppliers or sites would I be looking after?
Why ask it
The number sets the kind of work. A few hundred items can be known one by one, while tens of thousands have to be run by rules and exception reports. Ask how the portfolio is split across the team, and whether your share is the steady part or the difficult part.
Who decides to expedite a late shipment, and how fast can that happen?
Why ask it
Expedite authority is a good proxy for the autonomy in the role. If every air freight decision needs a director's approval, the job is probably more administrative than the posting suggests.
Who sets the trade-off between cost, service, and inventory?
Why ask it
All three cannot be optimized at once, so someone decides. Finding out whether that is finance, sales, or supply chain tells you whose priorities you would spend your time executing.
Is there budget and time for improvement projects this year, or is the job to keep things steady?
Why ask it
Both are honest answers, and they suit different people. If you are being hired to fix things, ask what has already been approved. A mandate to improve with no money and no project time is a mandate to work evenings.
Where is the company headed over the next few years, and what would that change for this role?
Why ask it
A new plant, a second warehouse, another country or a push into online sales each lands on supply chain before most other teams. If the interviewer can connect the plan to this job, the role has been thought through. If growth is the plan and nobody has asked how it will be supplied, that work is probably coming your way.
Planning
What's your service level target, and where are you against it?
Why ask it
An interviewer close to the operation can usually quote fill rate or on-time-in-full without looking it up. A gap between target and actual is normal, so ask what is driving it and whether closing it is part of this job.
How much of the demand plan is system generated, and how much gets overridden by hand?
Why ask it
The override rate is the honest measure of whether anyone trusts the forecast. A high rate usually means a spreadsheet somewhere is the real planning system, and maintaining it would become your job.
When the forecast turns out wrong, who hears about it first, and what happens next?
Why ask it
Every forecast misses, so the interesting part is the response. A team that reviews the error and adjusts is in a different place from one where sales blames planning and planning blames sales. If you would own the forecast, ask how the last big miss was discussed.
Is inventory higher or lower than a year ago, and what moved it?
Why ask it
Stock that has climbed usually comes with pressure to bring it down, and that pressure lands on planners and buyers. A specific cause, such as longer lead times or a launch build, shows someone has looked into it. 'The market' as the whole explanation suggests nobody has yet.
How much slow or obsolete stock are you carrying, and whose job is it to clear it?
Why ask it
Dead stock is the bill for old decisions, and it often has no owner. Where the write-off conversation keeps getting postponed, the newest person on the team tends to be handed the list.
How are product launches and phase-outs planned?
Why ask it
New items have no history to forecast from and old ones leave stock behind, so both ends are where plans go wrong. A good answer describes the point at which supply chain is brought into a launch. Finding out at the same time as the customers is the bad one.
How do your sales and operations planning meetings run, and who attends?
Why ask it
Look at who attends. With sales and finance leaders in the room, the S&OP meeting decides things. Without them it tends to be a reporting session, and the plan gets changed somewhere else afterwards. A small company may have no formal meeting at all, so ask where sales and supply agree on the numbers.
How are safety stock and reorder settings decided, and when were they last reviewed?
Why ask it
For a candidate the point is ownership. If those settings have sat in the system untouched since it went live, tuning them is probably the first useful thing you would do. Ask whether a planner can change them directly or has to raise a request.
How far ahead does the plan look, and how often does it change inside supplier lead time?
Why ask it
A plan that is torn up every week inside the lead time means constant rescheduling and irritated suppliers. Ask whether there is a frozen period and who is allowed to break it. That tells you how much of your week would be replanning.
Buying and logistics
Which suppliers keep you up at night?
Why ask it
Listen for how specific the answer is. One part, one region or one sole source, named without hesitation, means the risk is known and watched. A shrug can mean a comfortable supply base or one nobody has mapped, and in a buying role you would be the person who finds out which.
How are your key suppliers managed: scorecards and regular reviews, or a call when something is late?
Why ask it
Scheduled reviews with shared numbers mean problems surface early and the relationship survives them. Contact only in a crisis means you would inherit suppliers who hear from the company mostly when it is annoyed.
How long does it take to onboard a new supplier?
Why ask it
Mostly one for sourcing and buying roles. If approving a new supplier takes many months of audits and paperwork, which can be right for a regulated product, then a second source is not a quick answer to a shortage. Ask who owns that process and how much of it you would run yourself.
How far past your direct suppliers can you see?
Why ask it
Plenty of shortages start two or three tiers back, at a supplier's supplier nobody had mapped. Many companies cannot see that far, so an honest 'tier one only' is a fine answer. What matters is whether anyone is working on it, and whether that work would be yours.
Is there a savings target attached to this role, and how is a saving counted?
Why ask it
Mainly one for buying and sourcing roles. A saving measured against last year's price is not the same as one measured against a budget or a first quote, and the definition decides whether the target is reachable. Ask who signs off that a saving is real.
Which categories would I be buying, and roughly how much spend sits in each?
Why ask it
A buyer of packaging and a buyer of electronic components need different knowledge, and a desk spread thinly over dozens of small categories is mostly order processing. Ask how the spend is divided across the team, and whether yours is a category where the company is a big enough customer to be listened to.
Who picks the supplier in practice: purchasing, or the engineers and departments who use the item?
Why ask it
In some companies the buyer runs the selection. In others the choice is made before purchasing hears of it, and the buyer is left to negotiate with a supplier who knows it has already won. Ask at what point this team is brought in on a new requirement.
How much of the buying is under contract, and how much is placed order by order?
Why ask it
Contracted spend makes the work negotiation, renewals and supplier performance. Order-by-order purchasing makes it quotes, chasing and price surprises. The share of each shows whether the job is sourcing or purchase order processing, whatever the title says.
When a supplier asks for a price increase, who decides what happens?
Why ask it
A price increase letter is the moment the rest of the business notices the buying desk. Find out who chooses between accepting, pushing back and looking for another source, and what evidence the buyer is expected to bring, such as material cost indexes or competing quotes.
What payment terms do suppliers get, and are their invoices paid on time?
Why ask it
A buyer's standing with suppliers rests on something the buyer rarely controls. Where accounts payable stretches payments, you would be asking for a rush order from someone still waiting on last quarter's invoice. It is fair to ask how often a supplier has held deliveries over an unpaid bill.
What happens when a batch or a shipment fails a quality check?
Why ask it
Ask for the most recent case. An answer that says who put the stock on hold, who called the supplier and how the gap was covered describes a real process. It also shows whether chasing the replacement and the credit would fall to you.
What was your last significant disruption, and what changed afterwards?
Why ask it
The incident itself tells you little, since most operations have had one. Listen for what is different now: a second source approved, more stock held on a critical part, a clearer route for raising the alarm. If nothing changed, you may be there for the repeat.
How exposed are you to tariffs, customs delays, and border checks?
Why ask it
Any operation moving goods across borders has a view on this, so skip it for a purely domestic one. A vague answer can mean a customs broker holds the knowledge and nobody inside the company can challenge what the broker says.
How much of your warehousing and transport is run in house, and how much by third parties?
Why ask it
Managing a logistics provider is a contract and relationship job, while running your own warehouse is a people and process job. The split tells you which one you are applying for, and how much control you would have when service slips.
How do you choose carriers, and how often do rates and lanes go out to bid?
Why ask it
Worth asking for any logistics role. A regular bid cycle means a busy season of analysis and negotiation every time it comes round. Long-standing handshake arrangements mean nobody has tested the rates in a while. Either way you learn how much of the freight spend you could influence.
How are delivery dates promised to customers, and does logistics get a say before sales commits?
Why ask it
A logistics team is often measured against dates it never agreed to. If sales can promise next-day delivery without checking capacity or the dispatch cut-off, the gap is closed with overtime and premium freight. Ask how the last promise the network could not meet was handled.
How are damage, loss and shortage claims handled, and who chases them?
Why ask it
Claims work is slow and heavy on paperwork, and it tends to land on the newest person in the transport office. Ask how many are open at the moment and whether the carrier contracts say who pays. A drawer of old unresolved claims means the process has no owner yet.
What happens to returned goods, and does this role own any of that flow?
Why ask it
Returns run the network backwards, and many operations treat them as an afterthought. Ask where a returned item goes, how long it takes to be back in saleable stock, and who decides what gets scrapped. If a site tour skips the returns area, notice that.
Which safety and transport compliance duties come with this role?
Why ask it
Logistics jobs can carry responsibility for things like driver hours, dangerous goods paperwork, load security or forklift licences, and the rules differ by country and by what is being moved. Ask which of them sit with this role, what training the company pays for, and who holds that responsibility today.
Has a sustainability commitment changed a sourcing or transport decision yet?
Why ask it
This separates reporting from operations. If no commitment has yet moved a supplier or a shipping mode, it is a disclosure exercise for now. If one has, ask what it cost and who agreed to pay, because that is the argument you would be joining.
Systems and data
Which ERP and planning systems do you run, and which of them talk to each other?
Why ask it
Ask about the joins between the ERP, the warehouse system and any planning tool. Where two systems do not connect, somebody exports from one and re-keys or reconciles in the other. In an analyst or planner role that somebody is likely to be you.
Are loads and routes planned in a transport management system, or by hand?
Why ask it
A spreadsheet and a whiteboard can run a small fleet, but they leave the knowledge with one or two experienced planners. Ask how a load gets built and tracked today, and who can see where a shipment is without phoning the carrier. That shows how much of a logistics role is planning and how much is finding things out.
How accurate are the stock records, and how is stock counted?
Why ask it
Every plan and every promise to a customer starts from what the system says is on the shelf. Regular cycle counts with a tracked accuracy figure are a good sign. A once-a-year full count that throws up large corrections means planners are working from numbers they cannot trust, and it may mean a weekend in the warehouse for you.
How reliable is the master data, things like lead times, pack sizes and minimum order quantities, and who maintains it?
Why ask it
A planning system can only be as good as the lead times and order quantities loaded into it. If nobody owns that data, expect it to be wrong in ways people have learned to work around, and expect to become the owner.
What's the biggest process here that still runs on spreadsheets?
Why ask it
Most operations have one, often a file that one person built and only that person fully understands. Ask who maintains it and what happens when they are away. Replacing it can make a good first project, if that is the kind of work you want.
What has the team automated recently, and what did that change day to day?
Why ask it
Automation tends to move work as well as remove it: orders now release by themselves, and someone checks the ones the system rejects. An interviewer who can name that new manual step is being straight with you. Ask whether it sits with this role.
Is a system change planned, such as an ERP migration or a new planning tool, and where would this role sit in it?
Why ask it
A migration can swallow a team for a long stretch, and it turns the job from running the operation into testing and data cleansing. Some people want that on their record and some do not, so find out before you accept.
Where is the team using analytics or AI today, and where did it not work out?
Why ask it
Nearly every company says it is investing here, so ask for one example in daily use. A forecast model the planners trust counts. A pilot that produced a slide deck does not, and an honest account of the failed attempt is a good sign.
Which reports would I produce, and who reads them?
Why ask it
Reporting can quietly take over an analyst or planner role. If a weekly pack takes a day to build and nobody can say which decision it feeds, that is either a day you could ask to win back or a hint about how the role is valued.
Working here
How big is the team, and who would I work with most closely?
Why ask it
A team of three covers everything between them, while a team of thirty will have specialists. Ask for names and roles, and whether you could meet one of them before an offer. A peer is the best source on what the work is really like.
How do you prefer to work with the people who report to you?
Why ask it
Only for the hiring manager. Listen for concrete habits: a weekly one-on-one, how they want bad news delivered, how closely they check in during a crisis. In a job full of exceptions, a manager who wants to hear about every one will wear you down.
Where does this team most often disagree with sales, finance or production, and how does it get settled?
Why ask it
Supply chain sits between those functions, so some tension is built in. An interviewer who can describe the usual argument calmly, and say who makes the final call, is describing a workable place. Contempt for another department is the thing to notice.
Do other departments share any of supply chain's targets, or does this team carry them alone?
Why ask it
Shared targets change behavior. A sales team that is also scored on forecast accuracy thinks twice before promising a rush order. Where supply chain alone answers for stock and service, the team tends to absorb the results of decisions made elsewhere.
What does training look like in the first few weeks?
Why ask it
Good onboarding in this field includes walking the warehouse or the plant, meeting the main suppliers and having system access from day one. Being handed a login and the open order book is common and survivable, but better known in advance.
Does the company support professional certifications or courses?
Why ask it
Planning, procurement and logistics all have professional qualifications, and they are costly to fund yourself. Ask what has been paid for in the past year and whether study time is given. Policies differ by employer, and some ask for fees back if you leave soon after.
Where have people who held this role gone next?
Why ask it
Supply chain careers often move sideways, from planning into procurement or logistics, before they move up. Real examples of people who made those moves show the route is open. No examples may mean people leave the company to get their next job.
Is this role on site every day, or is some remote work possible?
Why ask it
A job tied to a warehouse or a plant has less room for remote days than a planning desk does, and policies differ a lot between employers. Ask what the team actually does from week to week, and whether the pattern changes at month-end or in peak season.
How much time would I spend on the floor, at warehouses, or at supplier sites?
Why ask it
Some supply chain jobs are spent entirely in a planning system, and others expect you at the dock door or on a plane to a supplier every month. Ask for a rough share of the week and how much notice travel usually comes with.
When is your busiest season, and what does it do to this team's hours?
Why ask it
Peak is predictable in most businesses, so the plan for it should be too. Listen for specifics like limits on time off, weekend cover or extra temporary staff. 'We all pull together' with no detail usually means long days that nobody has counted.
What happens after hours when a shipment goes wrong: is there an on-call rotation?
Why ask it
Trucks and vessels do not keep office hours, and somebody's phone rings when one is stuck. Find out whether that is shared on a rotation, paid or given back as time off, or simply falls to whoever picks up. It varies a great deal by employer, so ask instead of assuming.
Closing
If I started next month, what would you want fixed first?
Why ask it
One clear answer, such as getting a warehouse's stock records straight or sorting out one late supplier, means a plan is waiting for you. A long list of everything that is wrong means you would set the priorities yourself. Some people want exactly that, so know which you are.
What would make you say, six months in, that this hire worked out?
Why ask it
This asks how you will be judged, which is not always the same as what needs doing. A measurable answer, such as a service level recovered or a backlog cleared, gives you a target to agree on before you start. A vague one means the bar gets set later, by mood.
What do the people who do well on this team have in common?
Why ask it
Calm under pressure, comfort with numbers and the nerve to push back on sales are all common replies, and each hints at what the job asks of you daily. Compare the answer honestly with how you like to work.
Is there anything in my background that makes you hesitate about me for this role?
Why ask it
It takes some nerve, but it lets you answer the doubt while you are still in the room. If the worry is that you have planning experience and no procurement, or know one industry and not theirs, you can speak to it now. Skip it if the interview has plainly gone badly.
What has kept you here?
Why ask it
A good one for a peer, or for a manager with a few years in the company. People who like their job answer quickly and in detail, about the team, the product or the problems. A long pause followed by 'the people' is worth weighing.
What are the next steps, and when should I expect to hear?
Why ask it
Ask it last, every time. Knowing whether a case study, a site visit or a panel is still to come lets you prepare, and a stated date gives you a polite reason to follow up once it has passed.
How to use these questions
Practical guidance for the conversation itself
Before the interview
Work out what they actually move
Perishable food, spare parts, and consumer electronics create completely different problems. Knowing whether the constraint is shelf life, service level, or launch timing lets you ask about their operation rather than supply chain in general.
Check the public record for disruption
Annual reports, trade press and recall notices sometimes mention shortages, port delays or supplier failures. Bringing up a specific one usually gets a fuller answer than asking about disruption in the abstract.
Know which numbers you would ask for on day one
Decide in advance whether you would want forecast error, inventory turns or on-time delivery first. Asking for that number by name shows you have done the work before, in a way that calling yourself experienced does not.
Choose five or six, by role
The list is a menu, not a script. A planner should draw mostly from the planning and systems groups. For a buying interview, start with the supplier questions at the top of the buying and logistics group, and for a logistics interview with the carrier, claims and returns questions lower down. Everyone should take one or two from the role and closing groups. Five or six that you care about are enough for one interview.
What the answers tend to tell you
- A service level or forecast error figure quoted from memory suggests the interviewer works close to the operation.
- Heavy manual override of the plan usually points to a shadow spreadsheet, and looking after it may come with the role.
- If expediting needs senior sign-off, ask what else does. It often goes with narrow decision rights across the whole job.
- An interviewer who names the new manual work a recent automation project created is describing an honest, self-aware team.
- When several answers point to the same broken join between two systems, that is likely the real first-year project.
- A reporting line into finance, operations or sales tells you which of cost, output and availability wins when they collide.
Common pitfalls
Asking only about technology
Systems questions are easy to prepare and easy to answer. The harder information sits in who decides trade-offs and how quickly exceptions can be handled.
Treating the interviewer as the expert on everything
A recruiter on a first screen usually cannot answer questions about forecast accuracy. Save the operational questions for the hiring manager or a peer, and use the earlier rounds to ask about the hiring process and the shape of the team.
Skipping the scope question
Two jobs with the same title can differ by an entire function. If you ask nothing else, ask what this role owns and where it hands off.
Reading a single disruption as a red flag
Most operations have had a bad quarter. What matters is whether anything changed afterwards, so ask about the fix before you judge the incident.
Leaving hours, travel and on-call until the offer
These feel awkward to raise, so candidates put them off and then find out during the first peak season. Ask plainly in a later round, once the interviewer has seen that you are interested in the work itself.