0 day streak

Swiggy behavioral interview: Company values

ProductE-commerce and consumer India Machine coding / LLD

The values are published on the company blog; culture fit is discussed in the manager round rather than scored value by value.

0%ready
ProgressPrincipleThey will ask something likeYour story
Be HumbleCollaboration and inclusion Describe a decision you argued against but then had to carry out.Tell me about a time you helped a teammate succeed. Write a story
Sample answer: Describe a project that needed several teams. How did you get them aligned?

Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out.

Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other.

Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me.

Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part.

Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs.

Tip: Show how you helped others succeed and made people feel they belonged. Collaboration and inclusion: weak answer, follow-ups and level differences

Always be Curious, Always be LearningCuriosity and growth Tell me about the hardest feedback you have given or received.Tell me about a project that failed. What did you learn? Write a story
Sample answer: Tell me about something you had to learn quickly for a project

Whether you can learn something unfamiliar quickly and on purpose: a plan for what to learn first, using people and code as well as documents, and applying it to real work. Curiosity should lead to a result, not just a course you finished.

Situation The engineer who owned our team's pricing service moved to another team with two weeks' notice. The service was written in a language nobody else on the team knew, and it was due for a change to support a new discount type in five weeks.

Task I volunteered to take it over. I had never written that language, so I needed to become safe on call for the service within two weeks and ship the discount change on time.

Action I made a plan around the service rather than the language. In the first three days I read the code path for a single price request from start to finish and drew it, writing down every language feature I did not understand. I learned only those features first, from the official tutorial and by writing small throwaway programs. I booked three one-hour sessions with the departing owner and used them only for questions I could not answer from the code, such as why certain decisions were made. To learn by doing, I fixed two small open bugs in my first week and asked an engineer from another team who used the language daily to review them. I kept a notes page of patterns and pitfalls, which became the service's onboarding guide.

Result I took over on-call for the service after two weeks and shipped the new discount type a week early, with no incidents. A second teammate onboarded in four days using my notes. I still use the same approach for unfamiliar systems: trace one real request, learn what it needs, and ship something small in week one.

Tip: Show something you learned on your own and how you used it at work. Curiosity and growth: weak answer, follow-ups and level differences

Be Honest, Display Highest Level of IntegrityDisagreement and candor · Integrity and trust Tell me about a time you disagreed with your manager. What happened?Describe a decision you argued against but then had to carry out. Write a story
Sample answer: Tell me about a time you disagreed with your manager

Whether you can disagree with someone who has more authority using data rather than emotion, listen to their reasons, and then commit fully once a decision is made, even if it did not go your way. They also check that the relationship survived.

Situation My team was moving our notification service from an old message queue to a new one. My manager wanted to switch all traffic in a single cutover two weeks before our busiest season, because running both systems in parallel would delay other work.

Task I was the engineer leading the migration, and I thought a single cutover that close to peak traffic was too risky. I needed to make that case without simply blocking the plan.

Action I asked my manager what worried them most: the cost of keeping two systems alive for weeks. So I focused on that. I measured how long a partial rollout would really take and found it was four extra days, not weeks. I also listed the three failure cases we could not test without real traffic, such as ordering under retries. I brought a short written comparison: the single cutover, and a plan that sent copies of real traffic to the new queue for three days, then moved twenty, fifty and a hundred percent of traffic with a quick switch back. I was clear that it was their call. My manager agreed to the shadow traffic but kept the original date for the full switch. I disagreed with the date, said so once, and then committed to it; I worked the weekend plan with the team so we would make it.

Result The shadow traffic caught a message-ordering bug that would have sent duplicate notifications to about two percent of users. We fixed it and finished the switch on the original date with no incidents during peak. My manager later asked me to write up the staged approach as the default for future migrations.

Tip: Disagree with data, respectfully, then commit fully once the decision is made. Disagreement and candor: weak answer, follow-ups and level differences

Consumer Comes FirstCustomer focus Describe a time you changed a plan because of what you learned about the user.Tell me about a time you had to balance a customer need against a technical constraint. Write a story
Sample answer: Tell me about a time you changed a plan because of what you learned about the user

Whether you start from a real user problem rather than from the technology, and whether you are willing to change your own plan when the evidence about users points elsewhere. They want a decision that made a measurable difference for someone outside the team.

Situation I was on a team building the payments flow for a subscription app. Our plan for the quarter was a new saved-cards feature that product had asked for.

Task Before starting, I wanted to understand why payment-related support tickets had been rising, because they were the second biggest ticket category and nobody on the team had read them.

Action I spent an afternoon with the support team and read about a hundred recent tickets. Most were not about saved cards at all. When a bank declined a payment, we showed one generic "payment failed" message, so people retried the same card, got declined again and wrote in. I pulled our decline codes and found that about a third were recoverable: an expired card, a bank asking for extra verification, or a simple timeout. I wrote up the numbers and proposed pausing saved cards for two weeks to fix this first. Product agreed once they saw the ticket count. I mapped the common decline codes to plain messages that told people what to do next, added one automatic retry for timeouts, and added a prompt to update an expired card. We shipped it behind a flag to ten percent of users first and compared.

