I'm moving into a DevOps role next month after about five years in infrastructure and systems administration. My background includes VMware and vSphere, Windows and Linux administration, networking and troubleshooting, NetApp storage, PowerShell automation, monitoring, backups, and general infrastructure operations. I've also had some beginner-level exposure to Docker, Kubernetes, Git, GitLab, Argo CD, Ansible, and Terraform through labs and small projects, but I'm not yet highly experienced with those tools. I'd like to use the next month to prepare effectively. For anyone who has made a similar move from infrastructure or sysadmin work into DevOps, what should I prioritize first? I'm especially interested in practical courses, video playlists, or a structured learning path that focuses on skills I'm likely to use on the job.
5 Answers
You already have a stronger foundation than many people starting in DevOps. Rather than trying to learn every tool, use a broad DevOps roadmap to identify the major areas, then work backward from the skills your new role actually requires. Your infrastructure, troubleshooting, automation, and systems experience will transfer well.
Talk to your new team before choosing courses. DevOps varies a lot between organizations, and the tools and processes can be completely different. Find out what they use for source control, infrastructure as code, containers, orchestration, and especially CI/CD. Learning the pipeline platform your team relies on will probably give you the quickest practical benefit.
Your existing background is also a natural fit for reliability-focused work. Don’t worry if the role turns out to involve more SRE or platform operations than application development; the systems, networking, automation, and troubleshooting experience you already have is highly relevant. Use the first few weeks to learn the team’s stack and gradually build the developer-facing skills around it.
Build one small project from start to finish instead of taking separate introductory courses for every tool. For example, create an application environment with Terraform, package a simple service with Docker, deploy it to Kubernetes or another container platform, add a Git-based CI/CD pipeline, and include logging and monitoring. An end-to-end project will show how the pieces fit together and expose the gaps worth studying.
Don’t focus only on tools—learn how the development team works. Understanding the software delivery lifecycle, how developers build and test applications, and where deployments tend to get stuck will help you apply your infrastructure skills to higher-impact problems. DevOps is as much about improving collaboration and delivery as it is about operating technology.
Exactly. Tooling changes frequently, so reaching out early is useful both for preparation and for showing that you’re proactive. Ask for internal documentation, examples of existing pipelines, and the team’s preferred way of deploying and monitoring services.