Given big responsibility from the start, which is great. There is a lot of trust towards developers.
You won't be given useless projects. Everything is used.
A lot of communication between the business side of a project and the tech side.
Unique, challenging, and interesting problems to solve (although this could vary depending on which part of Amazon).
Values aren't just posted on the walls; they're drilled into everything you do.
Easy to transfer internally to a new job (requires at least a year between teams and a good performance review).
Relative transparency between manager and employees. Although it's only with your direct superior, there isn't much interaction with anyone higher than that.
Use of new and relevant technologies (i.e., they're not stuck using outdated languages/stacks). I'm sure this varies from team to team though.
This sounds trivial, but the office chairs are amazing. They did not skimp on those.
It's generally easy to work remotely. Although it's not really encouraged, it is doable.
Being able to bring a dog is awesome. Seriously, a huge benefit.
Frugality is the one value that you will end up hating. They abuse it to the point of being cheap. Pretty much all the negatives about the company stem from this single value.
The development environment you get isn't that great (although they're slowly getting better). Laptops and desktops just don't have enough processing power to do what they need to do, and they JUST started issuing dual-monitors as standard.
Growing too fast. Some buildings are filled to the brim. They had to take down the interior walls in some buildings to make room for more people to fit. It literally can feel like a factory sometimes.
Instead of being just a mouthpiece for the higher-ups, try learning more about the people who answer to you. Relationships build trust. Repeating Amazon's values at me isn't going to make me better at my job.
I took an online quiz about how I would react in certain situations, then took a coding quiz online. After that, I had an all-day in-person interview. During the interview, I updated a code package based on three tasks, with one-on-one meetings inte
Average interview with 3 rounds: two live coding rounds and one system design round. There was also an initial offline coding round with a time limit of 1 hour. The coding rounds were pretty much medium level.
I had an OA which contained work assessment and coding. Then two VOs were scheduled back-to-back, two months later. Each VO contained BQ questions and a coding challenge. The recruiter rejected me a few days after. Their recruiting process seems to b
I took an online quiz about how I would react in certain situations, then took a coding quiz online. After that, I had an all-day in-person interview. During the interview, I updated a code package based on three tasks, with one-on-one meetings inte
Average interview with 3 rounds: two live coding rounds and one system design round. There was also an initial offline coding round with a time limit of 1 hour. The coding rounds were pretty much medium level.
I had an OA which contained work assessment and coding. Then two VOs were scheduled back-to-back, two months later. Each VO contained BQ questions and a coding challenge. The recruiter rejected me a few days after. Their recruiting process seems to b