"Employers looking to fill quality analyst positions want applicants with the problem-solving capabilities to detect software-level errors and make improvements to their products. In an interview, expect to be quizzed on technical questions that will test your analytical and critical thinking skills. You may be asked to resolve a programming error or explain the uses of a particular function."
↳
I won't believe, both r important. we are doing documentation and writing test cases manually, then we are converting manual test cases into test scripts and executing them. It is the process of testing life cycle. Less
↳
In these sorts of interviews you really need to drill down and understand what the interviewer is looking for. A good way to simulate a real interview experience is to do a mock with one of the Workday QA Automation Engineer experts on Prepfully, rated super strongly on TrustPilot... prepfully.com/practice-interviews Less
↳
Your question is somewhat vague. When it comes to service tests then automation is more important; When it comes to graphic design manual is more important. when it comes to regression tests automation is more important than manual testing. Less
↳
No, We should not release the application with critical defects. Make sure the management team how the impact of the critical defects in the application without fixing and quality of the product not guaranteed. Less
↳
Decline to release and ask if I can have time to fix the defects
↳
This was my favorite question as it completely illustrated how bad these guys were at interviewing. I began to ask the manager that asked the question for more information and he snapped back at me " You have all the information you need!" Really? He might as well have asked me how much it costs to build a house. Because the answer would be the same - "I need more info and detail in order to give you my estimate". Any QA worth their salt will asks tons of questions in order to understand what it is they are working on. In the end I told the panel that if I had worked on the product or similar products I would base my estimate on prior experience. If I had no prior experience I would research historical metrics from similar projects and also discuss those historical project actual development/test hours with other QA and developers to come up with an estimate. Less
↳
I said "Rather than answering with the standard 'I will need more information' 'lets make it less hypothetical. "'Before I can give you an answer I will need to gather more information from your people'. This gives the interviewer an out when they don't have any additional information, and you the chance to get the information you need" Converting from 'Hypothetical' to 'Real' helped make my answer stand out from other candidates. It also made it harder for the interviewer to return with the Hypothetical "you have all the information you need" Less
↳
Too long to write, they did a great job making sure I was not just putting popular tag words on my resume to make me look more appealing. They do a great job of finding out the truth. Less
↳
Before I would stop a line I would make sure that I had evidence which I could use to justfy the stop. If this evidence was insufficient to stop the line or if the decision by the policy holders was not to stop the line but I felt that the problem was important enough to the customer I would escalate the problem to the Director of Quality. Unfortunately I could provide no examples that actually showed me being effective because they were all company confidential. The minor issues I could describe were not very impressive Less
↳
I'm a synergistic person. I find ways to be more efficient and share what I learn with my coworkers. I explained that if I share what I know that made my job easier, then perhaps that coworker will remember me and share what they learn back in the future with me as well as with the entire corporate structure. This is synergy. Less
↳
I told him that I spend time out on the floor talking with operators to tell them about the quality issues we're finding and how to eliminate them. I told him that quality would get very better as we worked together on the production floor. Less
↳
I followed up with the customer and asked how they discovered the defect. I then determined what part of the troubleshooting process we missed that would have revealed the defect to us. Less
↳
I would try to create a form of a prototype of said idea and present it along with taking ownership and compassion for the new feature. Less