Staff Engineer Layoff Survival Guide: Lessons from 2008, 2020, 2023 — and Now

Staff engineering during economic uncertainty

The view from my desk during the 2020 layoffs

March 2020. I'm on a Zoom call with 47 engineers. Half of them are about to lose their jobs. I know who. They don't.

That was my second recession as a staff engineer. The first one (2008) I got laid off. The third one (2023) I helped decide who stayed.

I originally wrote this in October 2023. The core is still true. But the AI boom between 2023 and now changed enough of the calculus that this needed a real update. What follows is the original playbook plus a new section on what's different now.

What the AI Boom Changed (2024-2026 Update)

I'll get to the evergreen advice in a moment. But first: the 2023 version of this article missed something important, because it didn't exist yet.

The headcount math shifted. Engineers using AI tools effectively are doing more work per person than before. That's great until it isn't — it means companies can sustain the same output with fewer people. The question "is this engineer revenue-critical?" now has a second dimension: "is this engineer productively amplified by AI tools, or are they getting lapped by peers who are?"

AI skills are the new revenue proximity. The 2023 version of this article said to get close to revenue systems. That's still true. But there's a new category of protection: engineers who own the company's AI capabilities — the evals, the agent workflows, the prompt infrastructure — are increasingly hard to cut. That work is new enough that few people understand it deeply, and it touches everything.

Agency beats intelligence. This is the most underrated hiring and survival insight I've seen in the last two years. The engineers thriving in the AI era aren't necessarily the most technically brilliant ones. They're the ones who can direct AI systems toward useful outcomes — who set clear success criteria, catch when models are heading the wrong direction, and iterate deliberately. That's agency: the ability to pursue goals, act on feedback, and self-correct. It's more scarce and more valuable than raw technical knowledge, and it's observable in how someone works.

The side project signal changed. In 2023, "has a deployed side project" meant you were keeping your skills current. In 2026, the more specific signal is: have you shipped something using agents or AI workflows? The former shows you can build; the latter shows you understand the new paradigm. Both matter, but the second gets attention.

The time-vs-timing distinction. There's a concept worth having in your head: some career investments compound over time regardless of when you start them (deep domain expertise, relationships, foundational skills). Others depend heavily on timing — catching a wave when it's peaking. AI skill-building right now is one of those rare things that is both. The compounding value of becoming technically fluent with AI systems is high. And the window where this is differentiated rather than table stakes is closing.

The Brutal Truth About Who Gets Cut

It's Not About Performance

2008: I had the best performance reviews on my team. Still got cut. Why? I was expensive and working on a "non-essential" project.

2020: We kept the mediocre engineer who knew our billing system inside-out. Let go the brilliant engineer working on our future platform.

2023: The first cuts were contractors, then the most recent hires, then anyone on experimental projects.

The pattern is always the same:

  1. Revenue-critical goes last - If you touch money, you're safer
  2. Institutional knowledge matters - That legacy system nobody else understands? Job security
  3. Cost per impact - Two mid-levels often survive over one senior

I've seen staff engineers with 15 years at a company get cut while a junior who maintains the payment system survived three rounds.

How to Actually Prepare (Before the Layoffs Start)

1. Follow the Money

Every quarter, map out where revenue comes from:

Product A: $40M (60% of revenue)
├── Payment processing (Team: 3 engineers)
├── User analytics (Team: 8 engineers) ← Overstaffed
└── Core features (Team: 5 engineers)

Product B: $10M (15% of revenue) 
└── Entire team: 12 engineers ← Danger zone

If your team's revenue per engineer is below company average, start planning.

2. Build Your Evacuation Plan

