How to Tailor Your Resume for Zepto.

Zepto sells speed. The promise of a delivery in minutes is not a marketing line on top of an ordinary e-commerce business, it is the constraint that every team works inside. Inventory has to be right, because there is no time to discover a stockout after the order. Forecasting has to be right, because a dark store holds only a few thousand items. Routing has to be right, because the delivery window is measured in minutes rather than days.

That constraint is what your resume should answer. The strongest quick-commerce resumes show someone who has worked against a hard limit, whether that limit was latency, inventory, headcount or time, and can say what they traded away to hold it.

Show that you have worked against a hard constraint

Most candidates describe what they built. In quick commerce the more useful thing to describe is the limit you were working inside and how you stayed within it. An engineer who held a p99 under a threshold during a demand spike, an analyst whose forecast reduced stockouts without raising wastage, or a store manager who kept picking times down while headcount was fixed are all telling the same kind of story.

Say what you gave up. Every quick-commerce decision is a trade: assortment against availability, speed against cost, wastage against stockouts. Naming the trade you made is a stronger signal than claiming an improvement with no cost attached, because the reviewer knows there was one.

Lead with the right evidence for your role family

Engineering: the systems you owned under time pressure. Order orchestration, real-time inventory, rider allocation, routing and live tracking are the interesting surfaces. State the traffic at peak, the latency you held, and what you did when it broke. Demand here is spiky by hour and by weather, so a resume that shows load handling and graceful degradation reads well.

Data science and analytics: demand forecasting at store and item level, assortment selection, wastage against stockout tradeoffs, delivery-time prediction, and rider supply planning. Say the baseline you beat and by how much, because forecasting claims without a baseline mean nothing.

Product: the customer promise is time, so the metrics are availability, delivery reliability and order completion. Name the experiment, the metric and the decision.

Supply chain and category: fill rate, inventory accuracy, shrinkage and wastage, replenishment cycles, supplier lead times and assortment decisions per store format.

City and store operations: this is a large share of the hiring and is often overlooked by candidates. Picking time per order, orders per rider hour, store throughput at peak, staffing plans, and how you handled a bad day are the evidence. Operations experience from retail, quick-service restaurants or logistics transfers directly, so do not bury it under a generic summary.

Use quick-commerce metrics

Native vocabulary: fill rate, in-stock percentage, inventory accuracy, forecast error such as MAPE or WAPE, wastage percentage, picking time per order, orders per rider hour, on-time delivery percentage, average delivery time, cancellation rate, and cost per order.

Weak: "Worked on inventory systems." Stronger: "Owned the real-time inventory service across 90 dark stores; cut oversell incidents by 71% by moving from a nightly sync to event-driven updates with a reconciliation job."

Weak: "Improved forecasting." Stronger: "Rebuilt the item-level daily forecast for 40 stores; WAPE fell from 38% to 24% against the moving-average baseline, which cut wastage 1.8 points at the same in-stock rate."

If you do not have the figure, describe the scale honestly. The number of stores, SKUs, riders or orders you worked across is real evidence and does not require you to invent an outcome.

If you are a fresher

Build something with a time or capacity constraint in it. A delivery-slot or routing optimiser over real map data, an item-level demand forecast with a baseline you actually beat, an inventory reconciliation tool that detects drift between two systems, or a dashboard that tracks on-time performance by hour all read as relevant. A storefront clone does not.

For each project, state the problem, the stack, the data size, the metric and the outcome, and link the repository. Two explained properly beat six listed.

Operations roles hire freshers directly and value different things: shift work you have done, teams you have coordinated, languages you speak, and any experience where you were accountable for a daily number. Put those on the page rather than assuming they do not count.

Check your match score before you apply

Upload your resume to ReachRole and check the match score against the specific posting, not against the company in general. Fix the missing keywords and weak bullets it flags before you submit.