Supply chain analyst screening questions: forecasting, inventory, planning systems and S&OP
On this page
- Which supply chain analyst: demand, inventory, procurement or transportation
- Forecasting: accuracy, bias and overrides
- Inventory: safety stock, reorder points and turns
- Procurement and supplier analysis
- S OP and working with planners
- Systems and tools: user, power user or builder
- Certifications: CPIM, CSCP and CPSM
- Knockout checklist and scorecard
- Questions people ask
A supply chain analyst screening call should find out which decision the candidate's analysis controlled: how much to order, how much to hold, which supplier to use, or how to ship. Ask how they measured forecast accuracy and bias, how safety stock was set and when they last changed it, what they did in the planning system beyond running reports, and what they brought to the S&OP meeting. Analysts who did the work talk in weeks of supply, service levels, lead times and SKU counts. Inflated resumes say "optimized inventory" and "data-driven insights" without a number that moved.
This is not the general data analyst phone screen, which tests SQL and dashboards in any domain. For the people who run the floor, use operations manager screening questions; for shipment execution roles, see logistics coordinator screening questions.
Which supply chain analyst: demand, inventory, procurement or transportation
| Focus | What the work usually is | Facts to ask for | Common overstatement |
|---|---|---|---|
| Demand planning | Statistical forecasts, overrides from sales input, accuracy tracking, consensus forecast | SKU count, forecast horizon and level, accuracy metric, tool | "Built forecasts" meaning they loaded sales history into a tool with default settings |
| Inventory or supply planning | Safety stock, reorder points, replenishment, purchase order suggestions, excess and obsolete stock | Locations, SKU count, service level target, turns or days of supply | "Reduced inventory 20 percent" during a year when sales fell 20 percent |
| Procurement or sourcing analyst | Spend analysis, supplier scorecards, bids, price variance | Spend under analysis, categories, supplier count, savings method | "Negotiated savings" as the person who built the bid spreadsheet |
| Transportation or network analyst | Freight spend, carrier performance, lane analysis, network modeling | Modes, shipment volume, TMS, carrier count | "Network optimization" meaning a one-time freight cost comparison |
| Supply chain reporting analyst | KPI dashboards, data pulls for planners and managers | Which reports, who used them, what decisions followed | Planning experience claimed for a reporting role |
Forecasting: accuracy, bias and overrides
Ask: "How was forecast accuracy measured where you worked, at what level, and what was it?" Candidates who owned a forecast know the metric and its weaknesses. Candidates near a forecast know the number from a dashboard.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| Which accuracy metric did you use, and at what level? | "Weighted MAPE at SKU by distribution center, monthly, with a three-month lag." | "About 90 percent" with no metric or level. |
| Did you track bias separately? | Yes, and explains why: accuracy can look fine while the forecast is always high or always low. | Never heard of forecast bias. |
| How did you handle sales or marketing overrides? | Tracked whether overrides improved or hurt accuracy and used that in the conversation. | Accepted every override, or ignored sales input entirely. |
| How did you forecast a new product or a promotion? | Analog products, promotion lift history, a review point after launch. | "We guessed." |
| Which forecasting method or tool did you use? | Names the tool (SAP IBP, Kinaxis, Blue Yonder, o9, Oracle, or Excel and Python) and what they tuned, such as model selection or seasonality. | Tool name with no setting ever changed. |
Worked example: why bias matters (invented numbers)
Two SKUs, forecast versus actual over three months:
- SKU A: forecast 100, 100, 100; actual 90, 110, 100. Errors: +10, −10, 0. Total bias: 0.
- SKU B: forecast 100, 100, 100; actual 95, 95, 95. Errors: +5, +5, +5. Total bias: +15, always high.
SKU B has the smaller average error (5 versus about 6.7) yet quietly builds inventory every month. Ask the candidate which one they would worry about. A planner picks B and explains why in a sentence.
Inventory: safety stock, reorder points and turns
- "How was safety stock set, and when did you last change it?" Strong: a method tied to demand variability, lead time variability and a service level target, plus a change and its effect. Red flag: "a fixed two weeks for everything," with no awareness that it is a simplification.
- "What service level were you targeting, and for which items?" Strong: different targets by segment, such as higher for A items. Red flag: 100 percent for everything.
- "How did you segment the SKUs?" Strong: ABC by value or volume, sometimes XYZ by variability, and a policy per segment. Red flag: one policy for all.
- "Tell me about excess or obsolete inventory you had to deal with." Strong: how it built up, the root cause (a forecast, a minimum order quantity, a cancelled program), and the disposition. Red flag: "Finance handled that."
- "What happened to service when inventory went down?" Strong: they tracked both together. Red flag: celebrates the reduction without mentioning fill rate.
Worked example: check an inventory claim (invented numbers)
The candidate says: "I improved inventory turns from 4 to 6."
- Turns = annual cost of goods sold ÷ average inventory value.
- With COGS of $24M: 4 turns means about $6M average inventory; 6 turns means about $4M.
- Ask: "Did COGS stay about the same? What did you change to take out roughly 2 million, and what happened to fill rate?"
If sales grew and inventory stayed flat, turns rise without any inventory work. A strong candidate says so.
Procurement and supplier analysis
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| How did you measure supplier performance? | On-time in full with a clear definition, lead time variability, quality rejects, and a review cadence with the supplier. | "We knew who the bad suppliers were." |
| Tell me about a spend analysis you did. What did it change? | Data source, how they cleaned and categorized it, and a decision: consolidation, a bid, a contract term. | A pivot table nobody acted on. |
| How did you calculate savings? | Against a defined baseline, agreed with finance, separating cost avoidance from price reduction. | Savings counted from the supplier's first quote. |
| What was your part in a supplier disruption? | Found exposure by SKU, calculated weeks of cover, modeled alternatives, communicated to sales. | Only heard about it afterwards. |
S&OP and working with planners
Sales and operations planning is where analysis meets decisions. Ask: "What did you bring to the monthly S&OP or IBP meeting, and what decision changed because of it?"
- Strong: "I built the supply review: capacity versus consensus demand by product family. In March it showed we'd be short on two families in Q3, and leadership approved weekend shifts in May."
- Weak but honest: "I prepared the demand slides; my manager presented." Fine for a junior role.
- Red flag: describes S&OP as a meeting they attended, with no input or output.
Follow-ups: "Who disagreed with your numbers?" and "What did you do when demand and supply plans could not both be met?" Listen for scenarios and trade-offs, not only charts.
Systems and tools: user, power user or builder
| Claim | Question | Strong answer | Red flag |
|---|---|---|---|
| SAP (MM, PP, IBP), Oracle, Dynamics, NetSuite | "Which transactions or screens did you use daily, and did you maintain master data like lead times or MOQs?" | Names tasks and a master data fix that changed planning results. | ERP name with reports only. |
| Kinaxis, Blue Yonder, o9, Logility | "What did you configure or tune?" | Parameters, planning rules, scenario setup. | Only accepted system suggestions. |
| Excel | "What was the most important model you maintained?" | A replenishment or safety stock model, with inputs, outputs and who used it weekly. | "Advanced Excel" with no model. |
| SQL, Python, Power BI or Tableau | "Did you write the queries or scripts yourself, and how often did they run?" | A recurring job or dashboard and its users. | One course project presented as work experience. |
Master data is an underrated depth signal. Wrong lead times and minimum order quantities break every plan, and analysts who have cleaned them up talk about it without prompting.
Certifications: CPIM, CSCP and CPSM
These are optional for most analyst roles. Know what each involves (as of September 2026):
| Credential | Issuer and what it involves | Question to ask | How to check |
|---|---|---|---|
| CPIM | ASCM (APICS). One exam covering planning and inventory management modules, per ASCM's CPIM page | "Which part of it do you use most at work?" | ASCM's credential verification |
| CSCP | ASCM. End-to-end supply chain exam; ASCM has eliminated its eligibility requirements | "What did you apply from it?" | ASCM credential verification |
| CPSM | Institute for Supply Management. Three exams plus three years of professional supply management experience with a bachelor's degree, or five without, per ISM's CPSM page | "Which sourcing work qualified you?" | Ask for the certificate; confirm with ISM if required |
| Six Sigma belt | Many issuers | "Who issued it, and what project did it require?" | Depends on issuer |
Knockout checklist and scorecard
Must-ask on every supply chain analyst screen
- Focus: demand, inventory, procurement, transportation or reporting.
- Scale: SKUs, locations, suppliers or spend.
- Forecast accuracy metric, level and bias, if they forecast.
- How safety stock or reorder points were set, and one change.
- One analysis that changed a decision, with the before and after.
- Systems at the right depth, including master data work.
- Credentials checked if the client requires them; salary expectation, on-site days, notice period.
Knock out, or flag before submitting, if a planning role's candidate cannot explain how their own forecast or inventory policy was measured; if every result is a percentage with no baseline; if the client's planning system is a hard requirement and the candidate has only seen reports from it; or if the role is sourcing-heavy and the candidate has only done reporting.
| Area | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Domain depth | Buzzwords | Knows concepts | Applied them with numbers | Changed a policy and tracked the trade-off |
| Decision impact | Reports nobody used | Inputs to a manager's decision | Own recommendation adopted | Recurring decisions depend on their model |
| Systems | Name only | Reports | Power user with master data work | Configured or built planning tools |
| Communication | Jargon | Clear with analysts | Clear in S&OP | Handled disagreement with data |
| Logistics fit | Deal-breaker | Two open questions | One open question | All aligned |
Beside each score, write the evidence as said: "Weighted MAPE at SKU-DC level, tracked bias; cut safety stock on C items and held 97 percent fill rate." Interview Signal attaches quotes like that to each score from the call, which keeps the numbers exact when you write the submittal.
Questions people ask
What is the difference between a supply chain analyst and a data analyst screen?
A data analyst screen tests SQL, dashboards and stakeholder requests in general. A supply chain analyst screen tests whether the candidate understands what the numbers control: forecasts, safety stock, reorder points, supplier performance and the trade-off between service level and inventory cost.
Do supply chain analysts need a certification?
Usually not. ASCM's CPIM and CSCP and ISM's CPSM are respected, but the CSCP currently has no eligibility requirements and none of them proves the candidate has changed an inventory policy. Treat them as knowledge signals and test the work.
What does a good forecast accuracy number look like?
There is no universal benchmark; it depends on the product, the level of aggregation and the time horizon. What matters on the screen is whether the candidate knows how their accuracy was calculated, at what level, and whether the forecast was biased.
Should I test Excel or SQL on the phone?
No. Ask what they built and how often it ran. A candidate who maintained a weekly inventory model can describe its inputs and outputs in a minute, and the hiring team can test the skill afterwards.