HeroApply
Auto Apply to hundreds of jobs in a few hours
English (US)EspañolItalianoPortuguêsFrançaisDeutsch日本語한국어
Sign up

Supply Chain Analyst interview questions and how to answer them

A supply chain analyst interview is less about definitions and more about whether you can find the real problem inside a messy dataset. Expect a mix of concept questions, a hands-on exercise, and a lot of "tell me about a time" questions from people who've been burned by bad numbers before. Here's what they'll ask and what a good answer sounds like.

11 questions7 minute read

Part 1

1.Walk me through how you'd set a safety stock level for a product.

Why they ask

Safety stock is where demand variability, lead time and service targets meet. It shows whether you understand the tradeoff between running out and tying up cash.

How to answer

  • Name the inputs: demand variability, supplier lead time and how much that lead time moves, and the service level the business wants
  • Explain that higher service targets and less reliable suppliers both push the buffer up
  • Mention that you'd segment items, since a fast-moving A item and a slow C item shouldn't get the same treatment
  • Say you'd review it on a schedule, because a formula set once and forgotten drifts out of date

2.Our forecast accuracy dropped last quarter. How would you figure out why?

Why they ask

This is the everyday job. They want to see whether you break a vague problem into pieces before jumping to a fix.

How to answer

  • Start by checking how accuracy is measured and whether the metric itself changed
  • Break the miss down by product family, customer, region and week to see where it's concentrated
  • Look for bias, meaning a forecast that's always high or always low, as opposed to random error
  • Check for known causes: promotions, new products, lost customers, stockouts that hid real demand
  • Close with how you'd share the finding with the planning team

3.Tell me about a time you found a data problem in an ERP report.

Why they ask

Every analyst in this job fights bad master data. They want proof you catch it rather than passing wrong numbers along.

How to answer

  • Describe the report and what looked off, like a unit of measure mismatch or duplicate item numbers
  • Explain how you confirmed it, for example by tracing a sample of transactions back to the source
  • Say who owned the fix and how you got them to act
  • Share what changed afterward, such as a check you added to catch it next time
4.How would you decide which items to look at first if inventory is too high across the board?

Why they ask

They're testing whether you prioritize by impact instead of trying to fix thousands of SKUs at once.

How to answer

  • Rank items by the value of excess stock, not by count
  • Use ABC or a similar segmentation to find where the money sits
  • Separate slow movers you can still sell from obsolete stock that needs a write-off conversation
  • Look upstream at order quantities, minimums and lead times driving the overbuying
5.A key supplier just told you a shipment will be late. What do you do in the first hour?

Why they ask

Disruptions happen weekly. They want to know if you stay calm and quantify the damage before anyone panics.

How to answer

  • Find which customer orders or production runs depend on that shipment
  • Check stock on hand, in transit and at other sites that could cover the gap
  • Price the options: expedite, split the order, substitute a part, or reschedule
  • Give planners and sales a short summary with a recommendation, not just the bad news

Part 2

6.Which KPIs would you put on a supply chain dashboard, and why?

Why they ask

It shows whether you know what the business cares about and whether you can keep a dashboard focused.

How to answer

  • Pick a handful: fill rate or on-time in full, inventory turns or days of supply, forecast accuracy, supplier on-time delivery
  • Tie each one to a decision someone makes with it
  • Mention that metrics pull against each other, like service level against inventory cost
  • Say you'd ask the audience what they need before building anything
7.Explain the bullwhip effect to someone in sales.

Why they ask

It's a classic concept, but the real test is whether you can explain it without jargon to a non-analyst.

How to answer

  • Use a plain example: a small bump in store sales turns into a much bigger order swing at the distributor and the factory
  • Point out the causes, like batching orders, reacting to promotions and everyone padding their own forecast
  • Link it to something sales controls, such as sharing promotion plans earlier
8.Show me how you'd approach this dataset. (Usually an Excel file of orders, receipts or inventory.)

Why they ask

This is the hands-on round. They care about your process as much as your answer.

How to answer

  • Check the data before analyzing it: blanks, duplicates, odd dates, mismatched units
  • Restate the question in your own words before building anything
  • Use pivots, lookups or a simple query to answer it, and explain each step out loud
  • End with a finding and the next question you'd ask
9.Tell me about a time a planner or buyer disagreed with your analysis.

Why they ask

Your reports only matter if people use them. They want to see how you handle pushback from people with more floor experience.

How to answer

  • Describe the disagreement and what each side believed
  • Show that you listened, because the planner sometimes knows something the data doesn't
  • Explain how you checked your work or brought in more evidence
  • Share how it ended, even if they turned out to be right
10.Why supply chain, and why this company?

Why they ask

They want to know you'll stick around and that you've looked at their products and network.

How to answer

  • Give a real reason you like this work, like solving problems that show up on a shelf or a loading dock
  • Mention something specific about their business, such as seasonal demand or a large supplier base
  • Connect your past work to the problems they're likely facing

Part 3

11.Tell me about a time you had to deliver an analysis under a tight deadline.

Why they ask

Ad hoc requests with same-day turnaround are common, and they want to know you can give a good-enough answer fast.

How to answer

  • Set up the request and who needed it
  • Explain what you chose to skip and what you refused to skip
  • Say how you flagged the limits of a quick answer
  • Describe the result and whether you followed up with a fuller version

Questions to ask them

Ask at least two. It shows you're picking them too.

  • Which ERP and planning tools does the team use, and how clean is the master data?
  • Who are the main people using this role's reports, and what decisions do they make with them?
  • What's the biggest supply chain problem the team is trying to solve right now?
  • How much of the job is standing reports and how much is ad hoc analysis?
  • What does a strong analyst on this team usually move into next?