Amazon's pay is very competitive. And with the number of smart people working for the company, you will learn a vast amount, especially since there is no real limit on what frameworks and languages a team uses.
It is a vast corporation. As such, you are just a worker ant; you will have very little sway in a greater sense.
If you plan on being a developer that codes a lot, you will not be able to move much further than SDE II, as Principal engineers act more as TPMs than developers within Amazon as a whole (barring some outliers).
Create structures that allow for those more technically inclined to move upward to Principal Engineer. The current structuring leaves an awfully sour taste in everyone's mouth.
The promotion and compensation evaluations are completely ridiculous. There is no way everyone will meet every requirement; you are just fooling yourself. Furthermore, expecting someone to do the work of the next level for an extended period of time, but not receive that pay, is disgusting.
Coding + Behavioral questions: The interview will include a combination of coding challenges and behavioral questions, focusing both on your technical problem-solving abilities and on how you collaborate, communicate, and approach real-world team si
Interview process: Online assessment, followed by a recruiter screen, then four technical rounds — two coding interviews focusing on algorithms and problem-solving, one coding interview like low-level system design, and one system-design interview ev
Recruiter reach out -> OA. Solved one question completely and passed half of the other question's tests. Later, I was rejected due to lack of experience on my resume. I actively asked if there were any SDE I positions, but they were unable to provid
Coding + Behavioral questions: The interview will include a combination of coding challenges and behavioral questions, focusing both on your technical problem-solving abilities and on how you collaborate, communicate, and approach real-world team si
Interview process: Online assessment, followed by a recruiter screen, then four technical rounds — two coding interviews focusing on algorithms and problem-solving, one coding interview like low-level system design, and one system-design interview ev
Recruiter reach out -> OA. Solved one question completely and passed half of the other question's tests. Later, I was rejected due to lack of experience on my resume. I actively asked if there were any SDE I positions, but they were unable to provid