Logistics Manager interview questions

I look for the lowest sustainable total cost that still meets the service promise and risk appetite.

• I translate the customer promise into constraints such as order cutoff, delivery lead time, and fill rate by channel.
• I model transport, facilities, labor, inventory, duties, and working capital together because optimizing one cost moves another.
• I compare viable designs under base, growth, and disruption cases rather than presenting one mathematical optimum.

I need demand, product, service, and cost data at the level where network decisions are actually made.

• I use order-line history by origin, destination, SKU family, channel, and season, not monthly revenue by region.
• I normalize facility, labor, transport, inventory, tax, and capacity assumptions so sites are comparable.
• I challenge future demand and service assumptions with sales and finance because a precise model on an unowned forecast is misleading.

I start unconstrained to understand the economic shape of the network, then add real operating constraints.

• A center-of-gravity or optimization model identifies candidate locations from demand density, inbound flows, and service times.
• I screen candidates for labor, transport access, utilities, taxes, permitting, and expansion options.
• I test demand shifts and cost inflation because a site that wins only in the base case is fragile.

I give each facility a clear role based on the flow it serves, the inventory it holds, and the service it enables.

• A national DC can hold broad assortment and replenish regional nodes that carry faster movers near demand.
• Cross-docks and sortation hubs earn their place through flow consolidation, not by duplicating stock.
• I remove overlapping mandates because they create excess inventory, transfers, and competing priorities.

Hub-and-spoke works when consolidation value exceeds the extra handling and distance through the hub.

• Thin spoke lanes can become economical when their volume is combined at a common node.
• The hub needs capacity and schedule discipline because congestion or failure affects many lanes at once.
• I keep dense or time-critical pairs direct when the hub adds cost without useful consolidation.

I set service zones from achievable transit time and delivered cost, then make the boundaries operationally clear.

• Carrier lane performance and cutoff times matter more than radius because roads and schedules distort distance.
• Each postal area gets a primary node and a controlled fallback so orders do not bounce between sites.
• I review border areas separately because small volume or rate changes can alter the best source.

I compare recurring network benefit with transition cost, service impact, capacity risk, and lost resilience.

• Fixed cost, labor scale, and inventory pooling may improve while outbound miles and peak congestion rise.
• I test receiving capacity by process area and season, not just average pallet positions.
• Closure, severance, inventory transfer, and customer migration costs belong in the payback.

I share inventory where pooling creates value but separate execution rules where channel economics differ.

• Common stock improves availability, while allocation rules protect critical store and digital demand from each other.
• Fulfillment source reflects order profile, labor, parcel zones, store capacity, and split-shipment cost.
• Returns need an explicit path to resale, refurbishment, or disposal because reverse flow can erase the benefit.

I use a cross-dock when inbound supply can be synchronized with known outbound demand and dwell adds little value.

• Predictable high-volume flows with supplier-ready labels can move through short staging without reserve storage.
• Appointment reliability and accurate advance shipment data are essential because late or mixed freight creates congestion.
• I keep buffer stock elsewhere for volatile or service-critical items instead of forcing every SKU through the model.

I validate both the model mechanics and whether its recommended flows can survive real operations.

• Historical back-testing should reproduce known volumes, costs, capacities, and service closely enough to explain gaps.
• Operations, finance, sales, and tax owners challenge handling, growth, cutoff, and customer assumptions.
• Sensitivity analysis identifies assumptions that can reverse the decision, so I improve evidence for those variables.

I convert the business promise into lane-level service needs and design capacity, modes, and carriers around them.

• Margin, shipment profile, geography, and customer commitments show where speed, flexibility, or unit cost matters.
• I separate stable base volume from volatile demand so contracts cover the core without premium rates everywhere.
• The strategy has owners and review triggers because growth, fuel, and carrier performance change the answer.

I design the portfolio to secure reliable core capacity while preserving competition and recovery options.

• Primary carriers receive enough predictable volume to invest in lanes and understand our operation.
• Secondary carriers receive meaningful freight, not dormant awards, so they remain ready and engaged.
• I limit fragmentation because too many small awards weaken accountability, data quality, and leverage.

I single-source when the lane is stable, strategically useful to the carrier, and recoverable if that carrier fails.

• Concentrated volume can improve price, equipment commitment, and operating consistency.
• I avoid it where capacity is tight, failure stops production, or an alternative cannot start quickly.
• Even with one primary, I prequalify a backup and keep rates, onboarding, and contacts current.

I treat sourcing as lane and capacity design, not a spreadsheet auction for the lowest rate.

• Clean shipment history, forecast volume, accessorial rules, and operating needs let carriers price the real freight.
• Award scenarios consider rate, service, network fit, capacity commitment, and concentration risk together.
• Before go-live, carriers accept the lane guide and the team tests tender and EDI flows.

The contract must make the commercial offer enforceable under the operating conditions we actually face.

• I define base rates, fuel, accessorials, volume assumptions, payment, liability, and review triggers without gaps.
• Service obligations need measurable definitions for tender acceptance, pickup, delivery, claims, and data.
• Exit, capacity shortfall, audit, and dispute clauses matter because a low rate is worthless when execution fails.

I separate asset ownership from capacity dedication, then match each model to lane stability, control needs, and risk.

• A private fleet gives the most control but puts capital, drivers, maintenance, empty miles, and residual asset risk on us.
• A dedicated contract reserves a carrier's or 3PL's drivers and equipment for our operation without our owning the fleet, usually against volume, term, and indexation commitments.
• Common carriage shares a carrier network across customers and gives more flexibility, so I use it for variable or fragmented lanes after comparing service, fully loaded cost, and recovery options.

I match modes to product economics, service need, shipment profile, and lane reliability rather than one company-wide rule.

• Ocean or rail suits planned volume, while truck and air protect short lead times or high-value interruptions.
• The choice includes inventory in transit, variability, handling, damage, and shipment size, not only freight rate.
• I plan conversions on stable flows and keep a premium-mode policy for genuine exceptions.

I govern modal mix as a lane policy with explicit economics, exception authority, and review triggers, not as planner discretion.

• I segment lanes and flows by service window, volume, variability, product value, and handling constraints, then set a primary mode, fallback mode, and consolidation cadence using total landed cost.
• Exception rules state when a premium or alternate mode is allowed, who approves it, which reason code and cost owner apply, and when the exception expires.
• I review exceptions monthly for structural leakage and revisit lane rules when volume, rates, reliability, inventory economics, or the customer promise crosses an agreed threshold.

I protect predictable base volume with contracts and use spot capacity deliberately for volatility.

• Contract carriers need realistic volume and tender behavior to keep pricing and commitments credible.
• Spot suits launches, disruptions, surges, and thin lanes, but repeated use signals a planning or routing-guide gap.
• I track cause and total premium so commercial urgency does not hide structural leakage.

I separate paper savings from realized savings and manage the behaviors connecting them.

• The baseline uses comparable volume, fuel, accessorials, and service so sourcing gets fair credit.
• Routing-guide compliance, tender acceptance, spot leakage, and accessorials show whether awards reach invoices.
• Finance validates savings after mix effects, while operations fixes freight that bypasses the award.