Interview experience
Delhivery Interview Questions
Overview
Section titled “Overview”Delhivery’s loop is short (often under a week) but technically dense - a long, multi-problem DSA marathon followed by a design-and-behavioural round that leans on Delhivery’s own logistics-scale problems rather than generic prompts.
Delhivery interview process at a glance
Section titled “Delhivery interview process at a glance”| Round | Duration | What it tests |
|---|---|---|
| Online Assessment (HackerEarth) | 60-90 min | CS fundamentals MCQs + 3 medium coding problems |
| Technical Interview 1 | 60-120+ min | Long DSA session (multiple problems) + project deep-dive |
| Technical Interview 2 | 45-60 min | Low-level design, SQL, behavioural, sometimes a puzzle |
| HR Discussion | 20-30 min | Fit, offer discussion |
Online Assessment
Section titled “Online Assessment”Hosted on HackerEarth: MCQs spanning computer networks, OOP, DBMS, SQL, operating systems, and system security, combined with 3 coding problems at medium difficulty, often on trees and linked lists.
Common questions
- MCQs on TCP/IP basics, normalization, OOP pillars, and process scheduling
- Tree and linked-list manipulation problems
- SQL query MCQs (joins, aggregations)
- Basic system-security conceptual questions
Technical Interview 1
Section titled “Technical Interview 1”A genuinely long DSA round - one candidate account on GeeksforGeeks describes a 2+ hour Codepair session with 5 problems and thorough edge-case probing - paired with a detailed project discussion.
Common questions
- Find pairs in an array that sum to a given target
- Design a stack that supports push, pop, top, and retrieving the minimum in O(1)
- Tree/linked-list problems with follow-up edge-case questions
- Detailed walkthrough of a resume project - architecture, hardest bug, trade-offs
Round-by-round narratives are on the Delhivery interview experience page.
Technical Interview 2
Section titled “Technical Interview 2”Shifts to low-level design and SQL, sometimes run same-day as Round 1. Design prompts commonly borrow from Delhivery’s own logistics domain rather than staying purely abstract.
Common questions
- Design a URL-shortening service - schema and scaling approach
- Design a database for warehouses - entities, relationships, query patterns
- Explain the CAP theorem with a distributed-database scenario
- Write a SQL query to find the Nth highest salary/value in a table
- Which design pattern (Singleton, Factory, Builder, Abstract Factory) fits a given scenario, and why
HR Discussion
Section titled “HR Discussion”A closing conversation on motivation, logistics-domain interest, and offer details.
Common questions
- Tell me about yourself and why Delhivery
- How would you design a system to track a shipment across thousands of hubs in near real time
- Tell me about a time you optimized a slow SQL query or a process end to end
- Are you comfortable with the operational, high-volume nature of logistics tech
Sample answer frameworks for each of these are on the Delhivery HR interview questions page.
Why Delhivery’s design questions feel different
Section titled “Why Delhivery’s design questions feel different”Because Delhivery runs a physical logistics network at national scale - warehouses, hubs, and delivery partners generating constant high-volume writes - its low-level and system-design questions are usually anchored to that reality: a warehouse database schema, a shipment-tracking system, or a URL-shortener-style service used internally for tracking links. Candidates who can reason about write-heavy, geographically distributed data (not just a textbook CRUD app) tend to stand out more than those who only rehearse generic LLD templates.
Frequently asked questions about Delhivery interviews
Section titled “Frequently asked questions about Delhivery interviews”What is Delhivery’s interview process for freshers?
Delhivery’s process typically runs 3-4 rounds: 1. Online Assessment (on HackerEarth) - MCQs on computer networks, OOP, DBMS, SQL, operating systems, and 3 medium-difficulty coding problems. 2. Technical Interview 1 - a long DSA session (candidates report 5+ problems solved live on a shared coding pad) plus project deep-dive. 3. Technical Interview 2 - low-level design, SQL, and behavioural/puzzle questions, sometimes same-day as Round 1. 4. HR discussion - fit and offer. The full loop can move fast, sometimes wrapping within about a week.
What does Delhivery’s online assessment cover?
It’s hosted on HackerEarth and combines MCQs (computer networks, OOP, DBMS, SQL queries, operating systems, system security) with 3 coding problems of medium difficulty covering data structures like trees and linked lists.
How many technical rounds does Delhivery have?
Most candidates go through 2 technical interviews after the OA, followed by an HR discussion - so 3-4 rounds total. Given Delhivery is a logistics-technology company, expect at least one round to touch practical, scale-oriented problems (like designing a warehouse database or a URL-shortener-style service) rather than pure textbook DSA.
How should I prepare for Delhivery interviews?
Practice medium-level coding problems (trees, linked lists, arrays, and a stack-with-getMin-in-O(1) style question), revise SQL and be ready to write queries live (e.g., finding the Nth highest salary), brush up on OOP/DBMS/OS/networking basics, and practice low-level design fundamentals - design patterns (Singleton, Factory, Builder), CAP theorem, and a warehouse or shipment-tracking data model - since Delhivery’s business is logistics at high volume.
Is Delhivery’s technical round long?
Candidate reports describe the DSA round as unusually long and marathon-like - one GeeksforGeeks account describes a 2+ hour Codepair session with multiple problems and full edge-case discussion, followed by a same-day second round covering low-level design, behavioural questions, and a puzzle. Pace yourself and don’t rush the first problem expecting a short round.
Does Delhivery ask logistics-domain system design questions?
Yes. Beyond generic LLD, interviewers frame design questions around Delhivery’s actual domain - a database design for warehouses, a URL-shortening-style service, or a system for tracking shipments across hubs at scale. Being able to reason about high-write-volume, geographically distributed data (not just a textbook CRUD app) is a real differentiator here.