They sent me a 3 part assessment: debugging, coding, and workflow assessment. The debugging was challenging. I did not get all test cases to pass on the coding challenge and I did not get the optimal solution, but I still made it to the next round. At the end of the coding challenge, they gave me a workflow survey where I'd have to choose between two statements of which I agreed with more (I'm pretty sure this was to evaluate whether I'm severely depressed, as one I had to choose between was something like "Sometimes I think my life will never get better" and "My life is incredible"). I was honest and so chose some positive statements and some negative, but I'm pretty sure if you answer all positive or all negative it's a red flag. The workflow assessment was the easiest. Keep the amazon leadership principles in mind, and you'll ace it. In general, never push code without a code review and prioritize the customer's needs over the due date. I passed the assessment and they had an 'onsite' 3 coding assessment with interviewers. Each round they asked me 1 or 2 behavioral questions (prepare several projects to talk about in the STAR format), then moved on to the coding question. Round 1: Recursive: The interviewer's camera was not facing his face so it was difficult to read him. He approved my solution early on and redirected me if I made mistakes. At one point he had me go through a test case when checking my work, which was helpful. I didn't have enough time at the end to fix a recursion bug, but the interviewer said he thinks I would have gotten it if there were a few extra minutes. Round 2: Data Structures (It was a graphing question): The interviewer was very harsh and kept interrupting me while I was explaining my approach. I don't even think I got a full sentence in. He didn't let me code until the last 5 minutes, which was too late. I'm not really sure if he had something personal against me, or if he was just a generally rude person. I think in general make sure to use data structure and algorithm buzz words when explaining your approach so the interviewer doesn't have a chance to misinterpret what you mean (ie: don't start with explaining how to implement djikstra's algorithm, start with "I will use djikstra's algorithm" and THEN explain how you will implement it). Round 3: Object-Oriented Programming: This round went the smoothest. The interviewer asked a follow up question about optimizing the solution.

OA followed by a technical phone screen round. Was later invited to the final stage which was a 3round interview loop of 3h. each interview was 30min technical and 30min behavioural