171 Tech Layoffs, 55,911 Workers, and 'Culture-First Restructuring'—Are We Just Putting a Better Face on Continuous Cuts?

[vp_eng_keisha]

The numbers landed in my inbox this morning, and I had to read them twice: 171 tech layoffs affecting 55,911 workers in 2026 so far. That’s 736 people per day losing their jobs. But what caught my attention wasn’t just the scale—it’s the new label attached to these cuts: “culture-first restructuring.”

As someone who’s led through layoffs at two different companies, I know the weight these decisions carry. I’ve been in rooms where we debated every name on the list, where we tried to balance business necessity with human impact. And I’ve seen the aftermath—the survivors who stay behind, working harder to fill the gaps, wondering if they’re next.

The Framing Has Changed

Compare this to 2025, when we saw 245,000 tech jobs cut globally. Back then, companies cited “market corrections,” “over-hiring during the pandemic,” or vague “efficiency measures.” Now in 2026, the language has shifted. Companies are talking about aligning teams with core values, retaining top talent, and building “agile and innovative environments.”

Block cut 40% of their workforce. Amazon announced 16,000 cuts. Meta trimmed Reality Labs by 1,500 employees. Each framed their decisions around culture and strategic alignment.

But What Does “Culture-First” Actually Mean?

Here’s my question: Is this genuinely different, or have we just gotten better at messaging?

On one hand, I want to believe that companies are being more thoughtful. That they’re asking: “Who embodies our values? Who will help us navigate this AI-driven transformation?” Research shows that about 20% of 2026’s cuts are directly AI-related—companies are restructuring around automation in ways they never did before. That IS structurally different from post-pandemic corrections.

On the other hand, I’ve seen the data on what happens to survivors. Studies consistently show decline in engagement and creativity among those who remain after layoffs. Burnout risk increases. Trust erodes. When you’re asking 60% of a team to do the work of 100%, talking about “culture” feels… disconnected from reality.

The Geographic Reality

What also concerns me is the concentration of impact. Seattle lost approximately 16,590 tech workers (Amazon + Microsoft). San Francisco saw 9,395 layoffs. These aren’t just numbers—they’re entire professional networks being disrupted, local economies taking hits, and communities losing talent that took years to build.

The tech unemployment rate hit 5.8% in early 2026—the highest since the dot-com bust. Median re-employment time jumped from 3.2 to 4.7 months. The math is brutal: even if “culture-first” decisions are more strategic, the human cost is severe.

My Honest Take

I’ve been thinking about this a lot, especially as I scale our engineering org during uncertain times. Here’s what I believe:

“Culture-first” becomes meaningful only if it’s paired with radical transparency. Tell people WHY. Explain the AI strategy, the market pressures, the product pivots. Don’t hide behind buzzwords. If you’re cutting because quarterly numbers demand it, say that. If you’re genuinely repositioning for the future, show the roadmap.

Culture is tested most during crisis. How you treat people on the way out—severance, transition support, honest references—reveals more about your values than any mission statement. Do you offer extended healthcare? Career counseling? Or are you escorting people out the same day?

The survivors are watching. Every decision you make about layoffs sends a signal to those who remain. “Culture-first” can’t mean “optimizing for the people we keep” while treating those we let go as disposable. That’s not culture—that’s expediency.

Questions for This Community

I’d love to hear from others navigating this:

• Have you seen examples of layoffs that genuinely felt aligned with company values? What made them different?
• For those who’ve been on the receiving end of these “culture-first” cuts—did the framing match the experience?
• As leaders, how do we maintain team cohesion and culture when we’re constantly asking people to do more with less?
• Is this the new normal? 736 people per day feels unsustainable for the industry long-term.

I don’t have all the answers. But I think we owe it to our teams—and to ourselves—to ask these questions honestly. The language we use matters. “Culture-first restructuring” is either a genuine evolution in how we think about organizational design, or it’s 2026’s version of “right-sizing.”

