employer cover photo
employer logo
employer logo

Amazon Web Services

Parte di Amazon

Questa è la tua azienda?

Worked with a great team - Recensione dipendente - Sr Program Manager presso Amazon Web Services

4,0
2 nov 2023
Consiglia
Gradimento del CEO
Pronostico commerciale

Vantaggi

I really enjoyed my time at AWS! Unlike other aspects of the business, the marketing and go to market teams were gender balanced, and I felt like my contributions were appreciated. Everyone I worked with (with one exception) was remarkably smart, expert, and supportive. The work was challenging. It is said that working at AWS for five years is the equivalent of getting an MBA. While I don't have an MBA, I would agree with that! The amount of clear writing, project planning, goal attainment calcuations, annual planning, and hands-on budget tracking required was significant.

Svantaggi

Most of my managers were amazing, supportive, and wanted to help me be my best. I had one, however, for just a few months. She told many untruths and sabotaged everyone who tried to leave the team--and that was everyone. It took three months to get her out of a management position, but not before she managed to lie enough to cut my salary by $50K. Ultimately, I was forced out by the return to work mandate, even after I had received approval to work remotely permanently. Two months to move a family of three and two pets 3,000 miles isn't realistic or fair.

Esplora altre recensioni su Amazon Web Services

5,0
8 giu 2026
Consiglia
Gradimento del CEO
Pronostico commerciale

Vantaggi

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.

Svantaggi

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

4,0
12 mag 2026
Consiglia
Gradimento del CEO
Pronostico commerciale

Vantaggi

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

Svantaggi

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.

Vedi recensioni per: Utile|Valutazione|Data|Tutto