> Now, there is a lot of skepticism around this article, and you should take it with a huge grain of salt, but the timing is curious, although we do not claim it is true or is somehow connected to the systems' crash.
I wouldn’t be surprised by a causal relationship. Most people planning layoffs don’t actually know what the laid off people do. When Fisker laid everyone off, their OTA updates went down hard. Had they taken a day to perform a safe shutdown they would have saved months of recovery work. Management likes to lay off with no warning, but for professional infrastructure people that causes more harm than good. Every pro I know will faithfully wrap up the work because they have professional pride.
Layoffs cause loss of institutional knowledge. Minor irritation can balloon into a major outage simply because the person who can fix it easily left the building for the last time.
us-east-1 is the OG region. It has had significant dns problems before. There’s probably a subtle and complicated series of steps for general care and feeding.
Good journalism would identify the process, the owner, cross reference with the layoff list… any of the laid off people would be able to supply those details off the record.
It turns out that anyone who wants to can just go on the Internet and spout bollocks. I like how there isn’t even a byline here, just “editorial staff.” Because who’d sign their name to this kind of tomfoolery?
I’m an AWS engineer and I haven’t seen any evidence of engineering layoffs within AWS since early this year. As others have suggested we generally don’t have ”DevOps Workers” either. There’s definitely a push for AI tools, but there’s no indication that it was related to any off this from what I’ve seen.
10 comments
[ 3.0 ms ] story [ 33.4 ms ] thread> But by the afternoon, nearly 40% of AWS’s DevOps employees were cut in a single internal strike.
> An email memo, which was briefly posted on the internal wiki before being taken down, blamed the cuts on strategic automation initiatives.
Good advice.
Layoffs cause loss of institutional knowledge. Minor irritation can balloon into a major outage simply because the person who can fix it easily left the building for the last time.
us-east-1 is the OG region. It has had significant dns problems before. There’s probably a subtle and complicated series of steps for general care and feeding.
Good journalism would identify the process, the owner, cross reference with the layoff list… any of the laid off people would be able to supply those details off the record.
my guess is 4 out of 10, which would make it a single sub team rather than "all devops roles in aws". would love to see something more official.
It's also very opportunistic, you're telling me you were sitting on this story and you decided to release it right after AWS had issues ?