Source description
About the role
- Own network stability (the constant)
This is the through-line of the role regardless of what else you pick up:
Set up and govern the automated dashboards, early-warning frameworks, and control-tower rituals tracking end-to-end SLAs, TAT, RTO, and cost health across first-mile, middle-mile, and last-mile.
Detect real-time and structural exceptions across the linehaul and sorting ecosystem, and trigger rapid-response protocols before they hit the customer.
Lead structural RCAs on daily/weekly deviations, and drive permanent corrective and preventive fixes with ground ops - not one-off patches.
- Take on whatever moves the needle (the variable)
The problems below are illustrative of what may land on your plate - the list is not exhaustive, and priority shifts with the network:
Network Design: Design and continuously optimize the end-to-end layout (sorting hubs, micro-nodes, linehaul lanes, last-mile catchments).
Capacity & Demand Planning: Build predictive volume models and capacity plans that hold up in BAU and scale seamlessly through peak festival events.
Risk & Redundancy: Build contingency frameworks and fail-safes that stop regional shocks from cascading into network-wide failures.
Cost & Efficiency: Drive structural cost reduction through route optimization, load utilization, and node efficiency, in partnership with Product and Data.
New mandates: Take ownership of emerging, high-stakes problems across Fulfilment & Experience that don't yet have a clear owner.
- Standardize what works
Partner with central teams to design and enforce scalable SOPs and operating guidelines across an asset-light partner ecosystem - so fixes become the default, not tribal knowledge.
- Orchestrate across the network
Act as the bridge between central Strategy, Product, Tech, Regional Ground Ops, and external 3PL/micro-entrepreneur partners - aligning network capability with growth targets and translating ambiguity into execution.
More at Meesho