I’m hoping it’s the former. But I’m watching closely to see if actions match the words.

[cto_michelle]

Keisha, this cuts right to the heart of what I’ve been wrestling with as we navigate our own org planning for 2026.

You’re absolutely right that something fundamental has shifted. This isn’t just post-pandemic correction anymore—20% of cuts being AI-driven represents a structural transformation of the workforce, not a temporary adjustment. And that distinction matters enormously for how we should think about “culture-first.”

The AI Reality vs The AI Excuse

Here’s what concerns me: I recently read a survey showing that 59% of hiring managers admit they exaggerate AI’s role in layoffs because “it plays better.” Only 9% say AI has fully replaced roles. That’s a massive gap between rhetoric and reality.

So when companies say “culture-first restructuring around AI,” are they:

• Genuinely repositioning teams for an automated future? (Strategic)
• Using automation as cover for cost-cutting they’d do anyway? (Reactive)

The difference is profound. One is building for the future. The other is managing decline with better branding.

What “Culture-First” Should Actually Mean

If we’re serious about culture-first in the context of AI transformation, it should mean:

1. Protecting core values while adapting to technology shifts

• Not “who can we replace with AI?” but “how do we augment human capability?”
• Investing in upskilling alongside automation
• Being honest about which roles are truly redundant vs which are being cut for cost

2. Transparency about the trade-offs

• Amazon cut 16,000. Block cut 40%. Meta cut 1,500 from Reality Labs.
• Were these decisions driven by AI capability? Market pressure? Product pivots?
• The framing should match the reality.

3. Long-term thinking over quarterly optimization

• Your point about survivors watching is crucial. Every cut sends a signal.
• If “culture” means anything, it’s that we value institutional knowledge, customer relationships, and team cohesion.
• Cutting 40% of a company destroys all three, regardless of how you frame it.

The Credibility Test

Here’s my litmus test for whether “culture-first” is genuine or just PR:

Look at what companies are investing in alongside the cuts.

• Are they funding training programs for remaining staff?
• Are they hiring in new AI-adjacent roles while cutting others?
• Are severance packages generous or minimal?
• Do they offer transition support or just escort people out?

If the answer is “cut costs everywhere and call it strategic,” then culture-first is branding. If they’re genuinely reshaping the org with investment in people and technology, that’s different.

The Unsustainable Pace

Your number—736 people per day—is staggering. And you’re right to ask if this is the new normal.

From a technical leadership perspective, I worry about organizational memory loss. The engineers who understand why systems were built certain ways. The product managers who remember what customers actually asked for. The designers who know what’s been tried and failed.

When you cut at this pace, you lose context. And context is often more valuable than code.

My Question for the Group

How do we distinguish between companies doing hard but necessary strategic restructuring vs those using “culture-first” as a euphemism for continuous workforce reduction?

Because right now, I see a lot of similar language being used for very different realities. And that linguistic drift makes it harder for all of us to have honest conversations about what’s actually happening in tech.

The stakes are too high—for the 55,911 people affected, for the survivors trying to keep things running, and for the industry’s long-term health—to settle for buzzwords over clarity.

[eng_director_luis]

Both of you have articulated the strategic and organizational concerns brilliantly. I want to add the perspective from the middle—those of us leading teams through these cuts while trying to maintain morale and productivity.

The Reality on the Ground

Here’s what “culture-first restructuring” looks like from where I sit:

Monday morning: Three senior engineers get pulled into HR meetings.
Monday afternoon: The rest of the team is told this is part of “strategic realignment.”
Tuesday: I’m in planning meetings being asked how we’ll deliver the same roadmap with 30% fewer people.
Wednesday: The surviving team members are updating LinkedIn, just in case.

The disconnect between “culture-first” messaging and lived experience is profound.

What Happens to Survivors

Michelle mentioned organizational memory loss. Let me add to that: psychological toll.

