# A software engineer layoff needs a 30-day system

> A software engineer layoff plan for severance, health insurance, references, unemployment, and a measurable job search starting on day three.

A layoff creates two separate jobs. The first is preserving money, insurance, legal rights, and professional evidence before deadlines close. The second is finding work. Mixing them together produces a month of anxious motion and very little progress.

Treat the first 30 days as an operating period with dates, decisions, and a visible search pipeline. You do not need to feel optimistic before you begin. You need a system that still works on the mornings when rejection lands badly.

This article assumes a US employment context because severance, unemployment insurance, COBRA, and WARN are US concepts. State law, your employment agreement, your benefit plans, and your immigration status can change the answer. Use the process below to find the questions that need a benefits administrator, accountant, or employment lawyer, rather than treating a general article as personal legal advice.

## The first 48 hours are for preserving options

Your first task is to collect facts while company contacts and systems are still reachable. Do not negotiate from memory, and do not let embarrassment stop you from asking basic administrative questions. HR handles departures every week. You may handle one or two in a career. Written records correct that imbalance.

Save the separation agreement, benefits summaries, equity documents, recent pay statements, performance reviews, promotion letters, and any written praise that you are allowed to retain. Also save the names and personal contact details of colleagues who may act as references. Use a personal device and account. Do not take source code, customer data, internal road maps, private chat archives, or anything else you would have refused to send outside the company while employed. Losing access does not turn company property into a portfolio.

Write down the termination date, last day of active work, last day of health coverage, deadline to sign the release, expected final paycheck date, severance payment dates, equity exercise deadline, and the contact for each benefit. These dates often differ. A calendar entry called "insurance" is useless; an entry called "Marketplace enrollment deadline, verify against coverage-loss date" can prevent an expensive gap.

Ask who will answer payroll and benefit questions after your company account closes. Send important questions by email and keep the replies. If a manager tells you verbally that a bonus, commission, or equity exception will be honored, ask for that term in the agreement. Good intentions disappear during reorganizations because the person who made the promise may leave next.

Change the email address and phone number on personal accounts that used your work identity, including professional networks, developer communities, conference accounts, password managers, and any personal cloud service. Rotate passwords that you reused, even though you should not have reused them. Do not delete or alter anything on the employer's systems. The clean exit matters when a reference check arrives six months later.

## Severance buys a release, so price the whole exchange

A severance agreement is a contract, not a thank-you note. The company usually offers pay or benefits beyond what it already owes in exchange for a release of claims and other promises. Read it as a transaction. Separate earned compensation from new consideration before deciding whether the offer is fair.

Create four columns on paper: already owed, offered in exchange, rights restricted, and unresolved. Earned salary belongs in the first column. Accrued vacation may belong there depending on state law and company policy. Severance pay, employer-paid insurance, or accelerated vesting may sit in the second. The third includes the release, confidentiality language, cooperation duties, non-solicitation terms, and any limits on what you may say. Put unclear bonus treatment, expense reimbursement, equipment return, and equity dates in the fourth.

Federal law generally does not require severance pay. An employment contract, company plan, collective agreement, or state law may create an obligation, so "there is no federal requirement" does not settle your case. The US Department of Labor says the federal WARN Act can require 60 calendar days of advance notice for certain plant closings and mass layoffs by covered employers. WARN has coverage thresholds and exceptions, and some states have broader mini-WARN laws. A large layoff without notice is a reason to check, not proof that your employer violated the law.

People often negotiate only the number of salary weeks. That is too narrow. Ask about the payment schedule, treatment of bonus or commission, the stated termination reason, health premium support, equity exercise time, vesting, company equipment, reference wording, and whether the company will remove restrictions it does not need. A lump sum and salary continuation can affect taxes, cash flow, and unemployment benefits differently under state rules. Get the payment mechanics in writing before comparing two offers.

If you are 40 or older and the agreement asks you to waive claims under the Age Discrimination in Employment Act, the EEOC explains that federal rules generally require at least 21 days to consider an individual offer and seven days to revoke after signing. A group termination program generally uses a 45-day consideration period and requires more disclosure. Those protections do not mean every clause is valid or that every worker has the same deadline. They mean a same-day signature demand deserves scrutiny.

Pay for an employment lawyer when the agreement contains a broad noncompete, disputed commissions, meaningful equity, possible discrimination or retaliation, a WARN issue, immigration consequences, or enough money that one clause could change the outcome. A short review can also produce a focused negotiation letter. Do not threaten litigation as a bargaining pose. State the term, explain the concrete problem, and propose exact replacement language or compensation.

