Delhivery is India's largest integrated logistics company, moving hundreds of millions of parcels a year through a nationwide network of sortation centres, warehouses, and last-mile hubs. Now publicly listed and headquartered in Gurugram, Delhivery builds the routing, tracking, warehouse-management, and network-optimisation systems that let e-commerce work at national scale. For software engineers who want to work on hard logistics, routing, and operations-research problems rather than consumer apps, Delhivery offers deep supply-chain engineering. This guide covers the interview process, what Delhivery looks for, and how to prepare.
The Delhivery hiring process: what to expect
The Delhivery software-engineering interview process typically runs across 3–4 rounds:
1. Online assessment or resume screen: Most pipelines start with an online coding assessment (data structures and algorithms) or a resume screen for experienced candidates. The bar is solid CS fundamentals and clean code.
2. Technical round 1, DSA and coding (45–60 min): A live coding interview focused on data structures and algorithms: arrays, strings, hashmaps, two pointers, sliding window, trees, graphs (especially shortest-path and routing problems), heaps, greedy, and dynamic programming. Be ready to state time and space complexity.
3. Technical round 2, backend and low-level design (60–90 min): A deeper engineering interview. Topics: REST API design, object-oriented and low-level design, database schema design (SQL, indexing, transactions), concurrency, caching, and queues. You may be asked to design the data model and classes for a shipment-tracking system, a sortation-centre workflow, or a warehouse-management feature.
4. Logistics / high-level design round (mid and senior): A scalable-systems interview grounded in logistics. Examples: design a nationwide shipment-tracking system, design a route-optimisation and network-planning engine, or design a warehouse-management and inventory system. Focus on scale, real-time tracking, and optimisation under operational constraints.
5. Hiring-manager and culture round: A conversation with the engineering manager or leadership. Topics: your past projects and the impact you owned, how you reason about scale and trade-offs, why Delhivery and logistics, and how you handle operational pressure. Delhivery values engineers who can build reliable systems for a physical, operations-heavy business.
What Delhivery interviewers look for
Based on what is known about Delhivery's engineering culture, these qualities tend to stand out:
1. Strong algorithms and optimisation thinking: Logistics is full of routing, scheduling, and optimisation problems, so interviewers reward candidates with strong graph and algorithms skills who can reason about shortest paths, assignment, and optimisation under constraints.
2. Practical backend and systems depth: Delhivery runs tracking, sortation, and warehouse systems under heavy real-world load, so applied backend skills (API design, data modelling, caching, consistency, and queues) carry real weight. Interviewers look for clear reasoning about scale and reliability.
3. Domain awareness for logistics and supply chain: Logistics has distinct problems: shipment tracking, network and route optimisation, sortation, warehouse management, and last-mile delivery. Showing that you appreciate this operational complexity differentiates you from candidates who only think about generic web apps.
4. Ownership and reliability: Delhivery values engineers who take end-to-end ownership and build reliable systems for a business where software failures have physical consequences. Being able to talk concretely about a system you owned and its outcome is a strong signal.
How to prepare for a Delhivery interview
Targeted preparation for Delhivery software-engineering roles:
1. Sharpen data structures and algorithms: Practise arrays, strings, hashmaps, trees, graphs (BFS/DFS and shortest-path for routing), heaps, greedy, and dynamic programming. Do timed LeetCode-medium problems, always state time and space complexity, and practise writing correct, edge-case-handled code.
2. Study backend and low-level design: Be fluent in REST API design, object-oriented design, and database design (indexing, transactions, SQL). Practise low-level design problems: a shipment-tracking system, a sortation-centre workflow, or a warehouse-management service, including the classes, interfaces, and data model.
3. Prepare logistics and routing system design (mid/senior): Study scalable-system building blocks: caching, message queues, sharding and replication, consistency models, and idempotency. Practise logistics systems specifically: nationwide shipment tracking, route optimisation and network planning, and warehouse management.
4. Learn the logistics and supply-chain domain: Read about how integrated logistics works: first-mile pickup, sortation, line-haul, last-mile delivery, route optimisation, and network planning. Being able to reason about these flows and their optimisation problems in a design round is a clear advantage.
5. Prepare your projects and 'why Delhivery' story: Be ready to walk through one or two projects in depth: the problem, your design decisions, trade-offs, and the outcome. Have a genuine answer for why Delhivery and logistics: the national scale, the optimisation challenges, and the impact of software on a physical operations business.
Frequently asked questions
Explore more