Research consistently shows that survivors of layoffs experience:

• Decline in engagement and creativity
• Increased burnout risk
• “Survivor’s guilt” that impacts performance
• Constant anxiety about being next

And then we ask these same people to work harder, cover more ground, and maintain the same quality standards. It’s not sustainable. At some point, efficiency becomes extraction.

The Math Doesn’t Work

Let’s be honest about the numbers. If you cut 40% of your workforce (like Block did), you’re not asking people to be 40% more efficient. You’re asking them to do impossible things:

• Cover knowledge gaps from departed colleagues
• Take on responsibilities outside their expertise
• Maintain system they didn’t build and don’t fully understand
• Do all this while wondering if they’re next

That’s not culture-first. That’s culture-destructive.

When I’ve Seen It Done Right

I have seen layoffs handled with genuine care and alignment to values. Here’s what made the difference:

1. Honest Communication

• Leadership explained the financial situation without sugar-coating
• They showed us the runway, the revenue projections, the hard choices
• No buzzwords, no corporate speak, just truth

2. Generous Support

• Extended severance packages
• Career counseling and resume support
• Allowed people time to transition rather than same-day exits
• Continued healthcare coverage during job search

3. Clear Strategy

• Explained what the company would look like after restructuring
• Showed how remaining roles aligned to new focus areas
• Provided roadmap for survivors, not just platitudes

4. Follow-Through

• Actually reduced scope to match reduced team
• Didn’t expect same output with fewer people
• Invested in remaining team’s development

That’s what “culture-first” should mean. And it’s rare.

The Constant Anxiety Problem

Keisha, you mentioned 736 people per day across the industry. That number creates ambient anxiety for everyone in tech right now.

Even if YOUR company isn’t cutting, your peers are getting laid off. Your professional network is full of talented people suddenly job hunting. The median re-employment time jumping from 3.2 to 4.7 months means people you know are struggling.

This affects:

• Retention (people leave proactively rather than wait for cuts)
• Innovation (hard to think creatively when you’re worried about survival)
• Collaboration (teams become political when resources are scarce)
• Recruiting (why join a company that might cut you in six months?)

My Question

How do we, as engineering leaders, maintain team cohesion and psychological safety during industry-wide instability?

We can’t control macro trends. We can’t prevent AI transformation. We can’t guarantee job security in an uncertain market.

But we CAN:

• Communicate honestly
• Treat people with dignity
• Match expectations to reality
• Invest in those who remain

The language we use—whether it’s “culture-first” or something else—matters less than whether our actions back it up.

And right now, I’m seeing a lot of great messaging paired with questionable actions. That gap is eroding trust faster than any single layoff could.

[product_david]

This thread is hitting on something crucial that I think about constantly from the product side: What happens to product strategy when you optimize for quarterly cost reduction instead of long-term value creation?

The Product Leader’s Dilemma

Luis, your timeline—Monday layoffs, Tuesday “how do we hit the same roadmap?”—is painfully familiar. But here’s what also happens:

Week 1: We lose the PM who understood our enterprise customers’ workflows
Week 2: The engineer who built our core pricing engine is gone
Week 3: The designer who ran all our user research leaves
Month 2: We’re making product decisions without the context that those people carried

“Culture-first restructuring” should mean aligning the team to product strategy. But what I’m seeing looks more like cost targets first, strategy justification after.

The Strategic Clarity Problem

Michelle asked how we distinguish genuine restructuring from continuous workforce reduction dressed up with better language. From a product perspective, here’s my test:

Do layoffs come WITH clear strategic pivots, or INSTEAD of them?

Examples of strategic alignment:

• “We’re exiting the SMB market to focus on enterprise” → cut SMB specialists, invest in enterprise
• “We’re sunsetting Product X to double down on Product Y” → restructure around the new focus
• “AI will handle Tier 1 support” → reduce support staff, invest in AI engineering and escalation specialists

