employer cover photo
employer logo
employer logo

Amazon Web Services

Part of Amazon

Is this your company?

Literally Worst Experience of My Life - Operations Manager Amazon Web Services Employee Review

2.0
7 Jun 2024
Recommend
CEO approval
Business outlook

Pros

Company gave alot of merch, bonuses & gifts to management, during peak there was a managers closet full of snacks to keep us energized for long shifts, encouraged building morale in employees. Great for people who like high pressure/stress/demanding work environments.

Cons

Management was unhelpful and condescending, departments switch every 6 months including schedules, promotions based on how much management liked you over actual stats and accomplishments. A senior leader once asked me “are you dumb or just blind” on the floor in front of my employees, HR and upper management did not assist in that situation. Never ending messaging from management, support staff, etc including your days off (the shift are 10-12 hrs each, 3-4 days/week) There is only on the floor training when they switch you to another role (department) and a very small window of errors. Not the best environment if you’re sensitive, slow paced, or seeking a non stressful work environment. This job is very stressful

Explore other reviews about Amazon Web Services

5.0
8 Jun 2026
Recommend
CEO approval
Business outlook

Pros

Great team when you have a manager and full team that works well and collaborates well. Stock is great. And you know when youre doing well, the pay increase is roughly the same as everyone else.

Cons

Low perks compared to other FAANG companies and most teams have high turn over

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