Amazon.com, Inc. — Supply Chain Manager Interview Guide

role overview, interview process, what each round tests, sample questions and cases, a step-by-step case walkthrough with concrete arithmetic, the evidence you must bring, a preparation plan, scoring signals, FAQs, and final tactical tips. Use it directly to prepare for phone screens, take-homes, and onsite loops.

1. Role overview — what hiring managers want?

A Supply Chain Manager in this company is expected to own operational reliability and cost efficiency across fulfillment (warehousing), transportation, and inventory for a node or region. Success metrics are concrete: on-time fulfillment, cost per unit shipped, inventory turns, forecast accuracy, and customer experience (delivery promise adherence). Hiring managers want:

• Strong problem solvers who can move from data → hypothesis → controlled experiment → sustained ops change.

• Operational leadership: run daily ops, fix root causes, coach teams, manage third-party partners.

• Cross-functional influence: work with product, finance, regional operations, network planning, and engineering.

• Quantitative fluency: Excel/SQL, simple optimization reasoning, KPI dashboards.

• Program management: launch capacity changes, lead peak readiness, de-risk supply constraints.

• Continuous improvement mindset (Lean / Six Sigma, Kaizen).

Be ready to show crisp examples where you reduced lead time, improved fill rate, cut costs, or scaled a process under pressure.

2. Typical interview process (stages & timeline)

Process varies by location/level but commonly:

1. Recruiter screen (20–30 min) — resume fit, logistics, compensation baseline, brief motivation.

2. Phone / hiring manager screen (30–45 min) — depth on prior ops ownership, a behavioral example, quick metric questions.

3. Take-home case or pre-work (24–72 hrs) — solve a network/inventory or capacity planning brief with assumptions and calculations.

4. Onsite loop (3–5 interviews, 45–60 min each) — mix of:
   • Operations problem solving & case.
   • Analytics / SQL & metrics.
   • Behavioral / leadership (influence, crisis management).
   • Program/project management (launch, cross-functional).
   • Partner management (3PL, vendor negotiations).

5. Final hire committee review — may be additional calibration questions.

Expect 2–5 weeks total. Prepare to defend numbers and assumptions.

3. What each interview round tests (and how to prepare)

Operations problem-solving / Case (45–60 min)

What it tests: structured thinking, root cause analysis, practical solutions, measurable outcomes, trade-offs between cost, speed, and complexity.

How to approach: clarify objectives (metric to improve), ask for constraints (budget, time horizon), propose hypotheses, outline quick experiments, recommend scale changes with ripple effects.

Sample prompts:

• “One fulfillment center’s on-time rate fell from 98% → 92% in 6 weeks. Diagnose and propose immediate and 90-day fixes.”

• “You need to cut last-mile cost per package in the West region by 10% without harming the delivery promise. How?”

Analytics & Metrics (30–45 min)

What it tests: KPI definitions, data interpretation, basic modeling, SQL/Excel comfort.

Sample prompts:

• “How do you calculate OTIF? How would you detect whether late deliveries are due to picking or transportation?”

• “Given weekly shipment and demand data, how would you measure forecast accuracy? (Show formula).”

Inventory & Network Planning (30–45 min)

What it tests: safety stock logic, reorder points, network trade-offs (centralized vs distributed), supplier lead time management.

Sample prompts:

• “Design a safety stock policy for a new high-velocity SKU with variable lead time.”

• “Trade-offs between increasing DC count vs increasing transportation spend — how to decide?”

Program / Project Management (30–45 min)

What it tests: ability to scope launches, manage dependencies, risk mitigation, stakeholder communication.

Sample prompts:

• “You must open a new fulfillment center in 16 weeks. What’s your 90-day launch plan?”

• “How would you prepare for peak season if a major vendor’s lead time doubles?”

Behavioral & Leadership (30–45 min)

What it tests: ownership, influence, hiring/coaching, escalation judgment.

Sample prompts:

• “Tell me about a time you had to stop a production line or delay launches for safety/quality reasons. How did you communicate it?”

• “Describe a situation where you persuaded a stakeholder to change course using data.”

4. Sample interview questions (behavioral + technical)

Use STAR (Situation → Task → Action → Result), quantify results.

Behavioral

• “Describe a time you improved the fill rate. What steps did you take and what was the delta?”

• “Talk about a failed experiment and what you learned.”

Technical / Situational

• “Explain how you would design a test to determine whether picking errors are due to WMS UI or insufficient training.”

• “If inventory turns drop from 8 → 5, what are the possible causes and immediate checks?”

Quick metric checks

• “How do you compute inventory turns? (Inventory Turns = COGS / Average Inventory).”

• “What’s MAPE? (Mean Absolute Percentage Error = (1/n) Σ |(Forecast − Actual)/Actual| × 100%).”

5. Full case walkthrough — step-by-step example

Example brief: “A regional fulfillment center (FC-West) serves 8 western metro markets. OTIF has dropped from 98% to 92% over 6 weeks during a ramp in volume. You have 60 minutes to present diagnosis, immediate actions, and a 90-day plan. Show calculations where needed.”