## Health insurance is a comparison with hard dates

Compare COBRA, an Affordable Care Act Marketplace plan, and a spouse or partner's employer plan before choosing. The familiar plan is not automatically the least expensive option, and the lowest monthly premium is not automatically the least expensive year. Network access, prescriptions, deductible progress, expected care, and the end date of any employer subsidy can outweigh the headline premium.

The Department of Labor says a person generally has 60 days to elect COBRA, measured from the later of the loss of coverage or the election notice. COBRA can continue the same group coverage and is often retroactive to the date prior coverage ended once elected and paid under the plan's rules. That feature can matter when you are between jobs and uncertain whether you will need care. It does not make COBRA free. You may pay the full premium plus an administrative amount. Read the election notice for payment dates and plan-specific terms.

HealthCare.gov says losing job coverage creates a Special Enrollment Period, generally with 60 days after the loss of coverage to enroll in Marketplace coverage. Marketplace coverage can start on the first day of the month after job coverage ends, and the application determines whether household income qualifies for premium tax credits or programs such as Medicaid. Estimate full-year household income carefully and update it when the estimate changes. Severance and a new job can alter the subsidy calculation.

A spouse's or partner's employer plan may have a shorter special enrollment window. HealthCare.gov notes that job plans must provide at least 30 days in relevant special enrollment situations, but the plan administrator should give you the actual deadline and required proof. Do not wait for a COBRA packet before asking.

Compare each option using the same expected period. Add premiums, remaining deductible, likely copays or coinsurance, prescription costs, and the cost of losing access to current clinicians. If you have ongoing treatment, call the insurer and provider to verify network status. A directory entry is evidence to investigate, not a guarantee that a particular clinician and location will bill in network.

Check the final date to spend health care FSA funds and the rules for submitting claims. An HSA belongs to you, but payroll contributions and employer contributions stop with employment. If your coverage ends mid-month, confirm whether the plan, HSA eligibility, and any COBRA election affect how much you may contribute for the year. This is a good question for the plan administrator or a tax professional because the answer depends on dates and coverage type.

## File unemployment before the paperwork feels complete

Apply for unemployment insurance as soon as possible after becoming unemployed. The US Department of Labor gives that instruction directly and notes that each state runs its own program. Eligibility, weekly amounts, waiting periods, severance treatment, work-search rules, and certification procedures vary. Your former employer does not make the final eligibility decision.

File in the state where you performed the work unless the relevant agencies direct you elsewhere. Remote engineers often assume the employer's headquarters controls, while workers who moved or worked in several states may have a choice or an interstate claim. Ask the state agency instead of guessing. A claim filed in the wrong place costs time, and backdating may be limited.

Use exact dates and preserve the confirmation number, submitted answers, separation notice, pay statements, and severance agreement. Report severance, vacation payout, contract work, and other earnings as the form requests. If the agency asks why employment ended, "lack of work" or "position eliminated" is materially different from resigning, but copy the facts rather than choosing the phrase that sounds most favorable.

Certify on the required schedule even while an issue is pending, and keep a search log that meets the state's rules. If the claim is denied, read the determination and appeal deadline immediately. Many applicants lose on procedure because they set the letter aside while trying to reach someone by phone. A phone call rarely extends a written appeal deadline.

## References need evidence and an explicit agreement

Ask for references while your work is fresh, but ask for a specific kind of help. "Can I use you as a reference?" often produces a polite yes and a vague call later. Tell the person the roles you will target and the two or three projects they directly observed. Ask whether they are comfortable speaking about those examples.

Your best reference may be a product manager, staff engineer, customer-facing peer, or former manager who left earlier. Titles matter less than firsthand knowledge. Build a small reference set that covers different claims: technical judgment, delivery under constraints, collaboration during disagreement, and ownership after release. Four people with distinct evidence beat twelve names who can only confirm that you were pleasant.

Confirm the company's official reference policy. Some employers provide only dates and title through a verification service, while individual colleagues may still give personal professional references. Never ask someone to evade policy. Instead, learn which channel verifies employment and which person can discuss the work they personally saw.

Send each reference a compact packet when an employer reaches the final stage: the job description, your current resume, the name of the hiring manager if known, and a reminder of relevant work. Do not script praise. Correct dates, project context, and your exact contribution prevent an honest reference from underselling you by accident. Tell the reference when the call may arrive and thank them after it happens.

