Swiggy HR interview questions and answers

12 Swiggy HR interview questions with sample answers: why HR asks each one and how to answer. From public candidate reports. Free.

At Swiggy the HR round sits at the end, after your online assessment and the technical and design rounds, and often after a hiring manager conversation. It is run by a recruiter or a member of the talent acquisition team, and candidates usually report it taking around 20 to 40 minutes. By this stage the technical bar is already cleared, so the round is mostly about fit, salary, notice period, relocation and paperwork.

What the Swiggy HR round checks:

The first question is always some version of "tell me about yourself". Write your self introduction for the interview (free, no signup).

Swiggy HR interview questions with answers

5 of these 12 questions appear in public Swiggy interview reports; the rest are standard HR questions the company is known to ask.

1. Why did you choose Swiggy? (reported)

Why they ask: They want to hear a reason tied to Swiggy's product or scale, not a generic 'good company' line.

How to answer: Pick one concrete thing about Swiggy's business, like food delivery at city scale or Instamart's quick commerce, and connect it to work you have actually done. Keep it to two or three sentences and avoid praising the brand in the abstract.

Sample answer: I have used Swiggy for years, but what pulled me in is the scale of the delivery problem. Getting an order from restaurant to doorstep in under thirty minutes across hundreds of cities is a hard systems problem. In my last project at [current company] I worked on [a scheduling or routing feature], and that is the kind of work I want to keep doing. Swiggy is one of the few places in India where that problem is the core business, not a side project.

2. What is your current salary and what are you expecting? (reported)

Why they ask: They are checking whether your number fits the band for the role before they invest more time.

How to answer: State your current fixed pay honestly, then give a range rather than a single figure. Anchor the range on market data for the level, not on a random hike percentage. If they push for one number, give the top of your range and say it is negotiable for the right role.

Sample answer: My current fixed pay is [amount] with a variable component of [amount]. For this role I am looking at a range of [lower bound] to [upper bound], based on what I have seen for backend engineers at this level in Bangalore. I am flexible on the exact number if the role and the learning are right. What I care about more is that the work is close to the kind of systems I want to build.

3. How soon can you join? What is your notice period? (reported)

Why they ask: They are mapping your joining date against a team's immediate need.

How to answer: Give your actual notice period in weeks and mention any buyout clause if your contract has one. If you can join earlier, say so clearly, because that is often the deciding factor. Do not promise a date you cannot legally meet.

Sample answer: My notice period is [number] weeks, and my contract allows a buyout of [amount] if the company agrees. Realistically I can start within [number] weeks of a written offer. I have already spoken to my manager about my plans, so there is no surprise on that side. If your team needs someone sooner, I can check whether an early release is possible.

4. Are you open to relocating to Bangalore or to another Swiggy office? (reported)

Why they ask: Swiggy's engineering teams are concentrated in a few cities, and they want to avoid a joining surprise.

How to answer: Answer with a clear yes or no, and if yes, say what you need to make it work, like a joining window to sort out accommodation. Do not say 'I can adjust' if you actually cannot, because that turns into a dropout later.

Sample answer: Yes, I am open to relocating to Bangalore. I have lived in [current city] for [number] years, so I would need about two weeks after the offer to sort out a place to stay. My family is supportive of the move. I would rather be in the office with the team than work remotely, at least for the first few months while I learn the codebase.

5. Are you comfortable with the shift timings and any on-call rotation? (reported)

Why they ask: Delivery platforms run close to the clock, and they want to know you have thought about late evenings or weekend on-call.

How to answer: Say plainly whether you can handle evening or rotational shifts, and mention any hard constraint like a family responsibility. If you have done on-call before, say what it was like, because that is the real signal.

Sample answer: I am fine with the standard shift and with an on-call rotation. At [current company] I was on a weekly on-call for about a year, so I know what it means to get paged at night and debug under pressure. The only thing I would want to understand is how the rotation is split across the team, so it is fair and not one person carrying it every week.

6. Tell me about yourself.

Why they ask: It is the standard opener, and they use it to see whether you can summarise your background without rambling.

How to answer: Keep it to about ninety seconds: current role, one or two things you have built, and why you are here now. Skip the school marks and the hobbies unless they are relevant. End on the role you are applying for so the conversation has a direction.

