I had three conversations last week that hit the same painful note. A senior backend engineer I mentored at Google—7 months into job search. A former Slack colleague who led our platform team—5 months, 200+ applications. And a friend’s daughter, fresh CS grad from Georgia Tech—4 months, no offers.
The data confirms what we’re seeing in our networks: median re-employment time for laid-off tech workers jumped from 3.2 months in 2024 to 4.7 months in early 2026—a 47% increase. With 52,000+ US tech workers laid off in Q1 2026 alone and tech unemployment at 5.8%, the highest since 2001-2002, the question isn’t whether the tech safety net is fraying—it’s whether it’s already gone.
What Changed?
The jump from 3.2 to 4.7 months isn’t just a number—it reflects several compounding factors:
Volume meets skills mismatch. We have more displaced workers competing for fewer appropriate roles. New software engineering job postings declined 15% in the first two months of 2026 compared to the same period in 2025. Meanwhile, companies are cutting traditional backend, customer support, and generalist engineering roles while struggling to fill AI/ML positions that average 89 days to fill.
The junior engineer crisis. Recent computer engineering graduates face a 7.5% unemployment rate, and computer science graduates 6.1%—both significantly higher than the 3.6% overall unemployment rate. Junior and mid-level hiring is down 40-60% in some segments. We’re cutting the pipeline that feeds senior roles in 3-5 years.
The AI paradox. 8% of Q1 2026 layoffs were explicitly attributed to AI, with 55% of hiring managers expecting layoffs and 44% citing AI as a top driver. Yet companies can’t actually deploy AI at the scale they’re claiming justifies these cuts. We’re eliminating roles based on future AI capabilities, not current reality.
The Financial Reality Nobody’s Talking About
Remember when the standard advice was “keep 2-3 months of expenses as an emergency fund”? That guidance assumed tech workers would bounce back in 6-8 weeks.
The new math:
- Old assumption: 2 months = $30K-45K in savings for a senior engineer
- New reality: 6 months = $90K+ in living expenses
- That’s not “between jobs” money—that’s a down payment on a house, a year of college tuition, or the difference between career setback and financial crisis.
And this assumes you can save 6 months of expenses. For early-career engineers, parents supporting families, people with student debt or medical expenses—this isn’t a reasonable safety net. It’s a barrier that disproportionately impacts those without existing wealth.
The Human Cost Beyond the Spreadsheet
Extended unemployment isn’t just a financial issue—it’s a career trajectory disruptor. Six months out of the market means:
- Skill obsolescence anxiety in a field that moves quarterly
- Resume gap explanations that compound with each additional month
- Confidence erosion that affects interview performance
- Network atrophy as people withdraw during extended searches
- Geographic immobility when you can’t afford to relocate for opportunities
At our EdTech startup, I’m watching this affect how my team thinks about risk. People are turning down stretch opportunities because they’re terrified of being the “last one in” before the next round of cuts. The best engineers are optimizing for safety, not growth.
The Questions We Need to Ask
1. Is this cyclical or structural?
Are we in a tech market correction that will recover in 12-18 months, or has AI fundamentally reshaped the employment landscape such that 4.7 months becomes the good case?
2. Should companies track re-employment time as organizational debt?
When we lay off a senior engineer who takes 5-7 months to find their next role (vs. the 2-3 months we used to see), that’s not just their problem—it’s a signal about industry health. If we measured this as a metric, would it change our calculus about who and when to cut?
3. What does “career stability in tech” even mean anymore?
For 20 years, the industry narrative has been “tech workers are always in demand—you’ll land on your feet.” If that’s no longer reliably true, how should people think about building a tech career? How should we advise the next generation?
4. Are we cannibalizing our own talent pipeline?
By cutting junior roles and training opportunities while simultaneously complaining about a lack of AI-skilled engineers, are we creating a self-fulfilling prophecy of talent shortage?
What I’m Wrestling With
As a VP of Engineering, I make decisions that affect people’s livelihoods. I’ve had to make cuts. I’ve also had to hire during this market and watched incredible candidates go months without offers while we can’t fill specialized roles.
The uncomfortable truth: if the “tech safety net” is gone, we—the leaders making staffing decisions—are complicit. We can’t keep optimizing for quarterly efficiency while ignoring the human and industry-wide costs of extended unemployment.
What are you seeing in your markets? How are you thinking about financial planning given these timelines? And for those of us in leadership—how do we balance business needs with our responsibility to the humans whose careers we impact?