Laid Off Software Engineer? Your 30-Day Action Plan for 2026

A laid off software engineer should spend the first 72 hours protecting money, health coverage, and legal options, then spend the next four weeks building a high-volume job pipeline backed by focused interview prep. The order matters: severance agreements, COBRA elections, equity windows, and visa grace periods all start ticking on your last day, while job applications can wait a few days. This guide gives you a day-by-day 30-day plan plus word-for-word scripts for interviews, recruiters, and LinkedIn.

Key Takeaways

• Do not sign a severance agreement on the day you get it. Read it, list every deadline, and ask questions in writing.
• H-1B workers in the US generally get up to 60 days after their last day of employment, and severance pay does not extend that clock.
• Your layoff explanation should be two sentences: a factual cause, then a pivot to what you built and want next.
• Treat the search as a funnel. Aim for 10 to 15 targeted applications and 5 or more networking messages per week, and track conversion at each stage.
• Spend week one on admin and story, weeks two and three on pipeline and prep, and week four on interviews and offers.
• Budget energy like money. A sustainable 5 to 6 hour search day beats a 12-hour day that burns you out by week three.

The First 72 Hours Checklist

The first 72 hours are about preserving options, not applying to jobs. A rushed application with a stale resume wastes a good lead. A missed deadline on equity or health coverage can cost thousands of dollars.

Work through this list before you send a single application:

1. Do not sign anything yet. Ask HR for the full severance agreement, the deadline to sign, and any benefits summary in writing.
2. Save your records. Download pay stubs, your offer letter, equity grant documents, your last W-2, and performance reviews to personal storage, if your access still allows it. Do not take confidential company material.
3. Collect contacts. Get personal email addresses or LinkedIn connections for managers and teammates who can refer you or vouch for you.
4. List every deadline. Severance signing date, COBRA election window, option exercise deadline, FSA claim deadline, and any visa grace period.
5. File for unemployment. Rules differ by state and country, and some states treat severance differently, but filing early rarely hurts. Check your state's labor department site.
6. Calculate your runway. Savings plus severance plus expected unemployment, divided by monthly spending. This number sets how picky you can be.
7. Write your two-sentence story. You will use it in every conversation for the next month (templates below).
8. Tell close people first. Partner, family, or a friend. Isolation makes everything that follows harder.

These are typical windows, not legal advice. Your agreement and plan documents control, so read them line by line.

Severance, Benefits, and Visa Considerations

Severance is a negotiation, even when it looks like a form letter. Large layoffs usually apply a formula (for example, a set number of weeks plus extra weeks per year of service), and the formula itself rarely changes. The items around it are more flexible.

What you can usually ask for

• Pay or employment through a vesting date when you are a few weeks from an RSU vest or cliff.
• Longer COBRA subsidy if the company pays part of your premiums.
• Extended option exercise window for startup equity. Exercising within 90 days can cost far more than many engineers have in cash.
• Neutral reference and agreed-upon reason for leaving, written as "position eliminated."
• Outplacement services or a training stipend.

Ask once, in writing, with a reason. A short, polite email works better than a long argument. If the release waives significant claims or you suspect the selection was unfair, an hour with an employment lawyer is cheap insurance.

Notice pay and the WARN Act

Under the federal WARN Act, US employers with 100 or more employees generally must give 60 days' notice before a mass layoff or plant closing, or pay in lieu of notice. Many tech layoffs show up as "you are on paid non-working notice for 8 weeks." Some states have stricter versions. If your notice period is unpaid or missing, ask HR how it applies.

Health coverage, 401(k), and FSA

COBRA lets you keep your employer health plan, usually for up to 18 months, at full cost plus a small admin fee. You generally have 60 days to elect, and coverage is retroactive, so many people compare it against marketplace plans before deciding. Spend down any health FSA balance before your last day if you can, since unused funds usually do not carry over. Leave your 401(k) alone or roll it over; cashing out triggers taxes and, under age 59 and a half, usually a penalty.

Visa holders: act in week one

For H-1B workers, USCIS regulations provide a grace period of up to 60 consecutive days after employment ends, or until the I-94 expires if that is earlier. The clock starts on your last day of employment, not your last paycheck. Your realistic options are a new H-1B petition from another employer, a change of status (for example, to B-2 or a dependent visa), or departure. F-1 students on OPT face a separate unemployment-day limit. Book a consultation with an immigration attorney in the first week, and use our guide to H-1B sponsorship jobs to focus on employers that actively sponsor. Engineers open to relocating can also compare UK and Canada routes.

The 30-Day Plan, Day by Day

The 30-day plan front-loads admin and story, then shifts almost all your time to pipeline and interviews. It assumes you can search full time; halve the volume targets if you are caregiving or working on notice.

Days 4-7: build assets. Rewrite your resume around impact, with numbers where you have them, and make sure it parses cleanly with our ATS resume guide. Post on LinkedIn (template below). Build a target list split into three tiers: dream companies, solid fits, and fast-moving companies that can close in two to three weeks.

Days 8-14: fill the funnel. Referrals convert far better than cold applications, so spend at least half your outreach on people you know. Our guide on how to get a referral at a tech company has message templates for warm and cold contacts. Apply to roles within a few days of posting, when recruiter attention is highest.

Days 15-21: practice and screen. Schedule your weakest-company screens first so you warm up before the interviews you care about most.

Days 22-30: run loops in parallel. Try to cluster onsites so offers land close together. That timing gives you real choices instead of one exploding offer.

