Amazon has an odd culture, due to the fact that it's made up of lots and lots of relatively small teams. While this promotes lots of bottom-up innovation, it also leads to having to sometimes deal with a lot of people to get things done, and their priorities don't always line up with yours. It makes for an environment where informal relationships make all the difference.
If you're on a team responsible for systems with significant software issues or a team that hasn't made the investment in documentation to get the support team to take most pages, pager duty can be hell. It's a lot better today than in times past, and there are corporate-level initiatives in place to drive changes for the better. It seems to be working.
Like all workplaces, if you don't set some boundaries, Amazon will take all of your time and ask for more. During peak season, expect to work lots of extra hours if the heat is on your team. Otherwise, if you're burning out, you'll need to have enough spine to set some boundaries.
On the whole, you're doing pretty well in an environment where others founder. That's good; let's have more of that.
Pay more attention to the data warehouse and HAM systems, though.
I was contacted by a recruiter, and then I had a phone screening interview. Usual questions about Amazon Leadership Principles were asked, and I answered them using the STAR methodology and data-driven situations. Surprisingly, I received a rejection
1-hour phone screen. If successful, this is followed by: * A 5-person loop interview (1 hour each) * 4 behavioral interviews based on Amazon's Leadership Principles * 1 technical design interview Breaks will be provided in between. Additiona
After the initial phone screen, I went to the final stage, which consisted of five interviews spread across two days. I spoke with a hiring manager, some SDEs, and a TPM. There were many situational and behavioral interview questions, with one system
I was contacted by a recruiter, and then I had a phone screening interview. Usual questions about Amazon Leadership Principles were asked, and I answered them using the STAR methodology and data-driven situations. Surprisingly, I received a rejection
1-hour phone screen. If successful, this is followed by: * A 5-person loop interview (1 hour each) * 4 behavioral interviews based on Amazon's Leadership Principles * 1 technical design interview Breaks will be provided in between. Additiona
After the initial phone screen, I went to the final stage, which consisted of five interviews spread across two days. I spoke with a hiring manager, some SDEs, and a TPM. There were many situational and behavioral interview questions, with one system