Swiggy Business Analyst candidates report SQL, analytical reasoning, marketplace and quick-commerce cases, plus discussions of prior work and behavioral fit. Reported processes span two to three rounds.
$90K
Avg. Base Comp
$106K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Swiggy Business Analyst interview reports point to a mix of analytical execution and practical business judgment. Reported formats range from two to three rounds, so the exact sequence can vary. Across accounts, candidates encountered SQL alongside marketplace and quick-commerce problem solving, followed by a conversation with a hiring manager or HR.
Make your reasoning visible. Technical preparation should include SQL problems involving joins and restaurant-order data. One candidate described medium-to-hard SQL, while another reported SQL scenarios alongside aptitude and puzzle questions. Practice explaining how you frame the query and validate the result, not only producing an answer.
Business cases were tied to operating questions: increasing quick-commerce revenue, diagnosing a 5% drop in orders, estimating order volume, and helping a restaurant that is not receiving orders. Start by clarifying the objective, state assumptions, identify plausible drivers, and turn the diagnosis into practical next steps. The later conversation may explore your CV or portfolio, how your previous work could help Swiggy, and behavioral themes such as leadership, time management, or handling pressure. Connect your past work directly to the case or business problem under discussion.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Swiggy process.
I went through four rounds for the Business Analyst role. The first was a HackerRank SQL assessment with eight questions across difficulty levels—three easy ones to start, then three medium and two hard questions that required real practice to complete within the 1.25-hour time frame. Then came the technical interview covering SQL and Python in practical scenarios: handling outliers, replacing null values, and statistical concepts like hypothesis testing and A/B testing frameworks. The third round was case studies and estimation—they presented business problems and wanted me to think through guesstimate solutions and root cause analysis. The final round was with the hiring manager. Throughout, the interviewers were friendly and approachable, more like senior colleagues than rigid corporate types. The whole vibe was collaborative.
To succeed, prioritize practicing HackerRank SQL problems at medium and hard difficulty. You'll be under time pressure, so preparation is essential. Also make sure you understand A/B testing and hypothesis testing frameworks—those came up in the technical round. The case study round tests analytical thinking and communication more than a specific 'right' answer, so focus on showing clear reasoning and business intuition.
Prep tip from this candidate
Practice HackerRank SQL at medium to hard difficulty levels within 1.25 hours. Be ready to discuss A/B testing and hypothesis testing frameworks. In case studies, demonstrate clear analytical thinking and business sense rather than searching for a perfect answer.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Swiggy
Create top_ads with the top 3 ads and return the row counts for inner, left, right, and cross joins with ads
| Question | |
|---|---|
| Z and t-Tests | |
| Forecasting New Year Revenue | |
| Unified Event Pipeline | |
| Increased Cancellations | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Customer Orders | |
| Button AB Test | |
| Experiment Validity | |
| Month Over Month | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| 500 Cards | |
| Comments Histogram | |
| Closest SAT Scores | |
| Longest Streak Users | |
| Subscription Overlap | |
| Top Three Salaries | |
| Prime to N | |
| WAU vs Open Rates | |
| Upsell Transactions | |
| Paired Products | |
| Top 3 Users | |
| Weekly Aggregation | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Recurring Character | |
| Scrambled Tickets | |
| Post Composer Drop |
Synthesized from candidate reports. Individual experiences may vary.
Candidates reported a technical round featuring medium-to-hard SQL. Examples included joins, SQL scenarios, and a question about the number of orders per restaurant in November. Another account also included aptitude and puzzle questions. Prepare to write or describe a clear approach, explain assumptions, and talk through how you would check the result.
Reported case prompts included increasing quick-commerce revenue, diagnosing a 5% decrease in orders, estimating Swiggy order volume, and improving outcomes for a restaurant that is not receiving orders. Use a structured approach: clarify the goal, segment possible causes or levers, state assumptions, and prioritize practical actions.
Candidates described a later hiring-manager or HR conversation covering their CV or portfolio, the contribution they could make, and behavioral questions. Reported behavioral themes included leadership, time management, and handling pressure. One hiring-manager discussion also included a business case, so be ready to connect prior experience directly to the problem presented.