How to Explain a Layoff in Interviews

Explaining a layoff in an interview takes two sentences, said calmly and without apology. Hiring managers in 2026 have seen many rounds of tech layoffs and know they rarely reflect individual performance. What they listen for is whether you sound bitter, vague, or stuck.

Use a three-part structure: cause, contribution, direction.

Cause:        "My role was eliminated when [company] cut [X percent / the Y team] to [reason]."
Contribution: "Before that, I [one specific accomplishment with a result]."
Direction:    "Now I'm looking for [type of team / problem], which is why this role stood out."

Here is a filled-in example for a backend engineer:

"My team was cut when the company shut down its marketplace product
and reduced engineering by about 20 percent. Before that I owned the
payments reconciliation service and cut failed payouts significantly
by redesigning the retry logic. I'm looking for a backend role on a
product with real scale, and your payments infrastructure work is
exactly that."

A few rules make this land well:

• Lead with the business reason. "Restructuring," "product shutdown," or "cost reduction" are enough.
• Never criticize leadership. Even when it was handled badly, the interviewer imagines you describing them the same way.
• If you were the only one cut, say so honestly and focus on fit: "The company refocused on mobile and my role was web-only."
• Fold it into your intro. Your story should flow naturally from your tell me about yourself answer, not appear as a separate confession.

Expect follow-ups like "Why do you think you were selected?" Answer briefly ("It was by team, not individual performance; my whole org was eliminated") or, if you do not know, say that the criteria were not shared and move to what you did well. The behavioral interview guide covers how to build the story bank you will need for the rest of the loop.

Building a Job Pipeline Fast

A job pipeline is the set of opportunities you are moving through each stage at once: applied, screening, interviewing, and offer. The single biggest mistake after a layoff is serial searching, where you put everything into one company and restart from zero when it fails.

Track every opportunity in a simple sheet with these columns: company, role, source (referral, recruiter, cold), date applied, current stage, next action, and next action date. Review it every Monday.

Weekly targets for a full-time search:

If applications are not turning into screens after two weeks, the problem is usually your resume or targeting. If screens are not turning into onsites, the problem is interview performance. Fix the stage that is leaking. For a fuller system, read our software engineer job search strategy.

Skill Refresh and Interview Prep

Most engineers coming off a layoff have not interviewed in two to five years, and formats have shifted. Some companies now run AI-enabled coding rounds, more use practical debugging or code review exercises, and system design remains standard from mid-level up. Start by asking each recruiter what the loop looks like.

A realistic four-week prep split for a mid-level or senior engineer:

• Coding (about 50 percent): Relearn patterns rather than grinding random problems. Our coding interview patterns cheat sheet covers the core patterns behind most medium questions.
• System design (about 30 percent): Practice out loud with a timer, two or three classic prompts per week. See how to practice system design interviews.
• Behavioral (about 20 percent): Prepare six to eight stories covering conflict, failure, ownership, and impact, including your layoff story.

Do one timed problem every morning before any applications. It keeps the skill warm and gives you an early win each day, which matters more than it sounds during a search.

Mental Health and Pacing

A layoff is a loss, and treating it purely as a logistics problem usually backfires around week three. Rejections arrive faster than offers, and engineers who were strong performers often take them personally. Plan for that dip instead of being surprised by it.

Practical guardrails that help:

• Set office hours. Search from roughly 9 to 3, then stop. Evenings are for people and rest.
• Measure inputs, not outcomes. "I sent 12 applications and did 5 practice problems" is a good week, even with zero offers.
• Keep one non-job routine. Exercise, a weekly call with a friend, or a side project you actually enjoy.
• Debrief rejections in ten minutes. Write what went well, what to fix, and move on. Our guide on handling interview rejection has a simple template.
• Ask for help early. If anxiety affects your sleep or performance, see a professional. Many people also find that the technical interview anxiety guide helps with pre-interview nerves specifically.

Scripts and Templates

These templates are starting points. Swap in your details and cut anything that does not sound like you.

LinkedIn layoff post

I was one of the [N] people affected by [Company]'s layoff this week.

Over [X] years I [accomplishment 1 with a result] and [accomplishment 2].
I work mostly in [stack], and I'm strongest at [area].

I'm looking for [senior backend / frontend / platform] roles,
[remote or city], starting immediately.

If your team is hiring, or you can introduce me to someone who is,
I'd be grateful. Resume in the comments. Thank you to [team] for
[short genuine note].

Referral request to a former coworker

Hi [Name], as you may have seen, my role at [Company] was eliminated.
I noticed [their company] is hiring for [role link]. Given our work
together on [project], would you be comfortable referring me? I've
attached my resume and a two-line summary you can paste. No pressure
either way.

Recruiter screen answer: "Why are you looking?"

"My position was eliminated in a company-wide reduction in [month].
I'm using it as a chance to be deliberate about my next team, and
I'm specifically interested in [domain] work like yours."

Severance clarification email

Hi [HR contact], thank you for the information. Before signing, could
you confirm: (1) the final date for signing, (2) whether my [date] RSU
vest falls within my notice period, and (3) whether the option exercise
window can be extended beyond 90 days? Given that my next vest is
[N] weeks away, I'd also like to ask whether employment could continue
through that date. I appreciate your help.

When offers arrive, slow down for 24 hours. A layoff can push you to accept the first yes, but you still have room to negotiate. Use our guide to software engineer salary negotiation before you reply.