Tech Unemployment at 5.8%—Highest Since Dot-Com Bust—Yet AI Job Postings Are Up 340%. Are We Replacing Workers or Just Rebranding Roles?
I need to talk about something that’s been keeping me up at night. We’re facing a paradox that I haven’t seen in my 16 years in tech—and I think we’re not having the right conversations about it.
The Numbers Don’t Add Up
Tech unemployment just hit 5.8%—the highest level since the 2001-2002 dot-com crash. Meanwhile, overall U.S. unemployment sits at 4.1%. Let that sink in: we’re in worse shape than the broader economy.
But here’s where it gets weird. AI-related job postings are up 340% since 2024. LinkedIn data shows a 92% increase in hiring for AI roles, with a 56% wage premium for high-demand positions. Traditional software engineering roles? Down 15%.
At my EdTech company, I’m living this tension daily. We’ve been asked to “right-size” our engineering team while simultaneously opening 5 new AI/ML positions. The board keeps asking why we can’t just “upskill” the people we’re letting go.
What’s Actually Happening
Q1 2026 saw 52,050 tech layoffs—a 40% jump from last year. In March alone, AI was cited as the reason for 15,341 layoffs (25% of the total). This isn’t about pandemic overhiring anymore. Companies are explicitly replacing roles with AI systems.
Block (formerly Square) announced 4,000 job cuts—40% of their workforce—with CEO Jack Dorsey citing “the growing capability of AI tools to perform a wider range of tasks.” That’s not restructuring. That’s replacement.
But when I look at who we’re laying off versus who we’re hiring, something doesn’t match up:
Laying off:
- Mid-level software engineers (5-10 years experience)
- QA engineers
- Customer support specialists
- Junior developers
- Technical writers
Hiring for:
- ML engineers with PhD-level expertise
- AI prompt engineers
- MLOps specialists
- Data scientists with NLP experience
- AI safety researchers
The Skills Gap Is Real—But Who’s Responsible?
Here’s what’s haunting me: 67% of US workers say their organization hasn’t been proactive in training them to work alongside AI. Only 17% report their company is doing anything meaningful to upskill workers in AI-impacted roles.
We’re not replacing workers. We’re abandoning them.
I’ve had three senior engineers come to me in the past month asking: “Should I learn prompt engineering? Is my Java expertise worthless now? Am I going to be replaced?”
These are people with 8-12 years of experience. They’re productive. They ship quality code. They mentor juniors. But they’re terrified—and I don’t have good answers.
The Question We’re Not Asking
Are we actually replacing workers with AI—or are we using AI as cover to shift to a higher-skilled (and more expensive) workforce while calling it “efficiency”?
Because if you’re laying off a $120K software engineer and hiring a $220K ML engineer, you haven’t saved money. You’ve just decided that engineer #1 isn’t worth investing in.
The rebranding is everywhere:
- “AI-powered customer support” = we fired the support team and built a chatbot
- “AI-assisted QA” = we eliminated manual testers and trust AI to catch bugs
- “AI-augmented engineering” = we’re hiring fewer engineers and expecting AI to fill the gap
What I’m Wrestling With
As a leader, I’m supposed to “drive efficiency” and “leverage AI capabilities.” But I’m also supposed to develop my team and create opportunities for growth.
How do I reconcile:
- Telling engineers to “embrace AI as a tool” while watching other companies fire entire teams and replace them with AI systems?
- Asking my team to learn AI skills when the AI roles we’re opening require PhD-level expertise most of them don’t have?
- Preaching about “career development” when the industry is signaling that traditional software engineering skills are becoming obsolete?
The 47% increase in re-employment time (3.2 → 4.7 months) tells me the market isn’t absorbing these displaced workers. They’re not just moving to new companies. They’re struggling to find roles at all.
The Equity Dimension
This hits different communities differently. Entry-level roles are down 40-60%. Bootcamp placement rates dropped from 75% to 40%. Internships are being paused.
The customer support roles getting eliminated? They’re 60% women, 40% people of color. The new AI roles requiring advanced degrees? They systematically exclude the diverse pipelines we’ve spent a decade building.
We’re not just replacing workers. We’re reverting to gatekeeping.
What Should We Do?
I don’t have all the answers, but I know what’s not working:
Ignoring it - “Let the market sort it out” is how you destroy careers and erode trust
Cosmetic training - A 2-hour “Intro to AI” course doesn’t turn a Java developer into an ML engineer
Pretending it’s neutral - “AI will create more jobs than it destroys” is cold comfort to someone who just got replaced
What I think we need:
Honest skills assessment - If someone’s role is at risk, tell them. Give them 6-12 months to pivot, not 2 weeks notice
Real investment in reskilling - Not courses. Not certifications. Actual role transitions with reduced expectations during learning
Hybrid roles - Not everyone needs to become an ML engineer. AI-assisted developers, AI trainers, AI operations specialists are all valuable
Accountability for claims - If you say you’re “augmenting not replacing,” prove it. Show retention numbers. Show internal transitions
My Question to This Community
For those of you leading engineering orgs: How are you handling this transition?
- Are you replacing or rebranding?
- What’s your actual reskilling strategy—not what you tell the board, but what’s really working?
- How do you maintain team morale when everyone knows their colleagues got laid off and replaced with AI tools?
- What do you tell that 10-year veteran engineer who asks “Am I obsolete?”
And for those of you who’ve been displaced or are worried about it: What do you need from leadership that you’re not getting?
I want to believe we can do this humanely. But the data suggests we’re optimizing for Q1 2026 efficiency while destroying the 2028-2030 talent pipeline.
Prove me wrong. Please.
Sources: Tech Layoffs 2026, Tech Jobs 2026, AI Skills Gap 2026, Tech Unemployment Data