Senior Manager - FnE

Meesho · Bangalore

Source and collection record

Last observed by our collector: 9 October 2026 at 12:46 am IST. This is not a manual review or a confirmation from the employer.

Employer requisition: 2b1ae28e-627b-40fd-8ed8-219c864178fa

Job type and experience labels are automated discovery categories. The employer determines eligibility. Original experience wording was not retained separately; check the current employer page.

How sourcing and classification work · Report a discrepancy

Your application evidence checklist

Mark the statements you can support after reading the employer source. This checklist stays on this page; it does not score your eligibility or submit an application.

Attendance and availability: I checked the employer page for work location, office attendance, start date and duration.Current requisition: I checked the current employer requisition and its application requirements.

0 of 2 checks marked. Keep unresolved requirements as questions for the employer.

Collected role description

About the Team ValMo is Meesho's logistics and supply chain organization, responsible for building India's most cost-efficient, reliable, and scalable fulfillment network. From first-mile pickup to last-mile delivery and reverse logistics, ValMo powers millions of shipments every month for small businesses across the country. As we scale, the complexity of our network increases exponentially. ValMo operates at the intersection of technology, operations, and partner ecosystems — where execution precision and systems thinking are critical to prevent cascading (domino) failures across the network. About the Role The Control Tower is where the stability, reliability, and cost-efficiency of ValMo's pan-India network is owned end-to-end. This is a deliberately generalist role in Fulfilment & Experience - your mandate is defined by an outcome, not a fixed function. Put simply: you are the person we point at the highest-leverage problem threatening the network, and you figure it out from first principles. The specific problem changes with what the network needs. In one quarter you might be redesigning the topology of a region; in the next, rebuilding the capacity-planning engine, running a structural cost-out program, firefighting an RTO or CX spike, or standing up readiness for a peak event - including problems that don't yet have an owner. What stays constant is the accountability: keep the network stable, predictable, and cost-efficient no matter what breaks or scales.