1. Clarify objective
   • Ask: Is the target to restore OTIF to ≥98% within 30 days or minimize cost while restoring to 98% in 90 days?
   • Assume: Immediate objective = restore to ≥98% in 30 days while keeping costs neutral.

2. Quick facts & assumptions (state them)
   • Current weekly shipments = 100,000 packages.
   • Baseline OTIF = 98% → 2% late → 2,000 late packages/week.
   • Current OTIF = 92% → 8% late → 8,000 late packages/week.
   • Incremental late packages = 6,000/week (8,000 − 2,000).
   • Average cost of a late delivery (penalty + customer dissatisfaction handling) = $10/package (assumption; state you will validate).
   • Immediate weekly late cost = 6,000 × $10 = $60,000.

3. (Arithmetic shown step-by-step per guidelines.)
   • 100,000 × 0.02 = 2,000.
   • 100,000 × 0.08 = 8,000.
   • 8,000 − 2,000 = 6,000.
   • 6,000 × 10 = 60,000.

4. Hypothesis tree (quick root cause branches)
   • Volume surge → capacity constraint (picking, packing).
   • Labor shortage / increased attrition.
   • WMS/IT regressions (sorting labels, routing).
   • Upstream inventory issues (stockouts shifting to split shipments).
   • Transportation capacity / carrier disruptions.

5. Immediate triage (next 24–72 hours)
   • Pull last 7 days of data split by: order ship time, pick start → pick end, pack time, manifesting time, carrier pickup time. Identify where average cycle time increased. (If pick time per order increased → ops; if carrier pickup delay increased → transportation).
   • Quick SQL/filters to compute late share by SKU, by time-of-day, by carrier, and by last-mile ZIP code. Prioritize top 20 SKUs and top 20 ZIPs causing 80% of lateness.
   • If picking time per order increased from baseline 5.0 min → 7.5 min (example), calculate capacity gap:
     • Baseline capacity: assume 500 pickers × 8 hours × 60 min = 240,000 picker-minutes/week.
     • Baseline throughput at 5.0 min/order: 240,000 / 5 = 48,000 orders/week capacity.
     • New throughput at 7.5 min/order: 240,000 / 7.5 = 32,000 orders/week capacity.
     • Shortfall = 16,000 orders/week (this aligns with worsening OTIF).

       (Show arithmetic carefully)

     • 500 × 8 × 60 = 240,000.
     • 240,000 ÷ 5 = 48,000.
     • 240,000 ÷ 7.5 = 32,000.
     • 48,000 − 32,000 = 16,000.
   • Short term fix: call in temporary headcount (agency), adjust shift schedules to cover peaks, or prioritize shipping high-value / time-sensitive orders.

6. Immediate action plan (0–7 days)
   • Rebalance labor: add temporary pickers for peak windows. Estimate temp cost vs late delivery cost. If temp picker cost = $25/hour; to close 16,000 order shortfall at baseline 5 min/order requires additional picker-minutes = 16,000 × 5 = 80,000 minutes = 1,333 hours ≈ 167 picker-days (8-hour days). If you hire 50 temps for 4 days: 50 × 4 × 8 = 1,600 hours > needed. Weekly temp cost = 1,600 × $25 = $40,000 vs weekly late cost of $60,000 — hire temps.
   • Re-prioritize orders: push non-urgent / low-value orders by 48–72 hrs (communicate to customers proactively).
   • Fix quick IT issues: patch label/routing bug if identified; if no root cause in IT in 24 hours, escalate.
   • Carrier triage: reassign delayed parcels to alternative carriers in hotspots.

7. (Arithmetic)
   • Needed additional picker minutes = 16,000 × 5 = 80,000.
   • 80,000 ÷ 60 = 1,333.33 hours.
   • 1,333.33 ÷ 8 ≈ 166.67 picker-days.
   • 50 temps × 4 days × 8 hours = 1,600 hours.
   • 1,600 × $25 = $40,000.

8. 90-day plan (stabilize & prevent recurrence)
   • Root-cause deep dive: Pareto analysis, Kaizen events at top problem areas.
   • Workforce planning: revise hiring plan, retention incentives, cross-training.
   • Layout & slotting optimization: move top 20 SKUs to forward pick locations to reduce pick time. Estimate time savings: if moving reduces pick time from 7.5 → 4.0 min for 20 SKUs covering 40% of orders, compute impact:
     • For 40,000 orders/week (40% of 100k), time saved per order = 3.5 min → total saving = 40,000 × 3.5 = 140,000 minutes = 2,333 hours/week.
   • Automation evaluation: put throughput vs cost model for conveyor/robotic pick for long term.
   • Supplier & inbound scheduling: flatten inbound volumes, reduce weekend peaks through vendor delivery windows.
   • Transportation contracts: add flex capacity and force majeure clauses.

9. (Arithmetic example)
   • 100,000 orders × 0.40 = 40,000.
   • 40,000 × 3.5 = 140,000 minutes.
   • 140,000 ÷ 60 = 2,333.33 hours.

