employer cover photo
employer logo
employer logo

Amazon Web Services

Part of Amazon

Is this your company?

Great Job, Horrible Culture - Solutions Architect Amazon Web Services Employee Review

1.0
20 Mar 2023
Recommend
CEO approval
Business outlook

Pros

In all honesty, the actual job of being a Solutions Architect isn't particularly bad, in fact I loved it. AWS SA's don't get commission, so we're not constantly barraging customers with sales pitches or anything - we work to help our customers meet their goals through whatever products we can offer through the cloud. That process is usually pretty enjoyable and it's nice that we get to meet so many customers and talk to so many new people through the job.

Cons

The culture. 100% the culture. I had a manager who was out for blood, who had a deep resentment for me and many other members of my team. Why did she bear such resentment? I'm honestly not sure. But she made it her life mission to make our lives a living hell, and Amazon Leadership Principles helped her do it. The job is fine, but the culture provides the necessary tools to horrible managers to be downright awful and needlessly cruel. My manager for example would make us work during lunch because technically as "salaried employees" we're not supposed to leave during lunch. She would constantly micro-manage every little decision we made, and audit everything down to the last dime. When we took PTO or vacation, she would remind us to take our laptops with us in case she needed us last minute. One of my coworkers had a medical emergency, and she chastised her for missing work the next day as well as not notifying her of the emergency - she even made her write an essay apologizing for missing work because of her medical emergency. She would go on to place 6 people from her team onto PIP, some of whom were the most talented individuals I know. She also was so deeply ingrained in Amazon culture (drinking the kool-aid as they say) that she would preach the leadership principles to us to practice in our daily lives. Many of us tried going to HR, which proved to be useless because ultimately HR sides with the company/management, not the employees. I don't think AWS is necessarily a bad place to work, but it definitely has issues with its cult-like culture, especially because it provides management so many tools to be abusive and callous. Oh also the 401k plan at Amazon is terrible. It's 50% match up to 4% of your salary. So if you make 100k, the most Amazon will give you is 2k towards your 401k. Lastly (this is just a small one) people who work at Amazon don't even get amazon prime for free, and the "employee discount" is 10% off any products shipped and sold by amazon, but only up to $1000 ( so basically just a $100 gift card, provided you spend $1000 first).

Explore other reviews about Amazon Web Services

5.0
11 May 2026
Recommend
CEO approval
Business outlook

Pros

Good culture for most teams

Cons

Not as diverse as it could be

4.0
12 May 2026
Recommend
CEO approval
Business outlook

Pros

Operated in systems that had real scale, operational constraints, and production consequences.

Cons

Working at Amazon Web Services gave me strong exposure to distributed systems, operational ownership, and production-scale infrastructure, but there were definitely tradeoffs as well. One downside was that, like many large organizations, ownership could become fragmented. You often own a subsystem or workflow rather than an entire product end-to-end, which can limit exposure to broader architectural decision-making unless you deliberately seek it out. There was also significant process overhead. Design reviews, operational processes, dependency coordination, and organizational alignment were valuable for learning rigor, but they can slow iteration compared to smaller engineering teams. Another challenge is that large internal ecosystems can abstract away infrastructure complexity. AWS has extensive internal tooling, deployment systems, and operational platforms, which are powerful, but some of that experience does not transfer directly outside the company. I also found that operational work could dominate engineering time at points. Handling production issues, retries, integration failures, and on-call responsibilities teaches reliability engineering well, but it can reduce the amount of time spent on deeper technical exploration or greenfield development. Finally, there is the perception aspect. AWS is a strong name, but experienced interviewers know there is wide variance between teams and roles. The company name opens doors, but ultimately you still need to demonstrate technical depth, ownership, and strong engineering judgment independently of the brand.

See reviews by: Helpful|Rating|Date|All