About Company
Swiggy is India’s leading on-demand convenience platform, delivering food, groceries (Instamart), and packages (Genie) to millions of customers. At its core, Swiggy is a logistics and data powerhouse. Handling millions of orders daily requires solving complex problems in real-time routing, demand forecasting, and high-concurrency systems. Swiggy’s engineering culture, documented on their “Swiggy Bytes” tech blog, is built on the philosophy of “customer-backwards” innovation and building for massive scale.
Job Details
| Role: | Software Development Engineer in Test |
| Salary: | UP to ₹10 LPA* |
| Location: | Bengaluru |
| Job Type: | fulltime |
| Posted Date: | 09/04/2026 |
| Application Deadline: | Apply Soon |
Job Description
Swiggy is looking for a Software Development Engineer in Test (SDET) for its Bangalore office. This is a technical individual contributor role where you are not just a “tester,” but a developer of testing systems. You are solely responsible for designing and implementing the test automation strategy (Functional and Non-functional) for specific modules. Your goal is to optimize the testing lifecycle to maximize ROI through innovative automation frameworks and infrastructure.
Requirements
- Education: Bachelor’s degree in Computer Science, Information Technology, or a related STEM field is standard for this role.
- Experience: 1 to 3 years of professional experience in Automation Testing.
- Technical Skills:
- Programming: Strong hands-on experience in Java is required. Familiarity with Python or other scripting languages is a plus.
- Automation Tools: Proficiency in Selenium (Web), Appium (Mobile), TestNG, and Maven.
- API Testing: Experience in API testing using Rest Assured, HTTP client, and an understanding of web services.
- Databases: Good understanding of relational databases like MySQL, Oracle, or SQL Server, including complex queries and joins.
- Advanced Tech (Big Plus): Exposure to ReactJS, NodeJS, Golang, or Spring Boot will set you apart.
- Design Patterns: Practical experience in implementing design patterns (e.g., Page Object Model, Singleton).
Roles and Responsibilities
- Automation Strategy: Set up and implement end-to-end automation strategies for functional and non-functional requirements.
- Framework Development: Add new capabilities and features to the internal automation framework used by the entire QA organization.
- Project Execution: Act as an independent executioner on single or multiple complex projects simultaneously.
- Reporting: Manage test coverage and provide periodic quality reports to engineering leaders and stakeholders.
- Innovation: Find and implement ways to optimize test strategies to ensure high software quality with minimal manual intervention.
- Stakeholder Management: Collaborate with developers and product managers to understand requirements and create optimal test plans for both short-term and long-term projects.
How to Apply?
Role Summary
The SDET at Swiggy is a “Quality Architect.” Because Swiggy deals with hyper-local delivery and real-time logistics, the software must be bulletproof. You aren’t just looking for bugs; you are building the “safety net” that allows developers to ship code multiple times a day without breaking the app for millions of hungry users.
Company Culture & Insights
Swiggy has a “High-Ownership” culture. As an SDET with 1–3 years of experience, you are expected to be an “Independent Executioner.” This means you won’t be micro-managed; you’ll be given a problem and expected to design the solution. The environment is data-driven and technically rigorous, as seen in their public engineering blogs.
Why We Recommend This Job
- Engineering at Scale: Swiggy is one of the few places in India where you can learn to test systems that handle millions of requests per second.
- Mobile Excellence: Since Swiggy is a mobile-first company, your skills in Appium will be pushed to the limit, making you a highly valuable mobile automation expert.
- Techno-Functional Growth: The “Plus” skills (Go, React, Node) suggest that SDETs at Swiggy are encouraged to understand the full stack, making the transition to a Developer role much easier later on.
Career Growth Potential
- SDET II / Senior SDET: Taking ownership of the testing architecture for a whole business vertical (like Instamart).
- Automation Architect: Designing global frameworks that are shared across all of Swiggy’s technical platforms.
- Engineering Manager (Quality): Transitioning into leadership, overseeing teams of SDETs and ensuring global quality standards.
Skills You’ll Gain
| Skill Category | Tools & Competencies |
| Automation | Appium, Selenium, Rest Assured, TestNG. |
| Performance | Non-functional testing (Load/Stress) using tools like JMeter or K6. |
| Infrastructure | Jenkins/GitLab CI, Docker, and potentially Kubernetes integration for testing. |
| Backend | Understanding distributed systems, API gateways, and microservices architecture. |
Salary & Benefits Info
- Estimated Salary: For an SDET with 1–3 years of experience at Swiggy, the Total Compensation (TC) typically ranges from ₹14,00,000 to ₹22,00,000 per annum, including a base salary and performance-linked bonuses.
- Benefits: Comprehensive health insurance, wellness programs, hybrid work flexibility (depending on team needs), and access to world-class internal tech learning resources
Frequently Asked Interview Questions
- Automation Frameworks: “How do you decide between a Data-Driven and a Keyword-Driven framework for a module like ‘Swiggy Checkout’?”
- Java/OOPs: “Explain how you use Interfaces and Abstract Classes in your current automation framework. Why are they necessary?”
- API Testing: “How do you validate a nested JSON response using Rest Assured? Walk me through the code to verify a specific delivery ‘Distance Service’ status.”
- SQL: “Write a query to find the top 5 restaurants in Bangalore with the highest number of failed orders in the last 24 hours, joining the ‘Orders’ and ‘Restaurants’ tables.”
Behavioral & Culture Questions
- Independent Execution: “Tell me about a time you were assigned a complex project with very little documentation. How did you go about building the test strategy?”
- ROI Optimization: “How do you identify which manual test cases should be automated first to provide the maximum ‘Return on Investment’ (ROI)?”
- Stakeholder Conflict: “How do you handle a situation where a developer says a bug you found is ‘by design,’ but you believe it will impact the user experience?”