2023 was the year IT learned what instability looked like. Mass layoffs in the first quarter. AI tools shipping faster than anyone expected. RTO mandates landing on teams that had built three years of productivity improvements at home. A company with 800 people in a boardroom crisis. By the time November rolled around, most IT professionals were exhausted just from keeping up with the news, let alone their actual jobs.

Now you’re heading into 2024, and if you haven’t thought about what you want your career to look like next year, this is the time. Not in January. Not when a crisis hits. Now, when you still have time to plan and prepare instead of react.

The good news: the skills that survived 2023 intact are the skills that are going to matter more in 2024. The bad news: you probably haven’t invested in those skills yet if you’ve been in survival mode for the past ten months. This is your checklist.

First, what actually worked in 2023

Before you plan forward, look back at what proved resilient.

Cloud skills made it through the layoffs. Companies were consolidating on-premise infrastructure and moving to AWS, Azure, or Google Cloud, and that trend didn’t stop in 2023. If you’re a cloud architect or a cloud operations engineer, you had job options even when the broader tech market was terrible.

Security specialization held value. Ransomware, compliance requirements, and breaches didn’t pause for economic difficulty. Companies still need security engineers, and they still pay well for them. The specializations that got hit hardest were the ones that felt discretionary, like pure AI research or emerging tech focus. But core security stayed strong.

AI operations didn’t emerge as its own specialty yet, but working knowledge of AI tools became practical. The people who’re thriving in late 2023 are the ones who figured out how to use GPT-4, Claude, or specialized tools in their workflow. Not as a niche skill, but as a baseline expectation.

Infrastructure automation held up. Terraform, Ansible, CloudFormation; any engineer who could write infrastructure as code had options. These skills are accelerating, not slowing down.

Anything labeled “full-stack” without deep specialization got crushed. “Senior engineer” without a focus area is less valuable than “senior engineer who can architect a Kubernetes cluster” or “senior engineer who runs compliance programs.” Breadth alone doesn’t protect you anymore.

What didn’t work: generalist positions without specialization, individual contributor roles without leadership potential, and careers built on one company or one technology.

What skills matter most in 2024

Cloud architecture and cloud operations remain table stakes. Not “I’ve used AWS,” but “I can design a three-tier architecture on AWS with auto-scaling, load balancing, and disaster recovery.” This is becoming a senior engineer baseline, not an advanced specialization.

Infrastructure as code and CI/CD pipelines are merging into a single skill set. You should be able to write your infrastructure in Terraform and then build the pipeline that deploys it safely. That’s one job, not two.

Security specializations are getting more specific. “Senior security engineer” is a job title. “Senior security engineer who specializes in cloud infrastructure security” or “in application security” or “in compliance automation” is a career path. The specialists make more and have more stability.

AI literacy and prompt engineering. Not machine learning. Not AI research. But the ability to integrate AI tools into your workflow, use them safely, and explain what they’re good for and what they’re not. This is becoming mandatory for most IT roles.

Data platform engineering is emerging as its own specialty. Companies are drowning in data and they need engineers who can build the systems that collect, process, and make it queryable. If you move into this space, you’re positioning for 2024 and beyond.

Soft skills, documented. Communication, documentation, and cross-team collaboration matter more than ever. The difference between a good engineer and a great engineer in 2024 is that the great engineer can explain their decisions and work with people outside their discipline. Document this in your work. Show examples in interviews.

Certifications to consider in 2024

Cloud certifications are still the safe bet. AWS Solutions Architect Associate, Azure Administrator, Google Cloud Associate Cloud Engineer. These certifications tell a story and they’re marketable. The companies you interview with recognize them, and they’re worth something in salary negotiations.

If you’re in security, the field-specific certifications hold up better than general ones. CISSP is worth the investment if you’re senior enough. For people earlier in career, CCSK (Cloud Security) or CEH (Certified Ethical Hacker) are more approachable and still marketable. Avoid certifications that are pure vendor marketing with no practical content.

If you’re considering a career shift in 2024, certifications can help. If you want to move from general infrastructure into security, a six-month CCSK program followed by some hands-on security work looks better to employers than just announcing your interest. If you want to move into cloud specifically, AWS Solutions Architect or Azure Administrator tells a story to hiring managers.

Skip certifications that don’t map to jobs you actually want. The world doesn’t need another ITIL certification. It needs cloud engineers, security specialists, and automation experts.

By end of 2023, the market has settled a bit. Salaries have come down from the Great Resignation peaks, but they haven’t collapsed to pre-2020 levels either. A senior engineer in a major metro area should expect 160K to 190K depending on specialty. A security specialist 170K to 210K. Individual contributors with deep specialization in cloud or infrastructure are still getting offers in the 180K to 220K range.