Examples of cost-cutting disguised as strategy:

• Cut 15% “across the board” without product scope changes
• Eliminate entire teams while expecting other teams to absorb their responsibilities
• Reduce headcount but keep the same product roadmap and revenue targets

Guess which one I see more often?

The Customer Impact No One Talks About

Here’s what worries me most: customers notice when you gut the team.

When you lose:

• The account manager who knew their business
• The support engineer who understood their integration
• The product manager who championed their feature requests

Your customers don’t see “strategic restructuring.” They see response times increase, quality decline, and promises delayed.

And in B2B SaaS (my world), customer relationships ARE culture. When “culture-first” restructuring damages customer trust, you’re not preserving culture—you’re destroying your business.

Amazon, Block, Meta—What’s the Strategy?

Let’s look at the big cuts Keisha mentioned:

Amazon: 16,000 cuts

• Is this about AI efficiency? Refocusing on profitable segments? Market pessimism?
• They’re not explaining clearly, which creates uncertainty for everyone in e-commerce and cloud

Block: 40% reduction

• Forty percent! That’s not restructuring, that’s near-total reinvention
• What’s the product vision that requires 60% of previous team?
• Or is this panic-driven contraction?

Meta: 1,500 from Reality Labs

• This one actually makes strategic sense if they’re deprioritizing VR
• But are they? Or just cutting costs while keeping the same ambitious roadmap?

The problem is we don’t know. The “culture-first” framing doesn’t include enough strategic transparency to judge whether these are smart pivots or desperate moves.

The Innovation Tax

Luis mentioned that survivors become risk-averse. From a product perspective, this is devastating.

Innovation requires:

• Psychological safety to experiment and fail
• Resources to explore new ideas
• Time horizon beyond quarterly results
• Trust that leadership has a plan

When you’re at 60% staffing doing 100% of previous scope, none of those exist. Everyone’s in survival mode.

You can’t innovate your way to growth while simultaneously cutting your way to profitability. The strategies are contradictory.

My Take on “Culture-First”

Real culture-first restructuring would look like:

1. Strategy Drives Structure

• Clear product vision → team organized to deliver it
• Sunset products you’re not investing in → don’t keep skeleton crews
• Focus areas get resources → everything else gets cut or divested

2. Honest Customer Communication

• “We’re exiting this market segment” rather than slow decline in service
• “We’re focusing here, not there” rather than trying to do everything with nobody
• Customer expectations aligned to new reality

3. Investment Alongside Cuts

• If AI is the future, hire AI talent while reducing elsewhere
• If enterprise is the focus, invest in enterprise sales and success
• Show where the money from cuts is being redirected

4. Long-Term Value Over Short-Term Optics

• Sometimes cuts are necessary and healthy
• But they should set up future growth, not just improve this quarter’s margin

The Question I Keep Coming Back To

Are we optimizing for quarterly results or long-term value?

Because 736 people per day—55,911 workers in less than three months—doesn’t feel like strategic positioning. It feels like an industry-wide contraction.

And calling it “culture-first” without the strategic clarity to back it up just makes it harder for those of us trying to build real products with real teams to have honest conversations about what’s actually happening.

We owe our teams, our customers, and ourselves more honesty than that.

[maya_builds]

Reading through this thread, I keep thinking about my startup’s final months. We didn’t have 55,911 people to cut—we had 23. But the experience taught me something about the gap between how layoffs are framed and how they’re lived.

Culture Is What You Experience, Not What Executives Say

When leadership talks about “culture-first restructuring,” they’re usually in conference rooms looking at org charts and budget models. That’s not where culture lives.

Culture lives in:

• The Slack channel that goes quiet when people realize their colleagues are gone
• The all-hands where leadership says “remaining team is our top priority” while everyone updates LinkedIn
• The 1:1 where your manager can’t look you in the eye
• The moment you realize the company values you talked about in onboarding were just… words

