← All posts
general

Interviewing After a Layoff: A Plan for Senior Engineers

The calendar invite said "Business update" and gave fifteen minutes' notice. By lunchtime your laptop was locked. If you have eight or twelve years behind you, interviewing after a layoff carries a particular difficulty: you are good at the job and badly out of practice at getting one. The last time you interviewed, the questions were different, the market was different and you were not doing it with a severance clock running.

The usual advice is to update the CV and apply widely, starting today. For a senior engineer that order is backwards. Applying widely before you can explain your last three years in two minutes burns your best leads on your worst interviews. This is a plan in the order that works: steady the ground, build the story, get fit, then run a pipeline wide enough to produce a choice.

The market as it is

Three figures, each with its source, because the numbers quoted online come from trackers that count different things.

Challenger, Gray & Christmas, which counts announced US job cuts, put technology at 171,501 cuts for January to October 2026, already above its 154,445 for the whole of 2025, according to TheStreet's report on the October release; October itself, at 5,576, was the sector's lowest month of the year.

Layoffs.fyi, which counts tech employees from public reports worldwide, had 125,759 people at 264 companies by 6 August 2026 against 122,606 for all of 2025, as IBTimes UK reported that week, while TrueUp, which includes more startups and non-US employers, counted 174,721 over a similar period. The trackers do not agree and are not meant to.

On the hiring side, Indeed's Hiring Lab reported in July 2026 that US software development postings had risen almost 15% since late February 2025 while remaining about 27.5% below their pre-pandemic level, and that senior roles accounted for 71% of the increase between May 2025 and May 2026.

Put together: a lot of experienced people are looking at the same time as you, and the openings that exist lean senior. That is a harder market than 2021 and a better one for your profile than the layoff headlines suggest. It also means a layoff is ordinary to the people interviewing you. They have colleagues it happened to, and some have been through it themselves.

The first two weeks

Do not interview in week one unless a process was already running. Use the time for things that are hard to do later.

Days 1 to 3: paperwork and proof.

  • Read the severance agreement before signing, including the deadline to sign, what happens to unvested equity, the exercise window for options and any clause about what you may say. Terms differ by company and country; for anything unclear, pay an employment lawyer for an hour.
  • Sort out health cover and any benefits or registration deadlines that apply where you live.
  • Write down what you worked on while you still remember it: projects, your role, numbers, names of people who saw the work. You have lost access to the documents, and in three weeks you will have lost the detail too.
  • Ask your manager and two peers whether they will be a reference, and ask now, while they feel it.

Days 4 to 7: money and direction.

  • Work out your runway in months: severance plus savings divided by real monthly spending. This number decides how selective you can be, so make it honest.
  • Decide what you are looking for in one sentence: role, level, kind of company, location or remote. "Anything senior" is not a search.
  • Tell people. A short message to former colleagues with that one sentence in it. Referrals move faster than applications, and people cannot refer you to something you have not named. The older post on job search strategies covers the outreach side in more detail.

Week 2: materials and a baseline.

  • Rewrite the CV around scope and results, two pages at most.
  • Build six to eight stories from the notes you made on day 2.
  • Do one timed coding problem and one design question cold, to see where you are. The result will be worse than you expect. That is the baseline, and you should not read it as a verdict.

The layoff in one honest sentence

Interviewers ask "why are you looking?" as a warm-up. They want a fact, a tone and a transition, and the answer takes ten seconds.

The structure: what happened, at the scale it happened, then where you are going. Invented examples:

  • "My team was part of the March reduction; about a fifth of engineering was cut. I'm using it to move toward infrastructure work, which is why this role caught my eye."
  • "The company closed its London office in September and my role went with it. I'd been leading the billing migration there for two years."

Rules that keep it clean:

  • Say "laid off" or "my role was eliminated". Euphemisms sound like something is being hidden.
  • Give the scale if it helps. A cut of a whole team, office or percentage shows it was not about you. Use only numbers that are public or that you know to be true.
  • No commentary on the company. Not about leadership, strategy or how it was handled. Even if the criticism is fair, the interviewer hears how you will one day talk about them.
  • Do not volunteer a defence. "It wasn't performance related" answers a question nobody asked. If they ask directly whether it was performance related, answer directly and briefly.
  • End on the future. The last clause should point at the job in front of you.

If you were selected individually and not as part of a group, the sentence still has the same shape: the fact, without decoration, and what you took from it. A reference from your former manager does more here than any wording.

A gap needs no excuse. "I took six weeks to reset and have been interviewing since October" is a complete answer.

Rebuilding interview fitness

