The Proactive Layoff Prep Guide: What to Do 90 Days Before You Might Be Cut

Most engineers only start preparing after the layoff call ends. By then, three things are already working against you: your documentation is locked in company systems, your network has gone cold from months of silence, and your financial runway is shorter than you thought. The engineers who land on their feet fastest didn't get lucky — they'd done the work months earlier. That same preparation mindset starts with knowing exactly what happens after the call, including what companies are legally required to offer under the WARN Act and in your severance package — details most people learn too late to use.

Ambitology Cortex · Free Chrome extension

You're learning right now. Is anything keeping score?

Cortex turns what you read (articles like this one, docs, tutorials) into a living Skill Graph, then shows which roles your newest skills unlock.

How do you keep track of what you learn?

Preview my Skill Graph

Free · 30-second install · Works while you read

Professional reviewing a strategic plan at a desk with documents and a laptop

The engineers who land well after a layoff started preparing months before it happened.

Why 90 Days Is the Right Window

Ninety days sounds like a long lead time for something that might not happen. But the activities that protect you in a layoff all share one trait: they take time to build, and they're nearly worthless if you start them after the fact. Network warm-outreach takes weeks to generate real signal. Emergency funds take months to accumulate. Work documentation requires careful thought, not frantic exports from a locked laptop.

The other reason 90 days works is psychological. At three months out, you're not panicking — you're planning. That difference in state produces dramatically better decisions across all of these areas.

  1. 1
    Install Ambitology Cortex
  2. 2
    Read as usual
  3. 3
    Turn skills to jobs in realtime
CHROME EXTENSIONDownload Ambitology Cortex

Know Your Number Before You Need It

The first thing to get clear is your personal runway calculation: how many months can you survive if the paycheck stops tomorrow? Take your fixed monthly expenses — rent, insurance, debt minimums, subscriptions you won't cancel — and divide your liquid savings by that figure.

Most engineers are surprised by how short the answer is. A $200,000 household income often comes with $200,000 worth of commitments. The number that matters is liquid and accessible: not RSUs, not 401k you'd have to raid under penalty, not equity you can't touch until a liquidity event.

The goal: three to six months of full expenses in cash or near-cash equivalents. If you're not there, the next 90 days is the window to close the gap. Pause discretionary spending. Redirect the difference. Boring advice — until you need it.

“The best job search starts six months before you're in the market. The engineers who have options aren't the ones scrambling — they're the ones who stayed ready.”

Document Your Work Before the Door Closes

When a company lets you go, your access is often revoked within hours. Sometimes minutes. Any performance reviews, project documentation, or positive feedback you'd want to reference — even just for your own memory — needs to exist somewhere outside company systems now.

Here's what to preserve while you still can:

  • Performance reviews and written praise — Save locally, not in company Google Drive or Confluence. Specific excerpts that speak to your impact are worth keeping.
  • Contact information for key colleagues — Not just LinkedIn connections. Personal email addresses for managers and collaborators you'd genuinely want to stay in touch with. These relationships are harder to maintain once you no longer share a Slack.
  • Project summaries with metrics — What you built, what you owned, what it achieved in concrete terms. “Reduced API latency by 40%” is vastly more useful on a resume than “worked on backend performance.”
  • Technical artifacts you're permitted to reference — Check your IP agreement, but architecture diagrams, design documents, and system descriptions you authored often have personal-reference carve-outs.

None of this is improper. It's about not watching years of career evidence disappear behind an access control screen on a Tuesday afternoon.

Keep Your Network Warm When You Don't Need It

The engineers who get the best opportunities after a layoff almost never find them through job boards. They find them through someone they already knew — a former manager who moved to a new company, a colleague who now works somewhere with an opening, a conference acquaintance who happens to know the right person.

The problem is most people only reach out when they need something. By that point, the relationship is cold, the ask feels transactional, and the person on the other end half-knows they're being activated. It still works, but far less well than it should.

The fix requires almost no time: two or three genuine outreaches per month to people in your field. A relevant article they'd care about. A job lead for someone they might know. A brief note about a talk or post you found useful. You're not building urgency — you're maintaining contact. When you eventually do need help, you're not a stranger with a request; you're someone they've heard from recently.

Build Your Job Search Infrastructure Now

Most people skip this because it feels premature. It's not. A modern job search has real setup cost, and doing it under financial pressure and a ticking clock is worse in every dimension.

Build this now, while you have time:

  • Updated resume — Reflects your current scope and accomplishments. Keep a running notes doc with achievements and metrics as they happen; retrofitting them from memory months later loses half the detail.
  • LinkedIn profile — Updated title, summary, and recent experience. The recruiter finding you is not planning to give you a heads-up first.
  • GitHub or portfolio — Repos you'd want a hiring manager to review should be clean, documented, and representative of your current level.
  • Target company list — Ten to fifteen companies you'd genuinely consider. Identify connections there. This takes real thought when you're calm; it's hard to do well under time pressure.
  • Consulting or freelance bridge plan — Even a rough one. Knowing you have an income option that isn't “take whatever offer comes first” dramatically improves your negotiating position.

The full financial math of a freelance or consulting bridge after a layoff is worth running through now, while the pressure is off. Many engineers with 90 days of preparation have used a consulting period to stay financially stable while waiting for the right full-time role, rather than rushing into one they'd leave within a year.

As you work through layoff prep — reading employment law, running financial calculations, researching compensation structures — you're building real skills that rarely show up on a resume: negotiation strategy, financial planning, employment law fundamentals. The Ambitology Cortex Chrome extension works quietly in the background while you read and learn anywhere on the web, capturing the skills you're actually picking up and feeding them into your Skill Graph. That means when you re-enter the market, Ambitology can surface and match the opportunities that genuinely fit the capabilities you've been building — not just the title on your last badge.

Ambitology Cortex · Free Chrome extension

Finished reading? Keep what you learned.

With Cortex, the next article you read lands on your Skill Graph automatically, matched to the roles it moves you toward.

Preview my Skill Graph

FAQ

What should I do first if I think a layoff is coming?

Start with your financial runway. Calculate how many months of full expenses you can cover from liquid savings today. That number tells you how much time pressure you'll actually be under — and determines how aggressively you need to move on the other steps. If the runway is under two months, that's the most urgent thing to address.

How much financial runway should I have before a layoff?

Three to six months of full monthly expenses in liquid, accessible accounts is the standard target. The right number depends on your market. Engineers in niche specializations or smaller cities with fewer employers should target the higher end. Mid-to-senior engineers in well-staffed markets (Bay Area, NYC, Seattle) can often move in under 90 days with the right prep, but six months gives you room to be selective.

What documentation should I save before a potential layoff?

Performance reviews, written praise from managers and collaborators, project summaries with concrete metrics, and personal contact information for colleagues you'd want to stay in touch with. Save these outside company systems — locally or in a personal cloud account. Also review your offer letter and equity grant documents; know your vesting cliff dates and any change-of-control provisions before you're in a time-pressured negotiation.

Should I start applying for jobs before a layoff happens?

Most engineers shouldn't apply proactively — but you should absolutely run a few exploratory conversations to calibrate your market. A casual chat with a former colleague now at a company you're interested in costs nothing, gives you live data on the hiring environment, and primes that relationship before you need it. Actual applications generate timelines you'll feel pressured to match; exploratory conversations don't.