My startup had great values on paper. Collaboration. Transparency. People-first.

When we hit financial trouble, those values evaporated. People were let go with minimal notice. Remaining team was asked to cover impossible gaps. Leadership communicated through vague all-hands rather than honest conversations.

The irony? Our final pitch deck still had a slide about our “people-first culture.”

The Geographic Reality Keisha Mentioned Hits Different When You’re Living It

I’m in Austin. Over the past three months, I’ve watched:

• My former coworker from IBM (laid off)
• A friend who was a senior PM at Oracle (laid off)
• Three people from my design systems community (laid off from different companies)
• My neighbor who was an engineering manager at Dell (laid off)

Seattle and San Francisco are taking bigger aggregate hits, but the density of impact in tech communities everywhere is profound. We’re not just seeing companies restructure—we’re watching entire professional networks collapse.

This creates ripple effects:

• Meetups have lower attendance (people are embarrassed or job hunting)
• Referral networks dry up (nobody’s hiring)
• Mentorship relationships strain (mentors can’t help mentees find roles)
• Community spirit erodes (everyone’s in survival mode)

“Culture-First” Feels Like Gaslighting Sometimes

David’s point about innovation under resource constraint resonates. But there’s something even more fundamental:

When you watch talented people escorted out of buildings, “culture-first” messaging feels like gaslighting.

It doesn’t matter if the executive memo says “we’re preserving our values” if the person being laid off:

• Gets two weeks severance after three years of work
• Loses healthcare immediately
• Is locked out of systems the same day
• Receives a generic message that could apply to anyone

The real culture test isn’t the memo. It’s how you treat people on the worst day of their professional lives.

What Genuine “Culture-First” Would Look Like

If companies were serious about preserving culture during necessary cuts:

Before layoffs:

• Transparent communication about financial situation
• Exploration of alternatives (reduced hours? pay cuts? voluntary departures?)
• Clear criteria for decisions (not “culture fit” which is often bias in disguise)

During layoffs:

• Dignity in the process
• Generous severance packages
• Extended healthcare coverage
• Time to transition rather than immediate lockout
• Honest references and job search support

After layoffs:

• Reduced scope to match reduced team
• Investment in remaining team’s growth
• Honest assessment of what’s no longer possible
• Rebuilding trust through consistent actions

I’ve seen exactly one company do all of this. Everyone else talks about culture while optimizing for quarterly optics.

The Hope Part (Because I’m Not Just Here to Vent)

Luis asked how we maintain team cohesion during industry-wide instability. From an IC perspective, here’s what’s mattered to me:

1. Managers who are honest

• “I don’t know if there will be more cuts” is better than false reassurance
• “Here’s what I know, here’s what I don’t know, here’s when I’ll know more”
• Treating us like adults who can handle hard truths

2. Leaders who match words to actions

• If they say “people are our priority,” they should act like it
• If they say “culture matters,” culture should influence decisions
• Consistency between messaging and behavior

3. Teams that support each other

• We check in on former colleagues who were laid off
• We share job leads and make introductions
• We’re honest about our own anxieties
• We remember that we’re people, not just resources

4. Individual agency

• Keep learning, keep building, keep your network active
• Don’t wait for company to invest in you—invest in yourself
• Have a plan B, because 736 people per day means none of us are safe

My Question for Leadership

Keisha, Michelle, Luis, David—you’re all in positions to influence how your companies handle this.

What are you doing to ensure that your company’s “culture-first” messaging matches the actual experience of people affected by cuts?

Because right now, there’s a massive trust deficit between leadership language and employee experience. And that gap is wider than any single layoff statistic.

The 55,911 people affected in 2026 deserve better than buzzwords. They deserve honesty, dignity, and genuine care—not PR-optimized euphemisms for cost reduction.

If we’re going to call it “culture-first,” let’s actually put culture first. Otherwise, let’s just call it what it is: layoffs. At least that would be honest.