I went through their complete interview process and was left very disappointed with the way it ended. I cleared three highly technical rounds, each of which was challenging and in-depth. The interviewers in those rounds clearly understood my skills and selected me through each stage, which gave me confidence that my capabilities were being fairly evaluated. After that, I was scheduled for a managerial round, which was not technical at all. I am still not sure whether I was rejected in this final round or afterwards. If the rejection was based on this stage, it raises a serious concern: were the three technical rounds not enough to validate my abilities? Since I would have been working closely with the technical team who had already approved me, why should a non-technical managerial discussion outweigh those evaluations? To make matters worse, there was no timely communication. After completing all four rounds, I heard nothing for over a week. Only after I personally followed up with HR did I receive a rejection mail on the same day. The lack of transparency, delayed response, and absence of constructive feedback made the whole process feel unprofessional and discouraging.

Interview Experience – SDET Role Position: Software Development Engineer in Test (SDET) Total Rounds: 3 Overall Difficulty: Medium Focus Areas: DSA, Test Engineering, and Resume-based Discussion Round 1: DSA – Problem Solving (Online or Technical Coding Round) Level: Easy to Medium Round 2: DSA + Experience-Based Discussion Level: Medium Format: 2 DSA questions + past project discussion Additional Discussion: Questions related to previous company experience: Test automation framework used Tools and languages used in daily work How flaky tests and CI/CD issues were handled Integration with reporting tools or test management systems Round 3: HR + Managerial Round Type: Behavioral + Technical Managerial Topics Covered: Past experience deep-dive based on resume Testing Scenarios: Performance testing (tools like JMeter, LoadRunner) Writing and reviewing test plans Creating effective and edge case–oriented test cases Situational/Behavioral Questions: How you handled bugs found late in the cycle Prioritization under tight deadlines Collaboration with developers and product owners Tone: Friendly but focused the manager evaluated both technical understanding and communication skills. Final Thoughts: This interview process was well-rounded strong focus on DSA and problem solving in the first two rounds, followed by real-world SDET responsibilities in the managerial round. Confidence in both coding and QA practices was important for success.