Result Payment-related tickets dropped by about forty percent and successful renewals rose by three percent, which was worth more than the saved-cards feature we had planned. We shipped saved cards three weeks later. Since then I read a sample of tickets before planning any feature in that area.

Tip: Start from a real user problem and show how your decision changed something for them. Customer focus: weak answer, follow-ups and level differences

Display a Founder MentalityOwnership Tell me about a time you took on something outside your responsibilities.Tell me about a time you made a decision that hurt in the short term but helped in the long term. Write a story
Sample answer: Tell me about a time you took ownership of something outside your role

Whether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work.

Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on.

Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip.

Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner.

Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it.

Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences

Think Win-WinCollaboration and inclusion Describe a decision you argued against but then had to carry out.Tell me about a time you helped a teammate succeed. Write a story
Sample answer: Describe a project that needed several teams. How did you get them aligned?

Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out.

Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other.

Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me.

Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part.

Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs.

Tip: Show how you helped others succeed and made people feel they belonged. Collaboration and inclusion: weak answer, follow-ups and level differences

Think BigInvention and simplification · Big impact and long-term thinking Tell me about a time you made a decision that hurt in the short term but helped in the long term.Tell me about a time you simplified a complex process or system. Write a story
Sample answer: Tell me about a time you simplified a complex process

Whether you look for a simpler or new way of doing something instead of accepting how it has always been done, and whether the change had a measurable result. Interviewers also check that you brought people along, because simplifying usually means changing other people's habits.

Situation Releasing our main backend service took a 14-step manual checklist: tagging, building, running database changes, updating three config files, a manual smoke test and posting notes. A release took about half a day, so we only released once a week, and roughly one release in five had a mistake in a manual step.

Task I was not asked to fix this, but I was the one releasing that month and I wanted to make releases fast and boring enough to do daily.

Action I timed each step for two releases and asked the three engineers who released most often which steps they feared. Most of the time went into three steps: updating the config files, waiting on the smoke test and writing notes. Instead of automating the whole checklist at once, I removed what I could first. Two of the config files only existed to hold a version number, so I replaced them with one value set by the build. I turned the manual smoke test into a short automated check against the staging environment, and generated release notes from merged pull request titles. Then I put the remaining steps into our pipeline with a single approval button. I ran the old and new process side by side for two weeks, and wrote a one-page guide so anyone on the team could release.

Result Release time went from about four hours to 25 minutes, and we moved from weekly to daily releases. In the next quarter we had no releases with manual-step mistakes, and two other teams copied the pipeline. The biggest win was removing steps, not automating them.

Tip: Show a simpler or new way of doing something and the measurable result. Invention and simplification: weak answer, follow-ups and level differences

Stand-up & Disagree but Commit FullyDisagreement and candor Tell me about a time you disagreed with your manager. What happened?Describe a decision you argued against but then had to carry out. Write a story
Sample answer: Tell me about a time you disagreed with your manager

Whether you can disagree with someone who has more authority using data rather than emotion, listen to their reasons, and then commit fully once a decision is made, even if it did not go your way. They also check that the relationship survived.

Situation My team was moving our notification service from an old message queue to a new one. My manager wanted to switch all traffic in a single cutover two weeks before our busiest season, because running both systems in parallel would delay other work.

Task I was the engineer leading the migration, and I thought a single cutover that close to peak traffic was too risky. I needed to make that case without simply blocking the plan.

Action I asked my manager what worried them most: the cost of keeping two systems alive for weeks. So I focused on that. I measured how long a partial rollout would really take and found it was four extra days, not weeks. I also listed the three failure cases we could not test without real traffic, such as ordering under retries. I brought a short written comparison: the single cutover, and a plan that sent copies of real traffic to the new queue for three days, then moved twenty, fifty and a hundred percent of traffic with a quick switch back. I was clear that it was their call. My manager agreed to the shadow traffic but kept the original date for the full switch. I disagreed with the date, said so once, and then committed to it; I worked the weekend plan with the team so we would make it.

Result The shadow traffic caught a message-ordering bug that would have sent duplicate notifications to about two percent of users. We fixed it and finished the switch on the original date with no incidents during peak. My manager later asked me to write up the staged approach as the default for future migrations.

Tip: Disagree with data, respectfully, then commit fully once the decision is made. Disagreement and candor: weak answer, follow-ups and level differences

Do More with LessDoing more with less Tell me about a time you achieved a lot with very few resources. Write a story
Sample answer: Tell me about a time you achieved a lot with very few resources

Whether constraints make you inventive rather than stuck: reusing what exists, cutting waste, and still delivering the result. They also check that you did not save money in a way that created hidden costs or risk.

Situation Our team's cloud bill for logging had grown about 60 percent in a year, much faster than our traffic. Finance asked every team to cut costs, and there was no budget for a new logging tool or extra people.

Task I volunteered to bring our logging cost down by at least a third within a quarter, alongside my normal work, without losing the logs we needed for debugging and audits.

