Interview experience
Stories
Delhivery HR Interview Questions and Answers
New to HR rounds? The basics that apply at every company - answer frameworks for the standard questions, a story bank, and the usual red flags - are in HR round basics. This page covers what is specific to Delhivery.
Overview
What this company’s HR round focuses on
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.
Common Delhivery HR questions
1. Tell me about yourself
Framework: Present → Past → Future (60–90 seconds). End with why you are interviewing for this Delhivery logistics-tech role today.
Sample answer (adapt): “I am a final-year CSE student at [college] with a focus on backend systems. Recently I built [project] that processed [volume/event count] using [stack], where the hardest part was [one concrete bug or trade-off]. Before that, my internship at [place] taught me to ship under SLA pressure. I am interviewing for Delhivery SDE because your network runs high-write tracking and routing problems - the same constraints I enjoyed solving in [project], and I want that at national logistics scale.”
Follow-ups to expect: “Walk me deeper into the project” (keep numbers consistent with technical rounds); “What would you improve if you rebuilt it?”
2. Why Delhivery?
Framework: Company fact → your skill match → what you will learn next - in that order.
Sample answer: “Delhivery is not a generic IT services shop - it builds software for hubs, line-haul, and last-mile at scale. I follow how you combine operations data with engineering (route optimization, warehouse systems, tracking). My strength is [DSA/SQL/backend], and I want to apply it where downtime or bad data affects real shipments, not just a dashboard metric. I am specifically interested in [Gurugram/Bengaluru/Hyderabad] engineering teams working on [fulfilment/routing/platform - pick one you researched].”
Avoid: “Fastest-growing unicorn” without a product detail; comparing only CTC to Flipkart/Amazon.
3. Why should we hire you?
Framework: Three proofs in under 90 seconds - technical depth, persistence, collaboration.
Sample STAR: “First, in my [project] I cut API latency from ~800ms to ~220ms by adding indexes and caching hot AWB lookups - I can show the before/after logs. Second, when our campus app broke during fest week, I owned the on-call fix across two nights until payments worked again. Third, in a hackathon team of four, I mediated a disagreement on Mongo vs Postgres by prototyping both for our read pattern - we shipped on time. That mix of optimization, ownership, and pragmatism is what I would bring to Delhivery’s engineering culture.”
4. Strengths and weaknesses
Strength (with evidence): “I am strong at translating vague ops problems into schemas and APIs - for example, I modeled shipment states as an append-only event log instead of overwriting rows, which made audits easier.”
Weakness (real + fix): “I sometimes jump to code before agreeing on edge cases. I now write a three-bullet contract - inputs, failures, success metrics - and share it in the channel before opening the IDE. My last two PRs had fewer review cycles after I started doing that.”
5. Where do you see yourself in 5 years?
Sample direction: “I want to grow as an engineer who owns a logistics domain service end to end - design, on-call, and cost trade-offs - not jump to manager in year two. Delhivery’s scale is a good place to learn write-heavy, geo-distributed systems. In five years I see myself as a senior IC who can mentor juniors on DSA plus production debugging.”
6. Tell me about a conflict in a team
Sample STAR: “Situation: Two teammates wanted different deployment strategies - big-bang release vs feature flags - three days before demo. Task: I was not team lead but owned the backend. Action: I listed failure modes for each approach on a shared doc, ran a 30-minute risk review, and proposed flags for payment flows only. Result: We demoed safely; full rollout happened the next week with zero payment regressions. I learned to make disagreements about data, not personalities.”
7. Are you willing to relocate / work shifts?
Framework: Answer honestly first; then constraints; then flexibility you do have.
Sample: “Yes - I am open to Gurugram or Bengaluru for the SDE role. My family is based in [city], so occasional travel home is fine; I do not need daily WFH. I understand logistics platforms can have incident load during sale peaks - I am willing to join rotation once I understand the team’s on-call norms.”
Campus reports also mention relocation, joining date, and notice period - decide those numbers before the call.
8. Explain a gap / low score / job hop
Sample: “I had a semester gap in 2022 for a medical issue in the family - one sentence, not a long story. During that time I completed [online course/project] and returned with a 8.x CGPA in the next two semesters. My projects since then are on my resume and I can walk through any of them.”
9. What do you know about Delhivery?
Prepare three facts: business (express parcel, B2B fulfilment, part-truckload - pick what matches the role), engineering (high-volume tracking, routing, warehouse systems; stacks often Java/Python/Go in candidate reports), recent public signal (earnings, hub expansion, tech blog - one verifiable detail).
Compensation context (candidate-reported): fresher bands often cited around ₹10–20 LPA depending on role and location - confirm base, variable, and ESOP in the offer letter, not HR small talk.
10. Do you have any questions for us?
Strong examples: “What does success look like in the first 90 days for this SDE team?” “How do you balance feature speed with on-call stability during peak season?” “What is the mentoring path for new grads?” Weak opener: “What is the CTC?” as question one.
11. Describe a challenging situation / tight deadline
Sample STAR: “Situation: OA plus two technical rounds were scheduled within five days while I was finishing exams. Task: Stay sharp for a long Codepair DSA round. Action: I timed three medium problems daily, kept a one-page SQL sheet, and slept on a fixed schedule. Result: I cleared the OA and completed five DSA problems in Round 1 - the prep plan mattered more than cramming new patterns the night before.”
12. How do you handle pressure or team disputes?
Tie to logistics: peak-season incidents, conflicting priorities between ops and engineering. Use the conflict STAR above or a shorter variant focused on listening first, then proposing a measurable experiment.
How Delhivery HR scores answers
| Signal | Strong | Weak |
|---|---|---|
| Why Delhivery | Network scale, routing, warehouses | Generic startup list answer |
| Ownership | Ops-impact metric from a project | Pure LeetCode identity |
| Ambiguity | Comfort deciding with partial data | Freezes without perfect specs |
| Location | Hub flexibility | Soft no after technical |
Extra STAR: optimisation under constraints
Prompt: “Tell me about improving a process with limited resources.” Sample STAR: “Situation: Club inventory of fest merchandise was counted manually and wrong. Task: Reduce stock-out. Action: I built a simple scan sheet, batched recounts, and flagged low SKUs daily. Result: Stock-outs dropped during the fest weekend.” Logistics cultures score constraint-aware impact.