~30 min: background, current company, project challenges and current work
Then 5 DSA problems one-by-one; any language; full edge-case solutions required
Pattern described: easy string (~10 min) → medium array + hard DP follow-up → medium tree + medium-hard follow-up
Exact prompts withheld by candidate (NDA); practise stamina and follow-ups
Closed with questions on role / tech stack
Result: Positive same-day → Round 2 scheduled
Round 2 - Technical + Behavioural (same day)
Senior engineer: LLD questions → one module became an algorithmic optimisation
Amazon-style situational / behavioural prompts
A puzzle (tough initially, then cracked)
Interviewer explained Delhivery domain work
Round 3 - HR
Formal offer discussion after a few days
Final result: Selected
Named DSA from another SDE-I select
Round 1: Min Stack; Linked List Cycle II
Round 2: project discussion + Number of Islands variant
Advice: map to known problems; ask for hints
Key takeaways: Lateral Delhivery is a DSA endurance test. Discuss approach before coding; never skip edge cases.
Takeaways
What decided it: Completing ~5 Codepair DSA problems with edge cases, then LLD-plus-behavioural and a puzzle in the same-day second round
Common fail: Correct medium solutions that break on follow-up DP/tree constraints, or rushing without discussing approach first
How to practise: 2-hour multi-problem sessions (string → array+DP → tree+follow-up); Min Stack, Cycle II, Islands variants; one Amazon-style STAR story
Managerial / LLD: experience deep-dive, LLD, DB architecture
Offer discussion after clears
Key takeaways: Lateral hiring may stack HLD/LLD + SQL after DSA; stamina across multiple backend dimensions matters.
HR interview experience
HR interview experience
Often a formal offer / role discussion after technical clears. Behavioural grilling may already have happened in Tech-2 (conflict, ownership). Campus HR reports (e.g., Medium on-campus 2025) describe light conversation on journey, relocation, career goals, and family background - still prepare “Why Delhivery?” with specifics. Gurugram hubs frequently cited.
Typical HR prompts
Why Delhivery vs other logistics/product companies
Relocation, joining date, notice period
Overall interview experience reflection
Salary components - clarify base vs variable in the offer letter, not informal chat
Sample answers for high-frequency questions
Q. Min Stack - O(1) getMin? A. Dual stack (or pairs): main values + parallel mins. On push, push min(x, currentMin) onto min-stack; pop both. getMin peeks min-stack.
Q. Linked List Cycle II? A. Floyd: slow/fast meet → reset one to head, same speed → meeting point is cycle start. Prove with pointer math if asked.
Q. Number of Islands variant approach? A. DFS/BFS flood-fill or Union-Find on grid; mark visited. Clarify 4- vs 8-connectivity and follow-up constraints early.
Q. unordered_map vs map for frequencies? A. Average O(1) vs O(log n) per op; unordered loses order and can worst-case degrade. For character counts, unordered_map (or array[256]/[26]) is enough.
Q. Hour and minute hands overlap between 2 and 3? A. Hands overlap every 65.45… minutes; between 2 and 3 at 2:10:54 approx (formula: m = (30H)/5.5). State the formula and compute calmly.
Dense prep checklist
Stamina: multi-problem Codepair with follow-ups
Classics: Min Stack, cycle detection, islands, max subarray, frequency maps
SQL joins; OS/DBMS MCQs for campus OA
If React on resume: Babel, virtual DOM, hooks, promises
These links are research inputs used to map Delhivery OA, Codepair stamina rounds, and LLD panels - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Confirm campus vs referral path against your invite before choosing prep emphasis.
