Being laid off is a business decision about a role, not a verdict on a person, and everyone tells you that on day one. It does not help much on day one. What does help is having a short list of concrete things to do while the rest of it is still sinking in, because most of them are time-limited and a few of them close quietly if you miss them.
The first week, in order
Some of these expire. Do them before the search, and before the feelings have finished arriving.
- Get your contacts out. Company email and internal directories are usually cut within hours, sometimes immediately. Personal email addresses and phone numbers for the people who would vouch for you are the single most valuable thing you lose access to.
- Write down what you did, while you remember. Projects, numbers, dates, systems, the things that went well. Six months from now the details will be gone, and they are exactly what your resume needs.
- Ask for references now. Your manager is often more willing in the week they had to deliver the news than in six months when they have moved on. A written recommendation while the work is fresh is worth more than a phone call later.
- Sort out health cover and benefits. Whatever the rules are where you live, they have deadlines and the deadlines are unforgiving. Find out what yours are this week.
- File for unemployment support if it exists where you are. Many people delay out of a vague sense that it is not for them. It is for exactly this, and claims frequently take weeks to process.
Before you sign anything
Severance agreements are usually presented as standard and final. They often are. They are also a contract, and there is normally more room than the framing suggests, particularly on the parts that are not money.
Ask what the notice period actually is, whether the end date can move to protect a vesting or bonus threshold, whether unused leave is paid out, what happens to any equity, whether an agreed reference wording can be included, and what the agreement stops you saying afterwards. Non-disparagement clauses are common and are worth reading carefully rather than skimming.
You are usually entitled to time to review, and if the sums involved are significant, an hour with an employment lawyer is cheap relative to what is on the table. Nobody is offended by a candidate who reads a contract.
Saying it on the resume
The resume does not need to explain anything. Roles have end dates; that is normal and no reader will be surprised by one. What creates a problem is an unexplained hole growing month by month, because a reader who cannot tell what happened will guess, and their guess is usually worse than the truth.
Once the gap is long enough to notice, give it a line: "2026 — Role eliminated in company-wide reduction. Contract work and open-source contributions during search." That sentence removes the question entirely, and it is far better than the reader inventing an answer.
Year-only dates rather than months make shorter gaps disappear without concealing anything, and are completely standard practice.
Saying it in the interview
Two sentences, delivered without apology, then move to the work. "My role was cut when the company reduced the platform team by about a third. I was there four years and shipped X and Y in the last one." That is the whole answer.
The instinct is to over-explain, and over-explaining is what creates suspicion where none existed. Long justifications signal that you think something needs justifying. Layoffs are unremarkable to interviewers; almost everyone in the room has either been through one or made the decisions.
One thing worth avoiding: criticising the former employer. It is often deserved and it never helps. The interviewer cannot verify the story and will file it as a data point about how you talk about employers, including the one they represent.
On "my job was automated"
Some roles are genuinely being reshaped by automation, and it is worth being precise instead of fatalistic about it. What is usually happening is not that an entire job disappeared but that a set of tasks inside it became cheap, which changes what the remaining role is for.
That distinction is actionable. If the tasks that got cheap were the bulk of what you did, the honest answer is that you need to move toward the parts that did not: judgement, context, responsibility for outcomes, the work that requires knowing why rather than how. If they were a fraction, your job is to become visibly good at doing the rest with the new tools rather than in spite of them.
Either way, the resume framing is the same and it is not defensive. Someone who used the new tools to do more, and can describe specifically what that produced, is a stronger candidate than someone who avoided them. Vague claims about being AI-literate are worth nothing; a concrete before and after is worth a great deal.
Use the network before you need it to work
The uncomfortable truth about being laid off alongside other people is that it is briefly an advantage. Your former colleagues are landing at other companies over the following months, and each one becomes an internal contact somewhere new. That is a network forming in real time, and it decays if you do not stay in it.
Tell people you are looking, specifically and early. "I am looking for backend roles, ideally payments or infrastructure, London or remote" gives someone something to act on. "Let me know if you hear of anything" does not, because it puts the work of figuring out what you want onto them, and they will not do it.
Ask for referrals rather than recommendations. A referral is two minutes of someone's time and often carries a bonus for them; a recommendation asks them to vouch for something they may not feel able to. Send the posting, three lines on why you fit, and your resume attached, so the whole thing is a forward rather than a task.
What actually compounds while you look
There is a strong pull toward filling the time with courses and certificates, because they are visible, structured and feel productive. Most of them do very little for a search. A certificate is evidence that you completed a course, which is a weaker claim than almost any piece of real work.
What holds up better in an interview is something you built, fixed, wrote or ran, however small, that you can talk about for five minutes. A contract engagement, an open-source contribution, a piece of volunteer work with an outcome attached, something you shipped for yourself. It fills the gap on the resume with an activity rather than a study period, and it gives you a recent story to tell when someone asks what you have been doing.
The part that is not tactical
A search takes longer than people budget for, and the gap between the expected timeline and the real one does its own damage. Someone who planned for four weeks and is at week ten starts making decisions from panic: accepting the wrong role, negotiating badly, or applying to two hundred things at once.
Two things help concretely. Decide now, while you are still calm, what you will accept and what you will not, and write it down. And keep a structure to the week, because an unstructured search expands to fill every hour and produces guilt in the gaps without producing more interviews. Applying is not the only useful activity, and it is the one that scales worst.
Get the pipeline out of your head
A board for every application with stages, notes and follow-up reminders. When the search runs longer than expected, the record is what tells you which stage is actually failing instead of leaving you to guess.
Start free