Academic snapshot
Marks: 65-70% or 6.5-7.0+ CGPA throughout (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA
Backlogs: None active
Year: Final-year and recent grads
Licious Placement Papers 2026
Licious is India’s leading direct-to-consumer meat and seafood brand, delivering fresh products to customers through its own supply chain and mobile app. Its technology teams build catalogue, logistics, and consumer-facing applications, hiring engineers for backend, mobile, and supply chain systems.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Licious eligibility & CGPA (2026)
Licious campus and off-campus SDE hiring is product-startup style, not a mass IT services funnel. The academic floor is a gate. The OA is the real filter.
Who this hub is for
- For: Students targeting SDE-1 / Software Engineer on the consumer app, supply-chain tech, or data-adjacent product teams, primarily Bengaluru.
- Not the same track: Pure operations, warehouse, or sales roles. Those bars do not map to this OA → DSA → design loop.
- Analyst / supply-chain analyst: SQL and domain stories matter more than hard DSA. Use SDE sections as a base, then swap coding volume for analytics case practice.
- Experienced hires: SDE-2 loops add mandatory system design (orders, inventory reservation, SLAs) and production ownership. Fresher sections still help for DSA.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college CGPA list when printed | Coding bar, interview depth |
| Careers portal / referral | Resume screen volume; sometimes no hard published CGPA | Still expect OA + two tech rounds |
| Intern → full-time | Conversion interviews may skip a stage | You still defend projects and code |
Off-campus does not mean easier coding. It often means more applicants fighting the same 60-90 minute filter. If your CGPA sits near 6.5, spend energy on mocks, not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 6.5 enough?”
Is 6.5 CGPA enough? It matches the commonly reported floor (or 65-70%) across 10th, 12th, and graduation. Some interview-experience pages cite 7.0+. Selection still hinges on OA correctness and interview narration. A 6.7 with clean timed coding beats a 9.0 that freezes on edge cases.
Branches: CS/IT/ECE dominate shortlists. Related streams show up when DSA is solid. If your college lists only certain branches, read the notice.
Gaps and backlogs: Active backlogs are a hard blocker on most Licious fresher drives. A short education gap is easier to explain with a skills story than silence. Lying about CGPA or backlog status is an instant integrity fail in HR.
What helps the resume screen: One project you can defend end-to-end, any internship with ownership language, even a small logistics or e-commerce side project. Certificates are optional extras. DSA and OA mocks matter first. See certifications only after fundamentals are solid.
Branch & skills
Preferred: CS / IT / ECE and related
Languages: Python, Java, JavaScript, C++, Go
Focus: DSA, SQL, e-commerce fundamentals
Differentiator: Cold-chain / order SLA product sense
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.5-7.0+ / ~65-70% across 10th, 12th, graduation | Some notes say 7.0+; verify every drive |
| Degree | B.Tech / B.E. / M.Tech / MCA | Related computing degrees on many posts |
| Branch | CS, IT, ECE (and related) | Strong DSA can help adjacent branches |
| Year | Final year + recent grads | Internship conversion paths also appear |
| Backlogs | No active backlogs | Clear them before offer paperwork |
| Coding languages | Python, Java, JavaScript, C++, Go | Stick to one for OA + interviews |
Licious CGPA criteria
The minimum CGPA required is commonly cited as 6.5-7.0+ / 65-70% across 10th, 12th, and graduation. Treat it as a shortlisting filter when printed. Licious still decides on OA correctness and interview narration.
| Academic Level | Minimum (typical) | Notes |
|---|---|---|
| 10th | 6.5-7.0+ CGPA / 65-70% | Listed on many drives |
| 12th | 6.5-7.0+ CGPA / 65-70% | Diploma holders evaluated similarly |
| Graduation | 6.5-7.0+ CGPA / 65-70% | No active backlogs at hiring |
| Backlogs | None active | Cleared backlogs generally accepted |
Clearing CGPA only gets you into the funnel. Coding speed decides whether you see an interviewer.
Licious previous year papers & PDFs
Download 2026 Licious placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What Licious previous year papers actually train
Licious does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds, not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on 2-3 medium DSA problems in 60-90 min |
| Technical 1 | Live coding narration: brute force → optimize → edge cases |
| Technical 2 | Order management, inventory, routing, schema/API sketches |
| Managerial / HR | Why Licious?, Bengaluru relocation, ownership stories with numbers |
Themes that keep repeating (2024-2026)
- 2024 cycles: Medium DSA on OA. Arrays, strings, and hash maps dominate practice sets. System design started showing up more in Technical 2. Students who skipped timeboxes left a second coding problem unfinished.
- 2025 loops: Write-ups describe coding-heavy OAs (2-3 problems) on platforms like HackerRank, then DSA + project deep-dives. Domain chat around food-delivery / inventory / SLA shows up after you clear the code bar. Sliding-window and DP knapsack-style prompts keep returning.
- 2026 prep expectation: Keep medium DSA warm. Expect design rounds to stay fresher-depth (actors, tables, APIs, bottlenecks), not staff-level distributed systems. Treat PDF packs as pattern catalogs. Own the hash-map + window templates, not a memorised story.
Public write-ups on Licious’s exact OA blueprint are thinner than for FAANG loops. That is why this hub stresses pattern trainers and “verify your invite.” When in doubt, practice two mediums under 75 minutes and keep an order-flow sketch ready.
How to use one paper set in a single sitting
- Timed: run a full 60-90 minute mock with the same language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases you missed (empty cart, single SKU, expired inventory).
- Map each coding miss to a theme (window / hash / tree / DP) and pull two cousins from coding questions.
- Spend 15 minutes explaining an order state machine or inventory reservation out loud like a teammate.
- Log one STAR ownership story the session reminded you of (on-call miss, unclear SLA, warehouse constraint).
Related problems to practice
| Theme you saw in a set | What to drill next | Why Licious asks it |
|---|---|---|
| Sliding window / unique chars | Variable window, at-most-K variants | Catalogue search / filter UX |
| Hash map counting | Frequency, anagrams, two-sum family | Fast lookups in cart and SKU maps |
| DP / knapsack lite | Subset sum, coin change | Allocation and constraint problems |
| Graph BFS | Shortest path, connected components | Delivery routing intuition |
| Heap / priority queue | Top-K, scheduling | Dispatch / SLA queues |
Licious placement process, round by round
Licious hires freshers through campus placement cells, the careers portal, referrals, and occasional internship conversion. After resume screen, the shape is product-company style: timed OA, two technicals, then people rounds.
Application methods
Campus recruitment
Through college placement cells: PPT, then OA and interviews on a batch timeline.
Online applications
Apply on licious.in careers for early-career / fresher tech roles; follow the invite mailer for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code and clear interviews.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (6.5-7.0+ / 65-70% commonly reported), backlogs, and year of passing. Projects and internships help when volumes are high. This is a gate, not the hard filter. Coding is.
2. Online Assessment - Licious Online Assessment (60-90 min)
Candidate reports commonly describe a 60-90 minute assessment with 2-3 coding problems. Some invites add a short aptitude/reasoning block. Exact splits vary; treat the table as a working map, not a sealed blueprint.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Coding | 2-3 problems | 60-75 min | Arrays, strings, hashing, DP |
| Aptitude / reasoning | 5-10 when present | 15-20 min | Quant, logic |
Languages: Python, Java, JavaScript, C++, Go. Platforms: HackerRank and similar appear in write-ups. Confirm yours in the invite.
Pass bar in practice: Fully passing solutions beat a brilliant half-answer. Aim to clear at least 1-2 problems with working code. Optimal complexity is preferred, not always mandatory on every drive.
Student tip: Spend 3-4 minutes skimming all coding prompts. Bank the solvable one first. Invent two edge cases before submit.
Example timing for a 75-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim all statements; mark easy wins |
| 5-35 | Problem 1: restate → brute → optimize → code → sample tests |
| 35-65 | Problem 2 (and 3 if present) or harden edge cases |
| 65-75 | Revisit flagged aptitude items or last failing test |
Deeper OA notes and drills: Licious Online Assessment.
3. Technical interview round 1 - DSA (~45 min)
Video shared editor. Expect 1-2 DSA problems plus a short project warm-up. Patterns candidates report: arrays, strings, hash maps, trees, DP.
You should:
- Clarify constraints (null inputs, duplicates, large N)
- Narrate brute force → bottleneck → target complexity
- Code in your chosen language without syntax stalls
- Walk edge cases and complexity at the end
Interviewers care about debugging out loud. Silent staring after a failed mental test case is a common reject signal even when the idea was right.
Example narration shape (two-sum / cart combo): “Brute force is check all pairs O(n²). Better: hash the complement as we scan. Empty array returns none; duplicates need a count, not a set.” That 30-second plan already signals interview readiness.
4. Technical interview round 2 - design + project (~45 min)
Fresher depth, not staff-architect theater. Typical prompts:
- Order management: states, payments, cancellations, refunds
- Inventory reservation for perishable SKUs (cold-chain SLA)
- Delivery routing / slot assignment at city scale
- Schema and APIs for cart → checkout → dispatch
Start with users → data → APIs → bottlenecks. Plain language beats “we will use Kafka and Redis” with no requirements. Tie one resume project to logistics or e-commerce if it fits, without forcing it.
Worked mini-outline - order state machine:
- Actors: customer, inventory service, dispatch, support.
- States: Created → Paid → Packed → Out for delivery → Delivered (plus Cancelled / Returned).
- Rules: who can cancel; what happens if a SKU expires in the cold room.
- Failure: payment success + inventory miss → compensate, do not silently ship nothing.
- Scale later: only after the above is clear. Caching catalogue lists is fine; do not lead with a buzzword diagram.
If the interviewer pivots to API design, talk resources, verbs, pagination, idempotency for creates, and auth at a fresher level.
A July 2023 Java Developer write-up (selected, referral) described the design prompt as “Build a System of Food Delivery App Like Swiggy/Zomato,” starting from schema/tables before class modeling, with interviewers steering trade-offs as the candidate iterated. That is the shape: tables first, then classes, then scale.
5. Managerial round (~30-45 min)
Ownership, conflict, impact numbers, and how you work with ops/product. Licious is a D2C company; they want people who can talk to supply-chain reality, not only LeetCode. Prepare STAR stories with metrics (latency, error rate, hours saved, orders affected).
6. HR / culture - ~30 min
Why Licious (not “cool D2C brand” only), relocation to Bengaluru, notice period / exams, integrity. Know the ₹12-18 LPA fresher band so CTC talk is grounded. Ask one real question about the team’s product surface (app, cold-chain tracking, demand forecasting). It beats “what is the culture?”
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding + optional aptitude) | 60-90 min | Timed accuracy |
| 2 | Technical 1 (DSA) | ~45 min | Code + narration |
| 3 | Technical 2 (design + project) | ~45 min | Orders / inventory reasoning |
| 4 | Managerial | 30-45 min | Ownership, impact |
| 5 | HR | ~30 min | Fit, location, logistics |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT week then OA window |
| OA completion → shortlist | Few days common | Some batches move faster |
| Interview loop | ~1-2 weeks | Tech 1 → Tech 2 → Managerial → HR |
| Offer / paperwork | Days after final round | Written offer wins over verbal |
| End to end | ~2-3 weeks campus batches often | Off-campus can be 2-4+ weeks |
How Licious differs from a generic D2C interview
Licious still filters hard on DSA, but later rounds feel like a perishable-goods logistics conversation:
- Order + inventory + SLA show up more than social-feed metaphors.
- Cold-chain constraints (expiry, temperature, last-mile slots) are fair game at fresher depth.
- Managerial rounds lean on ownership and impact harder than many product companies.
- Bengaluru is the usual India hub story. Treat relocation as a real HR question.
If you are also preparing for Blinkit or Swiggy, keep DSA shared and customise the product sketches per company.
Preparation resources for Licious
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 Licious
If a Licious 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 Licious sits around ₹12-18 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Licious fresher eligibility is candidate-reported. Common campus/SDE baseline: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; final-year students and recent graduates; typically 65-70% or 6.5-7.0+ CGPA across 10th, 12th, and graduation; no active backlogs. Some write-ups cite 7.0+ throughout. Always verify the drive notice.
What you are training for: Licious fresher SDE loops commonly run: Online Assessment (60-90 min, 2-3 coding problems) → Technical 1 (~45 min, DSA + projects) → Technical 2 (~45 min, e-commerce/supply-chain design + project deep dive) → Managerial (30-45 min) → HR (~30 min). Some drives merge managerial with HR. Campus batches often finish in about 2-3 weeks.
Short version of the prep split: Split time roughly: 50% DSA (arrays, strings, hashing, DP), 25% e-commerce/cold-chain system design lite, 15% core CS (SQL, OOP), 10% managerial/HR stories with impact numbers. Clear the 60-90 minute OA first. Languages: Python, Java, JavaScript, C++, 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 Licious 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 Licious 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 Licious 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 Licious?” 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 Licious-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 Licious story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Licious 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 Licious papers on three different days, then interview prep on the leftovers.
What to practise before a Licious drive
Week-by-week calendars live on the preparation guide. This section is the focus map: where hours go, what “good enough” looks like, and what to skip.
Time split that matches the loop
| Bucket | Share | This week’s proof |
|---|---|---|
| DSA | 50% | Two timed mediums, fully passing |
| Design lite | 25% | One order or inventory sketch spoken in 3 minutes |
| Core CS | 15% | 10 SQL queries + OOP one-liners from your project |
| People rounds | 10% | Two STAR stories with numbers + Why Licious |
If your OA is next week, raise DSA to 70% and keep one design sketch. If interviews are next week and OA is done, flip to live coding + design + stories.
What “ready” looks like (not a 12-week dump)
- You finish two medium coding problems in 75 minutes with passing tests.
- You can explain brute → better without staring at the ceiling.
- You can draw order states and say what happens when payment succeeds but inventory is short.
- You have one project with a metric, a bug, and a trade-off.
- You can answer Why Licious without saying “I like meat delivery.” Talk cold-chain tech, D2C ownership, or a specific product surface.
Error log (the only tracker that matters)
After every mock, write three lines: problem name, miss type (speed / concept / edge case), cousin problem to retry tomorrow. Ten logged misses beat fifty random LeetCode greens you cannot re-solve cold.
Weekend mock that matches a real drive
Saturday 10:00: 75-minute OA (2-3 coding).
Saturday 12:00: untimed rewrite + error log.
Saturday 16:00: 15-minute order/inventory sketch out loud.
Sunday 11:00: 45-minute live coding with a friend or a rubber duck.
Sunday 12:00: STAR stories + Bengaluru logistics.
Two weekends of that beat twelve nights of random YouTube.
What to skip
- Staff-level Kafka diagrams before you can name order states.
- Certificate stacks before you can pass two mediums.
- Memorising a “Licious company history” paragraph instead of one product fact you actually understand.
- Switching languages the week of the drive.
Night-before checklist
- Charger, ID, resume one page
- Language chosen; IDE/platform login tested
- One light DSA set already reviewed (not a new topic)
- Order-state sketch on one page
- Sleep. A 9 a.m. HackerRank after a 3 a.m. mock is how easy array problems go wrong
Licious fresher CTC in India (2026)
Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, team (consumer app vs supply-chain tech), hiring year, and written components (base / bonus / ESOPs).
Roles students ask about
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| SDE-1 / Software Engineer (fresher) | ₹12-18 LPA | Primary band for this hub |
| Data / Supply Chain Analyst (fresher) | ₹8-12 LPA | SQL + domain; lighter coding |
| SDE-2 (indicative) | ₹18-28 LPA | Not the fresher campus default |
Confirm base, joining bonus, and any ESOP language 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 family coverage
- Employee discounts on Licious products
- Learning / mentorship (manager-dependent)
- Hybrid or office norms for Bengaluru teams
- Relocation support when moving cities: ask HR, do not assume
How to talk CTC in HR without sounding lost
Know the ₹12-18 LPA fresher context, ask how the package splits (fixed vs variable vs ESOPs), and clarify joining date vs final exams. One calm clarifying question beats aggressive negotiation with no market anchor.
What’s changed in Licious hiring lately
- Digital / off-campus assessments remain common alongside campus drives.
- DSA after resume screen stays the real filter. Aptitude still appears on some OA invites, but weak coding rarely survives.
- Product awareness for orders, inventory, and cold-chain SLAs shows up in Technical Round 2 more than in 2010s-style pure HR.
- HackerRank-style platforms appear in recent write-ups; always trust your invite for duration and section list.
- Treat ₹12-18 LPA as a reported fresher SDE band, not a promise for every role or college.
- Ownership STAR stories matter more here than at many product companies. Prepare them early, not the night before managerial.
- Public detailed OA write-ups are still thin. Practice pattern trainers and verify the mailer.
Common questions about Licious hiring
Process & papers
What is the Licious placement process for freshers?
Typical fresher path: Online Assessment (60-90 min, 2-3 coding) → Technical 1 (DSA) → Technical 2 (design / project) → Managerial → HR. Campus batches often finish in about 2-3 weeks; off-campus timelines vary. Confirm round names on your invite.
How many interview rounds does Licious usually have?
Most fresher SDE loops report 4-5 stages (OA + two technicals + managerial + HR). Some invites skip managerial or merge it with HR. Count the mailer, not a random blog.
Can I download Licious placement papers PDF for free?
Yes. Free Licious placement papers PDF and 2024-2026 style practice sets are on this site: pattern trainers with solutions, not leaked live papers. No registration for the main downloads. Start with the 2026 PDF or the paper archive.
What does the Licious Online Assessment look like?
Candidate-reported OA is often 60-90 minutes with 2-3 coding problems (arrays, strings, hashing, DP) and occasional aptitude. Languages: Python, Java, JavaScript, C++, Go. Platforms like HackerRank show up in write-ups. Verify yours.
Eligibility & offer
What eligibility / CGPA do fresher SDE drives usually expect?
Commonly reported floor: 6.5-7.0+ CGPA / 65-70% across 10th, 12th, and graduation; CS/IT/ECE-related degrees; final-year or recent grads; no active backlogs. Some notes cite 7.0+. Licious does not publish one universal cutoff. Your drive notice overrides this page.
What is Licious fresher salary in India?
Candidate-reported SDE-1 fresher CTC often lands around ₹12-18 LPA (as of August 2026), mainly for Bengaluru roles. Analyst bands are often ₹8-12 LPA. The written offer letter is the only number that matters.
Do I have to relocate to Bengaluru?
Bengaluru is the main India hub candidates report for Licious engineering roles. HR usually checks relocation willingness and joining logistics. Be honest about constraints early.
Can I apply to Licious with backlogs?
Most drives require no active backlogs at selection. Cleared backlogs are usually fine. Check the specific posting.
Prep & Licious-specific
How should I prepare for Licious?
Split time roughly 50% DSA, 25% design/order/inventory lite, 15% SQL/OOP, 10% behavioral. Clear timed OA mocks first. Keep one coding language. Details: preparation guide.
Which programming languages are allowed?
Python, Java, JavaScript, C++, and Go are the usual set. Confirm on the invite. Do not switch languages the week of the drive.
What product topics should I revise?
Order workflows, inventory reservation for perishable SKUs, delivery routing, and search/filter at fresher depth: actors, data, bottlenecks, failure modes in plain language. Practice sketches beat memorised architecture diagrams.
How important is the managerial round?
It is a ranked round on many SDE loops. Ownership, conflict, and impact numbers matter. Coding still decides whether you reach that conversation.
Licious vs Zepto vs Blinkit for freshers?
All three care about DSA. Licious India loops often emphasise cold-chain and D2C supply-chain vocabulary with a Bengaluru hub story. Quick-commerce loops lean into 10-minute delivery scale and higher traffic. Prep DSA for all; customise product stories per company.
What certifications help before joining?
For campus SDE, DSA + OA mocks + one strong project beat certificate stacks. Cloud or domain certs are optional extras after fundamentals. See certifications.
Any pro tip that actually changes outcomes?
Bank solvable OA problems first, keep an error log, and rehearse one order/inventory explanation out loud before Technical Round 2. Correctness under time beats a half-finished clever solution. Quantify project impact.
Where can I read real interview experiences?
Start with Licious interview experience on this site, then cross-check recent community write-ups for your target level. Patterns shift by year. Use them as maps, not scripts.
Licious - recent candidate experiences
Fresher SDE loops (2024-2025)
Profile patterns that got selected: B.Tech CSE/IT, roughly 7.0-8.5 CGPA, tier-2 and tier-1 mix, one internship or a strong project, steady DSA practice rather than last-week panic.
Online assessment: Timed coding on HackerRank or similar. Clean, fully passing solutions beat partial cleverness. Shortlist mail often arrived in a few days. Students who triaged prompts early kept both coding problems alive.
Technical rounds: Coding such as array/hash problems and DP lite. Domain chat around orders, inventory, and food-delivery design. Project deep dive: stack choice, hardest bug, what you would rebuild. Later rounds sometimes leaned into schema first, then classes.
Managerial / HR: Why Licious? Working with unclear requirements? Conflict on a team? Relocation comfort for Bengaluru? Keep answers short: situation → what you did → result.
Takeaway candidates repeated: clear DSA plus a coherent order/inventory story beats a high CGPA with weak explanation. Talking through the approach before coding mattered as much as the final snippet.
What hurt other candidates in the same cycles: coding before clarifying constraints; treating managerial as a formality; system-design jargon without a simple bottleneck story; optimising one hard OA item while leaving an easy problem incomplete; freezing when asked “what happens if a SKU expires after payment?” with zero concrete answer.
Story-shaped notes students shared
Story 1 - Selected Java Developer, July 2023 (referral, off-campus): Four-round funnel: 60-minute DSA, system design, techno-managerial Spring/API work, and management. Design prompt was a food-delivery app “like Swiggy/Zomato,” starting from schema/tables before class modeling. Interviewers steered trade-offs as the candidate iterated. Source: Medium write-up. Takeaway: tables first, then classes; let the interviewer push scale.
Story 2 - SDE-3 backend, February 2024 (experienced loop, still useful): Three rounds framed as PS/DS but actually LLD for a creator-verifier-approver pipeline, then rate-limiter HLD/LLD, then HM on project infra plus a Kafka-like broker. Outcome was not a hard reject: “Verdict: Hold due to recent layoff at Licious.” Source: Medium. Takeaway for freshers: even senior loops stay concrete (pipelines, rate limits). Do not invent a layoff story into your HR answer; do treat “hold” as a real possible outcome and keep other processes live.
After you clear OA - what to do in the waiting week
- Re-solve every miss from your last two mocks cold.
- Speak two ownership STAR stories and one conflict story without notes.
- Sketch an order state machine and an inventory-reservation API on a blank doc.
- Warm one tree/DP medium in your interview language.
- Sleep and Bengaluru logistics. Do not open a new advanced DSA topic.
Mini design sketch students should rehearse
Payment succeeds, cold-room inventory is short:
- Actors: checkout, inventory, payments, support.
- Conflict: oversell vs block checkout. Pick one and say why for perishable SKUs.
- UX: tell the customer immediately; offer substitute or refund.
- Failure: do not dispatch an empty box; compensate the payment.
- Scale later: only after the above is clear. Do not lead with Kafka.
That 90-second sketch beats a memorised microservices diagram.
More fresher narratives: Licious interview experience.