Amazon Software Development Engineering reviews

3.5

56% would recommend to a friend

(6,758 total reviews)
avatar

Andrew Jassy

40% approve of CEO

53% positive business outlook

Software Development Engineering employees have rated Amazon with 3.5 out of 5 stars, based on 6,758 company reviews on Glassdoor. This indicates that most Software Development Engineering professionals have a good working experience there. Amazon is rated in line with the average (within 1 standard deviation) by Software Development Engineering professionals compared to other employers within the Tecnologías de la información industry (3.9 stars).

Reviews by job title

7K reviews
1.0
Jun 13, 2008
Recommend
CEO approval
Business Outlook

Pros

The starting salary is extremely competitive. The hiring pipeline is also extremely efficient, empowering Amazon.com to court and successfully hire some of the smartest professionals out there. Unfortunately, those are the only positive thing I can say about the workplace itself. Outside of work, when you aren't getting paged up the wazoo by legacy applications no one in the company has any idea about, life is awesome. Seattle is a beautiful city with plenty of culture and no lack of things to do. A nice side effect of working at a place with insanely high turnover and high starting salary is that you end up with tons of young professionals, all new to the same environment and in the same stage of their lives ~ if you're one of them, there are plenty of people to meet and hang out with.

Cons

Amazon does not value its employees and this severely affects every aspect of worklife. Employees are treated as replaceable, renewable resources, not as members of a working team to grow with the company. The focus is on new hiring with the expectation that any semi-intelligent employee will leave within the first two years. New hire salary is incremented at well over 2x the rate that top members of a team are given raises. New folks regularly make 5-10K more than their tech leads who are the highest contributors on the team, breeding poor sentiment. Promotions are easily promised during crunch times requiring 100-hr work weeks and just as easily forgotten when promotion or bonus time actually does come around. Additional responsibility, both in person and in project management, are regularly compounded upon top contributors without promoting individuals to the authority such a position requires, making it difficult to get things done in a culture where cross-team cooperation is like pulling teeth. In terms of quality of work, there is no value given to developer time and no emphasis on the importance of infrastructure. Build tools are down daily and ownership is a lost concept. Scapegoating is a regular occurrence when site-wide post-mortems require heads to roll. Few things are properly documented, rarely anything is QA'ed, and as all original product engineers tend to leave within two years, nearly everything is a legacy application. The product-development lifecycle emphasizes pushing new features/products out quickly, leaving little or no time for QA cycles. The same engineers who coded the features under crunch are sometimes asked to do QA sign-off. Yet when they come back to management with lists of blocking/non-blocking bugs, they are asked to hide the lists and just to provide the sign-off. The result ends up being shoddy services held up by a company of already-overworked engineers serving constant on-call rotations who know they will be paged, but even knowing this are rarely able to figure out how to even begin debugging the systems. When I joined, every single person on the previous generation of my team had left. I later discovered that this was a regular occurrence which had already happened for the third time. All the great projects and career opportunities I had been sold on before joining were back-burner items reserved for interns and other people they had yet to sell a permanent position to. Regular employees were delegated to continuous on-call rotations for applications no one knew anything about and left to debugging bugs hardcoded years before. The overwork, stress, and lack of self-fulfillment created quite the back-stabbing team. In my first week as a new hire, I was angrily told by my mentor "Every time I sit down to get something done, you ask me a question." Later the same day, I was told by my manager "So I've talked to the team and they say you never talk to them or make use of their expertise ~ you simply putter in a stuck corner when you could just ask." As my time there progressed, I regularly discussed the lack of opportunities and the disparity between my expected and actual roles with my manager, who always promised clear action items to address my concerns ~ none of which ever happened. When I found a new team where I thought I could make a greater impact, my manager blocked my transfer, going all the way through HR to accuse of poaching. When I tried to leave the company, my manager tried to delay my resignation. Good stuff.

4.0
Jun 13, 2008
Recommend
CEO approval
Business Outlook

Pros

Amazon has a lot of interesting projects going on at any given time. You will likely be dealing with projects that have a scale that few other companies can compete with. This will well prepare you for your next job. If you're interested in a project that you are not working on you can still access the code and explore the development environments. This helps when starting a new project so that you can see how others have done things before. Amazon tries to hire smart people, this means that you will likely be surrounded by people that will be able to teach you something.

Cons

The biggest downside is also one of the upsides. There are so many projects being actively developed at one time that often the wheel is re-invented many times. This can makes it difficult to decide the right way to do something. There are also a ton of proprietary tools. The build system is very complex and some would say overkill for java development. That's understandable considering it was built for complex C++ linking and library managment. The deployment tool is very robust, and thus hard to understand resulting in a large learning curve for even the more senior developers. Hopefully someone on your team knows how to work the thing!

5.0
Jun 12, 2008
Recommend
CEO approval
Business Outlook

Pros

being surrounded by very smart and passionate people who come from all over the country, great pay and options, job growth and opportunities if you demonstrate talent, they take technology very seriously and encourage experimentation and give more than enough resources, the pride that comes from working on a mass-scale consumer product for a globally recognized company

Cons

being in seattle, the weather is horrid, coworkers just running out the clock due to being discouraged to contribute big changes to a huge corporate bureaucracy with a million constraints,

Viewing 6751 - 6753 of 6,758 Reviews

Glassdoor has 250,403 Amazon reviews submitted anonymously by Amazon employees. Read employee reviews and ratings on Glassdoor to decide if Amazon is right for you.