Action I started by finding where the money went. A one-day analysis showed that four services produced 70 percent of our log volume, and most of it was debug-level messages left on in production and the same error repeated thousands of times a minute during retries. I fixed the cheapest problems first: I turned debug logging off by default with a way to switch it on for one service for an hour, and added sampling so a repeated error was logged once with a count. Then I looked at storage. We kept every log in fast, searchable storage for 90 days, but almost nobody searched past two weeks. With the security team's agreement, I moved logs older than 14 days to cheaper archive storage that could still be restored for audits. Everything used features our existing tools already had.

Result Our logging bill fell by 48 percent in two months with no new tools. Search actually got faster because there was less noise, and during the next incident nobody missed a log. Two other teams used my one-day analysis script to find their own savings.

Tip: Show a result you got with limited people, time or money. Doing more with less: weak answer, follow-ups and level differences

Move Fast, Break Barriers and Deliver ResultsSpeed and delivery Tell me about a time you missed a deadline.Tell me about a decision you made without all the data you wanted. Write a story
Sample answer: Tell me about a time you delivered under a tight deadline

Whether you deliver on time by making smart choices: cutting scope deliberately, removing blockers early and telling people the truth about risk. Heroics like working every night score lower than a plan that made the deadline safe.

Situation Our team had to support a new invoice format required by a regulation in one of our markets. The date was fixed by law, and we found out about the full requirements with five weeks left, when the original estimate was ten weeks.

Task I was the lead engineer for the change. I had to get something compliant out by the date without breaking invoicing for the rest of our customers.

Action In the first two days I went through the regulation with our compliance colleague and split the work into "required by the date" and "nice to have". Only about half was truly required: the new fields, the digital signature and storing invoices for the legal period. Automatic corrections, a nicer PDF layout and support for older invoice types could wait. I wrote this down and got product and compliance to sign off on it. The riskiest part was the signature service, which depended on an outside provider, so we built and tested that first, in week one, instead of last. I put the new format behind a flag for that market only, so other customers were untouched. I gave a short written status every Friday with what was done, what was at risk and what I needed.

Result We went live four days before the deadline. The later parts shipped over the next five weeks with no rush. Nobody on the team worked weekends, and there were no invoicing incidents during the switch. Agreeing the cut list in writing in week one was what made it possible.

Tip: Show a hard deadline met by cutting scope wisely, not by heroics alone. Speed and delivery: weak answer, follow-ups and level differences

Never SettleResilience and courage · Ambiguity and judgment Tell me about a time you had to balance a customer need against a technical constraint.Describe a project where the requirements were unclear. How did you move forward? Write a story
Sample answer: Describe a setback that almost made you give up. What kept you going?

Whether you keep going after something goes wrong, without denial or blame, and whether you have the courage to make or support a hard call. They want to see how you kept yourself and others steady and what changed because you persisted.

Situation My team rebuilt the checkout page of our shopping app to make it faster. We launched it twice, and both times we rolled it back within a day: first for a payment bug on one browser, then for a drop in completed orders we could not explain. Leadership was close to cancelling the project.

Task I was the lead engineer. Morale on the team was low, and I had to decide whether to argue for a third attempt and, if so, make sure it would not fail the same way.

Action I took a day to understand both failures. The browser bug was simple; the order drop was the real issue. From session recordings, I found that the new page hid the delivery-date selector behind a tap, and people abandoned when they could not see the date. Neither failure meant the rebuild was wrong; both meant our launch process was. I wrote a short plan for a third attempt with three changes: an automated test across our top five browsers, a gradual rollout starting at five percent with a comparison of completed orders against the old page, and an automatic switch back if orders dropped more than one percent. I presented it to leadership and said plainly that if this attempt failed, I would recommend stopping. I also talked to the team openly about the two rollbacks so nobody carried the blame alone.

Result The third launch went to a hundred percent over two weeks with no rollback. Page load time fell by 40 percent and completed orders rose by about two percent. The gradual rollout with an automatic switch back became the standard for every customer-facing launch on our team.

Tip: Show you kept going through a setback or made an unpopular call that was right. Resilience and courage: weak answer, follow-ups and level differences

How to answer

Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.

Behavioral questions by theme, with a tip for each · How the behavioral round is scored

Questions people ask

What is the Swiggy behavioral interview based on?

Company values: Be Humble, Always be Curious, Always be Learning, Be Honest, Display Highest Level of Integrity, Consumer Comes First, Display a Founder Mentality, Think Win-Win, Think Big, Stand-up & Disagree but Commit Fully, Do More with Less, Move Fast, Break Barriers and Deliver Results, Never Settle. The values are published on the company blog; culture fit is discussed in the manager round rather than scored value by value.

How do I answer Swiggy questions on "Be Humble"?

Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Show how you helped others succeed and made people feel they belonged. A typical question: Describe a project that needed several teams. How did you get them aligned?

How do I answer Swiggy questions on "Always be Curious, Always be Learning"?

Whether you can learn something unfamiliar quickly and on purpose: a plan for what to learn first, using people and code as well as documents, and applying it to real work. Curiosity should lead to a result, not just a course you finished. Show something you learned on your own and how you used it at work. A typical question: Tell me about something you had to learn quickly for a project