After a layoff · 4 min read
Laid off from tech? Do you have to leave tech?
The tech jobs market is uneven. Before leaving the field, test roles that use your systems knowledge in new settings, with no heroic reinvention required.
Written by Nivaan, founder of OffLadder · Last reviewed · Sources listed at the foot of this page
The short answer
A layoff from a tech company is not the same as the end of your technical career. It might be a reason to change employer, product, function or industry. Changing all four at once is possible, but it is an expensive way to discover what you wanted to keep.
Read the hiring data carefully
Indeed Hiring Lab reported in July 2026 that US software-development postings had risen almost 15% since late February 2025 while overall postings fell about 7%. The rebound was narrow: 71% of the increase from May 2025 to May 2026 came from senior roles, with AI-labelled roles accounting for a substantial share. Job-posting trends are not the same as hires, and this is US data. That means neither 'software is finished' nor 'the market is back' is a useful statement. Senior, junior, infrastructure, product and research candidates face different markets. Look at live openings for your experience level before deciding to leave.
Take your systems thinking somewhere it is less common
A developer used to debugging complicated systems might test accessibility work, energy operations, public-service technology or implementation. A product leader might move into operational change in healthcare or logistics. An engineer who dislikes building features but loves tracking down edge cases might enjoy evaluation or reliability work.
The test is not whether a sector sounds worthy. It is whether you like its constraints. Regulation, slow procurement and physical-world failure can be fascinating or maddening, depending on the person.
Work out whether you are leaving a company, a craft or a setting 'I'm done with tech' can hide four different complaints. You might be done with a particular employer, done with repeated layoffs, done with coding, or done with products you do not believe matter. The distinction affects your options. Someone who still loves diagnosing systems may enjoy technical operations in energy or healthcare. Someone who dislikes screen-heavy work altogether needs a more substantial test, possibly outside software.
Write down the last five projects that made you proud. Mark what you contributed: solving the technical problem, talking to users, coordinating the people, testing the outcome or understanding the domain. Then look for jobs that pay for that contribution. Titles are misleading. 'Implementation specialist' in one company can mean technically demanding integration; in another it means account management and paperwork. Read the responsibilities and interview for the working day.
Four adjacent experiments that do not require a new degree
Accessibility: select a public service website, navigate a key path using only a keyboard, log where you get stuck and compare the results with the Web Content Accessibility Guidelines. A browser check is a first pass, not a professional accessibility audit.
Workflow operations: diagram a repetitive process in a small business you know. Where do requests enter? Who approves exceptions? What fails when someone is absent? Improve the handoff before considering tools.
Climate and energy systems: learn the basic constraints of a local energy retrofit or flexible-load programme, then explain the data and decision points on one page. Do not pass off desk research as an engineering assessment.
Product implementation: take open documentation for a small software tool and create a first-week onboarding guide for a hypothetical customer, including likely failure points. If translating complexity feels more interesting than writing code, investigate solutions engineering or implementation roles.
How to read hiring signals without fooling yourself
A rise in vacancies does not mean all developers are in demand. Filter for your seniority, location, visa eligibility, industry and salary requirements. Check actual listings rather than general headlines, and examine the skills that recur. The Indeed Hiring Lab analysis cited below describes US posting trends, not your odds of getting an offer. If you are a junior developer, projects with users and careful testing logs may matter more than another tutorial certificate. If you are senior, the question may be whether your judgement belongs in a new sector.
Where OffLadder fits
OffLadder can suggest directions that use a technical background without assuming you must keep the same job title. Explore shows what the work may involve, what carries over and how established the direction is. Pick one experiment, make something small and ask Laddie what your reaction changes. See a starting point at https://offladder.com/. Your CV can still tell a tech story while your next test explores something else.
Questions people ask
- Should I learn AI tools before applying?
- Learn them while doing real work; be ready to show where they helped and where you checked the result.
- What if I do not want to code anymore?
- Name what you did enjoy: prioritising, explaining, diagnosing, designing systems or working with customers. Search for roles built around that activity.
Directions you could test
Sources
- AI and Job Postings: From Destruction to Creation? 8 July 2026 · Indeed Hiring Lab
How this page is written
We only state what can be checked. Where a page makes a claim about work, automation or the labour market, it links to a primary source rather than paraphrasing a secondary summary. We do not publish predictions dressed as facts, invented statistics, or lists of AI-proof jobs. Pages are reviewed and dated when the argument or the underlying evidence changes. More about OffLadder.