employer cover photo
employer logo
employer logo

Amazon Web Services

Part of Amazon

Is this your company?

Unstable Work Environment, Transition to Top-Down Authority Structure - Delivery Consultant Amazon Web Services Employee Review

1.0
21 Jan 2025
Recommend
CEO approval
Business outlook

Pros

- Decent Compensation - A good manager, team, and org. leads to a (generally) good day-to-day experience - Opportunities to learn and develop skills

Cons

Senior leadership is progressively taking away authority from organizations and mid-level managers in order to make sweeping rules such as returning to office 5 days without reference to any data in support of their position. Managers are unable to make decisions that are best for their own team and have diminishing authority to guide and direct their teams. Senior leadership expects the company to abide by leadership principles while actively refusing to do the same. The problems they identify are often problems that they themselves have created. Raises and compensation increases are low and infrequent (if stock price goes up, you will not get a raise). Promotion process is complex, bureaucratic, and often involves navigating office politics just to get a new compensation that is less than a new hire would make (existing employees are put on the bottom of the pay scale, new hires can negotiate better salaries). If you have a bad manager or a bad team, your life will be miserable. Employees are frequently overworked and under appreciated.

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