Cloud Engineer job description template

Last updated 2026-10-22

Short answer

A good cloud engineer job description lists concrete responsibilities, separates required from preferred skills, names the tools and states contract type, location and work authorization. Use the template below and edit the bracketed fields.

Staffing teams write or rewrite job descriptions all the time: to post a requirement, to brief a recruiter or to tailor a resume. This cloud engineer template is a starting point built from the skills and tools that decide a fit.

Copy-ready job description

Edit the bracketed fields for your requirement.

Cloud Engineer

About the role
We are looking for a Cloud Engineer to join our team. You will build and maintain cloud environments with code.

Responsibilities
- Build and maintain cloud environments with code.
- Design networks, access and security groups.
- Automate deployments and patching.
- Monitor cost, capacity and reliability.
- Support application teams moving workloads to the cloud.

Required
- AWS, Azure or GCP hands-on
- Infrastructure as code (Terraform or CloudFormation)
- Networking (VPC, subnets, routing)
- IAM and security basics
- Linux

Preferred
- Kubernetes
- CI/CD
- Python or Bash
- Monitoring and cost control
- A cloud certification

Tools and stack
Terraform or CloudFormation, The cloud CLI and console, Kubernetes or managed container services, CI/CD tools, Cloud monitoring, Python or Bash

Employment type: [Contract / W2 / C2C / Full-time]
Location: [City, ST / Remote]
Duration: [months]
Work authorization: [accepted types]

Responsibilities explained

Each responsibility maps to something a candidate should be able to describe.

  • Build and maintain cloud environments with code.
  • Design networks, access and security groups.
  • Automate deployments and patching.
  • Monitor cost, capacity and reliability.
  • Support application teams moving workloads to the cloud.

Required skills

Treat these as the screen. If a candidate cannot speak to them, they are rarely a fit.

  • AWS, Azure or GCP hands-on
  • Infrastructure as code (Terraform or CloudFormation)
  • Networking (VPC, subnets, routing)
  • IAM and security basics
  • Linux

Preferred skills

Use these to rank candidates who meet the required list.

  • Kubernetes
  • CI/CD
  • Python or Bash
  • Monitoring and cost control
  • A cloud certification

Other titles this role appears under

Search and post under the variants your clients use.

  • Cloud Engineer
  • Cloud Infrastructure Engineer
  • Cloud Platform Engineer
  • Cloud Operations Engineer

Seniority guide

Pick the level you need and state it plainly in the posting.

  • Junior: follows existing modules.
  • Mid: designs and delivers environments.
  • Senior: sets cloud standards and guardrails.

Tailoring a resume to this description

When you submit a consultant, mirror the required skills and tools in the summary and the most recent role, using only experience the candidate really has. MatchWire’s resume tailoring drafts this from the candidate’s stored work history and the posting.

Frequently asked questions

How long should a job description be?

Long enough to list the responsibilities, required and preferred skills, tools and logistics, usually 300 to 500 words.

Should I list a rate in the description?

If the client allows it, a range helps candidates self-select. Otherwise state it as “rate to be discussed” and confirm it before submitting.

Do your consultants match today's jobs?

Send two consultants and get back the real matches from current open IT jobs, with the rule behind each one. It is free.