Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.

I was laid off from my developer job. What should I do now?

Tauseef Fayyaz

Answered by Tauseef Fayyaz

Asked 7 timesUpdated 27 Sept 2026
Short answer

Take a few days to absorb it, then handle the practical things first: paperwork, final pay, references and a budget. Tell your network early and plainly, update your CV with recent work while you remember it, and run your job search as a daily routine with a steady pipeline, not a panic.

What people tell me

I was told on a short call that my role was being cut along with several others. It had nothing to do with my performance, according to them, but it still feels personal. I have some savings but not a lot. I do not know whether to start applying immediately, take a break, learn something new first, or how to explain the layoff in interviews without sounding defensive.

A composite of the messages behind this question, with personal details left out.

Key takeaways

  • A layoff is a business decision, not a verdict on you. Recruiters see them all the time.
  • Do the admin in the first week: final pay, documents, experience letter, references, and a simple budget.
  • Write down your recent achievements now, while details and numbers are fresh.
  • Tell your network plainly and specifically; many roles are found through people.
  • Treat the search like a job with a daily routine, and keep one small learning project going alongside it.

First, it is not a verdict on you

Layoffs happen when budgets change, projects are cancelled or companies restructure. Good engineers are laid off every year. Hiring managers know this and rarely hold it against anyone. It still hurts, and it is fine to feel angry or embarrassed for a few days. Just do not let the feeling write your plan.

Week one: the practical things

  1. Get everything in writing: last working day, final pay, any severance, leave encashment, and when you will receive them.
  2. Ask for documents: experience or service letter, and confirmation that the role was eliminated.
  3. Ask two or three people for references now, while they remember your work well. Your manager is often willing, even if they could not save your role.
  4. Save your own records. Only things you are allowed to keep, such as your own notes, public work and contact details. Do not copy company code or data.
  5. Make a budget. Work out how many months your savings cover at reduced spending. That number shapes every other decision.
Months of runwaySensible approach
Under 2Apply broadly and quickly, consider contract or interim work
2 to 4Focused search, with a backup plan by month two
4+Room to be selective and fill one skill gap on the side

Capture your recent work while it is fresh

Within a few days you will start forgetting the details. Write a page with every meaningful thing you did in the last year or two: features, systems you owned, incidents you handled, improvements with numbers where possible. This becomes your CV bullets and your interview stories. Why is my resume not getting shortlisted for software engineering roles? helps you turn it into a strong CV.

Tell people, plainly

Do not hide it. A short, factual message works well:

"My role at my company was one of several affected by a restructure last week. I am looking for backend roles, ideally working on payments or data-heavy systems. If you hear of anything, or know someone I should talk to, I would really appreciate it."

Send it personally to former colleagues and managers, then post a short version publicly if you are comfortable. Be specific about what you want; "anything" is hard for people to act on.

How to explain it in interviews

Keep it to two sentences and move on:

"The company cut a number of roles after losing a major contract, and my team was affected. I am proud of what I built there, for example..."

No blame, no long story. Interviewers mainly want to know it was not for cause and that you are not carrying bitterness into the next job.

Run the search as a pipeline

Treat it as a daily routine rather than bursts of panic. The blog post A Job Search Is a Pipeline, Not a Performance explains the mindset.

Daily blockTimeActivity
Morning2 hoursTargeted applications and personal messages to people at those companies
Midday1 to 2 hoursInterview practice or a small learning project
Afternoon1 hourFollow-ups, tracking, networking calls
EveningOffRest, exercise, time with people

Track every application in a spreadsheet: company, role, date, contact, stage, next step. Browse open roles and companies for targets.

A four-week plan

WeekGoals
1Admin, budget, references, achievement list, message to network
2Updated CV and LinkedIn, target list of 30 companies, first 10 to 15 applications
3Steady applications, practice interviews, one small skill project
4Review what is working (replies, interviews) and adjust targets or CV

Should you learn something new first?

Only if a clear gap is costing you interviews. Spending three months on a course before applying usually just delays things. Apply now, and learn in parallel based on what interviews reveal.

Look after yourself too

A layoff is a loss, and job searches are full of silence and rejection. Keep a normal daily structure: wake at the same time, get outside, exercise, see people. Set a clear end to each search day so it does not swallow your evenings. Tell the people close to you what is happening; hiding it adds pressure. If you notice weeks of low mood, poor sleep or hopelessness, talk to someone you trust or a professional. Protecting your energy is not a distraction from the search. It is what keeps you performing well in interviews in week eight as well as week one.

Common mistakes

  1. Taking a long break without a budget. Rest is fine, but know your runway.
  2. Applying everywhere with the same CV. Tailor to two or three role types.
  3. Hiding the layoff. It makes explaining the gap harder later.
  4. Accepting the first poor offer out of fear when your runway allowed more time. Should I take the first job I get, or wait? helps with that choice.
  5. Isolating yourself. Talk to people; the emotional side matters too.

If you are still stuck

The Job search roadmap lays out the search stage by stage. If you want help planning your next move, join Sefism. It is free to learn, you receive credits on joining, and members can ask their own question or book a 1:1 session to work through it together.

Was this answer helpful?

Ask your own

Your situation is not quite this one?

Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.

More questions people ask

All questions

AI is squeezing basic, repetitive freelance work first: plain data entry, simple transcription and translation, generic articles, basic logos and simple product descriptions. Work that combines a skill with judgement, client context or systems is holding up better, including automation, AI integration, analytics, specialist writing and full projects that own a business outcome.

Asked 14 timesRead the answer

It can be, but the maths has changed. Graduate tech jobs in the UK are harder to find, the Graduate visa drops from two years to 18 months for applications from 1 January 2027, and sponsored jobs have salary floors many junior roles miss. A UK master's is worth it if you want the degree itself, have a realistic plan for sponsorship, and can afford it without crushing debt.

Asked 14 timesRead the answer

Research a realistic range, avoid naming a number too early, let the employer make the first offer where you can, then counter once with a specific figure backed by your scope and the market. Look at the whole package, and for remote dollar roles compare the real take-home after fees, taxes and missing benefits.

Asked 13 timesRead the answer