# What to do after a tech layoff starts with buying time

> What to do after a tech layoff: protect your cash, explain the exit, activate your network, rebuild interview speed and judge offers without panic.

A layoff turns one problem into several at once. Income stops on a date you did not choose, your professional story suddenly needs an explanation, and a search process you have not practiced in years becomes your new job. The right response is to buy time first, then use that time with a weekly operating rhythm.

Do not begin by sending the same resume to fifty openings. That feels productive because it produces confirmation emails. It also burns good opportunities before your narrative, evidence, and interview reflexes are ready. Spend the first week protecting your options, the next two rebuilding signal and speed, and the following weeks running a measured search.

## The first 24 hours protect options, not pride

Your first day is for collecting facts and preserving access to records you are entitled to keep. Emotion can wait for a trusted person; deadlines and missing paperwork will not. Read the separation agreement, benefits notice, equity documents, and final pay statement before you sign or discard anything.

Write down the exact dates for final salary, severance installments, health coverage, equity exercise windows, bonus eligibility, and return of equipment. Save personal copies of your offer letter, performance reviews, promotion letters, compensation history, and any work samples the company has explicitly allowed you to retain. Never copy source code, customer data, internal plans, private messages, or confidential designs. A portfolio problem is cheaper than an problem with intellectual property.

Ask HR focused questions in writing. Which benefits end on the termination date and which continue through the month? Does severance depend on signing a release? When will unused leave be paid, if local rules or company policy require it? Who can confirm employment, and what information will that person provide? If equity is involved, ask the plan administrator for the governing documents and deadlines rather than trusting a summary in a meeting.

In the United States, the Department of Labor says eligible workers generally get at least 60 days to elect COBRA after coverage ends or the election notice arrives, whichever is later. HealthCare.gov also describes a 60-day special enrollment window after loss of job-based coverage. These are options, not a reason to wait until day 59. Compare total premiums, deductibles, provider networks, medication coverage, and family needs during the first week. Rules differ by country, state, employer size, and plan, so use the agency or plan administrator that governs your case.

File for unemployment promptly if you may qualify. Do not decide that severance, savings, or professional pride makes the application unnecessary. The state or national agency decides eligibility, and filing dates can affect payments. Record every submission, confirmation number, deadline, and person you speak with in one document.

## Week one is a week for cash control

Your financial task in week one is to calculate a conservative runway and reduce its burn without wrecking your health or search. A bank balance by itself is not runway. You need the amount available for living costs, the monthly floor, known exceptional bills, benefit income, and tax obligations in the same view.

Build a private sheet with four blocks:

- Available cash includes checking, savings, and severance after estimated tax. Exclude retirement accounts, an uncertain bonus, and unvested equity.
- The monthly floor includes housing, food, insurance, debt minimums, care, and transport. Exclude optional subscriptions, normal travel, and aspirational savings.
- Exceptional costs include a medical deductible, relocation, a tax payment, and essential equipment. Exclude purchases you can postpone.
- Expected inflow includes approved benefits and signed contract income. Exclude leads, verbal promises, and possible equity value.

Use a calculation you can audit:

`runway months = (available cash - exceptional costs) / (monthly floor - dependable monthly inflow)`

Then make three plans. The base plan assumes a normal search. The slow plan assumes the search takes twice as long as you hope. The emergency plan names the trigger for contract work, a move, a larger expense cut, or a conversation with creditors. Naming triggers now prevents a frightened decision later. For example: if runway falls below four months, widen the role and location criteria; below three months, add paid contract work; below two months, preserve cash before optimizing title. Choose thresholds that fit your household rather than copying these numbers.

Call providers before missing a payment. Lenders, landlords, utilities, and medical billing offices sometimes have hardship arrangements, but they work better before an account becomes delinquent. Ask what changes interest, fees, reporting, or the total amount owed. A lower payment can still be an expensive deal.

Treat retirement money as protected until a qualified adviser tells you otherwise. The IRS lists leaving money in an old plan, moving it to a new employer plan, rolling it to an IRA, or withdrawing it as distinct choices. If an eligible distribution is paid to you, the standard rollover period is generally 60 days, and an payment from an employer plan made to you can have mandatory federal withholding. A direct rollover avoids several ways to make an expensive clerical mistake. Tax rules and exceptions depend on the account and your circumstances, so this is a decision for source documents and professional advice, not a forum thread read late at night.

## Week one needs a calm, short layoff story

