What to Do After a Layoff: First Week, Month & Quarter Plan
A no-fluff action plan for the first 90 days after a layoff — from emergency triage to landing your next role.
Getting laid off is a gut punch — even when you saw it coming, even when it wasn't your fault, even when half your team went with you. The emotional weight is real, and anyone who skips past it to "here's how to update your LinkedIn" is selling you false comfort. But after you've given yourself a moment to process, the single best thing you can do is move with intention. Panic-applying to 200 jobs in week one is not a plan. Neither is taking three months to "decompress" while your runway shrinks. What works is a staged, deliberate approach: triage in the first week, foundation-building in the first month, and full execution in the first quarter. This guide gives you exactly that.
Week One Is About Triage, Not Job Applications
Resist every instinct to immediately blast your resume across every job board. Week one has one job: stabilize. That means four things.
First, handle the administrative reality. Before you close your laptop on severance day, get clarity on:
- Exactly how many weeks of severance you're receiving and when payments stop
- Whether your health benefits continue through severance or end immediately
- How long you have to exercise any vested stock options (this window can be shockingly short — sometimes 90 days)
- The terms of any non-compete or non-solicitation clauses in your severance agreement
If the severance package looks even slightly unusual, spend $300–500 on a one-hour consult with an employment lawyer. That's almost always money well spent. Many people sign away meaningful rights because they're in shock and just want it to be over.
Second, file for unemployment benefits immediately. In most Canadian provinces and U.S. states there's a mandatory waiting period before benefits kick in. Every day you delay filing is a day of benefits you may not recover. In Canada, file your EI claim with Service Canada within 4 weeks of your last day. In the U.S., file with your state's unemployment office the week your layoff takes effect.
Third, build a cash flow model. Open a spreadsheet and calculate your real runway: cash on hand plus incoming severance minus fixed monthly expenses. Be brutally honest. This number tells you whether you have 3 months or 9 months to find your next role — and that changes how aggressive your search needs to be.
Fourth, take two to three days to actually process what happened. Tell the people close to you. Go for long walks. Don't perform optimism you don't feel. Job searching while emotionally dysregulated produces bad decisions — lowball offers accepted out of fear, roles taken that are wrong fits, interview performances that don't reflect your actual capability.
"The candidates who land the best roles after a layoff aren't the ones who started applying fastest. They're the ones who started applying with the most clarity."
Month One Is About Building the Infrastructure of Your Search
By the time you've survived week one, you should be emotionally stable enough to build the machine that's going to get you hired. Don't skip this phase in the rush to "just start applying." A poorly prepared candidate with a weak resume and no clear positioning will get fewer callbacks than a well-prepared candidate who starts two weeks later.
Nail your positioning first. Decide — specifically — what you're targeting. Not "software engineering roles" but "Principal or Staff Software Engineer roles at Series B–D fintechs or mid-size tech companies in the $180K–$230K USD range, remote." The more specific your target, the more coherent everything downstream becomes: your resume, your outreach, your interview narrative.
Rebuild your resume for 2026 realities. A few things that actually matter this year:
- ATS systems are sophisticated but still keyword-sensitive. Mirror the exact language in job descriptions — if they say "distributed systems," don't just say "microservices architecture."
- Quantify everything you can. "Improved latency by 35%" beats "improved system performance" every single time.
- Keep it to two pages maximum. Recruiters at high-volume companies spend under 30 seconds on an initial pass.
- Remove the objective statement. Nobody needs to read "I am a results-driven engineer seeking opportunities to leverage my skills."
Rebuild your LinkedIn profile with the same seriousness. In 2026, LinkedIn recruiter search is still the dominant inbound channel for senior tech roles. Turn on "Open to Work" for recruiters only (not publicly, to avoid signaling desperation). Write a headline that includes your target role title and a key differentiator — not just your last job title.
Activate your network before you need anything specific. Reach out to former colleagues, managers, and professional contacts — not to ask for jobs, but to reconnect. A simple message: "Hey, I was recently laid off from [Company] — I'm starting to explore what's next. Would love to grab a coffee call and catch up." Most people are genuinely willing to help. Most laid-off candidates never ask.
The Hidden Job Market Is Real and You Need to Work It
About 70–80% of senior roles — Principal Engineer, Engineering Manager, Tech Lead — are filled through referrals or direct network connections before they ever hit a public job board. This is especially true at companies that treat recruiting as a competitive advantage. If you're only applying through LinkedIn Easy Apply and company career pages, you're fishing in the pond where everyone else is fishing.
Here's how to work the hidden market effectively:
- Identify 20–30 target companies — not 200, not 5. Research them, understand their tech stack, know their engineering blog, follow their key engineers on LinkedIn.
- For each company, find 2–3 people in your extended network who currently work there or recently left. Use LinkedIn's second-degree connections.
- Ask for 20-minute informational calls. Prepare genuine questions about the engineering culture, the team structure, the problems they're solving. Don't ask for a job. Build a real conversation.
- Follow up. Send the articles you mentioned. Connect them with someone relevant to something they said. Be the person who gives value, not just extracts it.
- When a role opens at that company — and you'll often hear about it before it's posted — you'll have a warm introduction path rather than being application number 847.
This process takes longer to start producing results, which is exactly why you should start it in month one, not month three.
Your Interview Prep Needs to Be More Systematic Than You Think
Most people treat interview prep as something you do the night before a call. That's not preparation — that's hoping. Senior-level technical interviews in 2026 are rigorous: system design rounds, behavioral depth interviews using structured frameworks, sometimes take-home architecture exercises. You need reps, not cramming.
For technical roles (Principal / Staff Engineer, Architect):
- Do one system design problem every two to three days. Use resources like "Designing Data-Intensive Applications" and system design interview guides as starting points, but practice out loud — ideally with a peer.
- Review the fundamentals you might have gotten rusty on: CAP theorem, consensus protocols, database indexing strategies, caching layers. These come up at FAANG-adjacent companies.
- If coding rounds are part of your target companies' process, do LeetCode medium problems daily — not to ace LeetCode specifically, but to stay sharp on algorithmic thinking.
For behavioral interviews:
Use the STAR format (Situation, Task, Action, Result) for every answer, but go deeper on the Result. Interviewers at senior levels want to hear about second-order impact, not just the feature you shipped. "We launched the feature" is table stakes. "We launched it, it drove a 15% increase in user engagement, and it informed how we restructured the entire search team's roadmap" is a senior-level answer.
Prepare 8–10 strong stories from your career that can flex to answer different questions. You don't need 40 different stories — you need 10 great ones.
Salary Negotiation: Know Your Number and Don't Blink
A layoff has a way of making people feel grateful to receive any offer, which is exactly when candidates leave the most money on the table. Don't negotiate from fear. Negotiate from data.
For senior tech roles in 2026, approximate market ranges (USD, remote-eligible):
- Senior Software Engineer (L5 equivalent): $180,000–$240,000 total compensation
- Staff / Principal Engineer (L6 equivalent): $240,000–$350,000+ total compensation
- Engineering Manager (first-level): $200,000–$280,000 total compensation
- Tech Lead / Lead Engineer: $200,000–$270,000 total compensation
For Canadian-based candidates at Canadian companies, discount these by approximately 25–35% due to CAD/USD differential and market dynamics, though U.S.-headquartered remote roles often pay closer to U.S. bands.
Never give a number first if you can avoid it. When asked for salary expectations, respond: "I'm flexible depending on the full compensation picture, but I'm targeting market rate for this level — can you share the band you've budgeted for this role?" Once you have their number, you know whether to counter or walk.
Always negotiate. Even a simple "I'm very excited about this role. Is there any flexibility on the base or equity component?" results in a higher offer more often than not. The worst they can say is no.
Quarter One Ends When You Have Leverage, Not When You Have an Offer
By the end of month three, your goal is not to accept the first offer that comes in — it's to have multiple conversations at the offer or late-stage stage simultaneously. Leverage is created by optionality. One offer means you take it or walk away with nothing. Two or three competing offers means you can negotiate meaningfully and choose the role that's actually right.
This is why the timeline matters. If you start building your pipeline — resume, network outreach, target company list, interview prep — in month one, by month three you'll have conversations maturing across several companies at the same time. If you panic-applied in week one and then burned out, you'll have a scattered, uncoordinated set of processes at different stages with no leverage.
If you reach the end of month three without an offer, it's diagnostic data, not a catastrophe. Run a structured retrospective:
- Are you getting recruiter screens but not advancing? Your resume is working but your phone screen needs work.
- Are you getting final rounds but not closing? Your system design or behavioral depth needs work, or your salary expectations are misaligned.
- Are you not getting callbacks at all? Your resume, positioning, or target company list needs a serious rethink.
Treat your job search like a product with a feedback loop. Adjust based on where you're dropping out of the funnel.
Next Steps
If you were laid off recently — or are reading this because you think a layoff might be coming — here are five things to do this week:
- Model your runway today. Open a spreadsheet. Add up your cash, severance, and expected unemployment benefits. Subtract your monthly fixed expenses. You need to know this number.
- File for unemployment benefits if you haven't. Do it today, not tomorrow. The waiting period clock starts when you file.
- Write your positioning statement. In one paragraph, define the specific role, level, company type, and compensation range you're targeting. Vague searches produce vague results.
- Contact five people from your network this week. Former colleagues, managers, or professional contacts. Don't ask for anything. Just reconnect. Tell them you're exploring what's next.
- Do one system design or behavioral interview practice session. Out loud, not in your head. Record yourself if you have to. You will be surprised by the gaps.
The job market in 2026 is competitive but not impossible. Senior engineers with real production experience and strong communication skills are still highly sought after. The candidates who land well after a layoff aren't luckier than the ones who don't — they're more deliberate.
Related guides
- How to Ask for a Promotion: The 90-Day Plan That Works — Stop hoping your manager notices. Here's the 90-day promotion plan that builds the case, earns the yes, and protects you if they say no.
- Dual-state tax for remote work in 2026 — when you owe two states and how to plan — Remote tech workers can trigger tax obligations in more than one state. This guide explains residency, nonresident wages, convenience rules, withholding, credits, and the planning steps to take before a remote move.
- PIP Survival Guide in 2026 — Surviving a Performance Improvement Plan When It Is Salvageable — A PIP is either a rescue plan or an exit track, and the first week is about telling the difference. This playbook shows how to clarify expectations, document progress, manage HR, and protect your downside.
- Post-Layoff Job Search Window Strategy — The First 30 Days That Determine Outcomes — The first month after a layoff should not be a blur of panic applications. This guide gives a practical 30-day job-search strategy for stabilizing, positioning, activating your network, and building interview momentum.
- Return-to-Office Mandates in 2026 — Your Options, Your Leverage, and Your Exit Plan — Return-to-office mandates in 2026 are often about control, real estate, management preference, or attrition as much as collaboration. This guide explains how to assess your leverage, negotiate exceptions, protect your role, and build an exit plan if the mandate breaks your life.
