This interview was for a new grad position. After applying, I got an email from a recruiter asking me to do a short online assessment. This assessment was a very simple debugging type of thing. Basically I just had to fix a few errors in already written code like adding missing brackets on a for loop or changing a less than symbol to a greater than symbol and then hitting the run button (20 mins total). The second part of this test was a "reasoning test" (35 minutes). This part was not that hard either. A few days later I received an email to do an online coding assessment and work simulation. Both of these are proctored. Basically you have to set up your web cam and an online proctor from a third party company will watch you and everything on your computer (tabs, browsers, ect.) to prevent cheating. You are allowed a few library reference websites during the assessment that they specify in the email. During the coding part of this proctored assessment I had to actually write code to solve a problem. You are given a certain amount of time and you have to pass all of the test cases. You can hit the run button as many times as you want. Then once you pass all of the given test cases, you hit the submit button and the system will check if you passed the hidden test cases. The second part of this assessment was the work simulation. I actually really liked this part of the interview process. This section of the process tries its best to mimic an actual on the job setting. You have to watch videos that are from your point of view and when the people look at the camera they are talking to you as if you were in the room. You are placed in certain scenarios throughout this process where you have to make important decisions such as delivering a project late while having all requirements or delivering a project on time while missing some key features. After passing the proctored assessment, I was sent an email inviting me to an onsite group interview. Amazon paid for everything. Plane tickets, hotel, Uber transportation costs, and food were covered for each day I was there. There were two parts to the group interview. The first part judged us on our teamwork and individual leadership skills. We had to come together as a team to pick which piece of code was most efficient and which was the least efficient. The second part was all individual work. We were given laptops from Amazon to use. They are all set in the language you choose. For example, if you choose C++, Visual Studio would be pre-loaded when you open your laptop or Eclipse if you choose Java. I was given a large complex pre-written code with multiple classes. You have to first study the code itself for a while to understand what is going on. There are functions/methods and different parts missing that you are assigned to fill in. This section of the interview requires very strong Object Oriented Programming skills. This part of the interview is why I didn't get selected. I mostly spent my time preparing for white board style challenges. As you are coding during the onsite, you will be pulled to the side twice by different engineers to discuss your code and how you could possibly optimize it. The two people who pull you to the side have a lot of power in determining whether you get the job or not. They will type/write notes on what you say to them so make it count. After all of the interviews are over, they will review your code that you wrote, the notes from the two interviews that pulled you to the side, and the notes from the person observing first part of the onsite(teamwork/leadership part). Then they will make a decision based on that. I'm not sure if the previous assessments that were taken before the onsite hold any weight when they make a hiring decision or not. I received an email the next week stating that I had been rejected. Also they do not provide any feedback as to why you were rejected. My advise to future applicants is to know in depth about polymorphism, inheritance, and other Object-Oriented principles. Definitely practice whiteboard style problems for the proctored part that takes place before the onsite. Also practice more OOP by creating an application yourself involving multiple classes and OOP principles. When I had my interview, I didn't brush up on my OOP nearly enough which cost me the job. Too much of my time during the onsite was spent figuring out how to use and manipulate certain variable/methods from other classes. After messing around with it for a while it started to come back to me, but by then I had ran out of time before I finished. If I was assigned white board style problems, I would have nailed it.