Hyperscalers are trimming cloud headcount while thousands of platform engineer roles go unfilled elsewhere. Here's where the actual demand is — and what your resume needs to say to reach it.
If you work in cloud infrastructure or platform engineering, the last few weeks of headlines could easily mess with your head. Microsoft cut roughly 9,000 roles in July — part of a broader restructuring that eliminated around 15,000 positions over two months. Amazon quietly trimmed roles inside AWS around the same time. Intel announced a 15% reduction to its global workforce. Meanwhile, technology companies shed more than 139,000 jobs through the first half of 2025, an 83% jump over the same stretch a year earlier, according to Channel Insider's 2025 layoffs tracker.
Read those numbers in isolation and it sounds like a rough time to be a cloud engineer. Here's what those numbers don't tell you: Indeed currently lists more than 8,000 open cloud platform engineer roles, with advertised annual salaries reaching as high as $257,550 at senior levels. The jobs exist. The map of where to find them just shifted.
Why Hyperscaler Cuts Don't Tell the Whole Story
Large hyperscalers restructure for reasons that have little to do with whether the market needs cloud engineers. They over-hired during the 2020–2022 boom, they are redirecting capital toward AI infrastructure, and they are under pressure from investors to show leaner cost structures. Cutting internal engineering headcount — especially in legacy infrastructure divisions — achieves all three goals simultaneously.
The mistake job seekers make is treating a hyperscaler layoff as a signal that cloud skills are losing value. It's the opposite. The companies doing the cutting are doing so partly because automation and AI tooling now let smaller teams run larger infrastructure. That dynamic creates demand, not less of it — just at a different tier of employer.
The July 2025 TechCrunch layoff tracker logged 16,327 tech workers let go in a single month, up from just over 1,600 the month before. That spike is real. But it reflects restructuring concentrated in large-company overhead — not the mid-market cloud-native firms, managed service providers, and regional SaaS businesses that are actively backfilling these exact skills and struggling to find candidates.

Where the Actual Demand Is Sitting
The clearest pattern emerging from current Indeed data is that cloud platform engineer hiring is spread across mid-market companies and managed-service providers rather than clustered at household names. Employers like Adobe advertise roles at $161,700–$257,550 at senior levels. Even organizations well outside the traditional tech sector — with salary bands starting around $130,500 — are actively advertising cloud infrastructure positions.
Here's a snapshot of the layoff pressure versus the open-role reality:
| Signal | Detail | Source |
|---|---|---|
| Microsoft layoffs (2025) | ~15,000 total cuts (9,000 in July, ~6,000 in May) | Channel Insider |
| AWS cuts | Undisclosed cloud-division reductions, mid-July 2025 | Channel Insider |
| Intel workforce reduction | 15% of global headcount, announced July 2025 | Channel Insider |
| Tech-sector cuts, H1 2025 | 139,156 jobs — up 83% year-over-year | Challenger / QZ |
| July 2025 layoffs alone | 16,327 — up from 1,606 in June | TechCrunch |
| Cloud platform engineer roles open now | 8,000+ active listings | Indeed |
| Senior-level salary ceiling (Adobe) | Up to $257,550 | Indeed |
The demand signal is real and the salaries are holding. What has tightened is the tolerance for generalist cloud experience. The roles getting filled fastest explicitly require Kubernetes, Terraform or Pulumi, CI/CD pipeline ownership, and — increasingly — experience operating the infrastructure that supports AI and ML workloads.
What the AI Layer Is Doing to This Role
Platform engineering used to mean keeping pipelines green and clusters healthy. That job description hasn't disappeared — but a meaningful layer has been added on top of it. Companies retooling for AI development need engineers who can build, deploy, and observe ML and LLM pipelines, not just traditional application pipelines. Engineers who can speak both languages — classic DevOps and emerging MLOps or LLMOps patterns — are the ones getting the most callbacks right now.
The Fortune and Challenger data point to companies explicitly restructuring toward AI investment. That means the infrastructure supporting AI workloads is growing, not shrinking. If your resume shows only traditional CI/CD work, now is the time to push a hands-on MLOps or LLMOps project to your GitHub — even something personal built on a public dataset demonstrates that you've done the work.

How to Prepare
Whether you were laid off from a hyperscaler or you're watching the news and wondering what to do next, here are concrete moves to make right now:
1. Reframe your target employer list. Stop focusing only on FAANG and hyperscaler job boards. Mid-market SaaS companies, managed cloud service providers, and digital-native firms in healthcare, fintech, and manufacturing are where the open cloud platform roles actually live right now.
2. Build the AI infrastructure layer onto your existing skills. You don't need to become an ML engineer. You need to understand how MLOps pipelines differ from app pipelines — model registries, feature stores, experiment tracking, inference serving. One real GitHub project that demonstrates this changes how a recruiter reads your profile.
3. Make your resume role-specific, not tool-generic. Hiring managers in this market are looking for Kubernetes plus CI/CD plus multi-cloud experience in the same candidate. Lead with outcomes — reduced deployment time, cut infrastructure cost, improved uptime — rather than a list of tools.
4. If you are on contract, surface your impact metrics now. Macro payroll data was revised downward sharply in July, and budget reviews tend to follow. Don't wait for a renewal conversation — make your manager aware of measurable results before the quarter closes.
5. Build cloud-agnostic IaC skills. If your profile is tied to a single vendor's native tooling, investing time in Terraform or Pulumi meaningfully widens your candidate pool — especially if your current role is tied to on-premises or hardware-adjacent pipelines, the category most exposed to Intel-style restructuring.
Ryzlink matches AI-fluent platform and cloud engineers with mid-market and enterprise teams — typically within 48–72 hours — and stays accountable for what actually ships, not just for filling a seat. If you're actively looking, current openings are listed at ryzlink.com/jobs.
Free Courses to Get You Ready
Each of the following is fully free — no trial period, no credit card required — and maps directly to the skills showing up most often in current cloud platform engineer job descriptions.
Microsoft Azure Fundamentals (AZ-900) learning path — Microsoft Learn. Builds foundational knowledge of cloud concepts, service types, and Azure architecture — the baseline hiring managers expect before any interview. Cost: Free. A free Microsoft account gets you in; use an existing one or set up a new one, then open any module to start learning.
Introduction to Kubernetes (LFS158) — Linux Foundation. Covers Kubernetes architecture, core components, and hands-on cluster setup using Minikube — exactly the hands-on experience the highest salary bands on Indeed require. Cost: Free. Head to the course page, set up a free Linux Foundation account if you don't already have one, and enroll directly.
Introduction to DevOps and Site Reliability Engineering (LFS162) — Linux Foundation. Connects DevOps and SRE principles to cloud computing and container fundamentals — the combination mid-market firms are explicitly hiring for right now. Cost: Free. Enrollment follows the same path as LFS158: a Linux Foundation account and a click to enroll on the course page.
Found this useful? Share it
Comments
No comments yet — be the first to share your thoughts.
