There’s a type of professional paranoia that’s completely reasonable, and we should talk about it. It’s not the kind where you’re constantly scanning for threats that don’t exist. It’s the kind where you maintain your parachute long before the engine sputters, and you don’t apologize for it.

The tech industry in early 2023 has taught millions of workers an uncomfortable lesson: the job you have today might not exist tomorrow, regardless of how well you’re performing. That’s not pessimism. That’s just market reality. The response isn’t to live in constant fear; it’s to maintain the professional equivalent of an emergency fund, and to do it as routine maintenance, not crisis response.

Keep Your Resume Current at All Times

Most people wait until they’re job hunting to update their resume, which is like waiting until your house is on fire to figure out where the exits are. That’s backwards.

Set a calendar reminder for the last Friday of each month and spend fifteen minutes updating your resume. What did you accomplish this month? Did you resolve a major incident? Did you implement a new monitoring system? Did you document something that hadn’t been documented before? Did you train someone on a critical process? Write it down.

The resume that served you well six months ago is now behind you. You’ve learned more, shipped more, fixed more. Your resume should reflect that trajectory. When you need to move quickly, you’re not trying to remember what you did in November while you’re sitting in a severance conversation; you’re just pulling from a running record that you’ve maintained all along.

This also has an immediate benefit: it clarifies what you’re actually contributing. Many IT professionals underestimate their own value because they’re focused on keeping the lights on, not on documenting the value of the lights staying on. Monthly resume reviews fix that.

Document Your Accomplishments, Not Just Your Tasks

There’s a difference between “managed Active Directory” and “redesigned our Active Directory governance model to reduce provisioning time by 60 percent and cut certification overhead by four FTEs worth of work annually.” The second one tells a story. The first one sounds like everyone else.

For each major accomplishment on your resume, know the story behind it. What problem were you solving? What made it hard? What did you actually change? What’s the measurable outcome? You don’t need to put all of that in your resume, but you need to know it before you walk into an interview or a severance meeting.

This is especially important if you’re in infrastructure or security work. Your job is often invisible when it’s working correctly. When systems are running smoothly and there are no breaches and uptime is 99.99 percent, it looks like you’re just… present. That invisibility is actually your biggest asset if you’re documenting it right. You’re responsible for the fact that nothing terrible happened. That’s quantifiably valuable.

Build and Maintain Your Reference Network

References are trust made portable. When you move to the next role, you need people who can explain to strangers why you’re competent and trustworthy. The best time to build that network is when you’re not desperate.

This doesn’t mean being artificial about it. It means being intentional. When you work with a senior engineer on a complex project, when you help someone through a crisis, when you mentor someone into growing, those relationships matter. Maintain them. Stay in touch. Comment on their LinkedIn posts occasionally. Grab coffee or video calls with people you respect.

If you’re genuinely concerned about layoffs at your company, a quiet conversation with trusted colleagues about staying in touch is completely normal. You don’t need to make it dramatic. “Hey, I’m just being proactive about my network. Can I grab you for coffee sometime this month?” Most people get it. Most people do the same thing.

When you’re interviewing or negotiating severance, you want references who can speak to your work directly and with specificity. That takes time to build. Don’t wait until you need it.

Build a Financial Cushion

This is unsexy advice, but it’s the most pragmatic thing on this list. You need three to six months of expenses in savings. This is doubly true if you work in tech, where layoffs happen in waves, not as isolated incidents.

Three months is the bare minimum; it’s enough to cover standard unemployment benefits in most states while you’re job hunting. Six months gives you breathing room to be selective, to negotiate properly, to not take a bad role just because you’re panicking about money.

If you have a mortgage or dependents, six months is closer to the baseline. This isn’t about being risk-averse; it’s about being able to make good decisions when circumstances change. The person with three months of savings can negotiate a salary increase. The person with no savings accepts the first offer and regrets it for three years.

Start now. Set up automatic transfers to a separate savings account. If you get a bonus or a tax refund, don’t spend it; add it to the fund. Treat it as part of your compensation package that you’ve decided not to spend yet.

Keep Your Certifications and Skills Visible

Your LinkedIn profile should be updated when your resume is updated. If you’ve completed a certification, add it. If you’ve learned a new tool or technology, mention it. If you’ve given a talk, written something, or contributed to an open source project, those belong in your professional profile too.

The point isn’t to brag or to play the LinkedIn game obnoxiously. It’s to make sure that when someone’s hiring manager runs a search for “people who understand Kubernetes in my network,” you show up. When a recruiter is looking for someone with your background, they should be able to find you quickly.

This is how passive job opportunities work. You’re not actively hunting; someone comes to you because your profile indicates you have exactly what they need. That only happens if your profile is current.

Gather Your Work Samples, Legally

You need a “go bag” of work samples that don’t violate intellectual property or confidentiality agreements. If you’ve written documentation, designed a system diagram, solved a thorny problem, or improved a process, you should have anonymized versions of that work that you can show.

The key word is anonymized. Don’t take proprietary code, internal designs, or anything with your company’s branding or specific details. But do take concepts. A well-documented runbook (with company names stripped) shows you can document. A system architecture diagram (with specific technology redacted) shows you understand infrastructure. Samples of your own work, your own writing, your own thinking, cleared of proprietary content.

When you’re interviewing, concrete examples of your thinking are worth more than abstract claims about what you can do. “I’ve reduced operational overhead” is a claim. Showing someone a process you designed that reduces overhead by 40 percent is evidence.

Understand Your Company’s Severance Policy

Do you know what your company would legally be obligated to offer if they laid you off? Most people don’t. Read your employee handbook or your benefits documentation. Some companies have severance policies printed explicitly; others don’t.

If there’s no explicit policy, that’s information too. It means your company is going to negotiate severance on the spot, which means you need to know what you’re entitled to under labor law in your state.

Understand whether you’re vested in any retirement benefits. Understand whether stock options have any remaining vesting schedule. Know what happens to your accrued PTO, because that varies significantly by state and company. This isn’t about being mercenary; it’s about not being surprised by the financial implications when the moment comes.

Know Your State’s Unemployment System

Unemployment insurance is a state-level benefit, and the rules are dramatically different depending on where you live and where you work. California’s benefits are more generous than some other states. Some states are faster at processing claims. Some have specific rules about severance that affect your eligibility.

Spend an hour exploring your state’s unemployment website. Download the guide. Understand how much you’re eligible for, what the claim process looks like, and how long it usually takes to receive benefits. If you’re laid off, you need to file immediately. If you’re already familiar with the system, you can move faster.

Frame It as Hygiene, Not Paranoia

Here’s the key reframing: this isn’t about being paranoid or fatalistic. This is about basic professional hygiene. You brush your teeth regularly even though most of the time you don’t have a cavity. You maintain your car even when it’s running fine. You don’t wait until disaster strikes to maintain things that matter.

Your career matters. Your financial stability matters. The fact that your company is stable today doesn’t mean it will be in six months, and that’s not a reflection on you. It’s just the nature of the industry we work in. Prepare accordingly.

The people who sleep well during industry upheaval aren’t the ones in denial about what might happen; they’re the ones who’ve already done the work to be prepared for it. They have current resumes, documented accomplishments, strong references, months of savings, updated LinkedIn profiles, and clear understanding of what happens next if things change.

That’s not paranoia. That’s professionalism.

Related reading: For deeper context on career resilience through economic cycles, see The Great Resignation: Why July 2021 Is Your Moment to Negotiate, and understand how to evaluate your worth in a competitive market with Salary Benchmarking in a Hyper-Competitive Market: Know Your Worth.