I'm a full-stack developer with nearly five years of experience building web and desktop applications, libraries, APIs, installers, and other software. About two years ago, I started working with GitLab and GitHub pipelines and became increasingly interested in DevOps. Since then, I've set up a local Jenkins server and built working pipelines that build, test, and deploy both the backend and frontend of an application I'm developing. I'm also learning Azure DevOps and have used tools such as Docker and Ansible.
I've been applying to junior, mid-level, and senior DevOps positions, usually sending out at least one application a day, but I'm rarely getting even a rejection email. I'm wondering whether my résumé, despite being formatted for applicant tracking systems, is part of the problem. My current employer is beginning to adopt more DevOps practices, but I haven't been given meaningful opportunities to participate, so I'm considering moving to another company.
How did you get your first DevOps or cloud engineering role? Did you transition internally, build a portfolio, apply for a related position, or use a different strategy?
5 Answers
Make sure you’re not treating CI/CD as the entire DevOps role. Many companies also expect experience with cloud infrastructure, networking, security, databases, storage, virtual machines, containers, and infrastructure automation. Read each job description carefully and tailor your résumé to the requirements instead of applying to every level indiscriminately. Applying for senior positions without corresponding production experience can also make your application look unfocused.
Internal transitions are extremely common. People start in development, support, system administration, networking, or operations and gradually take ownership of automation and infrastructure. Volunteer for deployments, monitoring, incident fixes, and environment setup whenever possible. If your current company blocks that path, related roles such as cloud support, platform engineering, systems administration, or operations internships can be a practical entry point.
There’s also a networking and timing element. Some people get their first opportunity because a manager or colleague knows their work, while others apply to dozens or even hundreds of positions before getting a break. Consider contacting hiring managers professionally, asking former colleagues for referrals, and applying to smaller companies where you can own more of the environment. Your résumé should emphasize outcomes—faster deployments, fewer manual steps, improved reliability—not just a list of tools.
A lot of people move into DevOps by expanding their existing role instead of getting hired directly as a DevOps engineer. Look for opportunities involving Linux, networking, deployments, monitoring, infrastructure, or automation, even if the title is developer, systems engineer, or platform engineer. Once you’ve solved real operational problems, the transition becomes much easier to explain on your résumé.
The most reliable route is often to create a small but complete demonstration project. For example, use Terraform or another infrastructure-as-code tool to create an environment, package an application with Docker, run tests in a CI pipeline, deploy it to a cloud service, and include logging or monitoring. Keep the project simple enough to demonstrate in a couple of minutes, and make sure it actually works before showing it to recruiters or interviewers.
I’ve already worked with Docker, Jenkins, Ansible, and several related tools. I’m planning to finish an independent application where I can connect everything together and demonstrate the result. My current employer has chosen to outsource this work, so a personal project may be the best way to show what I can do.