The culture of software engineer ownership of Amazon's offerings. I have repeatedly pitched ideas which Amazon funded two-pizza teams to pursue.
General engineering culture. It is expected that you have your own ideas and push back politely and with data in hand if you are asked to do something that you think is not the optimal thing to do right now. Yes, even as a software engineer intern. This leaves some interns slack-jawed; from other employers, I guess they sometimes expect that someone will tell them exactly what to do.
Amazon (most certainly Amazon Web Service) expects and rewards engineering and operational excellence, stuff I happen to love and specialize in. It has such scale that it is a top, perhaps the top, place to work to drive engineering excellence at a giant scale.
Amazon has world-class executive management. In the Amazon Web Service space, I know and can vouch for pretty much every Vice President or higher. The execs here are deeply technical while also focusing on employee happiness and career path, and typically have big, actionable vision for the future, too. Yes, really.
(This is not actually a con in many ways, but many people would say) that being on pager duty for your service as a Software Development Engineer is a con. After all, software engineers want to write code more than get paged at night for some operational issue. That being said, being on-call for your stuff is deeply ingrained into the Amazon engineering culture and goes hand in hand with "engineer ownership of products." Being on-call also gives you license as the on-call SDE to insist on a minimum engineering quality to protect your customers from operational problems. My point is, if you do not want to be on pager on-call for your service, definitely do not join Amazon as a software engineer.
Generally speaking, if you don't love being a software engineer, dread going to work, and are in it just for the paycheck, you probably really don't want to join Amazon. The people that I see thrive and be enthusiastic at Amazon the most are people who love what they do and have fanatical ownership (I am that way, so that's why I love being at Amazon so much, but I realize not everyone is). Note that you don't have to work 80 hours a week either; I choose to work 45-50 hours a week. Indeed, I was promoted to Principal SDE about two years after I decided to work a lot fewer hours a week.
It was good, but they didn't respond to me for a long time after 14 days. I asked them why, but they didn't respond back.
First round: Hiring manager screening. This covers leadership principles important for the job. Final round: Five interviews with a writing assessment. Each round covers around three leadership principles. All interviews are behavioral.
Initial phone call with a recruiter, followed by a 90-minute coding assignment. This consisted of standard LeetCode-style algorithm and data structures problems, loosely related to the specific role and easy to prepare for by using normal resources.
It was good, but they didn't respond to me for a long time after 14 days. I asked them why, but they didn't respond back.
First round: Hiring manager screening. This covers leadership principles important for the job. Final round: Five interviews with a writing assessment. Each round covers around three leadership principles. All interviews are behavioral.
Initial phone call with a recruiter, followed by a 90-minute coding assignment. This consisted of standard LeetCode-style algorithm and data structures problems, loosely related to the specific role and easy to prepare for by using normal resources.