# Microsoft's 4,800 Layoffs

Page: https://stenobird.com/podcast/generative-ai-101-6932184/microsoft-s-4-800-layoffs
Text version: https://stenobird.com/podcast/generative-ai-101-6932184/microsoft-s-4-800-layoffs.md
Podcast: [Generative AI 101](https://stenobird.com/podcast/generative-ai-101-6932184)
Published: 2026-07-08T10:13:00+00:00
Episode link: https://generativeai101.podbean.com/e/microsofts-4800-layoffs/
Audio file: https://mcdn.podbean.com/mf/web/ujbijnfnypfnue9t/MicrosoftAILayoffs.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/generative-ai-101-6932184/episodes/microsoft-s-4-800-layoffs
Duration seconds: 520

## Resource

Microsoft cut 4,800 jobs, and the savings cover roughly two days of its AI infrastructure spending. Host Emily Laird runs the arithmetic the press release skipped: a $190 billion capex bill, an Xbox division losing 64 cents on every dollar, and a $625 billion backlog where nearly half the money traces back to one cash-burning customer. This is the story of a company growing 18 percent while shedding a trillion dollars in market value. The layoffs were never a savings plan, they were a message. ────────────────── 📑READ DEAN BALL'S ESSAY https://www.hyperdimensional.co/p/what-should-be-done 🎯 JOIN THE AI WEEKLY MEETUPS https://www.uwstout.edu/ai-weekly-meetup 📩 EMAIL REMINDERS FOR THE MEETUPS https://app.e2ma.net/app2/audience/signup/2101263/1779703/ 💬 CONNECT WITH EMILY LAIRD ON LINKEDIN http://www.linkedin.com/in/meet-emily-laird ────────────────── You now know more about Microsoft's recent layoffs than you did before you arrived.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/generative-ai-101-6932184/episodes/microsoft-s-4-800-layoffs/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/generative-ai-101-6932184/microsoft-s-4-800-layoffs.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.