The interview process is pretty straight forward. You will have total of 5 rounds. First round will be a written pen paper based test which consists of usually 2-3 computer programs to write (Any language). Don't worry about the exact solution. the codes on your page should reflect your approaches. if they found your approach write they will shortlist you (P.S. I had two programs, one of them was correct although not optimized but i was shortlisted as the approach I took was promising) Second round can be anything from Coding round, test data generation-test case enumeration-test plan round. Coding Round: In the coding round the interviewer will present you the same codes you have written earlier (depends, in my case it happened) and will ask you to come up with some other efficient solutions. and will give you some extra coding problems to solve. First he will ask you to tell your approach in solving the problem and then he may ask you to implement it on paper. Once you have given the approach further to this you have to give more optimized solution in case the approach you have given was not very efficient. Duration of this round would be approx 45 mins to 1 hour. Key point to succeed in this round is just don't give up on the problem, put efforts in coming up with different solutions does not matter if they write, do not keep your thought process in mind keep speaking and let the interviewer know how you are thinking about the problem. Testing round: This round will broadly consist of 3 portions- 1. Test case enumeration: you will be given a scenario and you have to come up with different possible use cases. Number of use cases will not matter but what will matter here is scope. You have think about testing in a broader sense. Include all aspects of the that scenario. Think about scalability test cases, performance test case, networking if involved, database etc. Also keep your focus on every kind of device you can have this scenario like web mobile, fire tv etc. 2. Test data generation: This should be easy part for you . you have to just come up with all possible data sets for the given condition. Include positive scenarios, negative scenarios, Boundary cases, equivalence partitioning and more if you can think of. 3. Debugging: This is a kind of confusing round if you are not prepared for this. You will be given a problem scenario and you have to debug it. Debug here means you have to come up with approaches needed to solve that problem. Same as previous sections think in a broad sense what could be wrong like it could be issue with database, networking, Scalability, OS, UI, code error, memory leak, etc Bar raiser round: This round will be about everything asked previously. Just you will be grilled more. Don't stress out just keep coming up with ideas in a broader sense. Once you have cleared all this round you will be called some other day or next day for a F2F round with manager of it can be video conference depending upon the location you have applied for. he will ask more of behavioral type questions and all the same stuff asked before All the best!

Ancient- the way the entire interview was handled, the questions asked, and the conversations reminded me of applying for an associate-level position. The interviewer went on to say, "Try to break the code, that's what QA is supposed to do." I agree that it is part of the job, not the entire job.