When I survived 2008, I started keeping what I call the "Go Bag":

  • Resume updated quarterly (not annually)
  • Three references who'll answer within 24 hours
  • 6 months expenses in cash (not stocks)
  • Side projects deploying to prod (proves you're current)
  • Network warm (coffee chats when you don't need them)

The engineers who struggled most in layoffs? The ones who hadn't interviewed in 5 years and whose entire network was inside the company.

3. Skills That Survive Recessions

What gets hired in downturns:

  • Fixing broken systems (not building new ones)
  • Cutting costs (cloud optimization, vendor reduction)
  • Maintaining revenue systems
  • Security and compliance (regulations don't pause)
  • AI/agent infrastructure — new category, but real (see above)
  • Evaluation and measurement of AI systems — companies can't afford to ship blind

What doesn't:

  • Innovation labs
  • R&D projects
  • "Future of X" initiatives
  • New market expansion

In 2020, I watched our "AI Innovation Lab" disappear overnight while the team keeping our 10-year-old Java monolith running got raises. In 2025, I watched the inverse: an AI team lose headcount while the engineer who owned their evals and monitoring infrastructure got a promotion. The pattern isn't about AI vs. legacy — it's always about mission-criticality.

The Principal IC Question: What Work Only You Can Do?

This applies whether you're a staff engineer or aiming to become one.

The hardest career question to answer honestly: what work sits at the intersection of what you genuinely care about and what you're exceptional at? That narrow category is where you're hardest to replace. It grows deeper and narrower over the span of a career, but the people who find it early build compounding advantages.

The autonomy paradox is real: to reach staff or principal level, you become essential. To be effective at that level, you have to actively remove yourself from the critical path so the organization doesn't depend on you for execution. The leverage shifts from doing to enabling — connecting teams with problems to teams with solutions, mentoring engineers who can do 40 hours of work with 2 hours of your guidance, reshaping what the organization values through persistent documentation and advocacy.

During layoffs, this framing becomes survival advice. If you can answer "what would break, and how badly, if I left tomorrow?" with specificity, you can make the case for keeping you. If you can't answer it, neither can your manager.

If You're a Manager During Layoffs

The Shit Nobody Prepares You For

First time managing through layoffs? Here's what HR won't tell you:

1. You'll know before your team Sometimes weeks before. You'll sit in 1:1s discussing career growth with someone you know is getting cut. It's soul-crushing.

2. The list changes 2023: My initial cut list had 5 names. Final list? Only 2 were the same. Politics, last-minute budget changes, and someone's golf buddy intervening. Plan for chaos.

3. Survivors guilt is real The team that remains? They're not relieved. They're angry, scared, and wondering why them and not their friend. Productivity crashes for months.

How to Lead When Everything Sucks

Document everything:

## Team Impact Assessment
- Project X: Losing Sarah means 3-month delay minimum
- System Y: Only Bob knows this, need knowledge transfer
- Customer Z: Their dedicated engineer is on the cut list

I saved three jobs by showing leadership exactly what would break.

Fight for your people (but pick your battles):

  • ❌ "They're a great engineer" (everyone says this)
  • ✅ "They're the only one who knows our payment integration"
  • ✅ "Cutting them delays Project X by $2M worth of contractor costs"

Prepare your survivors: Before layoffs hit, cross-train aggressively. In 2020, we did "bus factor reduction sprints" — saved us when cuts came.

The Playbook That Actually Works

Month -6: See the Signs

  • Hiring freeze emails
  • "Efficiency" becomes every third word
  • Stock price below IPO/last funding
  • Executives jumping ship
  • Surprise "all hands" meetings

Month -3: Position Yourself

  1. Volunteer for the painful project - That legacy migration everyone avoids? Take it.
  2. Document everything - Become irreplaceable through bus factor
  3. Cut your own costs - Cancel that $50K tool before they make you
  4. Ship visible wins - Small improvements > grand visions
  5. Own something AI-adjacent — Even if it's just owning your team's evals, be the person who knows how to measure AI system quality

Month 0: Layoffs Hit

If you survive:

  • Don't celebrate publicly
  • Reach out to cut colleagues immediately
  • Document their work before knowledge disappears
  • Expect 2x workload at same pay

If you're cut:

  • Negotiate everything (I got 2 extra months by asking)
  • File for unemployment same day
  • Update LinkedIn before the press release
  • Use the company email while you have it

Month +3: The New Reality

Survivors face:

  • 50% more work
  • 0% more pay
  • Hiring freeze for "rebuilding"
  • Constant fear of round 2

This is when the second wave of departures hits — voluntary ones.

Hard-Won Lessons

From Getting Laid Off (2008)

  • Severance isn't guaranteed - I got 2 weeks. Period.
  • COBRA is expensive AF - Budget $2K/month for family healthcare
  • First to go, last to rehire - Took 14 months to match my old salary
  • Your manager can't save you - They tried. Corporate didn't care.

From Surviving (2020)

  • Survivor workload is brutal - Inherited 3 people's responsibilities
  • Good people leave anyway - Lost half the remaining team in 6 months
  • Promises mean nothing - "No more cuts" lasted exactly 90 days
  • Document or die - Only reason I managed the chaos

From Deciding Who Goes (2023)

  • The list is political - Merit is maybe 50% of the decision
  • Revenue is everything - Every argument must tie to money
  • Transparency helps - Team knew criteria, made it less personal
  • You'll lose friends - Some colleagues never spoke to me again

The Uncomfortable Truth

After three recessions and two years of watching the AI boom reshape what engineers are worth, here's what I know:

  1. Company loyalty is dead - They'll cut you in a heartbeat. Act accordingly.
  2. Cash beats equity - Options are worth $0 in a downturn
  3. Skills trump titles - "Staff at Google" means less than "can fix broken systems"
  4. Network constantly - The job that saves you comes from someone you helped 3 years ago
  5. Revenue proximity = job security - Everything else is philosophy
  6. Agency is the new moat - The engineers who can direct AI systems, set success criteria, and catch when things are going wrong are compounding value that's hard to replace

Your Action Plan (Do This Today)

  1. Calculate your runway: Expenses × 6 months = minimum cash needed
  2. Update your LinkedIn: Not just your resume — post content, be visible
  3. Pick a side project: Deploy something real using agents or AI tools. In 2026, "has a production AI workflow" is a stronger signal than "has a CRUD app"
  4. Map your revenue impact: Can you quantify your value in dollars?
  5. Build your network: Three coffee chats this month with people outside your company
  6. Own something AI-critical: Evals, agent workflows, prompt infrastructure. Anything that the organization needs to function and that few people understand

The next recession is coming. It always is.

The question isn't whether you'll face layoffs in your career — it's whether you'll be ready when you do.

I learned that the hard way in 2008. By 2023, I was the one holding the axe. The view isn't better from either side.

Prepare accordingly.