If the separation involved conflict, ask the company to confirm neutral wording in the agreement. A negotiated sentence such as "position eliminated in a reduction in force" may remove ambiguity if it is true. Do not request a false title or invented performance story. Background discrepancies create a larger problem than a candid layoff explanation.

## The search starts on day three

Start market contact on day three even if the resume is imperfect. The first two days protect administrative options. After that, isolation becomes expensive because job descriptions, recruiter responses, and conversations provide information that private polishing cannot. You can revise the resume while the search runs.

Do not begin with one hundred applications. Begin with a role thesis: the problems you solve, the environment where you solve them, the level you can prove, and the constraints you will accept. "Senior backend engineer" is a label. "I stabilize high-volume API systems, reduce operational load, and can lead a small team through a risky migration" gives a hiring manager something to test. Keep the thesis honest enough to defend with work examples.

Create two resume variants only when the evidence supports two real markets, such as senior individual contributor and engineering manager. Ten lightly different resumes create version errors and make results impossible to compare. The opening summary, selected achievements, and project order may change. Employers, dates, titles, and facts do not.

Contact former colleagues before strangers. A useful message contains context, direction, and a modest request: "My role was eliminated this week. I am targeting staff backend roles where reliability and platform migration matter. You saw the payments cutover I led. If a team comes to mind, I would appreciate an introduction; if not, I would still value 15 minutes on what you are seeing." That message gives the recipient a memory and a decision.

Turn the role thesis into an evidence map before a recruiter asks for it. For each claim in the thesis, name one project, the constraint you faced, the decision you personally made, and the observable result. If "reduced operational load" means you changed alerts and ownership but cannot support a percentage, say exactly that. A defensible description is stronger than a borrowed metric that collapses under one follow-up question.

Set practical filters early: acceptable titles, location, office expectations, compensation range, work authorization needs, company stages, and technologies you refuse to spend all day maintaining. These are decision rules, not a wish list. Mark which filters are fixed and which may change when the runway reaches a preset date. This prevents a difficult morning from turning one rejection into a random search across every engineering job on the internet.

Update your public profile so its title and recent work agree with the resume, but do not rewrite it as a billboard for desperation. Recruiters need to understand your level and specialty in seconds. They do not need a long post about resilience. If you announce the layoff, give contacts the role direction, location constraints, and a concrete way to help. The useful part of a public post is the routing information, not the performance of vulnerability.

Applications still matter. Referrals cannot cover the whole market, and many companies require every candidate to enter the applicant system. Use referrals to improve context, not to bypass process. Apply when you meet the central requirements and can explain the gaps. Waiting to match every bullet rewards job descriptions that were written without tradeoffs.

## A visible pipeline beats a heroic application count

Track opportunities as a pipeline because application totals hide where the search fails. A person with 80 applications and no recruiter screens has a positioning or targeting problem. A person with 12 screens and no technical interviews has a different problem. Treating both as "apply more" wastes another week.

A spreadsheet is enough. Use one row per role and keep the stage names stable. This header can be pasted into a CSV file or spreadsheet:

```
company,role,source,date_added,next_action,next_action_date,stage,last_contact,contact_name,comp_range,location,notes
```

Use a short stage set: prospect, contact sent, applied, recruiter screen, hiring manager, technical, final, offer, closed. "Waiting" is not a stage because it hides who owes the next action. Put that information in `next_action`, such as "Follow up with recruiter" or "Prepare database tradeoff example," and give every active row a date. Close duplicate, withdrawn, rejected, and stale roles instead of leaving them to inflate the pipeline.

Review conversion once a week. Count qualified applications, replies to direct contacts, recruiter screens, hiring manager interviews, technical rounds, final rounds, and offers. Do not publish these numbers as performance theater. Use them to locate the first weak transition. Fewer than ten data points at a transition usually tells you very little, so combine the numbers with what recruiters and interviewers actually said.

If qualified applications rarely become screens, narrow the role thesis, compare your resume language with the job's actual responsibilities, and check whether location or compensation filters remove you. If screens do not become hiring manager calls, record the questions that caused hesitation. Your level, compensation, work authorization, remote expectations, or layoff explanation may be unclear. If technical rounds fail, stop adding applications for two days and rehearse the exact weak skill under realistic time limits.

Separate activity metrics from outcome metrics. Messages sent and applications submitted are under your control. Interviews and offers are not. Commit to a sustainable activity floor, then diagnose outcomes weekly. A daily offer target turns ordinary hiring latency into personal failure and encourages desperate applications that damage signal quality.

