Pay is decent.
Diversity and inclusion - it's the same crap for everyone, no discrimination.
Work-life balance - I spend most of my day retrying the tools till things work, and I go at 5.
Forced (now that CodeCommit is gone) to work with the worst tools in the industry. It feels like they are designed to waste time (see the CEO's post on LinkedIn about migrating to Java 17 taking 50 dev days. This is true at Amazon due to the tools).
The philosophy (tools are evidence) is that they don't trust developers to do the right thing and prevent you from having any form of control.
Leadership Principles - not a single one holds true. The whole thing is just "do the minimum and PR it to match the principles".
Quality is a swear word. The only guideline is short-term gain only.
Don't try to introduce new concepts or frameworks. If it's not invented here, this won't go.
Toxic. There are some amazing people, but for the most part, you'll get comments on your PRs (called CRs because Amazon must rename everything for the sake of being different) based on the developer's identity, not the code.
Worst medical plan, no food or anything. With a wife and 2 kids, consider an extra $5000-$8000 a year you'll spend on medical co-pay and food compared to other companies.
You'll learn nothing besides the AWS stuff, which apart from SQS, SNS, and EC2 are mostly useless compared to the competition.
You'll work with the same methods as the industry did in 2006. Not a single concept has progressed since. You'll get to do that in Java 17, but the methodologies are the same.
No Agile (though we delude ourselves that we have sprints).
Huge monoliths with architecture that's based on teams' composition rather than solid logic.
Get rid of all the internal tools. There isn't a single one that's actually worth the effort.
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