Supply Chain Questions to Ask Interviewer
Questions to ask your interviewer when the role is in planning, procurement, or logistics. Specific enough that the answers tell you how the operation really runs, and which parts of the job nobody put in the posting.
The questions
Open any question for the note
What does this role own end to end, and where does it hand off?
Why ask it
Supply chain titles cover planning, buying, and logistics in different combinations at every company. The handoff points are where you will spend your weekly arguments, so they matter more than the title.
What's your service level target, and where are you against it?
Why ask it
Listen for whether they can quote fill rate or on-time-in-full without checking. Interviewers close to operations have the number; ones who describe the org chart instead usually are not.
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.
How does your inventory position compare with a year ago, and why has it moved?
Why ask it
Direction plus explanation. A rise attributed entirely to market conditions suggests limited root cause work, while a specific answer about lead times or a launch suggests the opposite.
Which suppliers keep you up at night?
Why ask it
Every operation has a sole source or a fragile lane. Whether the answer names a category, a region, or a specific part tells you how well the risk register is actually maintained.
What was your last significant disruption, and what changed afterwards?
Why ask it
The follow-through is the real answer. Operations that can describe an incident but no resulting process change tend to repeat it within a couple of years.
What systems are you running, and which of them talk to each other?
Why ask it
Ask specifically about the joins between the ERP, the warehouse system, and any planning tool. Manual reconciliation between systems is where analyst hours quietly disappear.
Where does data go missing between those systems?
Why ask it
An interviewer who can answer this in detail is describing the job honestly. It also tells you how much of your first year would be data cleanup rather than the work you were hired for.
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 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.
How do your sales and operations planning meetings run, and who attends?
Why ask it
Attendance is the signal. Without commercial leadership in the room, the meeting is reporting rather than deciding, and the plan gets overruled elsewhere anyway.
How long does it take to onboard a new supplier?
Why ask it
Long onboarding limits how fast the operation can respond to a problem. The answer also reveals how much procurement and compliance overhead sits on top of every change you would propose.
What happens when a batch or shipment fails quality?
Why ask it
Ask for the most recent case. An answer that names roles, timings, and who contacted the supplier indicates a real process rather than an improvised one.
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. Vagueness can mean a broker holds the knowledge and nobody internally can challenge what the broker says.
What have you automated recently, and what did it break?
Why ask it
Automation always moves work somewhere else. The honest answer names the new manual step created downstream, which is often the job you would inherit.
Which sustainability commitments have changed a sourcing or transport decision so far?
Why ask it
Separates reporting from operations. If no commitment has yet altered a supplier or a shipping mode, it is currently a disclosure exercise rather than a constraint on planning.
How is this team measured, and does any other function share those numbers?
Why ask it
Shared metrics with sales or finance change behavior considerably. Numbers owned by supply chain alone often mean the team absorbs the consequences of other people's decisions.
What's the biggest process here that still runs on spreadsheets?
Why ask it
Almost every operation has one, and it is usually where both the risk and the opportunity sit. The reaction to the question is informative even before the answer arrives.
Why is this role open, and what did the last person find hardest?
Why ask it
Backfills in supply chain are often about burnout or a scope that was never properly resourced. Ask what has changed since, and note whether anything has.
If I started next month, what would you want fixed first?
Why ask it
Turns the conversation into a work plan and shows whether there is one clear priority or an undifferentiated list of everything that is wrong.
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 often mention shortages, port issues, or supplier failures. Referencing one specifically gets a much more detailed 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 specific number signals experience faster than any answer you give about yourself.
What the answers tend to tell you
- A quoted service level or forecast error figure means the interviewer works with operations rather than around them.
- High manual override of the plan almost always means a shadow spreadsheet, and inheriting it is part of the role.
- If expediting requires senior sign-off, expect limited decision rights across the whole job.
- Naming the downstream mess created by a recent automation project is a sign of an honest, self-aware team.
- When several answers point to the same broken join between two systems, that is the actual first-year project.
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
An HR screen cannot answer questions about forecast accuracy. Save the operational questions for the hiring manager or a peer, and ask process questions in the earlier rounds.
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
Every operation has had a bad quarter. What matters is whether anything changed afterwards, so ask about the fix rather than judging the incident.