10. Measurement & KPIs
    • Primary: OTIF %, Average Delivery Delay (hours), Cost per Order, Fill Rate, % Split Shipments.
    • Leading: pick rate (orders/hour/picker), avg pick time, carrier pickup compliance, inbound appointment compliance.
    • Experiments: implement a phased slotting change in 1 wave and measure delta in pick time vs control FCs.

11. Risks & mitigations
    • Risk: temp hires underperform → mitigation: pair with experienced pickers and reduce complexity tasks.
    • Risk: customer backlash from delayed orders → mitigation: proactive refunds/credits and transparent communication.

12. Close with recommended next steps
    • Run immediate data pull to confirm pick time delta and top SKUs causing lateness.
    • Approve temp headcount for 2 weeks and measure OTIF improvement.
    • Launch slotting pilot in single pod and measure pick time per order.

This approach shows data-driven triage, cost vs benefit calculations, and practical execution.

6. How interviewers will score you (what to emphasize)

• Problem framing & hypothesis: Did you ask the right clarifying question and define the metric to move?

• Data-driven diagnosis: Use the right splits (by SKU, zone, carrier, shift) and show basic calculations.

• Feasible execution: Immediate fixes (0–7 days) should be operationally realistic and justified by cost math.

• Program thinking: 30–90 day levers with measurable success criteria.

• Stakeholder & escalation plan: Who needs to be involved (HR, carriers, vendors, engineering), and what decisions require escalation?

• Leadership: Evidence you led teams, trained staff, negotiated with vendors, and handled tradeoffs.

7. Portfolio & take-home assignment guidance

What to include (3–6 items; depth > breadth):

• One or two ops turnaround case studies (before/after metrics: OTIF, cost per order, cycle time), with concrete timelines and your role.

• A capacity planning example showing staffing model arithmetic and assumptions.

• A launch or scale project (e.g., new FC opening or automation pilot) with Gantt, dependencies, and outcomes.

• An experiment (A/B / pilot) with design, control groups, and measured impact.

Take-home deliverable structure:

1. One-page executive summary (top recommendation + numbers).

2. Problem statement & constraints.

3. Diagnosis & data analysis (charts or tabular numbers).

4. 0–7 day fixes, 30/60/90 day plan, and cost vs benefit.

5. Risks & contingency plan.

6. Appendix with raw calculations and SQL snippets (if applicable).

8. Skills checklist (must-show and nice-to-have)

Must-show

• Metrics fluency: OTIF, fill rate, inventory turns, cycle time, MAPE, cost per order.

• Excel modeling: staffing, throughput, basic optimization.

• SQL for data pulls (joins/aggregates), or ability to describe queries clearly.

• Ops experience: WMS, slotting, DC layout, 5S, Kaizen.

• Vendor & carrier management.

• Program management and escalation.

Nice-to-have

• Lean / Six Sigma certification (Green/Black Belt).

• Familiarity with network optimization tools and TMS/WMS names.

• Experience with automation (robots, sorters).

• Coding for analytics (Python) or advanced SQL.

9. Preparation strategy — intensive 8–12 day plan

Day 1–2: Metric & case fundamentals

• Refresh OTIF calculation, inventory turns, MAPE, fill rate formulas.

• Practice 4 ops cases (triage scenarios).

Day 3–4: Analytics & SQL

• Write 6 SQL queries: pick rate by hour, late rate by carrier, top SKUs by lateness, inbound compliance.

• Build Excel staffing model templates.

Day 5: Inventory & network

• Prepare one inventory safety stock example and one DC count trade-off mini-case.

Day 6–7: Behavioral stories

• Prepare 10 STAR stories: turnaround, escalations, vendor negotiations, hiring/training, safety incidents.

Day 8–9: Program plans & take-home

• Draft a 1-page executive summary template and a 6-slide take-home deck skeleton.

• Time for a take-home: practice delivering it in 15 minutes.

Day 10–12: Mocks

• Run 3 mock interviews: 2 cases (60 min each) and 1 behavioral loop.

Tactics: always state assumptions, show calculations, and name tradeoffs.

10. Common FAQs (short, direct answers)

Q: Will they ask for coding?

A: No production coding. Expect SQL/data questions and Excel modeling.

Q: How technical must I be?

A: Comfortable with SQL and analytical reasoning; not required to be an engineer but must interpret data and define experiments.

Q: Do I need automation experience?

A: Helpful but not mandatory for mid-level roles. Demonstrate you can evaluate the ROI of automation.

Q: How to discuss confidential metrics?

A: Use ranges and percent improvements rather than exact confidential numbers; show methodology and assumptions.

11. Final tactical tips — what wins interviews here

• Start with the metric you will move and frame decisions around that metric.

• State assumptions explicitly and show arithmetic for any numeric claim. Interviewers trust transparent assumptions.

• Be operational — offer immediate, pragmatic fixes and show how you'll measure progress. Big ideas without executable steps lose points.

• Demonstrate stakeholder thinking — who signs off, who executes, and what tradeoffs they must accept.

• Use short, quantified STAR stories: “I reduced late deliveries by X% and saved $Y/month by implementing Z, measured via metric A.”

• If you don’t know something, say what you would query (specific SQL or report) and what thresholds would change your recommendation.