After applying, a recruiter reached out after one week to discuss the role and process. She was pretty raw and didn't have much information.
I was emailed instructions to complete a timed (2-hour) test that focused on how to solve typical engineering management problems, such as architecture and project management.
I thought this was the best and most realistic/relevant part of the interview process. I did well on this, and the recruiter reached out one week later about setting up the last (virtual) round interview, consisting of five interview sessions, one hour each.
Four sessions were with SDMs (some Senior and some not). I believe I did well on three of them but bombed on one, as the questions were pretty tough and I couldn't give a good response. Unfortunately, I came to find out that the interview I didn't do well on was likely the hiring manager for the role.
There was only one tech-focused interview, which consisted of meeting with a couple of Senior SDEs. This was pretty straightforward, but they asked too many questions and rambled on, not giving me much time (20 minutes) to work on the system design, which luckily wasn't difficult. I still had to rush and couldn't finish with an optimal solution or have time to discuss it.
Mostly around LP, in the format of 'tell me about a time...'.
One system design question was focused around designing an inventory system.
The following metrics were computed from 1 interview experience for the Amazon Software Development Manager role in San Diego, California.
Amazon's interview process for their Software Development Manager roles in San Diego, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Amazon's Software Development Manager interview process in San Diego, California.