I was recently laid off and am starting to panic about whether I can recover professionally. I have about five years of systems administration experience, solid networking knowledge, a CISSP, several other certifications, and a strong security background. I've worked with Linux and Windows, written small scripts for different projects, supported a wide range of tools and environments, and I'm currently studying for an AWS certification.
The job market makes me feel unqualified because many positions seem to expect deep expertise in cloud platforms, Terraform, programming, automation, and security all at once. I've used Terraform in labs but not professionally, and I wouldn't describe myself as a strong programmer. I'm especially interested in finding a role where I can build practical experience with cloud operations and infrastructure as code, though I'm still open to security-focused positions.
Should I pursue another certification, focus on building more projects, or simply keep applying? How can I present my existing experience more effectively and find a role that gives me room to grow?
2 Answers
Don’t dismiss your lab experience. It may not be the same as managing Terraform in production, but it shows initiative and gives you something concrete to discuss. Put your homelab and projects on your resume, especially if they demonstrate automation, repeatable deployments, documentation, backups, monitoring, or recovery.
Also, apply directly through company career pages when possible. Job boards can be useful for finding openings, but applications sometimes disappear there. The market can require a lot of persistence, so don’t interpret a low response rate as proof that you’re unqualified.
You’re probably much closer than you think. Five years of systems administration, security experience, networking, scripting, and a CISSP is a strong foundation. Job descriptions often describe an imaginary candidate who is an expert in cloud engineering, development, automation, and security all at once.
Rather than collecting more certifications indefinitely, choose a direction such as cloud operations, cloud security, IAM, security engineering, or infrastructure automation. Then create a couple of focused projects that demonstrate it: a small AWS environment managed with Terraform, sensible IAM policies, CloudTrail logging, security groups, and a simple Bash or Python automation script. Lab work counts if you can explain what you built, why you made those choices, and how you would improve it for production.
Keep applying, but tailor your resume toward results and responsibilities instead of just listing tools. If you match the core requirements of a position, apply even if you lack every item in the description. This sounds more like a confidence and positioning problem after a layoff than a lack-of-skill problem.
I’ve been second-guessing the security path because I’ve experienced some extremely stressful security incidents, and I’m not sure I want that kind of pressure long term. I think I’d prefer the operational side of cloud computing, although I’m still open to security roles. Your advice helped me calm down and refocus after the layoffs.