Sample answer: I am a backend engineer with [number] years of experience, currently at [current company], where I work on [one line about your system]. Before that I graduated from [your college] in [year]. The work I am proudest of is [one concrete project and its impact, like cutting an API's p99 latency]. I am now looking to move into a product company at Swiggy's scale, where the systems are large and the feedback from real users is immediate.

7. Why are you leaving your current job?

Why they ask: They are checking for red flags like a conflict with a manager or a pattern of short stints.

How to answer: Frame it as moving toward something, not running away from something. Be honest but brief, and never badmouth your current employer. If the real reason is compensation or growth, say that in neutral words.

Sample answer: I have learned a lot at [current company], but the work has become more maintenance than building. Most of my time now goes into small fixes on a system that is not growing. I want to work on something with real scale and real users, where I can own a service end to end. That is the main reason I am looking, and it is why Swiggy's problems interest me.

8. Do you have any other offers in hand?

Why they ask: It tells them how fast they need to move and how serious you are about Swiggy.

How to answer: Be truthful. If you have offers, say so without using them as a threat, and explain why Swiggy is still your first choice if it is. If you have nothing, say that too, because lying here is easy to catch.

Sample answer: I am in the final stages with [one other company], and I expect to hear back this week. I have not signed anything yet. Swiggy is my first choice because of the scale of the systems and because the team I spoke to works on problems I find genuinely interesting. If Swiggy moves at a reasonable pace, I am happy to wait for it.

9. What are your strengths and weaknesses?

Why they ask: They want self-awareness, not a rehearsed list of virtues.

How to answer: For strengths, pick one that shows up in your work, with a short example. For weaknesses, pick something real that you are actively working on, and say what you are doing about it. Avoid the fake weakness like 'I work too hard'.

Sample answer: My strength is debugging. When something breaks in production, I stay calm and work from the logs and metrics rather than guessing, and that has saved my team a few long nights. My weakness is that I used to take on too much myself instead of asking for help early. I have been working on it by writing down blockers in our daily standup, and it has made me faster, not slower.

10. Where do you see yourself in three to five years?

Why they ask: They are checking whether your plan fits the role, or whether you will leave in a year for something else.

How to answer: Talk about depth in engineering, like owning a larger system or mentoring juniors, rather than a title you want. Tie it to the kind of work Swiggy does. Keep it short and grounded.

Sample answer: In three years I want to be the person the team trusts with the hardest service, the one who understands why it was built that way and can change it safely. I would also like to mentor a couple of juniors by then. I am not chasing a title in a hurry. I would rather grow into a senior engineer role by actually owning systems at Swiggy's scale.

11. Are you okay with the background verification and the documents we will ask for?

Why they ask: They want to know early if there is anything in your history that will fail a check.

How to answer: Say yes and confirm you can produce payslips, offer letters and education certificates. If there is a gap in your employment or a name mismatch on documents, mention it now rather than letting the check find it.

Sample answer: Yes, that is fine. I can share my payslips, the offer letter from [current company] and my degree certificate. One thing worth flagging now is that my name is spelled slightly differently on my [document], so I can send the supporting proof for that upfront. I would rather sort it out now than have it slow down the process later.

12. Do you have any questions for us?

Why they ask: It shows whether you have thought about the role beyond the salary.

How to answer: Ask two or three specific questions about the team, the on-call load or how performance is reviewed. Avoid asking only about the hike or the leave policy. Take notes on the answers, because they matter when you decide.

Sample answer: Yes, a few. What does the team's on-call rotation look like in practice, and how often does it actually get paged? Also, how is the first six months structured for a new engineer, is there a ramp-up project or do you start on the main service straight away? And how does the review cycle work here, is it twice a year or annual?

What candidates report about the Swiggy HR round

Offer letter timing. One candidate reported that Swiggy's HR asked them to resign from their current job before releasing the offer letter, which is unusual and risky for the candidate. Treat any such request as a serious point to clarify in writing before you resign.

Salary band. The same candidate reported being offered less than half of their existing pay for an Associate SDE (Backend) role, so expect the band to be tight for candidates switching from a different function or a higher-paying firm.

Interview stages. Candidates commonly report one online assessment, two design-focused interviews and a hiring manager round before HR, so the HR conversation is usually the last step.

Shift and on-call. Swiggy runs a delivery platform, so evening shifts and on-call rotations are commonly reported for engineering teams. Confirm the exact rotation for your team in the HR round.

Relocation. Engineering roles are concentrated in Bangalore. Relocation flexibility is commonly asked about, and a clear answer helps avoid a dropout later.

Background verification. Swiggy, like most large Indian product firms, runs a background check covering payslips, offer letters and education documents. Keep soft copies ready and flag any name or date mismatches early.

How to prepare

Practise the Swiggy HR round in a free 5-minute mock

Swiggy technical rounds

Quick answers about the Swiggy HR round

What is asked in the Swiggy HR interview?

Candidates report questions such as: Why did you choose Swiggy; What is your current salary and what are you expecting; How soon can you join? What is your notice period; Are you open to relocating to Bangalore or to another Swiggy office. Each one is answered on this page.

How long is the Swiggy HR round?

At Swiggy the HR round sits at the end, after your online assessment and the technical and design rounds, and often after a hiring manager conversation. It is run by a recruiter or a member of the talent acquisition team, and candidates usually report it taking around 20 to 40 minutes. By this stage the technical bar is already cleared, so the round is mostly about fit, salary, notice period, relocation and paperwork.

Can I fail the Swiggy HR round?

Yes. Candidates are rejected in the HR round for unclear answers on relocation, shifts or the package, for contradicting their resume, or for seeming uninterested in Swiggy. Decide your honest answers before the call.

Are these questions official?

No. They come from public candidate reports and are unofficial. PortLume AI is not affiliated with Swiggy.

Sources

Based on 14 public reports: YouTube (8), AmbitionBox (3), LeetCode Discuss (3), last updated Oct 2026.

Unofficial guide from public candidate reports. PortLume AI is not affiliated with Swiggy. HR questions for other companies · all company interview guides.

Featured on FoundrList

PortLume AI

Loading…