The New Reality: When 'Layoff-Proof' Becomes a Relic of the Past

[vp_eng_keisha]

Last Tuesday, a former colleague texted me: “My laptop just died mid-meeting. Thought it was a hardware issue. Turned out they’d revoked my access—that’s how I learned I was laid off.”

I’ve been in tech leadership for 16 years. I started at Google when the cafeteria food and perks felt like declarations: We value you. You’re building the future. You’re safe here. For two decades, tech workers believed we were different. Layoffs happened in manufacturing, retail, finance—not here. We had unlimited PTO, equity packages, and “we’re family” culture decks.

That belief is dead.

The 2026 Whiplash

In early 2026 alone, we’ve seen 45,000+ tech layoffs—764 people per day. Amazon announced 16,000 cuts. Meta, Salesforce, Oracle followed. The numbers are staggering, but the methods are what broke something fundamental.

Access revoked without warning. Impersonal emails. No goodbye meetings. No recognition of years of service. Companies that once flew employees to headquarters for free lunch now can’t afford 15 minutes of human decency during separations.

University of Washington researchers called it “cruel optimism”—the psychological contract breach when the promise of stability vanishes overnight. For 20 years, we traded work-life balance, geographic flexibility, and sometimes sanity for the belief that tech jobs were secure. That deal is over.

What This Means for Leadership

I’m a VP of Engineering at a high-growth EdTech startup. I navigate this from both sides:

From above: Pressure to show ROI for every headcount. CFO conversations about “right-sizing” and “AI-driven efficiency.” Board members asking why we need so many engineers when GitHub Copilot exists.

From below: My team asking if their jobs are safe. Engineers who are one Slack message away from losing healthcare for their families. Junior developers wondering if their first tech job will be their last.

I can’t promise security I don’t control. I can promise honesty, dignity, and advance notice if cuts happen. But the industry has shown that’s not the standard anymore.

The Questions That Keep Me Up

How do we rebuild trust when loyalty feels one-sided? I tell my team to invest in their growth, but I’ve watched companies eliminate entire learning & development budgets the same quarter they post record profits.

What does “career development” mean now? Traditionally, you stay 3-5 years, get promoted, build deep expertise. But if your role might vanish in 12 months, should we even pretend long-term planning matters?

Is this permanent or temporary? Are we witnessing a cultural reset where tech jobs become transactional—or will we swing back once the AI hype cycle corrects?

What I’m Doing Differently

I’m changing how I lead:

1. Radical transparency about company health, budget pressures, and risks
2. Portable skills development—I want my team to be hireable anywhere, anytime
3. External network building—I actively encourage engineers to speak at conferences, contribute to open source, build their brand
4. Mutual accountability—I don’t ask for loyalty I can’t guarantee. I ask for excellence while they’re here.

But I’m not sure it’s enough.

I Want to Hear From You

If you’ve been laid off: How did it happen? What would have made it less traumatic?

If you’re in leadership: How are you navigating the tension between protecting your team and executing business decisions?

If you’re early-career: Does this change how you think about tech careers? Are you building backup plans?

The “layoff-proof” era is over. The question is: what do we build instead?

---

For context: UW research on tech layoff psychology, 2026 layoff tracker

[eng_director_luis]

Keisha, this hits hard. I’ve been on both sides of this too—delivering the news and wondering when my turn comes.

Three months ago, I had to lay off two engineers I’d personally mentored for years. One was sending money back to his family in El Salvador. The other was a first-gen college grad whose parents worked in warehouses so he could get a CS degree. I gave them two weeks notice, personally helped with their resumes, and made introductions to my network.

Two weeks later, the CEO praised me in the leadership meeting for “handling the reductions professionally.” I wanted to throw up.

The Cultural Piece Nobody Talks About

For Latino engineers, for first-gen professionals—this isn’t just career disruption. We’re often supporting extended families. My parents still don’t fully understand what I do, but they know I “made it.” When I got promoted to Director, my dad cried. The idea that this could all vanish in a Slack message? That’s not just job loss. That’s generational trauma.

