employer cover photo
employer logo
employer logo

Amazon Web Services

Part of Amazon

Is this your company?

Technical writer jobs being replaced by AI (LLMs) - Sr. Technical Writer Amazon Web Services Employee Review

1.0
3 Dec 2025
Recommend
CEO approval
Business outlook

Pros

Was a super company to work for back when Jeff Bezos was at the helm - a real visionary that created a wonderful and creative work environment. We all loved our jobs, working with each other, and being at work everyday. You felt like the org really cared for you. Then, after Bezos stepped down and Jassy took over, the company's culture and work environment started to decline year after year. You were no longer a person, but a corporate commodity. Amazon became just another corporate machine boiling over with top-down bureaucracy. So, there are no longer any "pros" that I can tell you because all the pros that existed when I first started there, are now gone and won't ever be coming back.

Cons

Kind of already stated it above as the long, gone "pros". But, I'm looking to move on as management has stated that all the technical writing positions will be eliminated by next year as service teams will be using an AI-based application to write their own docs.

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