Got the offerSDE at Swiggy
- Difficulty
- Process took
- 2-3 Weeks
- Rounds
- 5
- Format
- Remote
- Applied via
- Referral
How it went
- When questions get tough, focus on structured thinking and break down problems into smaller pieces.
- Talk through your solutions clearly, Interviewers love hearing your thought process, especially when you explain why you chose a particular approach or tool.
What they would tell you
- When questions get tough, focus on structured thinking and break down problems into smaller pieces.
- Talk through your solutions clearly, Interviewers love hearing your thought process, especially when you explain why you chose a particular approach or tool.
How to prepare
- Master Java & Automation Fundamentals - Make sure you’re comfortable with core Java concepts, handling dynamic elements in Selenium, and writing clean, maintainable test code. Practicing building custom waits and listeners can give you a practical edge.
- Practice SQL Optimization - Optimizing queries, understanding indexes, and analyzing joins are key. This is a must-have skill for backend engineers to improve data retrieval times and overall system performance.
Round by round
- 1
Online Assessment (OA)90 min
The first round was a solid test of my core skills - Java programming, automation problem-solving, and SQL optimization. It wasn’t just writing code but also thinking about real test scenarios, like creating custom waits in Selenium and optimizing queries. What They Asked and How I Solved It
- Implemented a custom Selenium wait function to handle dynamic elements reliably.
- Optimized complex SQL queries by analyzing joins and using indexes efficiently.
- Wrote a program to generate test data systematically.
- 2
Technical Round 190 min
This round was mostly about how well I know Java and automation testing. The interviewer started by asking how I deal with elements on a page that appear after some delay. I explained how I use WebDriverWait in Selenium to wait until those elements show up. Then we talked about handling test failures. I described how I’ve set up a TestNG listener that takes a screenshot automatically whenever a test fails, makes debugging much easier. Lastly, we discussed building a data-driven testing framework. I shared how I use TestNG’s DataProvider to pass test data and manage that data using simple JSON files. The conversation felt smooth and interactive. The interviewer wasn’t just looking for correct answers, they wanted to understand my thinking and approach.
- 3
Technical Round 260 min
The toughest round was designing a cross-platform automation framework supporting Android and iOS with parallel execution, CI/CD integration, and reporting. Key Points & Approach:
- Proposed Appium with Page Object Model for maintainability.
- Used TestNG for parallel test execution.
- Managed test data through JSON files.
- Integrated Extent Reports and Jenkins pipeline for reporting and CI/CD.
- Focused on error handling, logging, and framework scalability.
- 4
System Design60 min
Designed an end-to-end automation framework for microservices, covering testing strategies, service virtualization, contract testing, and performance testing. Approach:
- Discussed Test Pyramid for test coverage.
- Explained service virtualization to simulate dependencies.
- Highlighted contract testing using Pact.
- Included performance testing with JMeter and monitoring with ELK stack.
- 5
HR Discussion45 min
This was a warm conversation about my remote work experience, teamwork style, growth plans, and alignment with Swiggy’s values.
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.