I have around 15 years of experience building applications with Spring and Java, and I'm considering moving into a dedicated DevOps or cloud engineering role with a focus on Google Cloud. Has anyone made a similar transition? I'd like to know whether it's a worthwhile move, what skills transfer well, and whether specializing in GCP could limit my opportunities compared with AWS or Azure.
4 Answers
I’d think carefully about what you want from the change. Development roles may offer better opportunities in some markets, while DevOps can involve more on-call work, operational pressure, and responsibility for production incidents. On the other hand, cloud engineering can be a good path if you enjoy automation, infrastructure, reliability, and working across many teams.
Your existing experience is a strong foundation. Fifteen years with Spring and Java likely means you already understand distributed systems, service dependencies, scalability, and failure modes better than someone starting DevOps from scratch. Kubernetes concepts also transfer between platforms, so experience with GKE can later help you work with EKS or other managed Kubernetes services.
The transition can make sense, but don’t focus too narrowly on GCP at first. There are generally more AWS and Azure openings, while GCP roles are concentrated in companies already using Google’s ecosystem, especially for data and machine-learning workloads. Once you understand the core cloud concepts, containers, networking, IAM, CI/CD, and infrastructure as code, moving between providers is much easier.
I made a similar move, and my background with microservices helped a lot. The infrastructure work felt familiar because I already understood distributed systems, deployments, and how services fail. You’ll probably spend less time writing application logic and more time dealing with logs, automation, reliability, and operational issues. If you have a team or manager willing to let you gain hands-on experience, I’d definitely consider trying it.
One advantage of DevOps is that organizations are still cautious about handing critical infrastructure entirely to automation tools. That responsibility can make the work valuable, although it also means the role may carry more operational stress.