Cloud Engineer Job Description, KRAs and Skills

A Cloud Engineer builds and runs a company's workloads on AWS, Azure or Google Cloud. Day to day that means provisioning virtual machines, networks, databases and storage through infrastructure as code, setting up monitoring and backups, applying patches, answering alerts and keeping costs tidy. Cloud engineers work within designs set by a cloud architect and usually report to the DevOps or infrastructure manager. A good one leaves every environment reproducible from code, responds to alerts quickly and catches waste before the monthly bill does.

Detail	For this role
Department	Information Technology
Level	Mid level
Reports to	DevOps Manager
Direct reports	None
Experience	2 to 5 years in cloud or Linux system administration, including hands-on production cloud work

Cloud Engineer job description template

Copy this job description, replace the text in square brackets and post it on your careers page or a job portal.

Job title: Cloud Engineer

Department: Information Technology

Reports to: DevOps Manager

Location: [City], [office, branch or site]

About the role

Key responsibilities

Provision compute, storage, networking and managed databases through Terraform or CloudFormation, following the approved reference designs.
Set up VPCs, subnets, security groups, load balancers and DNS records for new applications and environments.
Configure IAM roles and policies with least privilege, and rotate credentials and certificates before they expire.
Set up monitoring, log collection and alerts in CloudWatch, Azure Monitor or Grafana for every production resource.
Respond to alerts during business hours and on-call weeks, and write a short note for every incident.
Run backups and snapshots on schedule, and test restores of databases and volumes every quarter.
Patch operating systems and rebuild machine images through an automated pipeline.
Find idle, oversized or untagged resources each week and fix them or raise them with the owning team.
Support migrations from on-premise servers to the cloud, including data transfer and cutover checks.
Update runbooks and environment documentation after every change so the next engineer on call can follow them.

Requirements

B.E., B.Tech, BCA or MCA in computer science or IT
AWS Solutions Architect Associate, AWS SysOps Administrator or Azure Administrator Associate certification
Terraform Associate certification is an advantage
2 to 5 years in cloud or Linux system administration, including hands-on production cloud work

KRAs and KPIs for a Cloud Engineer

Key result areas for the appraisal form, each with a KPI you can measure every month or quarter.

Key result area	How to measure it
Infrastructure as code	At least 95 percent of cloud resources created and changed through code, with no manual console changes in production
Alert response	Production alerts acknowledged within 15 minutes during business hours and on-call weeks
Backup reliability	Scheduled backups succeed every day, with a successful restore test each quarter
Cost hygiene	Idle and untagged resources cleared within one week of the weekly cost report
Patching	Production servers and images patched within 30 days of a critical update
Change success	At least 97 percent of infrastructure changes deployed without causing a production incident

Skills and tools

AWS, Azure or GCP servicesTerraform or CloudFormationLinux administrationCloud networking and security groupsIAM policiesMonitoring and loggingBash or Python scriptingDocker basicsOwnership of alertsClear runbook writing

Tools used day to day: AWS or Azure console and CLI, Terraform, CloudWatch or Azure Monitor, Grafana, Git, Ansible, Jira.

Reporting line and career path

Moves up from: System Administrator, Linux Administrator, DevOps Engineer
Next roles: Senior DevOps Engineer, Cloud Architect, Site Reliability Engineer

Interview questions for a Cloud Engineer

Explain how a request reaches an EC2 instance in a private subnet behind a load balancer.
An application needs to read from S3. How would you grant access without access keys?
An instance is running out of disk at 2 am. What do you do?
How would you find the resources behind a sudden jump in the cloud bill?
What is Terraform state, and what can go wrong with it in a team?
Walk me through restoring a production database from a snapshot.

Managing a Cloud Engineer in ZeniaHR

AttendanceOffice days on a general or flexible shift and WFH on the rest, with an on-call week roughly once a month. Keep office-day punches on allowed office networks, and when on-call work eats into a weekly off, HR grants a comp-off credit through the leave ledger.LeavePlan leave around migration cutovers and the on-call rota. If on-call weeks are set up as shifts in the roster, engineers can trade them through shift swap requests, which take effect once the manager and HR approve.Performance and KRAsReview monthly in the first year and quarterly after that, with weighted KPI-type goals for infrastructure as code, alert response, backups and cost hygiene. A new joiner's probation review should note how soon they were ready for on-call duty.

Hire and manage your information technology team in one place

Post the role, onboard the new hire, and track attendance, leave and KRAs in ZeniaHR. Free for your first 50 employees.

Book a free demo See pricing

Frequently asked questions

What does a cloud engineer do?

A cloud engineer builds and maintains a company's infrastructure on AWS, Azure or Google Cloud. They provision servers, networks and databases through code, configure security and access, set up monitoring and backups, respond to alerts, apply patches and clean up unused resources to control cost. They usually follow designs set by a cloud architect.

Which cloud certification should a cloud engineer do first?

For AWS, most engineers in India start with Solutions Architect Associate or SysOps Administrator Associate. For Azure, Azure Administrator Associate is the usual first step. Pick the platform your target employers use and pair the certificate with hands-on practice, because interviews test real troubleshooting.

Is a cloud engineer the same as a DevOps engineer?

Not exactly. A cloud engineer focuses on cloud infrastructure: networks, compute, storage, access and cost. A DevOps engineer focuses on how software is built and deployed: CI/CD pipelines, containers and release automation. The skills overlap heavily, and in smaller companies one person often does both.