I'm trying to understand how experience carries over during an IT career, especially in a difficult job market. My long-term goal is cybersecurity engineering, and I'm considering a path like two years in IT support, two years in system administration, and then two years in security engineering. That would give me six total years in IT, but only two years directly in security engineering.
If I were laid off during a competitive market and security engineering roles required three to five years of specialized experience, would my support and systems experience still help me compete, or would I be viewed as underqualified? I'm also wondering about using system administration as a backup. With only two years in that area, would I still be competitive for roles asking for three to five years, or could I end up having to return to entry-level support?
For people who have experienced layoffs or career transitions, how much value does previous IT work retain as you move toward more specialized roles? Can related experience, skills, projects, and accomplishments make up for not meeting the exact number of years listed in a job posting?
4 Answers
Experience in support, systems, and security is highly connected. A systems administrator may already be responsible for identity, access control, patching, logging, backups, and incident response, so that work can count as security-related experience when you describe it accurately. Job postings often list an ideal number of years rather than an absolute cutoff. Your actual responsibilities and the results you achieved usually matter more than simply adding up years.
There isn’t a fixed, perfectly linear career ladder. Employers may care about the depth of your work, tools you’ve used, judgment, communication, and whether people trust you with more responsibility. Build skills that transfer across roles—networking, operating systems, scripting, cloud platforms, identity, PKI, and incident handling. A home lab or meaningful projects can also demonstrate ability when your job history is short in a particular specialty.
In a weak job market, competition gets tougher and some companies will be very literal about their requirements. Still, related experience can keep you from starting over. Tailor your resume to emphasize security tasks from previous roles, quantify improvements, and be ready to explain how your background applies to the target position. Strong interviewing and professional relationships can matter just as much as the number of years on paper.
Connections are especially useful during layoffs. Former coworkers, managers, mentors, and clients may know your capabilities and can help you find opportunities when applications are heavily filtered.
A title and a year count don’t tell the whole story. Two years in a demanding environment can provide more experience than five years doing a narrow set of repetitive tasks. Try to keep expanding your scope rather than chasing a specific number: automate work, troubleshoot difficult issues, participate in projects, and learn how the business uses technology. That broader experience gives you more options if you need to change roles.
The exact overlap depends on the organization. In some companies, the systems administrator is also the person handling most of the practical security work, so documenting those responsibilities is important.