To that point, I know personally the engineers who triggered several of the AWS outages you will have read about in the news over the last decade and more. Some of them are still with us, some have been promoted since then.
I broke it, hard. I’m not a software engineer so I had no idea how to undo what I had done.
People from 3 different teams, two of them experts from other teams who heard my call for help hopped on a call and spent all day helping me fix the issue I made and then some. This was a hard stop on a cortical package pipeline for 24 hours and at no point did I feel like my job was at stake despite it clearly being my fault, and due to me running a command I know I shouldn’t have and cutting corners.
Unfortunately people outside of Amazon make sweeping generalizations about the company.
However, several of the ex-Amazon employees were clearly scarred from their time working at Amazon. Whenever something went wrong (delays, outages, missed deadlines) one of them went so far as to spend hours or days preparing documents showing how it was actually someone else's fault, not his, because he thought it was necessary to avoid being fired. He said his experience at Amazon was basically one large game of "not it" whenever it came time to assign blame for the latest issue, and everyone had to become very good at blaming someone else. The worst was when he was actual at fault for something, because he would panic and scramble to distract from the issue he caused by raising concerns about everyone else around him. Easily the most toxic person I've worked with in the past few years.
On the other hand, I've known other ex-Amazon people who said their work was nothing like this, so YMMV