Background: 3 years in front end development\n\nInterview 1: \n* System Design\n\t* Was asked to go through the component architecture of an application\n* My thoughts:\n\t* I struggled with this as the interviewer was asking about some things I haven\'t had the chance to implement/work with yet (authentication) and I felt like we didn\'t really connect that well during the interview. \n\nInterview 2:\n* Leetcode questions off of amazon list\n* Behavioral questions\n* My thoughts: \n\t* This was very straight forward, the time for the question was very limited though so it was good that I recognized the question and was able to do it quickly. After I finished this and the behaviorial, instead of giving me time to ask questions the interviewer gave me another leet code question lol, also from the list. I didn\'t have time to finish this obviously and the interviewer was okay with it, just wanted me to talk through it\n\n\nInterview 3:\n* Custom DS&A question in javascript. Probably around easy level\n\t* Follow up question was to create a new function object constructor and was asked how to add my function as a method (the answer was to use the .prototype property and add it as a function, basic OOP stuff)\n* Behavioral questions\n* My thoughts:\n\t* Really enjoyed this interview as I had good conversation with the interviewer and I thought their question was very similar to what you would do on the front end.\n\nInterview 4:\n* Behaviorial (bar raiser because the people interviewing me were not from the team I was interviewing for)\n* My thoughts:\n\t* This was very straightforward and I thought we had good conversations\n\nInterview 5:\n* Front end interview:\n\t* Behaviorial questions\n\t* Was asked questions about javascript, closures, event loop and asked to implement some stuff similar off of https://bigfrontend.dev/\n\t* Also asked to implement a picture of a component using html. It was a very simple picture of a form basically.\n* My thoughts:\n\t* Straight forward as well and I thought the interview went okay and I was able to answer their quesitons.\n\nResult:\nA day later I received a rejection and my feedback was that even though my frontend, behavorial and conversations went well they thought my system design wasn\'t as good enough for the role I was applying to. Overall I thought the feedback was fair and happy to get in some interviewing practice with Amazon.\n\nMy recommendation for other front end engineers is to practice javascript really from https://bigfrontend.dev/ and also make sure you understand javascript (going through https://javascript.info/ was very helpful). There are a lot of other front end posts for amazon on leetcode as well so that was good. I also recommend just being yourself, being friendly and being engaged when talking to the interviewers. In the end it is about whether or not they want to work with you and the interview is just a way for them to help learn more about your communication and skills.\n\nFor the behaviorial questions I came up with around 15 stories based off the leadership principles and was able to refer to them during the interviews. This really helped make these questions a lot easier and really took the mental load off when interviewing.

Background: 3 years in front end development\n\nInterview 1: \n System Design\n\t Was asked to go through the component architecture of an application\n My thou