How to Bounce Back After a Tech Layoff

The call lasted 14 minutes. HR, a manager I’d met twice, and a line about “restructuring aligned to business priorities.” Then my Slack went read-only and my laptop pulled its last email sync. It was a Tuesday in March 2024.

If something similar just happened to you, here’s the honest picture: tech layoffs aren’t slowing down. Crunchbase’s running tracker logged at least 95,000 U.S. tech job cuts in 2024 and roughly 127,000 in 2025 – Intel, Microsoft, and Amazon each shed more than 14,000 roles. The macro signal doesn’t tell you how to get back on your feet, though. That’s what this is.

Week one: logistics before momentum

Don’t touch your resume for the first week. I know that’s counterintuitive – the urge to spray applications everywhere is strong, especially when the gap clock feels like it’s already running. But applications written from a place of panic don’t read well, and they don’t target well either.

Four things to handle in days 1-7:

• File for unemployment that day. Processing takes 2-3 weeks at most state agencies. File before you do anything else. You’ve paid into this system for years.
• Read your severance agreement before signing. Many companies have a standard 21-day review period baked in. If there’s a non-compete or broad IP assignment clause, a single hour with an employment attorney ($200-400 at most firms) can tell you whether it’s worth pushing back.
• Sort health insurance by day 7. COBRA keeps your existing coverage but is expensive – expect to pay the full premium your employer was covering plus a 2% admin fee. Healthcare.gov marketplace plans triggered by a qualifying life event (job loss counts) are often cheaper, especially if your income will drop this year.
• Tell your network before you’re ready. Not a mass announcement – a direct message to the 10-15 people who know your work and have hiring influence in their circles. The sooner they know, the sooner the right introduction can happen.

Your financial runway determines your strategy

Before you can decide how selective to be, you need a number. Add severance, unemployment benefit estimates, and current savings. Subtract monthly fixed costs. That quotient – months of runway – is your actual job search budget.

Six or more months means you can afford to wait for the right role, negotiate hard, and turn down first offers. Two months means something different: contract work, part-time roles, and a parallel permanent search all happening at once. Neither situation is wrong. But searching without knowing your number produces bad decisions, like holding out for a dream company when you have 6 weeks of cash left.

One thing to skip: tapping a 401k early. The 10% penalty plus the income tax hit at your marginal rate makes it an expensive bridge. It’s a last resort, not a plan.

The job search math most people get wrong

Volume feels like progress. It usually isn’t.

Ashby analyzed 38 million applications across 93,000 jobs from 2021 through 2024. Referrals represented about 1% of total applications but produced 40% interview conversion rates – versus the low single digits for cold inbound. The same dataset showed roughly 18% of all hires at companies of various sizes came through referrals, despite that tiny application share.

That’s the math. A warm referral from someone at the company is worth somewhere between 20 and 50 cold applications depending on the role and company.

The practical implication: post on LinkedIn that you’re looking before you start applying anywhere. Something short and factual works fine – “My role was eliminated in [Company]’s recent restructuring. Open to senior engineering roles in [area]. Happy to connect if your team is hiring or you know someone who is.” Most people skip this because it feels vulnerable. The ones who post usually find a lead within a week.

Structure your search like actual work

Set hours. 9 AM to 1 PM works well for most people – mornings for outreach and applications, late morning for interview prep, afternoons free. The afternoons matter. A job search with no downtime turns into a search with no stamina, and most searches take longer than people expect.

Track applications in a simple spreadsheet: company, role, date applied, source (cold/referral/recruiter), status. After 3 weeks you’ll have a real read on what’s converting and what isn’t. If cold applications have a 0% response rate, stop doing them and redirect that time to warm outreach. If recruiter inbound is generating interviews, make your LinkedIn profile the thing they find first.

Answering “why did you leave?”

This question worries people more than it should. The honest answer is the best answer: “My position was eliminated in a company-wide reduction.” That’s it. Don’t apologize, don’t over-explain, don’t badmouth the company – not because of politeness, but because none of those things help you and at least one of them actively hurts you.

Every interviewer in tech right now understands layoffs. They’ve either been through one or managed through one. The answer lands fine. What actually matters is what you do after it – which is pivot directly into why you’re interested in this specific role.

Getting sharp for interviews again

If you haven’t interviewed in 2-3 years, your behavioral stories are stale and your technical fundamentals have probably drifted. This is normal. Engineers spend most of their time in a specific codebase, not practicing distributed systems explanations.

Give yourself 2-3 weeks of prep before the first real interview if you can. That’s enough time to refresh system design fundamentals, revisit the behavioral questions you’ll definitely get (tell me about a conflict, a project you failed, a time you disagreed with a manager), and sharpen your code if the role requires it. The behavioral interview questions guide covers the patterns that come up most reliably.

One thing that’s become genuinely useful for this stage: AI mock interview practice. The feedback is blunter than what you’ll get from a friend, and blunter feedback is actually what you need when you’re rusty. Users running mock sessions on LastRoundAI consistently find that their first attempt at a STAR-format answer runs 30-60 seconds too long – something that’s hard to notice in your own head but immediately obvious in playback. You adjust faster when the feedback is specific.

How long this actually takes

I won’t tell you it’ll be quick, because I don’t know your situation – your level, your location, your target companies, how updated your skills are. Most senior engineers I know who went through layoffs in 2024 and 2025 found something in 2-4 months. Some took 6. One person I stayed in touch with took 8 months and ended up with an offer from a company he’d never heard of before the search, doing work he says is the most interesting of his career.

I think the people who take longer are often the ones who stay too narrow too long – only targeting the same tier of company they came from, only looking in one city, only applying to the exact same title. The layoff is a forced reset. It’s worth asking whether your next role should look exactly like the last one.

That’s a genuinely debatable point, and I’m not sure the answer is the same for everyone.