Technical Interview: The first technical discussion covered testing methodologies, design patterns, and my knowledge of Linux systems. Despite making it clear that my Linux expertise was limited, the process moved forward. Home Task: The task comprised three levels: UI tests, API tests, and a GCP-based task involving VM creation and test execution. I completed all levels within a very tight 2-day deadline using Terraform and GitHub Actions workflows. Strangely, my repository saw 240 clone attempts during this period, likely due to some bot or automated process, raising concerns about transparency and security. Post-submission, there was a lack of communication. I had to follow up with the manager to confirm receipt, and it took over 5-6 days for them to schedule the next step. Final Interview: What was supposed to be a discussion about my submitted task turned into a 30-40 minute interview focusing on Kubernetes, Linux, and bash scripting. Despite earlier clarifications that I’m not a DevOps expert, these irrelevant topics dominated the session. There were no questions about automation—the core focus of the role.
Senior Qa Interview Questions
5,123 senior qa interview questions shared by candidates
Tell me about your self
Just very simple questions on QA
What do you know about Amgen?
If given a chance to learn new tools and train your peers would you do that ?
Nothing.Difficult as such,if you know the coding
How can you access the variable of one js file in another js file?
How to identify the hidden elements in selenium?
How do you make sure automation is effective during agile sprint
Questions related to Selenium, TestNG, and core java concepts and Java program
Viewing 4211 - 4220 interview questions