Laid Off in 2026? Here’s What to Do Next.
An honest guide for software engineers navigating tech layoffs in2026 — from the first 48 hours to landing your next role.
Before we begin
If you’re reading this because you just got laid off — I’m sorry. It’s disorienting and it sucks, even when you know it wasn’t personal. Take a breath. You’re going to be okay. This guide will still be here tomorrow.
In 2026 alone, over 28,000 tech workers have already been laid off. In 2025, the number was nearly 250,000. You’re not alone, and a layoff is not a reflection of your ability as an engineer.
This guide is written specifically for software engineers who’ve been impacted by tech layoffs. It covers what to do in the first few days, how to organize your job search, how to prepare for interviews when you haven’t interviewed in years, and how to take care of yourself through the process.
Days 0–2
1. The First 48 Hours
The instinct after a layoff is to immediately start sending resumes. Resist it — at least for a day or two. You’ll make better decisions when you’re not in fight-or-flight mode.
Secure your finances
Understand your severance, COBRA options, and runway. If you have RSUs vesting soon, check if your termination date affects them. File for unemployment — it’s not a moral failing, it’s insurance you paid into.
Preserve your work artifacts
Before you lose access: save performance reviews, peer feedback, project documentation, and anything that demonstrates your impact. You’ll need these for your resume and interviews.
Connect with laid-off colleagues
Get contact info for coworkers who were also affected. They’ll be your support network, referral partners, and people who understand what you’re going through.
Let yourself feel it
A layoff is a loss. It’s okay to be angry, anxious, relieved, or all three at once. Don’t skip this step by immediately burying yourself in LeetCode. Process now so it doesn’t derail you later.
Days 3–7
2. Week 1: Get Organized
Once you’ve had a few days to decompress, it’s time to build your job search infrastructure. Treat this like a project — because it is one.
- Update your LinkedIn headline and turn on “Open to Work” (visible to recruiters only)
- Refresh your resume — focus on impact and metrics, not responsibilities
- Create a tracking spreadsheet: company, role, date applied, status, contacts
- Identify 10–15 target companies and research their interview processes
- Reach out to 5 former colleagues or managers for referrals
- Set a daily structure: applications in the morning, prep in the afternoon
Referrals matter more than ever
40% of referred candidates make it to the interview stage vs. ~2% of cold applicants. Your network is your strongest asset. Don’t be shy about reaching out — people want to help, especially fellow engineers who’ve been through layoffs themselves.
The Comeback
3. Interview Prep: The Part Most People Get Wrong
Here’s the uncomfortable truth: if you haven’t interviewed in 2+ years, you’re probably rusty. It doesn’t matter how senior you are. Interviewing is a skill that atrophies without practice.
The mistake most laid-off engineers make is spending all their time on LeetCode and none on the actual interview experience. You can solve problems in silence on your laptop, but freeze when someone’s watching and asking follow-up questions.
A realistic prep timeline
If you have 6–8 weeks before your target interview dates, here’s how to structure your time:
- Weeks 1–2: Fundamentals refresh. Review core data structures, algorithms, and patterns. Don’t grind new problems — reinforce what you know.
- Weeks 3–4: Targeted practice. Do company-tagged problems on LeetCode if you have premium. Start mock interviews (aim for 2–3 per week).
- Week 5: System design deep dive. Practice explaining designs out loud. Record yourself if you don’t have a mock partner.
- Week 6: Behavioral prep. Write out 8–10 STAR stories covering leadership, conflict, failure, and impact. Practice telling them until they’re natural.
- Weeks 7–8: Full simulation. Do complete mock loops. Light review only — don’t cram new material.
The system design trap
If you’re interviewing for senior roles (L5/E5+), system design is where you’ll pass or fail. Most candidates over-prepare on algorithms and under-prepare here. Knowing how consistent hashing works is different from explaining why you’d choose it while someone asks follow-up questions.
Reps Win
4. Mock Interviews: Why Volume Matters
Here’s data from interviewing.io: candidates who do 5+ mock interviews roughly double their pass rate in real interviews. The improvement comes from repetition — getting comfortable thinking out loud, managing time, and recovering when you get stuck.
The challenge is that quality mock interviews are expensive. Human coaching runs $150–$300+ per session. Most people can’t afford to do 15–20 sessions at that price.
Options to consider:
- Peer practice (free): Platforms like Pramp/Exponent match you with other candidates. Quality varies but it’s free and unlimited. Good for volume.
- AI mock interviews ($): Tools like Apex Interviewer let you run unlimited mock interviews for a flat fee. Useful for building reps without scheduling friction or per-session costs.
- Human coaching ($$): Services like interviewing.io pair you with FAANG engineers. Highest fidelity feedback but expensive. Best used for final polish after you’ve done volume elsewhere.
The optimal approach for most people: do 10–15 AI or peer mocks for volume, then 2–3 human sessions for calibration right before your target interviews.
Practice interviews without scheduling or per-session costs
Apex Interviewer runs AI mock interviews for coding, system design, and behavioral — tailored to specific companies like Meta, Google, and Amazon.
Start Practicing →Targeted Strategy
5. Company-Specific Prep
Not all interviews are the same. Amazon’s LP-focused behavioral rounds are completely different from Google’s Googleyness assessment or Meta’s “Move Fast” culture questions. Generic prep leaves points on the table.
Before each interview:
- Research the company’s interview process (Glassdoor, Blind, Levels.fyi)
- Understand their values/principles and prepare stories that map to them
- Look up common questions for your specific role and level
- If possible, talk to someone who’s interviewed there recently
For Amazon specifically: memorize the 16 Leadership Principles and have a STAR story ready for each. “Customer Obsession,” “Ownership,” and “Deliver Results” come up in nearly every loop.
Verified Interviews
Meta
Verified Interviews
Apple
Verified Interviews
Microsoft
Verified Interviews
Take Care of Yourself
6. Managing Your Mental Health
Job searching is emotionally brutal. Rejection is constant. Ghosting is endemic. The uncertainty grinds you down.
A few things that help:
- Maintain structure. Set work hours for your job search and protect your evenings/weekends. Burnout is real.
- Move your body. Exercise is the most effective intervention for anxiety. Even a daily walk helps.
- Connect with others. Join communities of people going through the same thing. Isolation makes everything worse.
- Celebrate small wins. Getting a recruiter call is a win. Making it to onsite is a win. Don’t discount progress.
- Consider therapy. If you have access through severance or COBRA, use it. A layoff is a legitimate reason to seek support.
What About AI Taking Our Jobs?
It’s impossible to write about tech layoffs in 2026 without addressing the elephant in the room. Yes, AI is changing the industry. Yes, some roles are being eliminated. No, software engineering is not dying.
The Bureau of Labor Statistics still projects ~15% growth in software jobs through 2034. What’s changing is the nature of the work — less boilerplate, more system design, architecture, and AI orchestration. Engineers who adapt will thrive. Engineers who refuse to learn new tools will struggle.
If you’re job searching now, lean into AI skills. Learn to prompt effectively. Understand how to evaluate and debug AI-generated code. Build projects that integrate LLMs. These skills are in demand and the supply of engineers who have them is still limited.
You’re Going to Be Okay
A layoff feels like an ending, but it’s often a beginning. Many engineers look back on getting laid off as the push they needed to find a better role, a better company, or a better path entirely.
The market is tough but it’s not impossible. Companies are still hiring. Your skills are still valuable. The discomfort you’re feeling right now is temporary.
Take it one day at a time. Build your system. Do the reps. Trust the process.
And when you land that next role — and you will — pay it forward. Help the next person who gets that unexpected Zoom invite.