79% of Tech Engineers Aren't Thriving. After Three Years of Layoffs, That's Not Surprising -- But It Is a Crisis.

79% of Tech Engineers Aren't Thriving: The Enterprise Employee Experience Crisis After Three Years of Layoffs

Only 21% of software engineers and engineering leaders surveyed in LeadDev's Engineering Leadership Report 2025 could be classified as "healthy" on standard burnout measures. The remaining 79% ranged from relatively low burnout to outright critical -- with 22% in the critical category and 24% in moderate distress. This is the state of enterprise employee experience in the US technology sector today.

Those numbers were published mid-2025. By the time you're reading this, another round of tech layoffs will likely have been announced. The wave that started in 2022 has never really ended -- it has just been renamed, reframed, and rescheduled quarter by quarter. And the workforce that survives each cut is carrying more, feeling less secure, and trusting their employers less.

This is no longer a burnout conversation. It's an enterprise employee experience crisis -- one that is beginning to affect product quality, innovation velocity, and the ability of US tech companies to hold onto the talent they most need to keep.

What Three Years of Layoffs Have Actually Done to the People Who Stayed

The immediate victims of a layoff are visible. The structural damage done to those who remain is less so -- but it compounds over time.

LeadDev's Engineering Leadership Report 2025 found that 38% of engineers and engineering leaders are working longer hours since the layoff cycle began, while only 7% are working less. The math is straightforward: headcount shrinks, expectations don't. Scope expands across a smaller team. And the implicit message from repeated cuts -- your role is always provisional -- lingers in every standup and planning cycle.

Researchers at the University of Washington, studying laid-off tech workers directly, found something striking: even workers who described tech jobs as often unfulfilling planned to stay in the industry. They were ambivalent -- attached to the identity, disillusioned with the reality. This ambivalent workforce is the one still showing up at your organization. Half-committed. Burned. Watching for what comes next.

This is what organizational psychologists call the "survivor syndrome" effect, and it's one of the least-discussed consequences of mass layoffs. Survivors frequently experience increased anxiety, decreased loyalty, and reduced willingness to take risks -- exactly the traits tech companies need their best engineers not to exhibit.

The Scope Creep Nobody Talks About Honestly

When teams shrink, individual scope grows. That's economics. But in knowledge work -- particularly in software engineering -- scope creep doesn't just increase workload. It changes the nature of the work itself.

Engineers hired to build are increasingly managing infrastructure they didn't design. Senior architects are doing the work of three people hired after the last RIF. Engineering managers are carrying direct reports they've never been able to properly onboard because the recruiting budget was frozen. The job title stayed the same. The job description quietly became unrecognizable.

ISACA's 2025 Tech Workplace and Culture Report identified role clarity and career advancement as top concerns for tech workers -- ahead of compensation in several categories. The organizations retaining talent are not necessarily paying the most; they are providing the clearest sense of what the job actually is and where it leads -- and investing deliberately in engineering employee experience to match.

Why "Culture" Initiatives Fall Flat -- and What Burnout Prevention Actually Requires

After a significant workforce reduction, many organizations respond with a wellbeing push: mental health resources, a town hall, an employee recognition program. These are not bad ideas. They almost never work well in isolation.

The reason is trust. Psychological safety -- the sense that you can speak honestly without career consequence -- is severely damaged by layoffs, especially when those cuts are perceived as opaque, unfair, or inconsistent with stated company values. You cannot rebuild trust with a wellbeing app if the underlying dynamic ("I might be next") hasn't been addressed.

Organizations that have successfully stabilized culture post-layoff tend to share three characteristics:

Radical transparency about what comes next. Ambiguity is the fuel of anxiety. Leaders who communicate clearly about the business outlook -- even when that outlook is uncertain -- give their remaining workforce something to work with. Silence implies the worst.

Genuine reductions in scope before new work is added. If a team of ten is now a team of six, the backlog needs to reflect that reality. Organizations that keep the same roadmap with a smaller team are accelerating burnout and guaranteeing quality degradation.

Recognition that rewards output, not presence. After years of return-to-office pressure and implicit performative productivity expectations, the teams recovering fastest are those that explicitly reward what people actually deliver -- measured against workloads that are honest about what's possible.

The Employee Wellbeing Gap Is Now a Business Risk

Tech employee experience has historically been treated as an HR issue. In a tight talent market, following years of reputational damage from mass layoffs, that framing is dangerously out of date.

Gallup's latest global workforce research shows disengaged employees cost organizations roughly 18% of their annual salary in lost productivity. In a sector where the median software engineer earns upwards of $130,000 in major US markets, that's a significant number applied across teams of dozens or hundreds.

But the deeper cost is competitive. The engineers who remain after layoffs have options. The best ones -- the ones companies most need -- are also the most marketable. If they aren't finding meaning, recognition, and genuine connection in their current roles, they are building profiles for the next opportunity. Tech workforce wellbeing is no longer a soft metric -- it is a competitive differentiator. The organizations that survive the current correction will not be those that cut deepest. They will be those that invested most deliberately in the experience of the people who stayed.

Three Things Tech Leaders Can Do to Strengthen Enterprise Employee Experience

Audit scope before you audit headcount. Before any further restructuring, map what individuals are actually delivering against their job descriptions. Where scope has expanded silently, acknowledge it explicitly and make resourcing decisions accordingly.

Build two-way communication channels that actually get used. Town halls are not enough. Regular, anonymous feedback mechanisms -- pulse surveys, open channels, structured skip-level conversations -- give employees a way to surface problems before they become attrition. And they signal that leadership is genuinely listening. Organizations that invest in a dedicated corporate engagement platform tend to see faster recovery in trust and communication scores after significant workforce changes.

Make recognition visible and consistent. After a period of instability, acknowledgement of individual and team contribution matters more, not less. Organizations that embed recognition into the operational rhythm -- not just the annual review -- see faster recovery in engagement and belonging scores.

The numbers in LeadDev's 2025 report are not an indictment of tech as a sector. They are a precise description of what sustained uncertainty does to skilled people. Fixing it requires honesty about what has happened, clarity about what comes next, and genuine investment in enterprise employee experience for the engineers still choosing to show up.

Technology organizations looking to rebuild genuine engagement and communication after periods of change can explore Me Business's enterprise employee experience platform or book a demo to see how the platform supports post-restructure recovery.