Lecture time: 4 min
Table of Contents
Key Takeaways
- Engineering demand is up: SignalFire data shows engineering hires declined only 11% vs 2019, versus a 25% drop in total tech hiring. Engineers now make up 55% of new hires at major tech companies.
- AI doesn’t replace — it amplifies: Early-stage startups hired 7% more engineers in 2025 than in 2019. AI tools boost productivity, which increases the demand for more engineering work (Jevons paradox).
- Leadership agrees, but actions matter: Nvidia’s CEO and Anthropic’s economists both refute the idea that AI eliminates engineering jobs. The data backs them up: real-world hiring patterns don’t show substitution.
The Headlines Don’t Match Reality
Tech layoffs hit their highest single-month total in years in May 2026. AI was the most-cited reason. The narrative: one engineer with an AI coding tool now does the work of ten. That’s what the press releases say.
Here’s what actually happens in production: hiring data tells a different story. SignalFire’s « State of Talent Report » tracked millions of employees across 80 million companies. Instead of focusing on layoffs (which are slow to reflect in data), they looked at real-time hiring. The gap between the narrative and the numbers is significant.
Engineering Is More Resilient Than Ever
Total hiring across large tech companies dropped 25% compared to 2019 levels. Engineering roles? A decline of only 11%. Let me be specific: at the 12 « Tech Majors » — Alphabet, Meta, Apple, Amazon, Microsoft, Netflix, Nvidia, Tesla, Uber, Airbnb, Block, Stripe — engineers constituted 55% of all new hires in 2025. That’s up from 46% in 2019.
Most people get this wrong. They assume AI-driven layoffs hit engineering first. The data shows the opposite: engineering is the most resilient job function in tech right now. If AI were truly substituting for engineering talent, engineering hiring would be the first to fall. It’s not. This isn’t theory.
Startups Are Hiring More Engineers, Not Fewer
The real cost of believing the hype? You miss what’s happening at early-stage startups. SignalFire’s data shows that startups collectively brought on 7% more engineers in 2025 than in 2019. That’s not a blip — that’s a structural shift.
Here’s why: AI tools make engineers more productive. They write boilerplate faster, but they don’t replace the need for architectural decisions, debugging in messy production environments, or understanding business logic. The demo worked. Production didn’t. Here’s why — because every new feature generates 24 edge cases, legacy integrations, and performance constraints that no AI agent navigates alone.
The CEOs and Economists Agree (But Actions Are Louder)
Nvidia’s Jensen Huang said flatly: « Somebody said AI is going to destroy all of the software engineering jobs. » He argued the opposite is true. At Nvidia, where every engineer uses agentic AI, « software engineers are busier than ever. » Agents write code near instantaneously — but they constantly push engineers to generate « the next idea. »
Anthropic’s head of economics found zero significant difference in unemployment rates between workers heavily using Claude for tasks and workers in less exposed jobs. That’s not automation — that’s a productivity amplifier. When AI handles the repetitive parts, the human bottleneck shifts to complexity, not capacity.
Engineers Are Experiencing Jevons Paradox in Real Time
This is the classic Jevons paradox: greater efficiency doesn’t reduce demand — it increases it, because work expands to fill the new capacity. That’s not automation — that’s a liability if you build for a future of less engineering, because it doesn’t exist.
As SignalFire’s head of research put it: « They’re suddenly a lot more productive, and there’s endless work for them to do. » I’ve seen this pattern play out in startup after startup. The moment you give a team agentic workflows, they don’t fire half the team. They reprioritize — migrations, observability, multi-agent orchestration, security architecture. The work expands.
What This Means for Automation Architects
If you’re building automation infrastructure — n8n workflows, VPS deployments, agent orchestrators like OpenClaw and Hermes — this data matters. The goal isn’t to eliminate engineering roles. It’s to build infrastructure that holds under real-world loads. Production-grade. Not demo-grade.
That’s not automation — that’s a liability. The real cost of building fragile pipelines is not one layoff cycle. It’s the endless debugging at 2am when an agent’s response breaks a production deployment. Startups don’t need less engineering. They need engineering that scales without burning out the team.
We built Rebirth Distribution’s tooling for exactly this reason: automation that actually works in production, not just in presentations. The data confirms what I see every day: engineering demand is not shrinking. It’s transforming. The engineers who understand infrastructure, reliability, and agent orchestration will be the ones building the systems everyone else depends on.