The interview process included two rounds.
The first was coding-focused, fair, and relevant.
The second was poorly managed, with delays, unclear, and irrelevant questions. HR coordination required repeated follow-ups for rescheduling.
Round 1 – Coding
This round was fair and good. The interviewer asked standard coding and problem-solving questions:
👉 Overall, this was a smooth experience, and I felt it was a fair evaluation of coding skills.
Round 2 – Automation Framework Design & Challenges (Worst Experience)
This was supposed to be an Automation + Framework design round, but it turned into a system design + DevOps/tool-based grilling session.
Problems I faced:
Questions asked:
My Feedback
The first round was good and relevant.
The second round was the worst experience of my career: unprofessional interviewer (late, dragged too long, unclear questions, rude attitude).
Instead of focusing on automation framework and challenges (as promised), they asked random DevOps + performance testing questions.
Poor HR coordination → had to follow up excessively for rescheduling.
👉 Overall, a very disappointing experience in Round 2.
The following metrics were computed from 8 interview experiences for the Swiggy Software Development Engineer In Test (SDET) role in India.
Swiggy's interview process for their Software Development Engineer In Test (SDET) roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Swiggy's Software Development Engineer In Test (SDET) interview process in India.