employer cover photo
employer logo
employer logo

Amazon Web Services

Part of Amazon

Is this your company?

Dread and isolation, even when surrounded by coworkers - Marketing Manager Amazon Web Services Employee Review

1.0
Feb 20, 2025
Recommend
CEO approval
Business outlook

Pros

The pay is good when stocks are up. Your salary will go down if stocks go down.

Cons

If you value work-life balance and a supportive workplace, AWS was never that company. If you’re willing to put up with the grind to advance your career, AWS is no longer the place for you either - return-to-office (RTO) mandate, plans to flatten the organization by reducing manager roles, limiting or eliminating the ability to backfill roles, and significant leadership churn from visionary leaders has made an already toxic culture that much more unbearable, even for the hardest workers. The RTO mandate has made this environment of constant pressure and lack of support all the more apparent, creating a sense of isolation, even when you’re surrounded by coworkers. All I need to do is look around to see the struggle with burnout, health issues, and declining morale. The sense of dread that has taken hold is depressing, with many feeling that their well-being is being sacrificed for corporate priorities. I would strongly encourage anyone considering a position here to carefully evaluate whether this environment is worth the pay.

Explore other reviews about Amazon Web Services

5.0
Jun 16, 2026
Anonymous employee
Recommend
CEO approval
Business outlook

Pros

Great company with challenging assignments

Cons

Lot is expected of you

4.0
May 12, 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