SDET (Software Development Engineer in Test)
Interview Date
2022
Result
Not Specified
Difficulty
Medium
Rounds
4 rounds (HR Interview, Technical Interview 1, Technical Interview 2, Techno-Managerial)
Drive Type
Full-Time
Topics asked
Detailed experience
College: Not Specified
Interview Date: 2022
Interview Type: Full-Time
Result: Not Specified
Difficulty: Medium
Rounds: 4 rounds (HR Interview, Technical Interview 1, Technical Interview 2, Techno-Managerial)
Topics Asked: HR questions, Java (OOPS concepts, Exceptions and their types, WAP to handle Exceptions), Selenium & Cypress (difference, architecture, Implicit Wait & Explicit Wait and their methods), DSA (WAP to Reverse words in a given string), Project discussion (roles, responsibilities, challenges), Automation & Manual testing, Real-time issues/challenges in automation, Scenario-based problem-solving.
The interview process consisted of 5 rounds, starting with an HR interview for resume shortlisting. The HR round included questions like "Tell me about yourself," "What experience do you have in this field?", "Do you have experience in Automation?", and "What are your salary expectations?".
Round 2 was a Technical Interview. The interviewer asked for an introduction, preferred coding skills (Java and Javascript), OOPS concepts used in projects and their rationale, Exceptions and their types, a program to handle exceptions, exceptions encountered in Selenium code, and real-life examples of exceptions. Questions specific to testing tools included the difference between Selenium and Cypress, their architectural differences, and the difference between Implicit Wait and Explicit Wait. A coding question was given: "WAP to Reverse words in a given string."
Round 3 was also a Technical Interview. This round focused on project discussions, including roles and responsibilities, challenges faced, and how they were handled. The interviewer also asked about comfort with both automation and manual testing.
Round 4 was a Techno-Managerial round. After an introduction, questions were asked about real-time issues and challenges faced during automation projects. A scenario-based problem was presented: how to prioritize testing multiple scenarios with limited time.