Discover the Best Amazon Invoice Sample for Quality Assurance

Amazon invoice sample for Quality Assurance

Hello friends Welcome to our YouTube channel artof testing.com I am Rohit agrawal and today we'll be discussing about cracking Amazon's QA interview and also Amazon's SZ interview so before we start let me give a brief about myself so I have around 10 plus years of experience throughout product based companies including but not limited to snapd Lime Road and Amazon so uh now let's before we start let me give you the brief about how we will be dividing this video so in the first section of the video we will be actually talking about the Amazon's interview process and in the second part we will tell you and I'll guide you through the various ways through which you can prepare for these interviews and even come out with flying colors so let's get started before uh uh so now when we talk about Amazon's QA interview or an S interview it is basically first is a phone screening round which is again followed by five different sets of on-site interviews with some candidates this these number of interviews can be increased from 5 to 6 now in this five rounds of your interviews it includes one your manager's round of for the team in which you would be applying your reporting manager if you go through and crack this interview round the other is a bar Razer round at Amazon It is believed that a bar raiser is there to evaluate you and understand your fitment in Amazon as an organization and the basic Theory they follow is that your skill set or your uh your knowledge should be more than the 50% of the present engineering resources as at Amazon so the bar rors round is to ensure that the bar of Amazon is kept high and it is not compromised so in your uh in your five round three rounds would always be core technical rounds where you would be gauzed on the technical expertise in the two rounds and the remaining two rounds it would be on your uh testing skills so every round would be basically on testing skills but in these two rounds they will focus more on the testing principles how you plan your things how the test strategy how you test plan how how you write test cases how how you coordinate and then some behavioral questions that would help them understand you as a person or a source so these are the five set of rounds now let's talk about the various ways or the tips through which you can prepare and crack these interviews now Amazon always works on 14 principles plus two 14 + 2 which is 16 so 14 are the core basic principles on which each employee is supposed to work the link to these principles is also there in the description of this video video or else you can always Google it out and you'll get the 14 principles that Amazon follows please bear in mind that in all your five to six rounds or the phone screen rounds you will always be evaluated on these principles the technical answers you give the behavioral answers you give will always be evaluated on these 14 principles inet shell each round actually uh is is having two to three of these principles assigned so the evaluator at that round knows the three principles on which he has to EV he or she sorry has to evaluate you so please always read those principles and if you give your technical answers or the behavioral answers always keep that in mind now coming to the technical rounds so for me I was able to solve my technical questions using Java as a programming language and shell scripts however Amazon does not force you to write your code in any specific language you can always choose the language you prefer so you would be aware that any product based company uh or a good a big company I an MNC would have various teams so you should always read about the team where you're applying the kind of work that they do how your skill set would bring uh would add to that team's work and what are the new things or the benefits that would come across when you are are hired into that team so please read about that team and when uh before you actually have an on-site interview at Amazon please have some time so that you are able to solve technical questions online you can visit websites like geek for geks or hacker rank where you can test your skills and always solve problems from medium to higher complexity and always whenever you are attempting that question please bear in mind the space complex or the time complexity of your solution that would be there so it would always give a good impression when you give these answers or the answers to the technical questions with these things and then it would actually give a good impression about yourself onto that interviewer now for a given technical questions there will always there can always be more than one ways of solving it where one where you where the uh where the type of answers you give may be uh time bound or maybe Space Bound so if you if you know that there are n ways to which you can solve a given technical problem it is always good that you tell the interviewer about all these approaches and which one you believe is the best approach and why it is so this will help them understand that you know things in detail the other thing that you should always bear in mind is that whenever you are attempting any any question or if you have any doubt regarding that question please be vocal enough to clear your doubts always remember do not assume things anyways as a QA or a test engineer you always know that that we should not assume things and what assume means in our terminology so never assume things always clear your doubts it at it at many times the interviewers leaves the questions half begged so that they would understand how you attempt that question whether you have that that uh that confidence in you to clear those doubts or not so always clear your doubts never assume things whenever you have be and and always make the interview R interactive please always answer or whenever you have doubt always ask so you should not think that it will give a bad impression it will actually give a good impression about how you approach problem statements now coming to the behavioral questions so some questions are always there which are frequently Asked in any product based companies for example what was the most toughest challenge you faced in your professional Journey how did you overcome that problem now the other question that could be asked to you is tell me some scenarios where you actually failed and please never answer that you never failed because each one of us would have failed at some point or the other so if you say that you have never failed it always tells the interviewer that you are faking yourself and you're not being true to him or her so always remember that whenever you answer this question you bring something and then you make that your strongest point so yes I faced this problem but this is how I tackled it this is how I got the learning and this is how I made it a point that in future I do not repeat this mistake it it's okay to commit mistakes but it's not okay to repeat those mistakes so always bear that in mind now in the test strategy and the test planning questions you should know the difference between test strategy and test planning how many approaches or what are the technical or uh test planning that you would be doing functional non-functional testing that you would be doing what are the different sets of functional testing non-functional testing always do load testing and performance testing which many of times people forget to do the other thing that you should bear in mind is the ede cases so please always always Corner cases and H cases should be considered in your test plan and test strategy so these are the ways through which you can prepare and crack this interview please let me know in the comment section if you need further details and I would be happy to help you out in that way if you like this video and it was helpful to you please do not forget to like give a thumbs up like this video And subscribe to our channel artof testing.com for more details you can always visit our website artof testing.com which captures many of things that would help you grow as a manual tester as an automation tester and as a professional overall thank you and keep testing bye-bye