HR interview questions
Common Swiggy HR questions, sample answer frames, and STAR tips.
Swiggy Interview Experiences
How Swiggy fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Swiggy placement process (from student reports): 1. Online Coding Assessment (90-120 min): 2-3 DSA problems, 2. Technical Interviews (2-3 rounds): DSA, system design, 3. Managerial/Team Fit (45 min), 4. HR/Offer Discussion (20-30 min). Total duration: 2-4 weeks.
Eligibility (from student reports): 6.5+ CGPA in 10th, 12th, and graduation.
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”These are rewritten from public candidate write-ups, not invented composites. Details differ by campus and year.
Experience 1: SDE-1, on-campus
Section titled “Experience 1: SDE-1, on-campus”Source: Swiggy Interview Experience for SDE-1 | On-Campus - GeeksforGeeks
Round 1 - Online assessment (HackerRank, 90 min)
- 3 coding problems (easy to hard) plus 1 SQL / database question at medium difficulty. The SQL question surprises people who prepped DSA only.
- The candidate solved roughly 3.5 of the 4; 11 students cleared to interviews.
Round 2 - Technical / DSA (~1 hour)
- Search in a row-wise and column-wise sorted matrix
- Design a stack that supports
getMin()in O(1) - Balanced parentheses check, then the harder “valid parenthesis string” variant with wildcards
- The write-up notes the interviewers were friendly and hinted when the candidate got stuck - so think out loud rather than going silent.
Round 3 - Managerial (~30 min)
- Strengths and weaknesses, project deep-dive, and why the candidate chose that stack.
- Backend vs Android preference, then follow-ups on React, Node, Express, MongoDB - whatever was on the resume.
Outcome: 9 reached the final round, 4 received SDE-1 offers, including this candidate.
Experience 2: SDE-1, off-campus (machine coding loop)
Section titled “Experience 2: SDE-1, off-campus (machine coding loop)”Source: Swiggy Interview Experience for SDE-1 (Off-Campus) - GeeksforGeeks
Background: ~6 months internship plus ~4 months full-time as a framework engineer before applying - Swiggy’s off-campus SDE-1 loop often skews to people with some work experience.
Round 1 - Online assessment (HackerRank, 75 min): 3 problems, one each easy / medium / hard.
Round 2 - Machine coding (120 min, 4 interviewers): “Design a Snake and Ladder game with working code.” Mandatory requirements first, optional features if time allowed. This round is the real filter on the off-campus path - it is about clean classes, working code, and handling the stated requirements, not algorithmic cleverness.
Round 3 - DSA (60 min): count the possible BSTs for a given N (Catalan), lowest common ancestor in a binary tree, and Gas Station (LeetCode medium).
Round 4 - Hiring manager (60 min): past experience, college projects, career motivation, and questions back about the team and culture. Result came about two days later.
Outcome: Selected.
Common thread across both write-ups: Swiggy pairs a DSA screen with something design-shaped - a machine coding round off-campus, or a stack-design / OOPs question on campus. The SQL question in the OA also shows up repeatedly and is worth an evening of revision.
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 order assignment and ETA, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this product?
- Working with unclear requirements
- On-call or weekend comfort
- Relocation
Practical tips for Swiggy
Section titled “Practical tips for Swiggy”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain order assignment in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Swiggy 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.
HR interview
Section titled “HR interview”After technical rounds, Swiggy 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.