When Companies Lay Off Then Rehire: What's Really Happening

The cycle has become predictable enough that people have stopped being surprised by it. A major tech company announces thousands of redundancies, the press covers the human cost, and then eight months later the same company posts hundreds of job adverts for roles that look suspiciously similar to the ones they cut.

This isn't mismanagement. Well, not always. It's usually something more specific: a forced reckoning with how the company was actually structured, triggered by a cost event that gave leadership the political cover to do what they knew needed doing.

The Redundancies Aren't What They Look Like

When Salesforce cut 10% of its workforce in early 2023 and then hired aggressively through the year, the headline was "chaos". The reality was more deliberate. They were reshaping around a different productivity model, one where engineers supported by AI tooling could cover more ground per head. The roles that went were often in areas where output was proportional to headcount in a near 1:1 way. The roles that came back were in areas where leverage was possible.

That distinction matters. If you're watching from the outside and thinking "these companies don't know what they're doing", you're misreading the signal. Most of these cycles are a blunt but effective way to reset the composition of a workforce without going through the slow, painful process of retraining everyone in place.

The Org Debt Problem Nobody Talks About

Most companies accumulate what I'd call organisational debt alongside technical debt. Roles get created to solve problems that no longer exist. Teams grow to handle volume that could now be automated. Processes get headcount attached to them when the right answer was identifying automation opportunities and removing the manual step entirely.

When a funding environment tightens or a board demands efficiency, a layoff is often the fastest way to clear that debt in one move. Redeployment and retraining take longer and require more management bandwidth than most leadership teams have when they're also trying to keep the business running.

The rehiring that follows is not the same workforce in different clothes. The new roles tend to require different skills: data fluency, AI tool proficiency, comfort with automation, and the ability to work alongside systems that weren't there two years ago.

What This Means If You're Building or Scaling a Team

If you lead a growing business or a scaling startup, this cycle should change how you think about headcount planning. The companies going through these painful rounds largely over-hired into a model that assumed linear productivity gains from linear headcount growth.

That assumption is broken. A developer working with AI coding tools is more productive than two developers without them. A customer success team using automated business workflows to handle routine queries has more capacity per person than one doing everything manually.

This doesn't mean you hire fewer people. It means you hire differently: fewer people doing repetitive, volume-based work; more people who can own outcomes rather than tasks.

The Capacity vs Capability Test

Before adding a role, run a two-question check.

First: is this role needed because there's too much work for the current team to do? That's a capacity problem. Capacity problems can often be solved with automation or tooling before they become hiring decisions.

Second: is this role needed because the current team lacks a skill or expertise area? That's a capability gap, and it usually can't be solved by a tool.

If you're hiring for capacity, you're building a future redundancy programme. If you're hiring for capability, you're investing in a skill that compounds.

I've seen this play out directly. A client we worked with through an architecture review and system design engagement had hired three people to handle data reporting and dashboard maintenance. The workload was real, but the root cause was an architecture that made reporting unnecessarily hard. We rebuilt the reporting layer, and those three people were redeployed onto work that actually required their judgement. The capacity problem vanished; the capability they brought didn't.

The Role of Technical Leadership in Breaking the Cycle

One pattern I see in companies that avoid this yo-yo is that they have someone with a technical leadership mandate who sits close enough to strategy to flag when headcount is being used as a solution to a systems problem.

That role doesn't have to be a full-time internal CTO. Fractional CTO Advisory works well for companies that aren't yet at the scale where a full-time technical leader makes sense economically. The point is to have someone asking "could we build this instead of hire for it?" before the job description gets posted.

The companies that skip this step end up hiring at the wrong layer, and they find themselves either over-staffed when the system improves or under-capable when the market shifts.

What the Rehiring Wave Tells You About AI Adoption

Pay attention to the profiles of the roles being hired in the second wave. At most major tech companies, the rehiring skews toward AI engineers, ML platform roles, and product managers with data and automation backgrounds. The roles that were cut were often in areas where AI tooling had made, or would make, the work faster per person.

This is a live demonstration of the digital transformation strategy question every business should be asking: where in our operation is the output-to-headcount ratio about to shift? The companies getting this right are modelling it before they have to act. The ones getting it wrong are finding out via a redundancy announcement.

The rehiring wave isn't a correction. It's a signal that the company has figured out where it wants to invest. The question for you is whether you can get there without the layoff round first.

Get a Clear Picture Before the Next Hire

If your business hasn't stress-tested its hiring decisions against what could be automated or simplified, an AI Discovery Sprint gives you a structured AI readiness review and a clear picture of where automation can absorb capacity before you commit to headcount. Fixed price, no long contract, and no guesswork about what you're buying.