Interview questions: recursion, probability
Qa Engineer Interview Questions
Qa Engineer Interview Questions
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.
Top QA Engineer Interview Questions & How To Answer
Question #1: What is the difference between quality assurance, quality control, and software testing?
Question #2: Describe positive and negative testing.
Question #3: What is build and release?
53,458 qa engineer interview questions shared by candidates
The brain teaser: what is the last digit of 2007 power 2007
test life cycle in assurance
First interviewer asked about potential scenarios to test APIs. Many follow-up questions based on my answers. Next interviewer, asked me to draw object-oriented design for a given animal hierarchy. Then, write code to find if the given coordinates are part of the four corners of a rectangle. Next, flip two dimensional array. Bar raiser asked many questions about i18n, testing web services etc. Behavioral questions such as examples of situations where you had conflicts with the idea of the majority of the team, approach when you find bugs after release etc were raised in each interview.
What is difference between abstract class vs non-abstract class in Java.
You are given a beaker and a single bacterium, which will reproduce into two bacteria in exactly 1 minute, at 12:00 noon. It is full at 1:00 pm. When was it half full?
I was asked to introduce the IT/supporting tools that i am familiar with?
There are 2 ropes not identical but their burning time is 60 mins.You have to measure 45 mins using both of them.
informations tirées de mon cv et de mon expérience de jeunesse
The guy asked me if I know what the quality means. His example of quality was super-expensive designer bags that his girlfriend impulse-buys on the internet. No, that is NOT a joke. He was visibly not interested in the whole process, I could tell. Not a single technical question, and his answers to mine were vague. My guess is he is a lousy programmer, even though he doesn't have to be one to do his job.
Viewing 61 - 70 interview questions