HR interview questions
Common Licious HR questions, sample answer frames, and STAR tips.
Licious Interview Experiences
How Licious fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Licious placement process includes: 1. Online Assessment (60-90 minutes) - 2-3 coding problems, 2. Technical Interview Round 1 (45 minutes) - DSA-focused, 3. Technical Interview Round 2 (45 minutes) - System design and project detailed discussion, 4. Managerial Round (30-45 minutes) - Behavioral discussion, 5. HR Round (30 minutes) - Compensation discussion and background verification. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): SDE-1: ₹12-18 LPA. Experienced / SDE-2 bands are higher and offer-specific - confirm on your letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | 2-3 coding problems |
| Technical Round 1 | 45-60 min | DSA + project discussion |
| Technical Round 2 | 45-60 min | System design (orders / logistics) |
| HR | 20-30 min | Behavioural + culture fit |
Real interview experiences
Section titled “Real interview experiences”Licious hires mostly off-campus and lateral rather than through mass campus drives, so the public write-ups are individual accounts from LeetCode, Medium and Glassdoor rather than college placement posts. Two things recur strongly across them: Java is often mandated in the coding rounds and your code has to actually compile, and there is a low-level design round that catches candidates who only prepped DSA.
Experience 1: SDE-1, Bangalore (selected)
Section titled “Experience 1: SDE-1, Bangalore (selected)”Reported flow: three rounds - two technical screens, then a hiring manager round.
Technical screen 1 (~1 hour)
- 2 DSA questions at medium level. Not a whiteboard conversation: write it in Java, and it must compile.
- Reported topic areas across SDE-1 accounts: arrays, strings, linked lists, trees and recursion. Named examples include House Robber II (DP) and lowest common ancestor in a binary tree.
- Interviewers push on optimisation after a working solution, so leave time to talk complexity.
Technical screen 2 (~1 hour)
- 2 low-level design problems - one easy, one medium - again written and compiled in Java.
- Plus CS fundamentals questioning alongside the design work.
- This is the round people report being least prepared for. Class design, interfaces and responsibilities matter more here than algorithmic cleverness.
Hiring manager round (~60 min)
- Cultural fit plus CS fundamentals in the same sitting.
- Long discussion of current and previous projects: your actual roles and responsibilities, the tech stack and why, and a deep dig into project architecture.
- Personal projects came up, and so did “how do you keep up with new technology” - answered concretely, not with a list of newsletters.
Experience 2: what the online assessment looks like
Section titled “Experience 2: what the online assessment looks like”Not every candidate gets an OA - referral and lateral routes often skip straight to the technical screens - but where one exists, reports describe it as unusually long and unusually varied:
- 2.5 to 3 hours total.
- A “gaming” section: reasoning, logical puzzles, quantitative problems and short memorisation tasks. This surprises people expecting a pure coding test.
- Coding challenges.
- Technical MCQs.
At SDE-2 the screening is much tighter and stack-specific instead: one reported 2025 cycle used 15 MCQs in 10 minutes on Java and Spring, followed by 2 easy coding questions in 20 minutes.
How the bar moves with level
Section titled “How the bar moves with level”- SDE-1: DSA at medium level, LLD, CS fundamentals, project depth.
- SDE-2: Java/Spring knowledge is assumed and tested directly; expect design and ownership questions rather than “explain a sorting algorithm”.
- SDE-3: reported rounds move to high-level design - one account describes being asked to design a message broker along the lines of Kafka.
What the pattern suggests
Section titled “What the pattern suggests”- Practise in Java, in an editor that compiles, if Java is your declared language. Multiple accounts specify this explicitly, and pseudocode does not pass.
- Prepare LLD as seriously as DSA. It is a full round at SDE-1, not a bonus question.
- Know your own architecture cold. The hiring manager round is largely your projects, examined properly.
- Domain knowledge about cold-chain logistics or delivery SLAs is not what published accounts report being tested on - useful context for the culture-fit conversation, but do not prep it in place of design and fundamentals.
Sources: Medium - Licious SDE-1 interview experience (selected) · LeetCode - Licious SDE1 Bangalore · LeetCode - Licious SDE2 hiring 2025 · Medium - Licious SDE-3, Feb 2024 · Glassdoor - Licious interviews
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Top-K frequent elements. Usually expects heap / bucket sort
- Shortest path in a grid. Usually expects BFS
- Merge overlapping delivery slots. Usually expects interval merge
- Discussion on cold chain inventory and order SLA, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
- SDE-2: order/slot design, idempotent payments, inventory reservation, incident ownership
- SDE-2: rate limiting / sliding window style coding with production complexity talk
HR / behavioural
Section titled “HR / behavioural”- Why this product?
- Working with unclear requirements
- On-call or weekend comfort
- Relocation
- (SDE-2) Notice period, current vs expected CTC, on-call ownership
Practical tips for Licious
Section titled “Practical tips for Licious”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain cold chain inventory in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Licious panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
- SDE-2 candidates: prioritise one end-to-end design (orders + inventory + SLA) and two production incident stories - do not only grind Easy/Medium lists.
HR interview
Section titled “HR interview”After technical rounds, Licious usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.