What to do after getting laid off as an engineer: a week-by-week plan

150,000+ tech workers have been laid off in 2026 so far. That's roughly 574 people per day, according to layoff trackers.

If you're one of them, you already know the standard advice: update your resume, network, apply to everything. You've probably started doing all three.

Here's the problem. That playbook is why most laid-off engineers end up sending 200+ applications, getting fewer than 10 callbacks, and wondering what's wrong with them.

Nothing is wrong with you. But something is wrong with the strategy. And the next 30 days matter more than the next 300 applications.

This is a week-by-week plan for engineers who just got laid off from tech. Not vague encouragement. Not "network more." A system.

---

Week 1: Handle the logistics before you apply anywhere

The instinct after a layoff is to immediately start applying. Resist it. The first week is for logistics, not applications. Every hour you spend here saves you weeks of wasted effort later.

Review your severance and sign nothing yet

Your company will hand you a separation agreement. It probably includes a severance payout, COBRA coverage details, and a release of claims. Do not sign it the same day.

You typically have 21 days to review (45 days if you're over 40, per the OWBPA). Use that time. Key things to check:

• Severance amount. Standard in tech is 2 weeks per year of service, but this varies. You can negotiate. Companies expect it.
• COBRA coverage. Confirm how long your employer-paid health insurance continues. COBRA lets you extend coverage for up to 18 months, but you pay the full premium (often $500-700/month for an individual plan).
• Non-compete and non-solicitation clauses. Some states (like California) don't enforce non-competes. Know your state's rules before you sign.
• Reference rights. Negotiate the right to list your manager as a reference. This matters more than you think.

If your severance is significant, spend $300-500 on an employment lawyer to review the agreement. It's worth it.

File for unemployment and sort out health insurance

File for unemployment benefits immediately. In most states, you can do this online on the same day. The weekly payout varies by state ($200-800/week typically), but it takes 2-3 weeks to start receiving payments. Don't wait.

For health insurance, you have three options:

1. COBRA. Keeps your current plan. Expensive, but nothing changes on your end. Good if you're mid-treatment or have a specialist you need to keep.
2. ACA marketplace. Losing your job is a qualifying life event, which gives you a 60-day special enrollment window. Plans can be significantly cheaper than COBRA.
3. Spouse's plan. If your partner has employer coverage, this is usually the simplest option.

If you're on a visa, your clock starts now

If you're on an H-1B, you have a 60-day grace period to find a new employer, transfer your visa, or change status. This is not flexible. USCIS is strict about this timeline.

Do these immediately:

• Talk to an immigration lawyer. Not next week. Now. Many offer free 15-minute consultations.
• File for B-1/B-2 change of status as a backup if your 60 days look tight.
• Focus your job search on companies that sponsor. This narrows your target list, which is a feature, not a bug. Targeted applications to sponsor-friendly companies will outperform 200 spray-and-pray applications to companies that don't.

If you're on a visa, everything in this article still applies. You just have less time, which makes the strategy even more important.

---

Why mass-applying after getting laid off from tech is the worst move

Here's what most engineers do after getting laid off: they update their resume once, open LinkedIn, and start hitting "Easy Apply" on everything that looks remotely relevant. 50 applications the first week. 100 by week two. 200 by month's end.

The result? A callback rate under 5%. Often under 2%.

This isn't because the market is impossible. It's because mass-applying with the same resume is the least effective job search strategy that exists.

The math behind low callback rates

The average callback rate for job applications sits between 10-20% when applications are targeted and tailored. When you mass-apply with the same resume? That drops to 2-5%.

Here's why. An estimated 75% of resumes are filtered out by applicant tracking systems before a human ever sees them. ATS software scans for keyword matches between your resume and the job description. If you're sending the same resume to a backend role, a data engineering role, and a DevOps role, you're failing the keyword match on at least two of those.

The 25% of resumes that make it past ATS then go to a hiring manager who spends an average of 6-7 seconds on their first scan. In that scan, they're looking for one thing: does this person's experience match what we need for THIS role?

If your resume reads like a general-purpose engineering summary, the answer is usually no.

The targeting problem nobody talks about

Every article about layoff recovery tells you to "tailor your resume." But nobody explains what that actually means.

It doesn't mean swapping a few keywords. It means understanding, for each specific role, which of your skills and experiences match, which ones are missing, and whether the gaps are dealbreakers or coachable.

Think about it like this. Every job ad has 5-8 requirements. You probably match 4-6 of them. The question isn't whether you're qualified. The question is whether your resume makes it obvious that you match the 4-6, and whether the 2 you're missing are things the hiring manager will overlook.

That's a gap analysis. And it's the step that most laid-off engineers skip entirely.

Tools like InterviewOS can run this analysis automatically, comparing your resume against a specific job ad and showing you exactly where the gaps are. But even if you do it manually, the principle is the same: diagnose before you apply.

---

Week 2: Diagnose before you apply

By week two, your logistics should be handled. Now it's time to build your targeting strategy. Not your resume. Your strategy.

Map your skills to the roles you actually want

Open a spreadsheet. List 10 roles you're genuinely interested in (not 100, not 50, ten). For each one, answer:

• What are the top 3-4 non-negotiable requirements?
• Which of those do I have clear evidence for on my resume?
• Which ones am I missing or can't demonstrate?

This takes about two hours. It will save you weeks.

What you'll find: you're a strong fit for 3-4 of those roles, a partial fit for another 3-4, and a stretch for the rest. That's normal. The point is to know which is which before you start applying.

Find the gaps between your resume and specific job ads

For the roles where you're a partial fit, the gaps matter. Is the gap "5 years of Kubernetes experience" when you have 2? That's closable. You can reframe your resume to foreground related container orchestration work.

Is the gap "machine learning experience" when you've never trained a model? That's a different problem. You either need to upskill first or deprioritize that role.

The point isn't to only apply to perfect matches. It's to understand, before you click "apply," whether your resume will make it past the 6-second scan.

You can do this manually by reading job ads carefully. Or you can use a tool like InterviewOS to see your gap analysis against a specific role in minutes. Either way, the diagnosis happens before the application. Not after 200 rejections.

Rewrite for the role, not for "the job market"

Once you know your gaps, rewrite your resume for each cluster of similar roles. Not 200 versions. Three or four.

If you're targeting backend roles at mid-size companies, that's one resume version. If you're also looking at data engineering roles, that's a second version with different emphasis on the same experience.

The key: every bullet on your resume should answer the question "does this match what the hiring manager is looking for in THIS type of role?"

If a bullet doesn't serve that purpose, cut it. Replace it with something that does.

---

Weeks 3-4: Launch a targeted job search

You've handled logistics. You've diagnosed your fit. Now you apply. But differently.

10 targeted applications beat 100 spray-and-pray

This is counterintuitive when you feel the pressure to "do more." But the data backs it up. Targeted, tailored applications convert at 15-22%. Generic mass applications convert at 2-5%.

Ten applications at 20% = 2 callbacks. One hundred applications at 3% = 3 callbacks. The math is clear: you get nearly the same result with 90% less effort, and the quality of those callbacks is higher because you actually fit the role.

For each application:

1. Read the full job description. Not just the title.
2. Check your gap analysis. Do you match the top requirements?
3. Adjust your resume to foreground the relevant experience.
4. Write a targeted cover letter if the application allows it (2-3 sentences connecting your experience to their specific needs).

Activate your network with specificity

"I'm open to new opportunities" is the least useful LinkedIn post you can write. Hiring managers scroll past it. Your network doesn't know how to help.

Instead, be specific:

• "I'm looking for senior backend roles at Series B-D companies in fintech or healthtech. I have 6 years of experience building payment systems in Go."
• "If anyone knows engineering managers at [Company A], [Company B], or [Company C], I'd appreciate an intro. Here's why I think I'd be a strong fit: [one sentence]."

People want to help. They just need to know exactly what help looks like.

The LinkedIn post that gets responses

Post about your layoff. It works. But skip the "grateful for the journey" template. Here's a format that gets responses:

1. State the facts. "I was laid off from [Company] on [date] as part of a reduction in force."
2. Say what you're looking for. Specific role type, specific company stage, specific tech stack.
3. Make it easy to help. "If you know someone hiring for X, I'd appreciate a DM."

58% of recruiters actively look for context around employment gaps. Being upfront about the layoff removes the question mark.

---

Common mistakes that keep laid-off engineers stuck

Applying to everything on day one

The urge to "do something" is real. But applying to 50 roles with an untargeted resume on day one means burning 50 chances before your strategy is ready. Those companies now have your generic resume in their ATS. You usually can't reapply for 6-12 months.

Handle logistics in week one. Diagnose in week two. Apply in week three. The delay feels painful but converts better.

Ignoring the skills gap

"I have 8 years of experience, I should be getting callbacks." Maybe. But the market has shifted. AI/ML is showing up in job requirements that didn't mention it two years ago. Cloud-native architecture is table stakes. If your resume doesn't reflect where the market is now, experience alone won't carry you.

New software engineering postings declined 15% in early 2026 compared to 2025. Fewer roles means higher competition. The engineers landing interviews are the ones who can demonstrate current, relevant skills for the specific roles they're targeting.

Waiting until you "feel ready"

There's no perfect moment. Your resume won't be perfect. Your confidence won't be fully restored. The best time to start your targeted search is when you've done the diagnostic work, not when you feel emotionally ready.

79% of laid-off tech workers found a new role within three months. That's the actual data. The market is hard, but it's not impossible. You're more hireable than your anxiety is telling you.

---

What to do next

Getting laid off is disorienting. The instinct is to move fast and apply to everything. The better move is to slow down for two weeks, diagnose your fit, and then apply with precision.

Here's the short version:

1. Week 1: Severance, unemployment, health insurance, visa status. No applications.
2. Week 2: Gap analysis. Which roles fit? Where are your gaps? Rewrite your resume for 3-4 role clusters.
3. Weeks 3-4: Ten targeted applications per week. Specific networking. Track your callback rate.

If you want to see the specific gaps between your resume and a role you're targeting, try InterviewOS. Upload your resume, paste the job ad, and you'll see your gap analysis in minutes. It shows you exactly what a hiring manager will see when they scan your resume against their requirements.

The problem isn't you. It's the strategy. Fix the strategy, and the callbacks follow.

---

FAQ

How long does it take a laid-off engineer to find a new job?

The average is 2-4 months for tech professionals. A ZipRecruiter survey found that 79% of laid-off tech workers found jobs within three months. Senior roles and niche specialties can take longer. The timeline shrinks significantly when you target roles that match your profile instead of mass-applying.

How do I explain being laid off in an interview?

Keep it short and factual. "My team was part of a reduction in force at [Company]. I'm now focused on finding a role where I can [specific contribution]." Then pivot to why you're excited about THIS role. Interviewers don't care that you were laid off. They care whether you can do the job.

Should I take the first job offer after a layoff?

It depends on your runway. If you have 3-6 months of severance, don't take a role out of panic in month one. Use the time to find the right fit, not just any fit. If you're on a visa with a 60-day clock, your calculus is different. Take the best available offer to maintain status, and keep searching if it's not ideal.

Is it harder to get a job after being laid off?

Research from the Bureau of Labor Statistics shows that unemployment duration alone doesn't significantly reduce callback rates. What hurts is an unexplained gap and an untargeted application. Address the layoff directly and apply strategically, and you're on the same footing as any other candidate.

What should I do on day one after being laid off?

Don't apply to anything. Secure your personal files and access before your corporate accounts are revoked. Screenshot any performance reviews, project documentation, or metrics you might need for your resume. Review (but don't sign) your severance agreement. File for unemployment benefits online. That's day one. If you just got laid off from tech, the single best thing to do on day one is protect your logistics, not send applications.