Uncertainty and speculation surrounding motives behind forcing employees back into the office and mass layoffs at Amazon

20min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

This chapter discusses the uncertainty and speculation surrounding the motives behind forcing employees back into the office and the occurrence of mass layoffs at Amazon. The speaker shares their own experience and expresses their concern for those affected by job loss. They also question the theory that layoffs cause a drop in stock price, citing examples where stock prices have actually increased following layoffs.

Justin Garrison joins us to talk about Amazon’s silent sacking, from his perspective. He should know. He works there. Well, as of yesterday he quit. We discuss how the cloud and Kubernetes have transformed the way software is developed and deployed, the impact silent layoffs have on employees and their careers, speaking out about workplace issues (the right way), how changes in organizational structure can lead to gaps in expertise and responsibility which can lead to potential outages and slower response times.

By the way, we officially let the cat off out of the bag in this episode. Justin has joined the ranks here at Changelog and is taking over as the host of Ship It! Expect new episodes soon.

Leave us a comment

Changelog++ members save 10 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

Neon – The fully managed serverless Postgres with a generous free tier. We separate storage and compute to offer autoscaling, branching, and bottomless storage.
Socket – Secure your supply chain and ship with confidence. Install the GitHub app, book a demo or learn more
Sentry – Get $100 towards your error monitoring with Sentry! Use the code changelog.
Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.