employer cover photo
employer logo
employer logo

Amazon Web Services

Part of Amazon

Is this your company?

Great Learning, But Management Needs a Reset - Cloud Support Associate Amazon Web Services Employee Review

3.0
Mar 26, 2026
Recommend
CEO approval
Business Outlook

Pros

Unmatched technical depth — You get hands-on exposure to services like, EC2, and large-scale architectures that most engineers only read about. The learning curve is steep but rewarding. Customer-facing experience builds rare skills — Working escalations for Fortune 100 customers sharpens your communication, troubleshooting under pressure, and ability to translate complex technical problems into business impact. Career brand and credibility — AWS on your resume opens doors everywhere. The certifications, internal training, and exposure to real-world distributed systems at massive scale are hard to replicate elsewhere.

Cons

Micromanagement erodes autonomy — Rather than trusting experienced engineers to manage their workload, management tends to over-track metrics and nitpick process, which kills morale and initiative. Constant pressure without proportional support — The expectation is always-on urgency, but the staffing and tooling don't always match the volume. Burnout is treated as a personal failing, not a systemic issue. Management prioritizes optics over people — Decisions often feel driven by what looks good on dashboards rather than what actually helps engineers grow or customers succeed. Feedback flows up but rarely leads to meaningful change.

Explore other reviews about Amazon Web Services

5.0
Jun 4, 2026
Recommend
CEO approval
Business Outlook

Pros

Chill, learn a lot, fast paced. Friendly

Cons

Nothing lol. No layoffs too at Annapurna labs (aws)

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