SDET Automation Mock Interview - 8+ YOE (Selenium, Java, API, Testing)

Introducing the mock interview setup and the candidate's background in automation with a focus on testing automation.

Discussion on the candidate's experience in automation testing, including backend testing using JMeter and Postman, and experience with Azure DevOps.

Exploration of challenges faced in testing e-commerce applications, such as automating APIs for mail portals and handling delays in automation.

Discussion on API automation challenges, schema validation, JSON requests and responses, and usage of Rest Assured and object mappers like Jackson.

Explanation of the importance of API gateways as a proxy, load balancer, and for verifying and encrypting APIs.

Insights into using Selenium for UI automation, dealing with alerts, handling windows, and utilizing listeners for test case management.

Strategies for prioritizing and executing test cases efficiently, including smoke and sanity testing, automation, and delegation.

Optimizing test case execution, handling resource crunch, and resource allocation during regression testing for timely releases.

Discusses how to approach joining a new team with junior engineers and learning from them, as well as seeking guidance from seniors if needed.

Deals with the situation where team members reject requests for contact and suggests proactive steps to learn and improve, including recording sessions for further understanding.

Addresses the concept of Reverse Knowledge Transfer (KT) and the importance of asking questions to clarify understanding during knowledge sharing sessions.

Feedback provided on communication skills, the need for more specific examples and scenarios, and the importance of showcasing responsibility in quality assurance and communication.

Focuses on the importance of understanding API functionalities, identifying areas for improvement in explaining technical concepts, and emphasizing the significance of knowing core features of Selenium.

Explains the concept of mutable and immutable strings, object creation in the constant pool, and the necessity of understanding Java concepts related to memory management.

Discusses the importance of having a comprehensive test strategy, avoiding over-reliance on automation, and the need for manual testing to complement automation efforts.