Network Planning interview prep.

Trained on network designer / supply chain engineer / solutions architect / optimization analyst interviews across brokers, asset-based 3PLs, forwarders, contract logistics, and integrated providers.

What interviewers look for

  • Can the candidate frame a network design problem - objective, constraints, decision variables, data needs?
  • Do they understand cost-to-serve mechanics - fixed vs variable, handling vs transport, allocation rules?
  • Are they fluent in mode + lane economics - TL vs LTL vs intermodal vs parcel break-points?
  • Can they navigate the RFP / tender process from a 3PL's commercial perspective?
  • Do they understand customer implementation reality - data quality, change management, go-live risk?
  • Are they grounded in S&OP + capacity discipline - peak planning, labor, dock capacity, fleet?
  • Can they speak credibly to sustainability + scope-3 + mode shift levers?
  • Long-game fit - analyst / senior / manager / director / VP network design trajectory?

Behavioural questions to expect

  1. Walk me through your background + your path into supply chain network work.

    What it tests: Story arc - quantitative / analytical training + commercial exposure + concrete network or modeling work. Interviewers screen for candidates whose path lands on 3PL network design as deliberate, not default.

  2. Tell me about a network design or optimization project you've owned end-to-end.

    What it tests: Modeling rigor + commercial + implementation lens. Can the candidate walk problem framing -> data -> model -> recommendation -> stakeholder handoff cleanly.

  3. Why 3PL vs shipper-side supply chain or consulting?

    What it tests: Authentic alignment - commercial pace, multi-customer pattern recognition, asset + operational stakes vs pure analysis.

  4. Why network planning specifically vs operations, procurement, or commercial roles?

    What it tests: Specificity. Generic 'I like analytics' fails.

  5. Why this firm?

    What it tests: Real homework - service mix + customers + tooling + recent moves - not 'great brand'.

  6. What's your read on our network and customer footprint?

    What it tests: Industry literacy - asset footprint, customer concentration, recent moves, where the design team likely focuses.

  7. Tell me what you understand about our network design + tooling capabilities.

    What it tests: Engineering maturity awareness - in-house solver, named tool stack, data infrastructure, recent investments.

  8. Walk me through how you'd design or redesign a customer's distribution network.

    What it tests: Modeling fluency + commercial instinct - can the candidate frame problem, choose tools, identify data needs, propose scenarios, quantify trade-offs.

Technical concepts to master

Network design fundamentals

Greenfield vs brownfield
Greenfield = optimal network from scratch (ignore existing assets); brownfield = constrained by current leases, labor, customer locations.
MILP + heuristic solvers
Network design typically formulated as Mixed-Integer Linear Programming (MILP); large problems solved with commercial solvers (CPLEX, Gurobi) or heuristics (genetic, simulated annealing).
Tool stack
Industry-standard network design tools: Coupa Supply Chain Guru (formerly Llamasoft), OptiLogic Cosmic Frog, AIMMS, AnyLogistix; many shops also run custom Python / Pyomo / OR-Tools.
Baseline + scenario discipline
Every network study starts with a validated baseline (current network, current costs) then layers 2-4 scenarios (consolidation, mode shift, service-level change, growth).

S&OP + capacity planning

S&OP cycle
Monthly cross-functional process aligning demand forecast, supply capacity, financial plan - typically 4-6 step cadence (product review, demand review, supply review, integrated reconciliation, executive S&OP).
Peak planning
Pre-positioning labor, dock, fleet, carrier capacity for peak periods (Q4 retail, harvest, Lunar New Year for forwarding).
Capacity buckets
Dock doors / hour, units / labor-hour, fleet tractors + drivers available, carrier contracted capacity by lane - each measured + planned distinctly.
Demand signal quality
Customer-provided forecasts (POS, promo, new-store), historical demand, leading indicators - quality varies wildly + drives planning accuracy.

RFP + commercial models

Commercial models
Common 3PL contract structures: cost-plus (open-book + margin), gainshare (shared savings vs baseline), fixed-fee (per unit / per shipment), transactional (spot brokerage).
Cost-plus vs gainshare
Cost-plus = customer sees all costs + a defined margin; gainshare = baseline cost agreed, savings split (commonly 50/50) creating mutual incentive.
RFP response architecture
Standard sections: executive summary, network design + ops plan, technology + visibility, implementation + transition, commercial + pricing, sustainability + ESG.
Pricing sensitivity + risk loading
Price built up from cost-to-serve + target margin + sensitivity to volume / diesel / labor inflation + risk premium for service or volume commitments.

Sustainability + scope-3 carbon

Scope-3 logistics emissions
Customer's scope-3 category 4 (upstream transportation + distribution) + 9 (downstream) - 3PLs are the data + lever owner.
Mode shift levers
Shifting volume from higher-emission modes to lower (TL -> intermodal -> rail, air -> ocean) typically saves cost AND carbon.
Network + load optimization levers
Higher cube + weight utilization, reduced deadhead, regional consolidation, drop trailers, multi-stop routing - all reduce emissions per unit shipped.
Alt-fuel + electrification
EV last-mile vans, electric yard tractors, renewable diesel, hydrogen pilots - capital + infrastructure intensive but increasingly common in 3PL roadmaps.

Practical drills

  • A customer ships 200 loads / month on a 1,000-mile lane via TL at $2,500 per load. Intermodal on the same corridor would cost $1,900 per load including drayage but add 2 days of transit. Customer service spec is 5 days. Walk through whether to shift, by how much, and the carbon + risk view. Show your numbers.
  • A customer runs 7 regional DCs across North America serving 8,000 retail-store ship-tos. They're asking whether to consolidate to 3-4 mega-DCs to save fixed cost. They have a 2-day standard service spec. How would you approach the study and what's your initial hypothesis?
  • A mid-sized industrial manufacturer ($800M revenue) issues an RFP for end-to-end North America logistics - inbound from 60 suppliers, 3 DCs, outbound to 2,500 customer ship-tos. They want a 3-year contract. Walk me through how you'd scope the response and what commercial structure you'd propose.

Smart-question anchors

  • Network design team org - centralized strategic vs embedded with customer teams
  • Tool stack maturity - in-house solver vs commercial, data infrastructure, AI / ML investments
  • Customer + vertical mix - where the design team's focus areas are likely to grow
  • Commercial model preferences - gainshare vs cost-plus, open-book transparency, contract terms
  • Sustainability + scope-3 - public commitments, customer scope-3 offerings, mode-shift programs

Sourced from

Ready to Generate Your Own Prep?

Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.