I've been with the same employer for almost eight years and lately I'm worried I've become too comfortable. With a merger recently announced, I'm concerned my position could eventually disappear, so I'm thinking about bootcamps, certifications, and learning new skills quickly. For those working in IT, how do you decide what to learn and keep your knowledge current without trying to chase every new technology?
4 Answers
After many years at one company, it’s worth exploring the job market instead of assuming classes are the only way forward. A new role can expose you to different systems, processes, and responsibilities while often improving your pay. Before spending heavily on training, compare the skills employers are requesting and see whether your existing experience can transfer into a stronger position.
Don’t try to chase every trend. The fundamentals—networking, DNS, operating systems, security concepts, abstraction layers, and models like OSI—change much more slowly than the tools built on top of them. Once those basics are solid, learning a new platform is mostly figuring out where it fits and how it differs from what you already know. Focus on being able to understand and apply concepts, not memorizing every product.
IT has always changed quickly. The most useful skill is being able to learn what a situation requires, apply it safely, and understand why it works. You don’t need to pretend you know everything before starting.
You don’t necessarily need to study constantly outside work. I manage technology for a few hundred users and contribute to AI-related projects, but I deliberately disconnect when I’m home. Trying to consume every new development is a fast route to burnout. Stay engaged at work, volunteer for unfamiliar projects when possible, and choose a sustainable learning routine rather than treating your career like an emergency.
I’d avoid most bootcamps unless you’ve researched a specific one carefully. Look at job postings for the roles you actually want, choose one or two recurring skill areas, and build something practical with them. Cloud, automation, identity, and security are reasonable directions, while certifications can provide structure and help get past hiring filters. A small lab or project is usually more valuable than collecting certificates without hands-on experience.
That makes sense. I already have experience with Microsoft 365, hybrid Exchange, Citrix, Active Directory, DNS, certificate services, vulnerability remediation, patching, PowerShell, and deployment work. I’m trying to figure out which direction would make the most sense next.
The merger makes the timing especially important. Whether your company is acquiring or being acquired can change the risks and opportunities, so I’d quietly update your résumé, document your accomplishments, and start researching options before anything is formally announced.