The “we’re family” rhetoric hits different when you’re actually sending paychecks home to your real family.

What I’m Doing (And It’s Not Enough)

Documenting everything. I tell my team: write down your wins, quantify your impact, keep a “brag document.” If layoffs come, you need proof of value for your next interview.

Building portable skills. I push my engineers to learn technologies that transfer across companies. Cloud architecture, not our proprietary framework. Industry-standard patterns, not our specific codebase quirks.

External networks matter more than internal politics. I used to tell people to focus on visibility inside the company. Now? Go to meetups. Contribute to open source. Make sure the industry knows you exist.

But here’s my question back to you: How do we maintain team morale when everyone knows job security is an illusion?

I see it in stand-ups. The hesitation before someone asks for time off. The junior engineer who stays online until 9 PM every night, thinking it’ll protect them (it won’t). The architect who turned down a sabbatical because “what if they eliminate my role while I’m gone?”

We’re all performing stability we don’t feel. And it’s exhausting.

[cto_michelle]

Both of you are describing the symptom. Let me address the disease.

I’ve been in tech for 25 years. I’ve executed layoffs. I’ve survived layoffs. I’ve watched this industry evolve from garage startups to trillion-dollar market caps. And I’m watching us repeat mistakes we should have learned from manufacturing in the 1980s.

The Business Reality (That Doesn’t Excuse the Execution)

Yes, AI is reshaping what roles we need. Yes, efficiency pressure is real—our investors expect us to do more with less. Yes, the era of “hire fast and figure it out” is over.

But impersonal layoffs are leadership failures, not business necessities.

You can cut headcount without revoking access mid-meeting. You can restructure without sending boilerplate emails. Companies choose to be cruel—and they justify it with “liability concerns” or “efficiency.” That’s cowardice dressed as strategy.

When I had to do a 15% reduction last year, we:

• Gave 4 weeks notice (not just 2 weeks pay)
• Offered resume support, interview coaching, network introductions
• Held exit meetings with every person being let go
• Extended healthcare benefits for 3 months

It cost us more. It slowed us down. Our investors hated it. But you know what happened? Our remaining team worked harder because they saw how we treated people on the way out.

What Actually Changes at the CTO Level

Luis, you asked about maintaining morale when job security is an illusion. Here’s the uncomfortable truth: you can’t sell certainty you don’t have.

What I do instead:

Radical honesty about business health. I share our runway, burn rate, and quarterly targets with my entire engineering org. If we miss revenue targets, they know layoffs are a possibility before I do.

Build resilience into org design. Cross-train teams. Document institutional knowledge. Don’t create single points of failure in your architecture or your people.

Stop treating tenure as loyalty. If someone leaves for a 30% raise, I celebrate them. If they want to interview while employed, I give them time off. The psychological contract is broken—pretending otherwise is gaslighting.

The Question Nobody Wants to Answer

Keisha asked: Is this permanent or temporary?

It’s permanent. Tech isn’t special anymore. We’re not immune to labor market forces. The 20-year run of “learn to code and you’re set for life” is over.

But here’s the harder question: Can we create sustainable tech careers, or are we accepting that this is a 10-15 year profession before people pivot to something else?

Because if it’s the latter, we need to radically rethink compensation, equity vesting, and career development. You can’t ask people to plan for a 30-year career arc in an industry with 18-month job security.

The companies that figure this out—that treat people as partners, not resources—will win the talent war. Everyone else will be stuck in a cycle of layoffs, rehires, and institutional knowledge loss.

We’re better than this. We just need to act like it.

[maya_builds]

Michelle’s comment about “cowardice dressed as strategy” just hit me in the chest.

I ran a startup that failed. At peak, we had 5 employees. When we ran out of runway, I had to let everyone go. It was the worst professional experience of my life.

But you know what I did? I gave them 3 weeks notice. I helped every single person find their next role—wrote recommendations, made introductions, even paid for resume coaching out of my own pocket. One person landed at Figma because I spent hours prepping them for the interview.

