Four rounds, first was coding, second was automation and testing, third was managerial round and last one was HR. Leetcode easy questions using Java and testing related questions like SDLC, STLC and more.
Hello there, thank you for your feedback. Inputs like these reinforce and improve our efforts to make processes seamless and fruitful.
Wishing you luck and success
Team Swiggy
Otras opiniones sobre las entrevistas para el puesto de Software Development Engineer In Test (SDET) en Swiggy
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 3 semanas. Acudí a una entrevista en Swiggy en oct 2025
Entrevista
I have completed three rounds of interviews, including the final one with the Hiring Manager. Since then, I’ve been trying to reach out for an update, but I haven’t received any response.
I understand that not every interview process results in an offer, but I believe candidates who invest their time and effort to clear multiple rounds deserve at least a courtesy update or feedback. Silence after the final round feels quite unprofessional and disappointing.
Preguntas de entrevista [1]
Pregunta 1
Oops, api testing, selenium, excel sheet data provider, json validation
Hello there, we are glad to hear that your interview experience was positive and productive. Inputs like these reinforce and improve our efforts to make processes seamless and fruitful.
Wishing you continued success!
Team Swiggy
Solicité el puesto por otro medio. El proceso duró 2 semanas. Acudí a una entrevista en Swiggy en jul 2025
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Round 1 – Coding
This round was fair and good. The interviewer asked standard coding and problem-solving questions:
Balanced Parenthesis problem.
Find the second largest element in an array.
Discussion on time complexity and space complexity of solutions.
How to improve time and space complexity.
👉 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:
Interviewer joined 25 minutes late.
Instead of 2–3 hrs, it dragged to 3 hrs 25 mins, overlapping with my manager meeting at current job.
I had to call the HR 30+ times to get it rescheduled, and only when I dialed a different number did she pick up.
Questions asked:
What do you mean by Redis?
What is Docker? Write Docker code. If I am a student, how would you explain Docker to me?
What is Kafka?
Login API case: username + password with 1 lakh characters → what should be the response code? (I said 400, but they expected 401.)
What is p90, p95 in performance testing? Steps to implement.
Apart from p90/p95, what about p50, p75, etc.?
What is JMeter?
Write automation code: login to Facebook → go to messages → open latest message of a friend → type and send.
What is sequential data vs non-sequential data? Which is faster?
5 classes running in parallel → add one more class → how to ensure no impact on speed.
What is asynchronous?
How do you ensure your code is correct (even mentioned ChatGPT)?
What are the types of performance testing and the tools?
If I said “I don’t know”, the interviewer responded rudely with: “You need to know everything. See me, in 4 years I became a Team Lead.” (Honestly, I don’t know how he became TL with that attitude, given he didn’t respect time commitments.)
What tests can we do in JMeter?
If 2 laptops send same request in Postman and one gets faster response → why? (Answer: cache. But question was poorly 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, very disappointing experience in Round 2.