Interviewing is a skill separate from engineering, and it decays. After five years in one company you are probably better at design than you have ever been and slower at a timed coding problem than you were as a junior. Plan for four to six weeks to get back, and start before the first interview that matters. The four-week prep plan for senior engineers lays those weeks out session by session.

  • Coding. Short daily sessions beat weekend marathons. Thirty to forty-five minutes, one problem, timed, aloud. Start with easy problems to restore speed and the habit of talking. Check whether your target companies allow AI tools or run rounds in person; both have changed since you last interviewed, as the guide to AI in coding interviews explains.
  • System design. Your experience is an asset here if you can structure it. Practise the first five minutes (requirements and numbers) until it is automatic, and learn to state trade-offs before being asked.
  • Behavioral. This is where senior candidates recover fastest, and where level is decided. Tell each story aloud three times. The first telling of any story is too long.
  • Mocks. Do one in week two of your prep, when it will go badly. The point of the first mock is to find out what is broken while it is cheap.

Sequence your real interviews the same way. Put two or three companies you would accept but do not dream about first. Your first live loop after years away is a rehearsal whether you intend it or not.

Pipeline arithmetic

One process at a time is the most expensive mistake available to you. A single process can take two months to end in a no, and then you start again with less runway.

Do the arithmetic with your own conversion rates, which you will know after a few weeks. As an invented illustration: if one in four recruiter screens leads to a full loop and one in four loops leads to an offer, then two offers need about eight loops and about thirty screens. Your rates may be better. The structure does not change: the number of conversations to start is far larger than feels natural.

Then manage time so offers arrive together:

  • Start applications in batches, a week apart, with the slowest companies first. Large companies often take far longer than startups; ask each recruiter for the usual timeline at the first call.
  • When a fast process reaches the final stage, tell the slow ones. "I expect an offer in two weeks" is the one message that reliably speeds a recruiter up.
  • Keep a simple tracker: company, stage, last contact, next step, who referred you.
  • Cap active loops at what you can prepare for. Three or four final-stage processes in the same fortnight is about the limit for doing each well.

Two offers in the same week change everything about the last conversation, which is the subject of the guide to handling competing offers.

Protecting level and pay

A layoff tempts people to accept the first offer at any level. Sometimes that is right. Decide it deliberately, because a level given up is slow to win back.

  • Fix the level before the loop. Ask the recruiter which level the role is and which level the loop is calibrated for. If they propose interviewing you a level down "to be safe", ask what evidence would support the higher one.
  • Bring evidence at your level. Level is read from the scope of your stories: how many teams, how ambiguous the problem, who made the decision. Stories about executing someone else's plan read a level lower, however well executed.
  • Do not reveal your runway. Whether you are employed has no bearing on what the role pays. "I'm in several processes and want to make a considered decision" is true and sufficient.
  • Anchor on the role, not your last salary. Where the law or your own judgment allows, decline to give your previous pay and ask for the band.
  • Know your floor before the call. Decide in advance the level and the number below which you keep looking, and how many more weeks of runway you will spend to hold it.

If the offer comes back one level under, there are more options than yes or no; they are set out in the guide to a down-levelled offer.

Money and time pressure

Pressure makes people interview badly: they talk faster, concede earlier and accept worse terms. You cannot remove it. You can stop it from driving.

Turn the runway into dates. Take the number of months from week one and mark three points: when you search only for the role you want, when you widen to adjacent roles or contracting, and when you take a reasonable offer and keep looking from inside. Write them down in advance, so they are not decided under pressure later.

Keep a working week. Four or five focused hours a day of search and preparation is more productive than ten anxious ones, and it leaves room for exercise and for people. Rejections will come, some of them after good interviews. Treat each as data on one of three things: the pipeline (not enough conversations), the story (screens not converting) or fitness (loops not converting). Fix the stage that is failing; do not rewrite everything after every no.

Where a coach saves weeks

The weeks go on problems you cannot see from inside: a story that sounds defensive, a level pitched too low, a design answer that stops short of trade-offs. A colleague can catch some of it. A coach who has hired at your level catches it in one session, which matters when each failed loop costs a month of runway.

The points where outside help pays for itself: the layoff sentence and the two-minute career summary before the first screen, one mock before the first loop that matters, and the level and offer conversation at the end. If you want a second opinion on the plan itself, a session with a career coach in week one or two is the moment it changes the most.

Where coaching fits

Career coaching is the most common specialty on techinterview.coach: 33 of the 40 coaches list it as of November 2026, and the career coaches page shows their backgrounds so you can pick someone who has hired for the level you are protecting. Twenty-nine of those 33 offer an intro call before a full session. For daily speaking practice that costs nothing, the practice interview runs a voice round with an AI interviewer on behavioral, system design, coding talk-through or salary negotiation, with a written recap. It is free; sign in to start.

Related guides