My 5-person startup—with no money, no investors, and a founder who was emotionally devastated—managed to treat people with more dignity than Amazon is showing to 16,000 employees.

Let that sink in.

This Is a Design Problem

I look at everything through a design lens. And impersonal layoffs? That’s a designed experience. Someone chose:

• The timing (mid-meeting laptop revocation)
• The communication channel (generic email)
• The access revocation sequence (immediate, no transition)
• The lack of human contact (no goodbye meetings)

These aren’t accidents. These are decisions. And the people making them have decided that efficiency matters more than humanity.

My Coping Strategy (And Maybe Yours?)

I stopped putting companies on pedestals after my startup failed. Now I treat every job as a mutual transaction:

• They pay me for my skills and time
• I deliver excellent work while I’m there
• Neither of us owes the other “loyalty”
• I maintain side projects and portfolio work that prove my value independent of any employer

I have a side project accessibility audit tool. I build it in public. I write about design systems on my blog. If I lost my job tomorrow, I have proof I’m still creating value. That’s my insurance policy.

The “we’re family” companies were lying to us. Maybe it’s time we stop believing them and start building our own safety nets.

Question for the group: If we all accept that tech jobs are now transactional, does that make us worse at our jobs? Or does it actually make us better because we’re not emotionally dependent on employer validation?

[product_david]

Maya’s question is exactly what keeps me up as a product leader: Does treating work as transactional make us better or worse?

Let me answer from a product and business perspective—because this isn’t just a culture issue, it’s a strategic failure.

The Hidden Cost Nobody’s Measuring

I’ve watched three companies do major layoffs in the past 18 months. Here’s what happens that doesn’t show up in quarterly earnings:

Institutional knowledge vanishes. That engineer who knew why we built the payment system that way? Gone. The designer who understood the accessibility requirements from our enterprise customer? Gone. The PM who had relationships with 50 beta users? Gone.

We spend 6-12 months relearning decisions that were already made. Roadmaps slow to a crawl. Product quality drops because nobody remembers the edge cases.

Research shows companies that do layoffs poorly see a 25% productivity drop in remaining teams. Not because people are less skilled—because they’re paralyzed by fear and resentment.

The CFO Pressure Is Real (But Misguided)

Michelle mentioned investor pressure. Let me be blunt: CFOs are demanding “Show me ROI for every hire” before approving headcount. I get it. AI tools promise to replace junior engineers. Why pay for 10 engineers when 6 with Copilot can do the same work?

But here’s what the spreadsheet doesn’t capture:

• Mentorship and knowledge transfer (gone when you cut senior people)
• Code quality and architectural thinking (doesn’t show up in velocity metrics)
• Customer empathy and product intuition (can’t be automated by AI)

We’re optimizing for quarterly optics at the expense of long-term capability. And when the AI productivity gains don’t materialize as promised (see: that study showing devs felt 30% faster but were actually slower), we’re left with skeleton teams that can’t deliver.

What Changes in Product Strategy

I’m adapting how we work:

Documentation obsession. Everything goes in Notion, Linear, Figma—with context, not just decisions. If someone leaves, the next person can understand why we built it this way.

Simpler systems. I push back on architectural complexity that creates dependencies on specific people. If only one engineer understands the caching layer, we’ve built a single point of failure.

Brutal prioritization. We can’t afford to waste time on features that won’t move metrics. Every sprint, I ask: “If we lost 30% of this team tomorrow, what would we still need to ship?”

The Leadership Challenge

Keisha, Luis—here’s the question I can’t answer: How do you ask for commitment when you can’t offer stability?

I need my PMs to think long-term. To build relationships with customers. To understand our market deeply. But if they’re interviewing elsewhere every 6 months, how do we create any institutional knowledge?

The companies that crack this—that treat people as genuine partners, not line items on a budget—will dominate. Everyone else will be stuck in a doom loop of layoffs, scrambling to rehire, losing to competitors who kept their talent.

This isn’t just about kindness. It’s about competitive advantage. And we’re throwing it away.