Do you believe automation is more important than manual QA?
Want the inside scoop on your own company?
Check out your Company Bowl for anonymous work chats.
Check out your Company Bowl for anonymous work chats.
In a QA Engineer interview, expect questions that test your understanding of the software testing process. While most questions will test your competency, the interviewer may also want to see that you can build a high-level strategy for preventing and resolving bugs and defects.
What is the difference between quality assurance, quality control, and software testing?
With this question, you can demonstrate an understanding of how these tasks are interrelated. Mention that quality control is where test results are analyzed and defects are identified, whereas quality assurance refers to the preparation of product standards and requirements. Testing is when the final product is checked for vulnerabilities.
Describe positive and negative testing.
The interviewer likely wants to see that you comprehend the importance of negative testing. Explain that positive testing ensures that the product works correctly, while negative testing ensures that if the user inputs invalid information, the product will respond accordingly. You may consider sharing a hypothetical example of a time when negative testing would be particularly valuable in identifying a bug during production.
What is build and release?
With this question testing your technical skills, you can display your mastery of the quality assurance process from start to finish. A successful answer would clarify that build is when software is handed over from the development team to the testing team, while release is when software is handed over to the user.
Do you believe automation is more important than manual QA?
What would you do if management asks you to approve a release with critical defects?
Hypothetical question: you have a team of ten software developers that have worked on a product for 5 years. They now have to develop a new version of this application but only have 3 months to develop and test it. What would the QA estimate be?
Have you ever stopped a line for a quality issue and how did you go about it? Can you provide examples.
What instrumentation are you familiar with?
In a typical sql query, what would happen when there are no bind variables? What happens when you put bind variables, does it help the performance or not? If so, how?
What exact experience with test automation have you had?
Have you had a defect that was found by a customer that should have been caught during the testing phase? If so, how did you handle the escaped defect.
Explain the difference between an inner join and outer join.
If you had a great idea to implement something new for a CA software product but management wouldn't take your word on it, how would you convince management to go along with your idea?