Last updated: September 11, 2026
By Mike Carter, Managing Director, KORE1
Most companies hiring after layoffs rebuild with contract talent first, because contractors restore capacity in weeks without betting a permanent headcount line on demand that hasn’t proven itself yet. Permanent reqs come back later, once the work has shown up two quarters in a row. Run in that order, a rebuild costs less, unwinds cleanly if the recovery stalls, and holds up far better if anyone ever asks why the cut happened in the first place.
September is a strange month to be writing this. The cutting hasn’t stopped. It has slowed, though, and in technology it slowed hard. Challenger, Gray & Christmas counted 6,103 tech job cuts in August, the sector’s lowest month of 2026, in a year that’s still running 52 percent ahead of 2025 with 155,126 tech cuts through eight months, according to the firm’s August 2026 job cuts report. Announced hiring plans across all industries are up 37 percent year to date.
Andy Challenger put one line in that report I keep coming back to. He noted the hiring plans were running ahead of last year’s, then added the part that matters to anyone reading this. “It doesn’t appear those positions are being filled quickly.”
Plans to hire. Not hires. Most of the calls we’re taking this month live somewhere in that gap.
What fills it first is almost never a full-time employee. Economists at the Bureau of Labor Statistics wrote about this exact pattern in a 2021 Monthly Labor Review analysis that looked back over the three recessions before COVID. Their version is drier than mine. When the economy expands, “employers are able to ramp up quickly by using temporary workers until permanent staff are hired.” Temp jobs came back several months before the broader labor market did each time. The early version of that is visible right now, too, with temporary help services employment at 2,519,500 in August 2026, up roughly 29,000 since April, per BLS data tracked by the St. Louis Fed.
A staffing firm arguing for contractors is about as surprising as a steakhouse recommending the ribeye, so weigh this accordingly. KORE1 runs contract staffing for technology and professional teams, and we make money when companies rebuild this way. There are also seats where I’d tell you to skip contract entirely. I’ll name them further down.
Contract-First Rebuilding, Defined
Contract-first rebuilding means restoring capacity after a reduction in force with contract and contract-to-hire workers before you reopen permanent requisitions, then converting or replacing those seats with full-time hires once the demand behind them has held steady for at least two quarters.
It is not the same thing as laying people off and sliding cheaper contractors into their chairs. People confuse the two. That second move undercuts the reason you gave for the layoff, and plaintiffs’ lawyers have a word for a stated reason that doesn’t hold up. Pretext.
The difference is what the new person is doing all day. Finishing the Snowflake migration the cut left half-built is rebuilding. Doing the exact job you told someone no longer existed is something else. Lawyers notice that one.
Why the First Hires Back Are Usually Contractors
Start with the forecast. Every layoff rests on a demand model, some spreadsheet that said revenue or pipeline or product scope was going to come in smaller than the team had been built for. When work comes back, the reflex is to reopen reqs. Finance will push back. You’d be reopening them on the word of the planning process that got the size wrong once already, and I have yet to meet a CFO who signed severance checks in March and was eager to sign offer letters in October off the same kind of spreadsheet. A contract seat asks for far less trust. It runs for a defined term, it sits outside the headcount number the board just watched you reduce, and if the recovery fizzles in the first quarter you end an engagement instead of announcing a second round.
Then there are the people who stayed.
They’ve been carrying the departed team’s on-call rotation, its backlog, and half its Slack channels since the day of the announcement. They’re tired. Charlie Trevor and Anthony Nyberg put a number on what a layoff does to the people left behind, in a study published in the Academy of Management Journal, and it’s an ugly one. Cutting a workforce by 1 percent was followed by a 31 percent increase in voluntary turnover the next year. I read that twice. So the rebuild isn’t only about new work. It’s about getting load off your survivors before the good ones start returning recruiters’ calls, and a contractor can be working that backlog in two weeks while a permanent search in a tight stack is still booking final rounds.
Here’s what that looked like at a Series C fintech in Irvine this year. They cut 14 percent of engineering in February, including both people who understood the company’s dbt models. By May, the Snowflake migration those two had started was stuck at roughly 60 percent, and finance wanted the old warehouse contract gone before Q3 ended. The VP of Engineering asked for two full-time data engineers. The CFO said no. Not until the second-half numbers came in, anyway. They settled on two contract data engineers for sixteen weeks at about $140 an hour, which sits inside the $108 to $175 range in our 2026 tech contractor rate table. The migration closed in August. One of the two is converting to full-time this month, now that next year’s roadmap has a budget behind it. The other moved on to a different client. He was always a sixteen-week hire.
Speed gets mentioned first by almost everyone. I’d rank it third. Our average IT search closes in 17 days, which is quick, but fast isn’t what gets a rebuild through finance. Reversible is.
The Six-Month Rule Isn’t in Any Statute
Look up advice on hiring after a layoff and one instruction shows up everywhere. Wait six months before filling a role you eliminated. HR blogs repeat it, and so do most of the pages ranking for this topic. It isn’t law. It’s a decent instinct wearing a costume of law.
No federal statute sets a waiting period. The WARN Act is about notice. Covered employers, generally the ones with 100 or more people, owe workers 60 days’ warning before a qualifying plant closing or mass layoff, and hiring afterward never comes up.
The six-month figure comes from somewhere else. An employee who believes a layoff was discriminatory generally has 180 calendar days to file a charge with the EEOC, and that deadline stretches to 300 days wherever a state or local agency enforces a similar law. Most states have one. California does. Age claims are pickier, since they only get the longer window when a state law and a state agency cover age discrimination, and a city ordinance by itself doesn’t count. If you’re hiring in Irvine or San Jose, then, the window people are nervously counting down is closer to ten months than six. Honestly, the calendar was never the real issue.
The pattern is. A layoff says “this position is no longer needed,” and everything you do afterward either supports that sentence or contradicts it.
| What people assume | What the rule actually says |
|---|---|
| You have to wait six months before hiring again. | No federal waiting period exists. The number traces to the EEOC’s 180-day charge deadline, which becomes 300 days in states with their own enforcement agency. |
| WARN restricts rehiring. | WARN governs notice before a qualifying layoff, 60 days for covered employers, and is silent on hiring afterward. |
| A contractor in the old seat doesn’t count. | A contractor doing the eliminated job contradicts the stated reason for the cut the same way a new employee would. |
| Bringing our own people back is always safe. | Usually the lowest-risk option, unless they return as 1099 contractors doing their old job, which runs straight into the IRS control test. |
| Age only matters when deciding who gets cut. | Group severance releases for workers 40 and over come with written disclosures of who was selected and who wasn’t, by age. The people you hire back will be read alongside that list. |
The last row surprises people. When severance in a group layoff comes with a release of age claims, the Older Workers Benefit Protection Act kicks in for everyone 40 and over. They get 45 days to think it over. Then seven more to change their minds. And they get a document most hiring managers have never laid eyes on, a written list of the job titles and ages of everyone in the decisional unit who was picked, sitting next to the ages of the people in those same jobs who weren’t, according to the EEOC’s guidance on severance waivers. That list exists. It is sitting in a file somewhere in your HR system. If the people you bring on for similar work six months later are a decade younger than the ones who left, nobody needs a subpoena to notice.
A healthcare IT company in Los Angeles found the other half of this out the awkward way. Eleven weeks after a reduction, a hiring manager reposted an Integration Analyst II req with the old job description pasted in word for word, typo included. One of the analysts who’d been let go saw it on LinkedIn the next morning. She took a screenshot. Nothing came of it legally. Their counsel had the posting pulled, rewrote the role around the HL7-to-FHIR interface work that was genuinely new, and put the first six months of it on a contractor while the scope settled. Cheap lesson. Could have been an expensive one.
Before anything resembling an eliminated role goes live, contract or permanent, we ask clients to have these on paper:
- A dated description of the work that’s new since the reduction, with the business reason that created it.
- A different title, a different scope, or both. Reposting the old job description is the single easiest mistake to avoid, and people still make it.
- Sign-off from employment counsel. Twenty minutes of their time costs less than one demand letter.
- A decision on whether the laid-off group gets invited to apply, which is often the cleanest signal you can send.
I’m not your lawyer. I place contractors for a living, and your employment counsel is the person to call before you post anything that shares a title with a role you cut.
Bringing Back Your Own People on Contract
The fastest rebuild usually isn’t a stranger. It’s the engineer you let go in March who still knows why the billing service falls over at every month-end close. She’d probably pick up. A lot of them would. Our tracker of where displaced tech talent is landing in 2026 has contract and fractional work as the fastest-growing destination for laid-off senior engineers, and plenty of them would rather do a three-to-six-month engagement than rush into the next full-time offer.
Where it goes sideways is the paperwork. The company pays them as a 1099 through accounts payable, same manager, same standup, same Jira board, same laptop, no end date. That isn’t a contractor. Under the IRS common-law test, what matters is whether the business has “the right to control the details of how the services are performed,” and a returning employee doing their old job for their old boss looks like an employee on nearly every factor the IRS weighs.
Microsoft paid for a much bigger version of this lesson. It had classified thousands of people as temps and freelancers, and some of them had been on its campus for as long as 14 years. They sued over being locked out of the employee stock purchase plan. Microsoft settled in December 2000, and the check came to $97 million, split among somewhere between 8,000 and 12,000 current and former workers. Classification follows the work. The paperwork doesn’t get a vote.
The safer shape is a W-2 contract through a staffing firm, with an end date and a scope that’s actually different from the old job. It costs more per hour. The firm becomes the employer of record, handling payroll, taxes, and workers’ comp, and the engagement has a defined finish. For the mechanics of W-2 against 1099 against corp-to-corp, our breakdown of contractor classification covers it. If what you really want is the person back permanently, that’s a different decision with different math, and Robert Ardell worked through it in his piece on what it costs to rehire the people you cut.
One more thing before anyone dials. Read the separation agreement. Some include no-rehire language that somebody will have to waive in writing.
Sorting the Post-Reduction List, Seat by Seat
Not every seat belongs on contract. A few shouldn’t go anywhere near it. Here’s how we’d sort a typical post-reduction list for a technology org, with bill rates pulled from our 2026 rate data.
| The seat | Start it as | Why | Typical 2026 bill rate |
|---|---|---|---|
| Backlog the cut left half-finished, like a migration, an ERP upgrade, or a platform cutover | Contract, 3 to 6 months | The work has an end, so the engagement should too | $108 to $175 an hour for a data engineer |
| Coverage the survivors are absorbing, such as on-call, release management, and support rotations | Contract-to-hire | Probably durable, and you find out before you commit | $85 to $140 an hour for DevOps |
| Security or compliance work with a date on it, like SOC 2 evidence or an audit remediation | Contract | Auditors don’t reschedule around your rebuild plan | $115 to $175 an hour for cybersecurity |
| The new capability the restructuring was supposed to fund | Direct hire | The strategy rides on it, and the strongest candidates won’t take it on contract | Salary, not a bill rate |
| Engineering managers and team leads | Direct hire, or an interim leader for one quarter | A team that just watched colleagues leave needs someone who’s staying | Salary, not a bill rate |
| An eliminated role you now need back unchanged | Nothing yet. Call counsel first. | This is where the pattern risk lives | Not applicable |
Rows four and five are the ones staffing firms tend to mumble through. We place those too. If the whole point of the reduction was to move money toward, say, an AI platform team, those first hires carry the plan, so put them on direct hire and pay what the market asks. A contractor can build you a prototype. Owning it for three years is a job.
A Rebuild Sequence That Holds Up
Order matters more than the ratio does. What follows is the sequence I’d run, and it’s close to what the smoothest rebuilds we’ve staffed this year have looked like, give or take a month.
Quarter One: Stabilize
Stabilize before you build. Contract seats go to the backlog and to whatever coverage is grinding down the survivors, and nothing with a permanent req number goes out for any title that resembles one you eliminated. Screen those contractors for the work in front of them, not for a five-year culture fit. The interview changes too. Interviewing contract developers and engineers takes a different loop than a permanent search. Spend the quarter writing down, in plain language, what new work has appeared and why. Most teams skip this. That document ends up doing two jobs later on. It justifies the hiring, and it answers the question if anyone ever challenges the reduction.
Months Three to Nine: Test the Demand
By now the demand is either holding or it isn’t. You’ll know.
Where it’s holding, move those seats to contract-to-hire and write the conversion date into the agreement before the person starts. Candidates notice. They take a C2H offer more seriously when a real date is attached. The fee structure lines up with that timeline, too. Under KORE1’s standard agreement, converting someone costs 20 percent of first-year salary during the first 800 billed hours, drops to 15 percent between 800 and 1,040 hours, and goes to zero after that. Around the six-month mark the conversion is free, which is also about when a hiring manager has seen enough to know. When a term runs out before the demand is clear, deciding whether to extend, convert, or release is its own call, and it deserves more than a default renewal.
Month Nine Onward: Hire the Owners
Now the owners get hired. Convert the contractors who earned it, end the engagements tied to finished projects, and open direct-hire searches for the leadership seats and the new capability the reduction was meant to pay for. By this point the demand has a track record and the documentation exists. You’re also coming up on the end of the 300-day charge window in most states, which is a coincidence of timing rather than the reason for it, and nobody should build a staffing plan around a filing deadline. It doesn’t hurt when they line up.
If the Cut Wasn’t Yours
Plenty of companies reading this didn’t lay anyone off. They froze. Then they watched Oracle and Amazon and a dozen others cut, and now they want to hire into a market full of experienced engineers. Same logic, lower stakes. The senior people coming out of those reductions are open to contract work in a way they weren’t two years ago, and an engagement lets both sides find out whether a smaller company without the big-tech perks is somewhere they’d actually stay. It goes both ways. If your own freeze hasn’t lifted yet, the contract staffing during a hiring freeze page is the better place to start.
Where Rebuild Conversations Usually Get Stuck
Is there a legal waiting period before we can hire again after a layoff?
No federal law sets one, and the six months people quote traces back to the EEOC’s 180-day charge deadline, which stretches to 300 days in states with their own enforcement agency. The real exposure is contradicting your own reason for the cut, by reposting an eliminated role or filling it with someone doing the same job, so bring counsel in before anything similar goes live.
Can a laid-off engineer come back as a 1099 contractor?
Sometimes, but a returning employee doing the same work under the same manager will almost always look like an employee under the IRS control test, so a W-2 contract through a staffing firm is the safer route. Give it a new scope. Put an end date on it, too, and then check the separation agreement for no-rehire language before anyone makes the call.
Do contractors count against the headcount we just cut?
On most org charts and in most board reporting they don’t, because contract labor is usually tracked as vendor spend rather than headcount, and that’s a large part of why rebuilds start there. Check how your own finance team defines it, though. They’ll know. Some boards count every badge in the building.
What happens when the contractor turns out to be the permanent answer?
Convert them, ideally on a conversion date agreed before they started, and under KORE1’s standard terms the fee shrinks as hours accumulate and reaches zero after 1,040 billed hours. Most managers know by then.
Is contract-first ever the wrong call?
For managers and for the capability the reduction was meant to fund, it usually is, because those seats need someone who’ll own the outcome for years, and the strongest candidates won’t take them on contract. Morale matters here too. A team that just watched a round of colleagues walk out reads a contract manager as a sign the company isn’t sure it’s staying either, and I can’t say they’re wrong to read it that way.
Realistically, how fast can a contract seat get filled this fall?
Seventeen days is our average across IT searches, and contract seats in common stacks like AWS, Kubernetes, and Snowflake often come in under that. Senior security searches run longer.
Rebuild in an Order You Can Undo
Every reduction is a forecast. The rebuild is where you find out how far off it was, and in which direction. Contract seats let you place the next bet one quarter at a time instead of all at once.
KORE1 has been filling technology and professional seats since 2005, and we keep track of what happens afterward. Ninety-two percent of our placements are still employed there a year later. If you’re sorting a post-reduction list right now, trying to decide which seats go contract, which convert, and which need a permanent hire on day one, talk it through with a KORE1 recruiter. Bring the list of what got cut and what came back. We’ll tell you which half is ours.
