Status: Employed, 1.5 YOE\nPosition: SDE1 at Amazon AWS\nLocation: Seattle, WA\nDate: Dec 5, 2019\n\nInterview process:\n\n**Technical Phone screen**: An hour long phone interview based on your resume projects and current work experience. One coding question for the number of islands with a variation of 8 nieghbors instead of 4\nhttps://leetcode.com/problems/number-of-islands/\n\n**Onsite interview (5 rounds):**\n\na. First unique character in a stream of characters : start with brute force, work your way to the most optimized solution. There were some variations and follow up questions. Instead of a string of fixed length, it was a stream on characters. Follow up questions like how to decide end of stream and how to handle billions of characters were asked.\nhttps://leetcode.com/problems/first-unique-character-in-a-string/\n\nb. A team specific question of finding objects in Amazon warehouse using Amazon services.\n\nc. Lunch informal talk with a currently working employee.\n\nd. A variation of the [longest common prefix](https://leetcode.com/problems/longest-common-prefix/)\nInstead of letters in a string, they were arrows. eg. ["->,->,<-" ; "->,->,->", "<-,<-"]\nAlso, the prefix wasn\'t supposed to be in every combination. The question was more like longest common prefix in maximum number of combinations/strings.\n\ne. Entirely behavioral round **heavily** based on the [Amazon LP](https://www.amazon.jobs/en/principles).\n\nf. Half coding half behvioral with the hiring manager. \nCoding question was to find common integers in 2 sorted arrays. For reference : https://stackoverflow.com/questions/4529819/finding-common-elements-in-two-arrays-of-different-size\n\nAll onsite interviews started off with 2 questions related to the [Amazon LP](https://www.amazon.jobs/en/principles)\n\nI received a call from them saying the position had filled up and they had a different team instead. So after the onsite, the new team wanted to schedule one phone interview.\n\nThis phone interview was with a Senior Software Engineer. The question was again specific to the EC2 instances team to find OS popularity. The coding question was that given a csv file of records containing details of EC2 instances; with one column displaying the OS on the instance, determine the most popular OS. Once that was coded; there were a lot of follow up questions:\n* How to test the code\n* How to handle billions of records (Data sharding/Map Reduce)\n* Once the code is deployed on multiple servers, how to maintain the code\n* What ways are there to maintain the code and to track if the code fails\n* If a certain server has some failure, how to determine the cause, how to fix it without letting it affect other servers (1000s of servers ofc)\n\nThis interview had half an hour of coding. The rest of the time was specific to the work the team did and questions on how I would handle the scenarios the team was facing on the day-to-day basis. They didn\'t expect me to answer all questions and understand the scale, but basic understanding of the system, scale and problem solving. The interviewer was looking for multiple solutions as opposed to just one.\n\nAll onsite and phone interviews asked about the time and space complexities.\n\nI received the offer 2 business days after the final phone interview.\n

Status: Employed, 1.5 YOE\nPosition: SDE1 at Amazon AWS\nLocation: Seattle, WA\nDate: Dec 5, 2019\n\nInterview process:\n\nTechnical Phone screen: An hour long 