Your narrative should explain the event in twenty seconds, remove doubt about performance, and turn toward the work you want. It does not need to defend your worth or expose the former employer's internal politics. A layoff is a business event. Tell the truth, use the language in your separation documents, and stop before resentment enters the sentence.

A useful structure has four parts: what changed, the scope if you can state it accurately, what you delivered, and what you want next. For example:

> My role was eliminated during a broader product reorganization. I led the release process for two services used by customers and cut rollback time by changing how we staged deployments. I am now looking for a staff engineering role where reliability and delivery ownership sit together.

If the company eliminated only your role, do not claim a reduction across the company. Say the role was eliminated and move on. If performance contributed, inventing a mass layoff will collapse under reference checks. State the separation briefly, describe what you learned, and show what changed in your work.

Write three versions: one sentence for casual contacts, a short paragraph for recruiters, and a answer lasting two minutes for interviews. Record the long version on your phone. Remove defensive details, apologies, and the chronological tour of your last six months. The listener needs a stable account, not courtroom testimony.

Update your resume headline, profile summary, and public status with the same target. Avoid the message that says you are open to anything. People cannot route an undefined request. "Backend or platform roles at growing companies, remote in the United States or hybrid in Seattle" gives a contact something to recognize. "Any tech opportunity" asks that contact to design your search for you.

Do not publish confidential metrics to prove impact. Replace sensitive absolute numbers with approved percentages, ranges, scale descriptions, or the operational change itself. When you cannot use a metric, describe the decision and consequence: you split a risky migration into reversible stages, changed the on-call handoff, or removed a deployment bottleneck. Specific work still sounds specific without exposing company data.

## Week two turns contacts into useful conversations

Network activation works when each person receives a small, answerable request. Broadcasting desperation to hundreds of weak contacts creates sympathy, not routing information. Start with people who have observed your work, then expand to people who understand the market you are entering.

Make a list of about thirty names across former teammates, managers, customers you may contact, vendors, community peers, founders, and recruiters. Mark each relationship as close, warm, or dormant. Also mark the request that fits: perspective on a company, an introduction, feedback on positioning, or news about an unposted need. Do not ask every person for a job.

Send five personal messages per weekday for two weeks. Each message should contain context, target, proof, and one request. This is enough:

> I was affected by the product reorganization at my company last week. I am targeting staff backend roles where I can own reliability and delivery, preferably at a company with a real production workload. You saw my work on the billing migration, so I would value your view: which two teams would take that background seriously?

A dormant contact needs a little more context and less obligation:

> We worked together on the infrastructure review three years ago. My role was recently eliminated, and I am looking for engineering leadership work with teams that need to improve release speed without lowering reliability. If one company or person comes to mind, I would appreciate the name. No introduction is needed unless you are comfortable making one.

Track the messages because memory becomes unreliable under stress. Use columns for name, relationship, date sent, request, reply, promised action, date to follow up, and outcome. Follow up once when you have new information or after a reasonable pause. Repeated "just checking in" messages spend social capital without adding a reason to answer.

The popular advice to announce the layoff immediately to everyone is incomplete. A public post can help after your target and story are clear. Before that, it often produces a wave of mismatched referrals that you must politely process. Prepare the routing information first, contact the people most likely to help, then publish if a broader signal fits your profession.

## Week two rebuilds evidence, not a fake workload

Your resume and portfolio need evidence for the next role, not a record of every responsibility in the last one. Hiring teams infer level from scope, decisions, constraints, and consequences. A list of tools tells them almost nothing about how you operate.

For each recent role, write six private evidence cards. Each card should answer: what condition existed, what decision you owned, what tradeoff you made, what changed, and who can verify the work. Then choose the cards that support your target. This produces stronger resume bullets and gives you interview stories from the same source.

Weak: "Responsible for Kubernetes infrastructure and CI/CD."

Stronger: "Separated application and infrastructure releases, added staged health checks, and reduced the number of changes that required a coordinated maintenance window."

The stronger version does not invent a percentage. It names an operational constraint and a change. If you have an approved measurement, add it. If you do not, resist the pressure to manufacture one. Experienced interviewers test suspicious precision.

Build one small public artifact only if it closes a proof gap. A staff engineer may write a concise design note comparing two migration strategies. A product leader may publish an anonymized decision memo. A designer may rebuild a flow with invented data and label it clearly as a retrospective exercise. Do not spend three weeks creating a grand portfolio site when two clear case studies would answer the hiring question.

Run a consistency audit before applications begin:

1. Does every public profile name the same role family and level?
2. Do dates and titles match across the resume, profile, and application form?
3. Can you explain every claim without revealing confidential information?
4. Do the top five bullets support the target role rather than the job you just lost?
5. Can a former colleague recognize the work and agree with your account?

References deserve preparation too. Ask permission, describe the roles you are pursuing, and remind each person of the work they observed. Never script their praise. Give them context so they can choose relevant examples instead of guessing what the employer wants.

## Week three makes interviewing a production skill

Interview performance improves through repeated, scored practice under realistic limits. Reading more material feels safe, but it does not expose rambling answers, silent assumptions, weak coding narration, or a system design that ignores the prompt. Practice must resemble the interview.

Create an interview matrix with the rounds likely for your target: recruiter screen, hiring manager, behavioral, technical exercise, system or product design, portfolio review, and executive conversation. Remove the rounds that do not apply. For each remaining round, define the signal being tested, two practice methods, and an observable pass condition.

For behavioral interviews, prepare eight stories that cover conflict, failure, ambiguous ownership, an unpopular decision, mentoring, speed versus quality, a customer consequence, and a project you would run differently. One story can answer several prompts, but the lesson must change with the question. Keep the situation short. Spend most of the answer on your decision, alternatives, action, and result.

For coding interviews, work in the language you will use on the day. Time the session, speak your assumptions, write tests, and review complexity. Afterward, label the failure precisely: data structure recall, syntax, problem framing, test coverage, pace, or communication. "Bad at algorithms" cannot guide tomorrow's practice. "Missed that the input was already sorted and chose an unnecessary hash map" can.

For system design, start by confirming users, load shape, consistency needs, failure tolerance, and the part you should design. Draw the basic path before naming technologies. Interviewers want to see how requirements constrain decisions. A tour of fashionable infrastructure often signals that the candidate has memorized diagrams without operating them.

Use a scorecard after every mock and real interview:

- Answer structure, score 1-5: record the evidence and the next drill.
- Technical judgment, score 1-5: record the evidence and the next drill.
- Communication, score 1-5: record the evidence and the next drill.
- Role motivation, score 1-5: record the evidence and the next drill.

Ask practice partners for evidence, not encouragement. "Where did you stop believing my answer?" and "Which decision did I leave implicit?" produce usable notes. Rotate partners when possible because a familiar partner starts filling gaps on your behalf.

## Week four needs a narrow message and a wider funnel

You can widen companies, industries, contract types, and locations without presenting yourself as five different professionals. Keep the problem you solve stable while changing where that problem appears. This preserves a coherent narrative and increases the number of plausible employers.

Separate opportunities into three lanes. The primary lane matches role, level, compensation range, and preferred environment. The adjacent lane changes one major variable, such as industry or company stage. The bridge lane covers consulting, contracting, or a role with lower risk that protects runway. Assign weekly effort according to runway and response, not ego.

Quality applications deserve more time than forms with a low probability, but perfection is another hiding place. A reasonable weekly rhythm might include five deeply matched applications, five warm conversations, two recruiter calls, two mock interviews, and one evidence update. Adjust the counts after two weeks of data. If warm conversations convert and forms do not, move effort. If recruiters call but hiring managers pass, positioning or evidence needs work. If late rounds fail, applications are not the constraint.

Keep an application ledger with company, role, source, date, contact, stage, next action, compensation information, and rejection reason. Add a field for "why this role" before applying. If you cannot write two concrete sentences without praising the company's mission in generic language, the fit may be weak or your research unfinished.

Do not lower your stated level after three quiet days. Titles vary widely across tech companies, and a smaller company may give a senior engineer more scope than a larger company gives a staff engineer. Compare decisions, reporting line, team expectations, and business consequence. Chase the work and compensation structure, not a word on a badge.

Recruiters belong in the funnel, but they do not own it. Ask which company they represent, whether they have a direct mandate, what stage the search is in, and which requirements have already rejected candidates. Never send sensitive identity documents or financial information merely because an unsolicited message uses urgent language. Verify the person and firm through independent channels before sharing more than a resume.

## Weeks five and six use rejection as diagnostic data

A rejection helps only when you classify where the process broke and change one variable. Treating every no as proof of a bad market destroys judgment. Treating every no as random prevents improvement. Most individual outcomes contain noise; a pattern across similar stages deserves attention.

Review the funnel once a week, not after every email. Count qualified applications, warm introductions, recruiter screens, hiring manager screens, technical rounds, final rounds, offers, and withdrawals. Do not compare raw totals between lanes because a warm introduction and an anonymous form have different probabilities. Compare each source with its own past performance.

