The new year opened with a grim headline that we’ve now learned to expect with eerie regularity: 34,000 tech workers lost their jobs in January 2024 alone. Google, Amazon, Discord, Twitch, Pixar. The names blur together after the first dozen rounds. But here’s what matters more than the headline: we’re no longer in “downturn” territory. We’re in the new normal. The layoff cycle has become structural rather than cyclical, and if you’re in tech, you need to operate as though your next pink slip could arrive any quarter for the next two years, minimum.

This isn’t pessimism. It’s realism. And realism is what keeps you employed when everyone else is panic-updating their LinkedIn profile.

The calculus has fundamentally changed from what worked in 2022. Back then, you could ride out the churn on deep specialization. You could be the Kubernetes wizard or the Salesforce configuration expert, and that scarcity would protect you. In 2024, that same deep specialization is sometimes what puts a target on your back. Specialized roles are the first to get consolidated when budgets tighten, because specialized roles mean specialized salaries and specialized headcount. The company discovers it can limp along without that expert, and suddenly you’re on the list.

This is where most tech workers get it wrong. They respond to layoff anxiety by either burrowing deeper into their specialty, hoping scarcity will save them, or they do the opposite: panic-spray credentials and certs across every area they can think of. Both approaches fail under sustained pressure.

What actually works requires thinking about yourself differently than you probably do now.

Employability Is Not About Your Resume

Your resume is a hygiene factor. It matters if it’s poorly written or full of typos. It matters if it’s obviously out of date. But employability in a rolling-layoff economy is about something else entirely: it’s about being the person who’s hard to let go of because you’re woven into too many places in the organization.

This means building what I call “portable structural value.” You want to be known not just as the person who does X skill really well, but as the person who also serves as a critical link between teams, who makes other people’s jobs easier, who solves problems that aren’t technically in your job description but matter to the business.

Here’s a concrete example: if you’re a network engineer, your base value is designing and maintaining networks. That’s replaceable, especially if your company consolidates operations. But if you’re also the person who knows the history of all the weird legacy decisions in the infrastructure, who can troubleshoot anomalies no one else understands, and who has built relationships with the teams that depend on your network, that’s substantially harder to remove. When the company tries to cut 5% of engineering, they’ll think twice about losing you because your knowledge isn’t just technical; it’s structural.

This applies across disciplines. If you’re in DevOps, you’re infinitely more valuable if you also understand the business logic of the systems you’re deploying and can communicate effectively with the teams using those systems. If you’re in security, you’re harder to justify cutting if you’ve built a reputation for actually enabling people to do their jobs safely, rather than just saying no.

The mechanism is simple: become the person whose absence creates immediate, obvious pain. Not through indispensability theater, but through legitimate usefulness across multiple problem domains.

Skills Diversification That Actually Matters

The instinct to diversify skills is right. The execution usually isn’t. Most people interpret “diversify” as “learn adjacent technologies,” so they add a programming language, a new cloud platform, a certification. This is the spray-and-pray approach, and it reads as resume stuffing. Hiring managers notice this, and it actually works against you because it makes you look unfocused.

What you actually want is one level of strategic broadness combined with operational depth. For example, if you’re a Linux systems administrator, your core specialism stays. But instead of learning “also Windows” and “also Kubernetes” and “also Go programming,” you might deepen in cloud infrastructure (AWS, Azure, GCP; pick one deeply and know it well) and pair that with either strong observability skills or strong security fundamentals. You become “the Linux/cloud systems person with serious security chops” rather than “the person who knows a little about everything.”

This works because it makes you legible. You have a clear story about what you do. You’re not the Swiss Army knife; you’re the screwdriver that works in the most critical areas of the house. And that story is the difference between being kept and being cut.

For anyone worried about technical obsolescence or industry shifts, the answer is the same. Rather than trying to stay current in twenty different technologies, pick the three to four areas that are actually moving your field forward and commit to real depth. In security, that might be cloud-native security, applied threat modeling, and incident response. In infrastructure, it might be platform engineering, observability, and chaos engineering. It depends on your domain, but the principle is identical: breadth within your domain, and one or two adjacent skill areas you actually own.

The time investment is reasonable because you’re not trying to be expert-level in everything. You’re trying to be legitimately knowledgeable in your domain and competent in adjacent areas that multiply your value.

Internal Visibility Is Your Best Insurance

Here’s something I learned watching a dozen layoff cycles: most people who survive aren’t the most talented. They’re the people whose absence would immediately be felt by leadership. Not by other engineers, necessarily; by people writing the checks.

This doesn’t mean bootlicking. It means ensuring that your work is visible to the people making decisions about layoffs. This is uncomfortable for a lot of us who were trained to let our code speak for itself, but that era is functionally over. Your code can be perfect, and if the people making cuts don’t know what you do, you can still be on the list.

Visibility means a few specific things. It means your manager knows what you’re working on and can articulate your value without prompting. It means you’ve shipped something that touched a major business metric or prevented a disaster that the broader organization is aware of. It means you’re in at least one meeting where non-technical leadership can see you contributing meaningfully to conversations about the business, not just the engineering.

This is where internal visibility differs from self-promotion. You’re not out there bragging. You’re just making sure your actual work product is known. Brown bag lunches, quarterly all-hands demos, cross-team collaborations, incident post-mortems where you present lessons learned. These are the mechanisms.

When layoff decisions come down, they often come down quickly. Your hiring manager might advocate for you, but if leadership doesn’t know you, that advocacy only goes so far. You want to be in the category of person where someone in the room says “wait, we can’t lose them” before anyone has to think hard about it.

Build a Professional Reputation That Isn’t Attached to Your Employer

This is the long game, and it’s the reason specialization versus generalism remains so relevant to your career trajectory. Your reputation inside your company is valuable only as long as you work there. Your reputation in your industry, or in an online community, or in public documentation you’ve contributed to, travels with you.

This doesn’t require you to become a conference speaker or YouTube personality. It means contributing meaningfully to open source projects in your domain, writing about problems you’ve solved, engaging substantively in professional communities online, maybe mentoring a person or two outside your company. It means when you eventually do have to find a new job, there’s a trail of evidence that you know what you’re talking about.

The secondary benefit is that this kind of public work often leads to opportunities that aren’t posted on a job board. People reach out. You hear about companies before they’re public with a hiring need. That’s worth more than almost anything else you can do with your professional time.

For people in security or data protection specifically, this is even more critical. There’s such a shortage of real practitioners in these fields that public reputation often becomes your ticket past the automated resume screening.

The Portable Survival Kit

The other dimension of employability is practical: having your layoff survival kit ready isn’t paranoia anymore. It’s logistics. This means up-to-date portfolio work you can share, references you’ve actually talked to recently, a version of your resume you could update in an evening, and if at all possible, some runway of savings. Not everyone can manage the savings part, and that’s real. But the documentation side is free and takes a weekend.

It also means knowing the market. You should spend an hour every quarter looking at job postings in your field, not to panic, but to understand what hiring looks like, what’s actually scarce, what salary ranges are real. This keeps you from getting blindsided.

And it means updating your mental model of your own value regularly. You’re probably more employable than you think, and probably in directions you haven’t considered. Sit down every six months and ask: what have I shipped that matters? Who would miss me if I left tomorrow? What could I explain clearly to a hiring manager that would make them want to talk to me? These aren’t ego questions. They’re calibration questions.

The layoff cycle isn’t ending soon. But your employment doesn’t have to be a casualty of it. Stay woven into your organization, stay visible, stay diverse in the ways that matter, and keep your professional reputation portable. That’s not a guarantee. But it’s the closest thing to one that exists right now.