Laid Off in Tech? A 30-Day Action Plan for Senior Engineers

If you are a senior+ software engineer and you just got laid off, take a breath. The market is grinding hard on people at your level — the pool of senior IC roles is smaller than it was three years ago and competition is denser. That said, it is fully workable. The pattern that compresses a six-month search into six weeks is consistent, and most of it has nothing to do with sending more applications.

Days 1–3: Triage, do not job-hunt

1. Confirm your separation paperwork. Severance, COBRA timing, equity vesting cliff, and PTO payout. Get clear answers in writing before signing anything.
2. Pull your offer letter and any non-compete or non-solicit clauses. In the US, most non-competes are unenforceable now — but state law varies. Skim once, talk to a lawyer if it looks aggressive.
3. Set a financial runway number. How many months of essential expenses do you have? This number drives every later decision.
4. Pick a dedicated job-search workspace. Separate browser profile, dedicated email, dedicated phone if needed. Mixing personal and search work degrades both.

Days 4–10: Story before search

The single biggest mistake senior engineers make is updating the resume first. The story has to come before the resume. Spend three days writing — by hand — the answers to: what do you actually want next, what is the one technical thing you want to be known for in three years, and what are the three projects in your past that demonstrate you can do that thing?

Once that is on paper, the resume becomes a lossy compression of those answers. Until then, the resume is just a list of frameworks and dates that nobody reads.

Days 11–17: Network, then resume

Reach out to 25 specific people: ex-coworkers, ex-managers, people you respect from old teams, people you've met at conferences. Not 'looking for opportunities' DMs — specific notes that say what you are looking for next, why this transition makes sense, and asking for a 20-minute call.

Eight to twelve will reply, four to six will take the call, and one or two will introduce you to a hiring manager. That is your real funnel. Your resume can ship at the end of this week, not the start.

Days 18–24: Apply with surgical precision

• Pick five to eight target companies — not fifty. Companies where the engineering culture, problem domain, and stage actually fit you.
• For each one, identify two to three live roles. If none fit, write a cold outreach to the engineering manager you'd want to work for and pitch a conversation.
• Apply with a tailored cover letter and resume per role. Generic applications at senior+ get filtered immediately by both ATS and humans.

Days 25–30: Interview prep, contracts, decisions

By the end of week four, expect three to six active conversations. Use the time to drill system design and behavioral interviews — the technical bar at senior+ is always design and trade-off thinking, not algorithm puzzles. Have a salary band ready before any conversation goes deeper than first round.

If a contracting opportunity shows up early — paid trial, six-month engagement, advisory work — take it seriously. It de-risks your runway and many of those engagements convert to full-time. Just don't sign exclusivity clauses that block your full-time search.

Tools that compress the timeline

UpJobz was built for exactly this scenario. The resume scorer flags which listings in your saved set actually match your background, the cover-letter generator drafts tailored variants in under a minute, and the interview-prep tool runs domain-specific question drills before each round. Every minute it saves you is a minute you spend on networking, which is what actually moves the search.