Use diagnoses tied to each stage. Few recruiter screens suggest the target, resume, geography, work authorization, or compensation range is mismatched. Recruiter success followed by hiring manager rejection points to role narrative, level, or evidence. Repeated technical failures require a narrower drill. Losses in the final round may involve executive communication, competing domain experience, team composition, or simple variance. Ask for feedback once, but do not wait for it to continue the review.

Change one major element for the next batch. Rewriting the resume, changing the target title, doubling applications, and altering interview answers in the same week makes the result unreadable. Run a small test: replace the top summary and first three bullets for ten closely matched roles, or practice one design weakness across three mocks. Keep what improves the conversion to the next stage.

Protect two periods each week from search activity. A job search expands to consume every hour because there is always another listing or exercise. Exhaustion then appears in interviews as flat answers and poor recall. Schedule exercise, care work, and time with people who do not need an update on the search. This is maintenance for judgment, not a reward you earn after an offer.

Watch for a different failure: accepting endless unpaid assignments. Before a exercise completed at home, ask the expected time, evaluation criteria, ownership of the work, and next step. A bounded simulation can be reasonable. Production work disguised as evaluation, vague tasks that require several days, or repeated exercises without a decision deserve a polite withdrawal.

## Consulting is useful only when it has boundaries

Consulting can extend runway, restore momentum, and reveal a better direction for the long term, but it can also consume every good interview hour for low rates. Decide whether it is a bridge, a deliberate career path, or a distraction before accepting the first request.

A bridge project needs a fixed problem, buyer, deliverable, price, payment schedule, and end date. Avoid arrangements described as "help us with engineering for a while." That language usually hides management work, support, architecture, and delivery inside one uncertain fee. Put scope changes and access requirements in writing. Protect confidential information from both the former employer and the client.

Price against the whole job, including discovery, meetings, sales time, tax, insurance, and gaps between projects. Dividing an old salary by working hours understates the cost of independent work. Ask for a deposit or short billing cycle where normal and lawful. Stop work according to the contract if invoices age beyond agreed terms. Generosity at the start rarely fixes a buyer who does not respect payment.

For senior engineers and technology leaders, advisory or fractional work may be a real lane rather than temporary cover. Test it with a specific offer: the kind of company, the operational problem, the decision maker, the engagement shape, and the result you can credibly pursue. On oleg.is, founder advisory and fractional CTO work are available month to month, which is also a useful reminder that buyers understand a concrete engagement better than an undefined promise to "help with tech."

Keep consulting and employment stories compatible. "I took a migration assessment lasting six weeks while looking for a permanent platform leadership role" shows initiative. A scattered collection of unrelated gigs can make employers wonder whether you want the job. Say which path is primary and why the project strengthens it.

## An offer should solve more than the immediate fear

Evaluate an offer against the conditions that made the last role work or fail. Salary matters, especially when runway is short, but a familiar logo and restored income can hide an unstable mandate, unclear manager, or hiring plan that depends on money the company does not have.

Ask the hiring manager what must be true after 30, 60, and 90 days, which decisions the role owns, why the position is open, and what changed in the budget since approval. Ask future peers how work reaches the team, how priorities change, and what happened during the last serious production or customer problem. Compare the answers. Small inconsistencies are normal; incompatible descriptions of the role are a warning.

Build an offer table before negotiating. Include base pay, variable pay and its actual conditions, equity terms, health costs, retirement match, leave, location costs, travel, on-call load, title, scope, manager, learning value, and failure risk. Mark unknowns instead of converting them into optimistic assumptions. Equity with an unknown denominator or unclear terms belongs in the unknown column, not in cash compensation.

Negotiate two or three items that materially affect the decision. State the evidence: competing scope, market information, forfeited compensation, required travel, or a mismatch between title and responsibility. Do not invent another offer. If base pay cannot move, consider signing compensation, a review date with written criteria, leave, location, start date, or scope. A promise that is not in the written offer may disappear with the person who made it.

Runway gives you the ability to inspect rather than plead. Use it. If the role has no stable owner, the interviewers cannot agree on success, or the company pressures you to sign before answering ordinary questions, another month of searching may cost less than another damaging exit. When the offer is sound, close the search professionally: accept in writing, withdraw from active processes, thank the people who helped, and keep the weekly system until the first day. A layoff removed your job; it did not remove your obligation to choose the next one carefully.