Interview | Software Quality Engineer | IC2 | ServiceNow

Phase 1: Initial Phone Screening from HR

I started my interview process with an HR phone screen. During this call, we engaged in a comprehensive discussion about my current role and responsibilities, which successfully set the stage for the subsequent technical rounds.

Technical Phone Interview (Round 1)

This round was a technical deep dive, guided by a veteran senior quality engineer who maintained a calm demeanor throughout. We covered a wide array of topics to assess my technical acumen and problem-solving abilities:

1. I provided detailed insights into my daily activities, emphasizing my key responsibilities and achievements in my current role.
2. We discussed the role of Maven in managing project dependencies, and I highlighted its primary benefit in simplifying the build process.
3. I clearly distinguished between method overloading and overriding, demonstrating a solid understanding of object-oriented programming (OOP) principles.
4. I gave a detailed explanation of the structure of the test automation suite I had implemented, showcasing its organization and efficiency.
5. I justified the use of POM.xml over alternative methods, highlighting its advantages in managing project dependencies.
6. I successfully tackled the LeetCode medium-level problem 'Three Sum,' demonstrating my problem-solving skills.
7. I enumerated the significance and use cases of various TestNG annotation methods, such as `@AfterSuite`, `@BeforeSuite`, and `@AfterClass`.
8. I articulated the importance of assertions in testing and how they ensure the expected behavior of the code.
9. I described the Jenkins setup I had implemented and discussed possible improvements and additional functionalities for continuous integration.
10. I explained the implementation of parallel test case execution, demonstrating approaches to achieve scalability and efficiency in testing.
11. I shared strategies I've used to address challenges in finding XPath for certain test cases, displaying my problem-solving skills in web automation.
12. I clarified the nature of the automation suite I developed, categorizing it as BDD (Behavior-Driven Development), KDD (Keyword-Driven Development), and DOM-based.

Following this comprehensive round, I was pleased to receive an invitation for Round 2, which made me believe the interview went well!

Round 2 Interview

This round provided a further comprehensive understanding of various programming concepts and practical application scenarios, significantly enhancing my problem-solving skills and programming proficiency.

1. I was asked to differentiate between overloading and overriding, and I provided an example related to automation, explaining how method overloading could involve having multiple methods with the same name but accepting different types of locator strategies.
2. I debugged several provided Java code snippets, determining their output and explaining the behavior in scenarios involving `System.exit(0)` in a `try-finally` block, method overriding with exceptions in a class hierarchy, and the misuse of a `break` statement within a `try-finally` block.
3. I explained how error codes are typically utilized in APIs when a resource is not present, citing common examples such as 404 for 'Not Found' and 400 for 'Bad Request'.
4. I listed common HTML tags automated in web automation, such as `<input>`, `<button>`, and `<select>`, and briefly explained how they are automated using tools like Selenium WebDriver. I also detailed how iframes are handled in web automation by switching to the frame using Selenium's `switchTo().frame()` method before interacting with elements inside and then switching back to the default content.
5. I was asked to manipulate an array to group negative numbers to the left and positive numbers to the right, for which I presented a Java solution.
6. I outlined the essential components that should be included in a bug report, such as detailed steps to reproduce, expected vs. actual results, screenshots or logs, environment details, and severity/priority assessment.
7. I described the process of using a package from one project in another project using Maven, explaining that it involves specifying the dependency in the `pom.xml` file of the target project.
8. I discussed the considerations that should be taken into account when automating APIs using Newman, including factors like endpoint URL, request parameters, headers, authentication, response validation, error handling, and reporting.
9. I defined the concept of packages in programming, specifically in Java, explaining their use in organizing classes into namespaces to aid in better code management, modularity, and avoiding naming conflicts.

Round 3 Interview

This round was diverse, focusing on cloud management, Linux systems, and practical Java programming.

1. The first question focused on strategies for managing permissions within Google Cloud Platform (GCP). I discussed role-based access control (RBAC) and Google's Identity and Access Management (IAM) policies as effective means to control access to cloud resources.
2. I explained how to conceal a running process in Linux so that it doesn't occupy the terminal and persists even after closing the virtual machine (VM). I detailed how to achieve this using background processes, `nohup`, and `disown` commands to detach processes from the terminal.
3. I implemented a Java program to identify duplicate numbers in an array and print their frequencies. My program accurately calculated the occurrences of each duplicate number, providing insights into the frequency distribution within the array.
4. I discussed the significance of `sudo` privileges and how to become a `sudo` user in Linux, outlining the `sudo` command's usage and its role in executing commands with elevated privileges.
5. I explored methods for connecting to a remote Linux server, including the SSH (Secure Shell) protocol, highlighting SSH's encryption capabilities and its role in secure remote access.
6. I delved into the concept of public-key cryptography and its application in authenticating users to remote servers, explaining how public and private key pairs facilitate secure authentication without transmitting sensitive information over the network.
7. I demonstrated how to edit environment variables in Linux using commands like `export` and by editing configuration files such as `.bashrc` or `.profile`.
8. I provided insights into viewing existing environment variables in Linux through commands like `env` or `printenv`.
9. I shared methods for updating environment variables in Linux, emphasizing the importance of persistence across sessions and system reboots.
10. I confirmed my proficiency and comfort with using the terminal for various tasks, including file management, process control, and system administration.
11. We discussed my prior experience and contributions in previous organizations, highlighting relevant projects and achievements.

Round 4: Hiring Manager Conversation

The final round was a casual 30-minute conversation with the Hiring Manager, where we focused on topics related to the prospective team, work culture, and other general aspects of the role.

I received the final selection call from HR the next day and am currently waiting for the official offer.