Those numbers vary by location, company size, and specialization. Use Levels.fyi, Blind, and Salary.com to get a realistic picture of what people in your exact position are making. Don’t benchmark against “senior engineer” in the aggregate. Benchmark against “senior engineer, cloud infrastructure, San Francisco” or whatever your actual profile is.

Once you know your market value, you have two real decisions: negotiate at your current company or test the market with a search.

Negotiate if: you like your team, you trust your manager, the work is interesting, and you’re underpaid relative to market. A three-month window where you’re clear about what you want (“I want to get to 175K by end of Q1”) gives your company a chance to keep you. Most will try if you’re good and they know the market rate.

Search if: you’ve been asking for higher pay and not moving, your company is in financial trouble, or you don’t trust the leadership. 2024 is a better hiring market than 2023 was, but it’s still a buyer’s market. You’ll have negotiating power if you’re specialized, but you should expect the process to take two to three months and multiple rounds.

The worst decision is staying silent and resentful, thinking you’re stuck. You’re not. You have options. You just have to take them seriously and act on them.

Building a professional development plan

Your company might have a career development program. Most probably don’t, or what they have is vague. Build your own instead. It takes two hours and it changes how you approach the year.

Document three things: where you want your career to go (not just “get promoted,” but what kind of work you want to be doing), what skills you need to get there, and what milestones matter between now and next December.

“I want to move from general infrastructure engineering to cloud infrastructure specialization. I need to get AWS Solutions Architect certification, lead at least one major cloud migration project, and demonstrate that I can design for scale. By end of Q1 I’ll pass the AWS exam. By end of Q2 I’ll be assigned to the cloud team. By end of Q3 I’ll own the design for our major migration. By end of Q4 I’ll have concrete examples to show in interviews at companies I’m actually interested in working for.”

That’s not vague. That’s a plan you can actually execute and measure.

If your company doesn’t support your plan, you execute it anyway. Cloud certifications don’t require your employer’s permission. Side projects that demonstrate your skills don’t require their approval. You’re responsible for your own development. Your employer can help, but they shouldn’t be the blocker.

Networking and relationship maintenance

The people who get hurt most in downturns are the ones who only reach out to their network when they need something. You probably spent 2023 in heads-down mode, shipping work, staying under the radar. In 2024, rebuild your network.

This doesn’t mean coffee meetings with every person you ever worked with. It means quarterly check-ins with the people you actually want to work with or learn from. You set a calendar reminder. You reach out. You say something like, “Hey, it’s been six months. I was thinking about that project you were working on and wanted to see how it turned out.” You listen to what they’re doing. You offer something useful if you can. You stay in touch.

By the time you need to job search, your network isn’t cold. You already know who’s hiring, what companies are doing interesting work, and who might be a good fit for a role.

Financial runway and market uncertainty

2024 will probably not be a disaster, but it also probably won’t be a roaring tech boom. Plan for continued uncertainty. If you don’t have an emergency fund that covers three months of expenses, build one. That’s not paranoia, it’s just acknowledging that tech layoffs happened in 2023 and could happen again in 2024.

You don’t need six months. Three months is realistic and achievable. That fund doesn’t mean you’re planning to lose your job. It means if your company has trouble or your role gets eliminated, you can make good decisions about your next move instead of desperate ones.

Practical monthly framework instead of vague goals

January through March: Complete any certifications you’re going to do in the first quarter. Take the exam, pass it, document it. Get one major project done that demonstrates a skill you want to build. This is your proof of work.

April through June: Shift to visibility. Present your work to a broader audience. Write about a technical decision you made. Present at an internal tech talk. This is when you’re building your professional narrative.

July through September: Accelerate specialization. You should know by July whether you’re going deeper into your current specialty or making a shift. If you’re shifting, the fall is when you do it. If you’re deepening, you’re taking on bigger scope.

October through December: Network and plan for next year. Do the planning exercise for 2025. Have conversations with people who can help you get where you want to go. Update your resume. Test the market if you’re thinking about moving.

This is a different pace than “set vague goals in January and check them in December.” It’s seasonal and it’s practical.

The actual strategic question

The thing nobody talks about is that in 2024, your career is increasingly something you’re managing as a small business owner manages a business, not something you’re entrusting to an employer. You’re making strategic decisions about what skills to build, what networks to maintain, what opportunities to pursue. Your employer is just the current client for your time and skills.

That mindset shift changes everything. You’re not asking, “Will my company invest in my development?” You’re asking, “How am I going to develop myself, and will this company support it?” You’re not asking, “Will my company give me a raise?” You’re asking, “Am I being compensated fairly for my market value, and if not, what am I going to do about it?”

It’s more work to think about your career this way. It’s also more stable, because you’re not dependent on your employer making good decisions about you. You’re dependent on yourself.

That’s the foundation for building resilience in a market that’s not going to be stable and for positioning yourself for the opportunities that are actually available.

Plan now. The people who’ll be in the strongest position a year from now are the ones who started planning in December, when they still had time to think clearly.