## The 30-day cadence protects both speed and judgment

Use a calendar that makes room for administration, search work, practice, and recovery. Eight unfocused hours on job boards is not a serious search plan. It is an anxiety loop with a browser history. A smaller block with a defined output is easier to repeat and easier to improve.

Use this cadence as a starting point, then adapt it to deadlines and family needs:

1. **Days 0 to 2:** Preserve documents, list every deadline, file unemployment, compare immediate insurance options, and send reference requests. Do not make a large financial or career decision while you still lack the separation facts.
2. **Days 3 to 7:** Write the role thesis, produce the primary resume, create the pipeline, contact close colleagues, and submit the first small batch of qualified applications. Book medical appointments only after confirming coverage dates.
3. **Days 8 to 14:** Run recruiter calls, test the layoff explanation, practice the interview format that your target roles use, and review the first conversion data. Follow up on missing payroll, benefit, or equity answers in writing.
4. **Days 15 to 21:** Expand outreach one ring beyond close contacts, correct the first weak pipeline transition, and decide whether a second resume variant has enough evidence to justify it. Review cash runway using actual severance and benefit costs.
5. **Days 22 to 30:** Concentrate on channels that produced serious conversations, close stale roles, ask for useful interview feedback, and decide whether to widen title, company stage, location, or compensation. Change one major variable at a time so you can see what worked.

Put search blocks on weekdays and set a stop time. Use one block for outbound work and one for preparation or interviews. Administrative calls get their own window so a 40-minute insurance hold does not consume the day. Exercise, caregiving, and sleep belong on the calendar because impaired judgment shows up in negotiation and technical interviews long before you admit you are exhausted.

Cash runway should influence the search without controlling every decision. Build a conservative monthly view using cash on hand, after-tax severance timing, unemployment estimates, insurance premiums, debt minimums, and essential spending. Do not count unvested equity, an unsigned offer, or a tax refund you have not verified. Set dates for widening the search before fear chooses for you, such as expanding company size after week four or considering contract work after week six.

## Your layoff explanation should be short and verifiable

A clean explanation states what happened, what you owned, and what you want next. It does not prosecute the former employer or pretend the event was a personal triumph. Most experienced hiring managers have seen strong engineers lose roles in budget cuts, acquisitions, and strategy changes. They listen for judgment and consistency.

Use two or three sentences: "My position was eliminated in a product group reduction. I owned the service migration and on-call improvements for the billing platform, and I left after completing the handoff. I am now looking for a staff role where reliability and platform change are central." Adjust every factual claim to your situation. If performance played a part, do not use reduction language that a reference will contradict. State the fit problem briefly, describe what you changed, and move to relevant evidence.

Prepare five work stories with artifacts you can discuss without exposing confidential material. Cover a difficult technical decision, an incident, a disagreement, a project that missed, and a result you can quantify honestly. Reconstruct the context, alternatives, your action, and what changed. If you cannot share an internal chart or code sample, describe the measurement method and decision. Confidentiality is a constraint on evidence, not permission to become vague.

Do not build a portfolio project by reflex. For a frontend specialist, designer-developer, or early-career engineer, a focused public artifact may answer a real evidence gap. For a staff infrastructure engineer, three weeks spent making a generic task app can distract from architecture practice, written case studies, and conversations with people who can assess senior work. Build only when you can name the hiring objection the artifact will resolve.

## Day 30 is a diagnosis, not a verdict

At day 30, judge the system by evidence: deadlines met, runway known, references ready, qualified opportunities created, and weak transitions identified. Hiring cycles often extend beyond a month, especially for senior roles. The absence of an offer by an arbitrary date does not prove the search has failed. An empty pipeline or repeated failure at the same stage does require a change.

Review the roles that created energy as well as the ones that advanced. A layoff can push an engineer toward the first familiar title even when the work has changed. You may discover that you want a smaller company, a management return, contract work, or a founder path. Test that choice through conversations and actual opportunities before rewriting your identity around it. If the founder route becomes serious, oleg.is offers founder and startup advisory on a month-to-month basis, but the first decision remains whether you want to build a company rather than merely escape a job search.

Keep the administrative file after you sign an offer. COBRA bills, unemployment certifications, expense reimbursements, equity notices, and tax forms can arrive later. Then keep the pipeline too. The contacts, work stories, and market notes are career infrastructure. Waiting for the next reorganization to rebuild them is an avoidable mistake.