How to cold email for a DevOps or cloud engineer job

The titles differ (DevOps engineer, cloud engineer, site reliability engineer, platform engineer), but most posts ask for:

• Linux, the shell and networking basics: DNS, ports, load balancers, and why one service can’t reach another.
• A cloud, usually AWS, then Azure or Google Cloud: compute, storage, networks (VPCs) and permissions (IAM).
• Containers with Docker, and often Kubernetes to run them.
• CI/CD: GitHub Actions, GitLab CI or Jenkins, building and deploying on every change.
• Infrastructure as code, mostly Terraform, sometimes Ansible for configuring servers.
• Monitoring and logs: Prometheus and Grafana, the ELK stack or a cloud’s own tools, and being on call for alerts.
• Scripting in Bash or Python, and for SRE roles, more programming than that.

As a fresher, show a system that runs, not a course you finished:

• A project you deploy yourself: an app in containers, built and shipped by a pipeline on every push, on a cloud account set up with Terraform. Put the code and a short write-up on GitHub.
• An internship where you automated a deployment, wrote a pipeline or set up monitoring someone relied on.
• Something you run for other people: a college club’s website, a fest’s registration server, a home lab. Say what you did when it went down.
• A cloud certification, as your second line: it shows effort, but the project shows the skill.

Tear down what you don’t use. A free-tier bill you forgot about is a poor story, and a public repository with your keys in it is worse.

Coming from system administration, IT support, networking, testing or development? Much of DevOps is work you already do, automated. Lead with that:

• From system administration or IT support: the servers you manage, the patching or backups you scripted, a move to the cloud you worked on.
• From networking: the network you run, and what you now configure with code or scripts.
• From testing: the test suite you wired into a CI pipeline, and how releases changed after it.
• From development: the Dockerfile, pipeline or deployment you set up for your team, and any on-call work you have done.

Name the scale plainly: servers, services, deploys a week. Small and true reads better than big and vague.

Sentence one: what you run or deploy, on which cloud, with which tools. Sentence two: the problem you solved and what changed (fewer failed deploys, faster releases, an alert that now catches something).

Both are made-up examples. The numbers in yours must be your own, and ones you can explain in an interview.

Nikhil, who leads infrastructure at a SaaS startup, posts for a DevOps engineer, 1 to 3 years, AWS, Kubernetes and Terraform, and asks for resumes by email. Faizan has three years as a Linux system administrator. This is the whole email.

What makes it work:

• The three tools the post names are inside the proof, in the order the work used them.
• It shows a change in how the team works (weekend releases became weekday ones), not just tools installed.
• Years as a system administrator are presented as the base of DevOps work, which they are.
• The code is a smaller copy of his own, so nothing of his employer’s is shared.

The role title as the post writes it, the cloud and one or two tools it names, your name and your stage.

• DevOps Engineer (AWS, Kubernetes): Faizan Ahmed, 3 years in Linux administration
• Cloud Engineer Intern: Aditi Joshi, B.Tech 2027, AWS and Terraform
• Site Reliability Engineer: Varun Pillai, 2 years in backend, on call

Avoid subjects like “Job application” or “Resume”. The person who posted may have several openings, and the role first tells them which one.

• A list of certifications as the email. Two lines about a system you run say more than five badges.
• Every cloud-native tool you have heard of on your resume. Name what the post uses and show it working.
• A project that only runs on your laptop. A deployed link, a pipeline run or a write-up shows it runs.
• Access keys, passwords or an employer’s server names in a public repository. Reviewers look, and it ends the conversation.
• Calling a one-click deploy on a hosting platform a DevOps project. Show the parts you set up yourself.
• Leaving out on-call or incident work. For SRE roles it is often the most relevant thing you have done.

And the ones that hurt in every role: a guessed address, a generic resume, and an email longer than a phone screen. More in how to email a recruiter about a LinkedIn hiring post.

• LinkedIn posts by heads of infrastructure, CTOs and engineering managers at SaaS, fintech and e-commerce startups.
• Other titles for the same work: cloud engineer, platform engineer, SRE, build and release engineer, DevSecOps engineer.
• Company job boards on Greenhouse, Lever and Ashby, under infrastructure, platform or engineering.
• Cloud consultancies and partners of AWS, Azure and Google Cloud, which hire for client projects.

A LinkedIn post search to start from (search Posts, Date posted Past 24 hours):

Interns can search ("DevOps intern" OR "cloud intern" OR "AWS intern") instead of the titles, without fresher. With years behind you, drop fresher and add your cloud: (AWS OR Azure). LinkedIn finds nothing at all once a search has more than five ORs, ANDs and NOTs: see how to find hiring posts on LinkedIn. If there is no reply in about a week, follow up once.

• Software developer (backend, frontend, full stack)
• Data analyst
• Data science, AI and ML
• Product manager
• UI/UX designer
• Digital marketing
• Sales and business development
• HR and recruiter
• Data engineer
• QA and software testing
• Mobile developer (Android, iOS, Flutter)
• Cybersecurity
• Business analyst and consulting
• Finance and accounts
• Core engineering (mechanical, electrical, civil)
• Content writer, copywriter and technical writer
• Customer success and support

All of them, with what to lead with for each: cold email by role.