Not much, really. Overall, a great place to work. But perhaps the only thing I can think of is the slow, clunky, and fragmented internal tooling used at Amazon, which means you have to learn new tools specific to Amazon. That is, if you ever leave, none of that knowledge is applicable elsewhere.
Please get someone to create a strategy to unify builder tools under one seamless system, rather than a collection of clunky systems that look like they're from 1999.
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
Introduction, some info about the project. A detailed explanation for why a particular tech stack was chosen. Two DSA questions were asked, the approach was discussed, and time complexity analysis was done.
I first had to complete an online assessment, which consisted of two Medium-level DSA questions and a series of multiple-choice questions about system design. The OA questions are more challenging than those encountered during the actual interview lo
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
Introduction, some info about the project. A detailed explanation for why a particular tech stack was chosen. Two DSA questions were asked, the approach was discussed, and time complexity analysis was done.
I first had to complete an online assessment, which consisted of two Medium-level DSA questions and a series of multiple-choice questions about system design. The OA questions are more challenging than those encountered during the actual interview lo