Academic snapshot
Marks: 6.5+ CGPA / 65% (candidate-reported)
Degree: B.E. / B.Tech / M.Tech / MCA
Backlogs: None active preferred
Year: Final-year and recent grads
Delhivery Placement Papers 2026
Delhivery is one of India’s largest logistics and supply chain technology companies, helping businesses move goods across the country through a nationwide delivery network. Founded in 2011, it hires engineers in Gurugram, Bengaluru, and other cities to build routing, warehouse, and last-mile delivery systems.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Delhivery eligibility & CGPA (2026)
Who this hub is for
- For: Students targeting SDE / logistics-tech roles at Delhivery - routing, optimization, and systems behind a large parcel network. Hubs candidates report: Gurugram, Bengaluru, Hyderabad.
- Not the same track: Pure operations / field / hub-supervisor roles. Those hiring bars do not map to a Codepair DSA marathon.
- Experienced / SDE-1 lateral: Public write-ups describe 2h+ Codepair with many DSA problems, then LLD + behavioural + puzzle the same day. Use fresher OA sections as a base, then add stamina and LLD.
On-campus vs off-campus vs lateral
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT, college CGPA list when printed | Coding bar |
| Careers portal / referral | Resume screen volume; sometimes no hard published CGPA | Still expect DSA |
| SDE-1 lateral (GFG-style) | Short screen, then marathon interviews; OA may be skipped | Edge-complete code + LLD |
| Intern → full-time | Conversion may skip a stage | You still defend projects |
Off-campus does not mean easier graphs. It often means more applicants and a longer Codepair. If your CGPA sits near 6.5, spend energy on mocks, not on hunting a mythical 6.0 cutoff.
Ops+tech culture in one sentence: interviewers like people who can code and respect that a missed scan at 2 a.m. is a real customer. You do not need warehouse experience. You do need to stop saying “just a delivery app” and start saying hubs, capacity, SLA clocks. That vocabulary is free and shows up after the first DSA problem.
Degree, projects, and “is 6.5 enough?”
Is 6.5 CGPA enough? It matches the commonly reported floor. Selection still hinges on DSA correctness and how you talk about routing. A 6.6 with clean timed coding beats an 8.5 that freezes on a BFS variant.
Branches: CS/IT/ECE dominate tech shortlists. Adjacent branches show up when DSA is solid. If the JD says “software,” do not assume every core branch is auto-included.
Gaps and backlogs: Active backlogs are the usual blocker. A gap is easier to explain with a skills story than silence.
What helps the resume screen: One project you can defend (stack, hardest bug, metric), any internship with ownership language, and honest keywords (Go if you actually use it). Certificates are optional. See certifications after fundamentals.
Branch & skills
Preferred: CS / IT / ECE and related
Languages: Java, Python, Go
Focus: DSA, optimization, systems
Differentiator: Routing, capacity, ops+tech culture
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.5+ CGPA / ~65% | Campus cells may pre-filter; off-campus is more OA-driven |
| Degree | B.E. / B.Tech / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE (and related) | Strong DSA helps adjacent branches on some drives |
| Year | Final year + recent grads | Drive-dependent |
| Backlogs | No active backlogs preferred | Clear them before paperwork |
| Coding languages | Java, Python, Go | Stick to one you can debug live |
| CGPA range (graduation) | On-campus feel | Notes |
|---|---|---|
| Below 6.5 | Low unless the JD is silent | Off-campus + exceptional DSA still possible |
| 6.5-6.9 | Eligible on many drives | Skills must carry |
| 7.0-7.5 | Common shortlisted band | With solid projects |
| Above 7.5 | Strong academically | Still must clear DSA |
Delhivery CGPA criteria
Minimum CGPA required (candidate-reported): 6.5+ CGPA / 65% is the commonly cited floor. Treat it as a shortlisting filter when printed. Clearing CGPA only gets you into the funnel - DSA and (on some loops) LLD decide the rest.
Delhivery does not publish one universal cutoff. Your placement cell mailer always wins.
Delhivery placement papers - last few years
Download 2026 Delhivery placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
How these packs train DSA and assignment stamina
Delhivery does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Campus OA | Timed DSA (and MCQ when present) |
| Codepair technical | Multiple problems, full edge cases, 2h+ stamina |
| LLD | Parcel scan, route assignment, capacity at fresher depth |
| Puzzle + behavioural | Think-aloud + ownership STAR |
| HR | Why logistics tech?, relocation, joining |
Themes that keep repeating (2024-2026)
- 2024 cycles: Campus-style sets still mix aptitude/MCQ with coding. Graph / heap / greedy themes appear because they map to routing and ranking. Students who only did one medium a day without a timer lost OA sitters.
- 2025 loops: Public SDE-1 colour is interview-marathon: projects, then five DSA on Codepair, then same-day LLD + behavioural + puzzle, with the interviewer explaining logistics domain context. Campus fresher drives may still add a classic OA - confirm.
- 2026 prep expectation: Keep medium DSA and one routing sketch warm. If your invite is Codepair, practise two-hour multi-problem sessions, not only 20-minute singles. Treat PDF packs as pattern catalogs: Own heap/bucket, then invent a “busiest hubs” cousin.
How to use one paper set in a single sitting
- Timed: one OA-length mock or a 90-120 minute multi-problem Codepair sim.
- Untimed review: rewrite cleaner solutions; list three edge cases (empty route, single hub, capacity 0).
- Map each miss to a theme (graph / heap / greedy / DP) and pull two cousins from coding questions.
- Spend 15 minutes explaining route assignment or scan-to-hub out loud.
- Log one STAR story and one puzzle you would think aloud.
Related problems to practice
| Theme you saw in a set | What to drill next | Why Delhivery asks it |
|---|---|---|
| Top-K frequent | Heap + bucket | Busiest hubs, alert priority |
| Shortest path / BFS | Grid, weighted Dijkstra lite | Routing intuition |
| Coin change / DP | Unbounded knapsack | Capacity / cost trade-offs |
| Linked list cycle | Fast-slow pointers | Classic Codepair warmup |
| Level-order tree | BFS queue | Hierarchy of hubs / zones |
| Move zeros / rotate | Two pointers, reverse | Implementation speed |
| Greedy interval / jobs | Sort + pick | Vehicle slots, SLAs |
2025 PDFs often drill “Top-K frequent.” Use the heap of size k template, then a related drill: top-k delayed shipments. Memorising the array in the PDF does not transfer.
Delhivery placement process, round by round
Delhivery hires freshers through campus cells, the careers portal, and referrals. After resume screen, campus often looks like OA → technical → HR. Lateral SDE-1 can look like a same-day marathon.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on delhivery.com careers for early-career / fresher tech roles; follow the invite.
Referrals
Employee referrals improve visibility. You still need passing code and clear interviews.
1. Resume / eligibility screen
Degree, CGPA floor when printed (6.5+ / 65% commonly reported), backlogs, year of passing. Projects help. This is a gate - DSA is the filter.
2. Online Assessment
Campus notes describe a timed coding and/or MCQ filter. Section-level splits are not locked in public SDE-1 posts - follow the email.
| Component (working map) | What to expect | Prep move |
|---|---|---|
| Coding | 1-3 DSA problems | Graphs, heaps, greedy, implementation |
| MCQ / aptitude | When present | Timed mock quiz |
| Languages | Java, Python, Go | Confirm runtime on invite |
| Platform | Drive-specific | Do a dry login if they send a link |
Pass bar: Fully passing solutions beat a clever half-answer. There is no single public percentage cutoff.
Student tip: Skim all prompts. Bank the solvable one. Invent two edge cases (empty graph, one node) before submit.
Campus OA vs Codepair - do not mix clocks. A 60-90 minute campus OA usually wants one or two fully passing solutions. A 2h+ Codepair wants several problems with boringly complete edges (null graph, one node, disconnected hub, capacity 0, duplicate scans). If you practise only 20-minute LeetCode mediums, the marathon feels like a different sport. If you only practise marathons, you may over-engineer a short OA and miss an easy implementation.
Deeper OA notes: Delhivery Online Assessment.
3. Technical - DSA / systems (~45-60 min campus; 2h+ codepair on some SDE-1)
Campus: 1-2 problems + project. SDE-1 GFG colour: projects first, then multiple DSA on Codepair with full edge cases.
You should:
- Clarify constraints (graph size, capacity, directed vs undirected)
- Narrate brute force → bottleneck → target complexity
- Code without syntax stalls
- Walk edge cases - this company cares
Example narration (nearest hub / BFS): “Unweighted hops → BFS from the parcel’s current node. I’ll store parent to reconstruct the path. If some hubs are closed, treat them as blocked cells.” Empty graph returns empty; a single hub is a trivial path.” That 40-second plan already signals readiness.
4. LLD + behavioural + puzzle
Same-day second round in the SDE-1 post: LLD + behavioural + puzzle, with logistics context explained by the interviewer.
Worked mini-outline - assign a rider to a pickup:
- Actors: shipment, hub, rider, assignment service.
- Happy path: scan → eligible riders in radius → score (ETA, capacity) → assign → notify.
- Failure: all riders full → queue + SLA timer; do not silently drop.
- Freshers: a class diagram + one bottleneck beats a 12-microservice slide.
Second mini-outline - inbound scan at a hub: parcel barcode → idempotent scan event (same barcode twice should not create two bags) → sort destination hub → bag/container capacity. Bottleneck is usually hot sort lanes at peak, not “we need Kafka.” Say you would queue overflow and raise an SLA clock. If they ask data, a scans(parcel_id, hub_id, ts, type) table plus a unique on (parcel_id, hub_id, type) is enough for fresher LLD.
Graph prompt cousin: “shortest path” in interviews is often unweighted BFS between hubs, then a follow-up: some roads closed (blocked nodes), then “what if travel times differ?” (you mention Dijkstra without implementing a textbook dump unless they want code). That ladder shows up more than random tree DP.
Puzzles: think aloud, state assumptions, check a small example. They are watching process, not a magic answer.
Puzzle habit (5 minutes): restate, pick a tiny example, say what you would brute-force, then tighten. If stuck, say what extra data you would ask for (map, capacities, time windows). That is the same muscle as a routing LLD - interviewers in the GFG SDE-1 loop explicitly framed logistics context while you solved.
5. HR (~20-30 min) - or merged into the later round
Why Delhivery (ops+tech, not “I like delivery apps”), relocation to Gurugram / Bengaluru / Hyderabad, joining vs exams. Know the ₹10-20 LPA fresher band.
| # | Round | Notes |
|---|---|---|
| 1 | OA (if present) | Timed DSA / MCQ |
| 2 | Technical | Campus 45-60 min or 2h+ Codepair |
| 3 | LLD / puzzle / HR | Sometimes combined same day |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Resume screening | 3-10 days | Campus / portal |
| Online assessment | 1 day (if present) | Follow invite |
| Interview scheduling | 2-7 days | |
| Technical / LLD | 1-2 weeks or same day | Lateral marathon colour |
| HR / offer | 1-5 days after final | Written offer wins |
| End to end | Often 2-6 weeks campus | Off-campus can stretch |
OA / interview cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| OA coding | Timed correctness | Two mediums back-to-back |
| Codepair stamina | 5 problems, edges | One 2-hour sim |
| LLD | Scan / assign / capacity | One 15-min sketch |
| Puzzle | Think-aloud | One puzzle with a friend |
| HR | Why logistics tech | Two STAR + relocation |
Delhivery aptitude, coding & interview practice
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How students actually prep for Delhivery
If a Delhivery invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Delhivery sits around ₹10-20 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Delhivery eligibility for freshers 2026 is candidate-reported. Common baseline: 6.5+ CGPA / 65%; B.E./B.Tech/M.Tech/MCA or as per notification; final-year students and recent graduates; no active backlogs preferred; skills in DSA, optimization, and systems. Always verify the official careers page or campus JD.
What you are training for: Campus fresher loops commonly run: Online Assessment (when present) → Technical (DSA / systems) → HR. Some SDE-1 write-ups skip a classic campus OA and describe a long Codepair technical (projects + multiple DSA) then a same-day LLD + behavioural + puzzle round. Timeline is often 2-6 weeks for campus batches.
Short version of the prep split: Treat Delhivery like logistics product hiring, not a courier-shop aptitude test. Split time roughly: 55% DSA (graphs, heaps, greedy, DP), 20% optimization/LLD (routing, capacity, puzzles), 15% CS + projects, 10% behavioral. Clear timed OA or Codepair stamina first. Languages: Java, Python, Go.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Delhivery previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Delhivery drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Delhivery usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Delhivery?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Delhivery-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Delhivery story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Delhivery PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Delhivery papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Delhivery papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Delhivery-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Delhivery paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Delhivery. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Delhivery, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Delhivery mistakes, you are collecting content, not preparing.
What Delhivery pays freshers (candidate-reported)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, location, and written components.
Bands students ask about
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Fresher / early-career SDE | ₹10-20 LPA | Primary band for this hub |
| SDE-1 lateral | Overlaps / higher | Experience and loop differ |
| Senior+ | Wide spread | Outside fresher default |
Confirm base, bonus, and any equity on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Policies vary by team and year. Candidates commonly care about:
- Health insurance and wellness
- Learning / certification support after joining
- Hybrid or office norms in Gurugram, Bengaluru, Hyderabad
- Relocation - ask HR, do not assume
How to talk CTC in HR without sounding lost
Know the ₹10-20 LPA fresher context, ask how the package splits, and clarify joining vs exams and city. One calm question beats aggressive negotiation with no market anchor.
Lateral vs campus letters: an SDE-1 Codepair loop is not automatically a higher band than campus fresher, and campus is not automatically the floor of ₹10 LPA. Ask base vs variable, joining bonus, and which city (Gurugram vs Bengaluru vs Hyderabad) is on the PDF. Do not negotiate from a Swiggy screenshot.
If the letter is internship-to-FTE: ask conversion criteria and stipend vs CTC in one sentence. The GFG SDE-1 post is a lateral colour story - useful for round shape, not for copying someone else’s package.
Delhivery hiring updates for 2026
- Ops+tech story is still the differentiator - routing/optimization vocabulary helps after you clear DSA.
- Campus OA remains common for volume; SDE-1 laterals may skip to Codepair marathons.
- Go stays more welcome than at many campus companies - only list it if you can debug it.
- LLD + puzzle same-day rounds appear in detailed public posts.
- Treat ₹10-20 LPA as a reported band, not a promise for every role.
- Timelines of 2-6 weeks are common for campus batches; same-day loops exist for some laterals.
- Public write-ups remain thinner than FAANG - lean on the GFG SDE-1 Codepair post plus campus mailers, not on a fake “official 40-question paper.”
- Optimization flavour (routing, capacity, greedy) is the prep differentiator vs a generic service-company OA. Keep it after DSA correctness, not instead of it.
FAQs students ask about Delhivery placements
Process & papers
What is the Delhivery placement process for freshers?
Typical campus path: OA (when present) → Technical → HR. Some SDE-1 loops: long Codepair DSA then same-day LLD + behavioural + puzzle. Campus batches often finish in about 2-6 weeks. Confirm on your invite.
How many interview rounds does Delhivery usually have?
Most campus fresher notes report about three major stages. Lateral posts describe a marathon technical plus a mixed second round. Count the mailer.
Can I download Delhivery placement papers PDF for free?
Yes. Free Delhivery placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. Start with the 2026 PDF or the paper archive.
What does the Delhivery OA look like?
Campus: timed DSA and/or MCQ - follow the email. A detailed SDE-1 post skipped a classic OA. No single public percentage cutoff. Languages: Java, Python, Go.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly reported floor: 6.5+ CGPA / 65%, relevant degree, no active backlogs preferred. Your drive notice overrides this page.
What is Delhivery fresher salary in India?
Candidate-reported CTC often lands around ₹10-20 LPA (as of August 2026), with Gurugram, Bengaluru, and Hyderabad as common cities. The written offer is the only number that matters.
Do I have to relocate?
Gurugram is HQ; Bengaluru and Hyderabad also appear. HR usually checks relocation. Be honest early.
Prep & Delhivery-specific
How should I prepare for Delhivery?
Split time roughly 55% DSA, 20% optimization/LLD, 15% CS/projects, 10% behavioral. Clear timed OA or Codepair stamina first. Details: preparation guide.
Which programming languages are allowed?
Java, Python, and Go are the usual set. Confirm on the invite. Do not list Go unless you can debug it live.
Does Delhivery ask LLD and puzzles?
Yes in some SDE-1 loops (same-day mixed round). Campus HR may be lighter - still prep one scan/assign sketch and one think-aloud puzzle.
Is Delhivery only for operations roles?
No. This hub is tech hiring - routing, optimization, systems. Ops/field tracks are separate. Expect real coding interviews.
How is Delhivery different from Swiggy or Blinkit for freshers?
All three care about DSA and real-world assignment problems. Delhivery’s flavour is parcel network / hub routing and a visible Go option, with Gurugram as HQ. Swiggy/Blinkit lean food/quick-commerce. Prep DSA once; customise routing stories.
What certifications help before joining?
For campus SDE, DSA + timed mocks + one strong project beat certificate stacks. See certifications.
Any pro tip that actually changes outcomes?
Practise multi-problem Codepair stamina with full edge cases. Rehearse one routing/capacity explanation. Correctness beats a half-finished clever graph.
Where can I read real interview experiences?
Start with Delhivery interview experience on this site, then the GFG SDE-1 Codepair write-up. Patterns shift - use them as maps, not scripts.
Real Delhivery interview notes from candidates
Campus fresher colour (2024-2025)
Profile patterns that got selected: B.Tech CSE/IT/ECE, often above 6.5, one internship or a strong project, steady DSA rather than last-week panic.
OA (when present): Timed coding. Clean, fully passing solutions beat partial cleverness. Shortlist mail timing varies by batch.
Technical: Graphs/BFS, heaps, greedy, implementation. Domain chat around routing and capacity - plain explanations worked better than buzzwords. Project: stack, hardest bug, what you would rebuild.
HR: Why this product? Ownership? Relocation? Keep answers short: situation → what you did → result.
Takeaway: clear DSA plus a coherent routing story beats a high CGPA with weak explanation.
What hurt others: coding before constraints; missing edge cases; treating HR as a formality; “I like delivery apps” with no network vocabulary.
A campus-week checklist: confirm whether your invite has an OA. If yes, two timed mediums the day before, sleep, language runtime checked. If no OA and a Codepair link arrives, block a 3-hour window (projects + DSA + possible same-day round two). Keep a one-page LLD (scan + assign) and two STAR stories in a notes app - you will not want to invent them at minute 110.
SDE-1 - codepair marathon
A Delhivery SDE-1 candidate on GeeksforGeeks described a long technical: detailed project questions, then five DSA problems on Codepair, then a same-day second round mixing LLD, behavioural, and a puzzle, with logistics domain context explained by the interviewer.
Freshers on a 60-minute campus OA should not copy five-problem depth blindly - the transferable signals are edge-complete code, stamina, and plain LLD.
How to train that stamina without burning out: once a week, pick five problems you already “know” (BFS, heap, greedy, list, DP) and re-solve them in one 2-hour block with a friend watching for skipped edges. The point is not new topics. The point is not collapsing at problem 4. Eat, water, bathroom before the call - 2h+ shared editors are tiring.
Go note: Delhivery lists Go more often than most campus companies. If you are a Java/Python person, stay there unless the invite forces Go. If you claim Go on the resume, compile a small slice (maps, slices, error returns) the night before. Interviewers notice when the language is costume jewelry.
More narratives: Delhivery interview experience.
Similar companies
DSA plus assignment/routing stories transfer across this set. Customise the domain: Delhivery = hubs and parcel SLAs; Swiggy/Blinkit = food/quick-commerce; Flipkart/Amazon = broader e-commerce + marketplace. Keep one language and one error log.