I completed my MCA in 2025 from a smaller college in Pune, Maharashtra. Before my master's, I worked for about a year in infrastructure support, and during the MCA I completed two DevOps internships. My long-term goal is to move into DevOps, but despite applying consistently since February, tailoring my resume, preparing for interviews, and building my skills, I have not been able to secure a full-time role yet.
My current technical skills include Linux, networking, AWS, Azure, Terraform, Docker, Kubernetes, Jenkins, GitHub Actions, Prometheus, and Grafana. I am considering either continuing to search for a DevOps position or returning to my previous employer in an infrastructure support role.
Would returning to infrastructure support make it significantly harder to transition into DevOps later? If I continue searching for several more months without success, how should I adjust my approach? I would also appreciate advice from anyone who moved from infrastructure support, Linux administration, cloud support, or NOC work into DevOps or SRE. What skills or experience helped you make that transition?
3 Answers
Going back to infrastructure support is not a bad choice. Linux administration, networking, troubleshooting, cloud support, and operating production systems are all useful foundations for DevOps. If you return, keep building automation in your day-to-day work, manage infrastructure with Terraform, improve monitoring, and create deployment projects outside work. It is usually better to gain relevant experience than to remain unemployed while waiting for the perfect title.
Your list is heavily focused on infrastructure and operations, but it does not show much of the development side of DevOps. Add at least one programming or scripting language, such as Python, Go, or strong Bash, and demonstrate that you can build automation and internal tools. Projects that show testing, deployment pipelines, APIs, and practical software delivery will make your profile stronger. Keep going, but make sure your resume shows more than a collection of tools.
Also apply for Linux administrator, cloud support, platform support, and junior SRE roles instead of limiting your search to jobs titled DevOps Engineer. Many people enter DevOps through operations and gradually take on CI/CD, infrastructure as code, scripting, observability, and release responsibilities. Learn the software development lifecycle as well, since DevOps involves supporting how applications are built, tested, released, and operated—not just managing servers and cloud services.
I have been applying for Linux and support roles too, although I have not had much success yet. I will broaden the search and make my projects show the full delivery process rather than only infrastructure setup.
That makes sense. I was worried that taking another infrastructure role would move me away from DevOps, but I can focus on automation and cloud responsibilities while continuing to prepare.