I'm a full-stack developer with nearly five years of experience building web and desktop applications, libraries, APIs, and installers. About two years ago, I started working with GitLab and GitHub pipelines, and I've continued learning ever since. I've also set up a local Jenkins server and built pipelines that build, test, and deploy both the frontend and backend of an application I'm developing. I'm currently learning Azure DevOps as well.
At my current company, I've tried to get more involved in DevOps while the team begins adopting these practices, but I keep getting pushed aside. I've been applying to junior, mid-level, and senior DevOps positions, usually sending out at least one application per day, but I'm not even receiving rejection emails. I'm wondering whether my résumé, despite being formatted for applicant-tracking systems, might be part of the problem.
How did you find your first DevOps job? Did you transition internally, use a particular type of job posting, build a portfolio, or rely on networking? I'd especially appreciate advice for moving from full-stack development into a role involving infrastructure, cloud platforms, automation, and CI/CD.
4 Answers
Networking and internal transfers are common paths into the field. People often start in development, support, systems administration, networking, or an internship, then take on progressively more automation and infrastructure work. Talk with infrastructure teams, ask to shadow them, and look for small tasks you can own rather than waiting for a perfect DevOps vacancy.
External referrals can help too, but they usually work best when your résumé clearly connects your existing experience to the target role. If direct DevOps positions are not responding, consider platform, cloud operations, or release-focused roles as an intermediate step. A temporary contract, internship, or lower-level position can also provide the missing production experience.
Build a small but polished demonstration project that you can explain in a couple of minutes. For example, use Terraform or another infrastructure-as-code tool to create cloud resources, deploy a containerized application, run tests through Jenkins or a hosted CI system, and include logging, monitoring, and basic security practices.
The point is not to use every popular tool. It’s to demonstrate that you understand how source code becomes a running, observable service. Make sure the project actually works, keep the documentation clear, and be ready to explain the design choices and trade-offs during interviews.
I’ve worked with Docker, Jenkins, Ansible, and several related tools already, so I’m planning to finish an independent project that combines them. My current employer has outsourced similar work, which makes it difficult to gain more hands-on experience internally.
A lot of people move into DevOps by gradually taking ownership of automation and infrastructure in their existing development or IT role. Volunteer to improve a deployment process, containerize an application, add monitoring, or build infrastructure from code. Once you have measurable results, your job title matters less because you can show what you actually delivered.
For your résumé, avoid applying indiscriminately to every level. DevOps roles vary wildly, so tailor each application to the actual requirements. Highlight outcomes such as faster deployments, fewer manual steps, improved test coverage, or more reliable releases instead of only listing tools.
That seems especially useful when the current employer does not have a formal DevOps position. Even small internal projects can become strong evidence if you document the problem, your solution, and the result.
DevOps is broader than CI/CD. Many employers also expect some combination of Linux administration, networking, cloud platforms, containers, virtual machines, databases, storage, security, monitoring, and troubleshooting. Your development background is valuable, but make sure your résumé also shows how you provision and operate the systems that run the software.
You may have better luck searching for titles such as cloud engineer, platform engineer, site reliability engineer, release engineer, infrastructure engineer, or DevSecOps engineer. Smaller companies may also advertise a general software or systems role that includes substantial automation work.
I initially applied to almost anything mentioning DevOps, even when I didn’t match the requirements closely. I’m starting to think that tailoring applications to roles where my experience genuinely fits would be more effective.
Several people I know moved over after starting in support or systems administration. They learned Linux, networking, monitoring, and deployment by taking on increasingly complex responsibilities, so there isn’t only one route from software development into DevOps.