Cloud Engineer: market
Data as of November 19, 2026: 1,161 open Cloud Engineer jobs, 27% remote among jobs that state a work format; median advertised salary $9,000/mo (from 138 postings that state a salary). Source: Zorky, updated daily.
Cloud Engineer — a DevOps specialisation with focus on deep knowledge of one cloud provider (AWS / GCP / Azure) + FinOps cost optimisation + multi-account governance. Role family: Cloud Engineer (general — provisions + manages cloud resources), Senior Cloud Engineer (multi-account architecture + cost optimisation + landing zones), Cloud Architect (org-wide cloud strategy + multi-cloud reality), FinOps Engineer / Practitioner (cost optimisation specialist — a rapidly growing dedicated role in 2026), Cloud Security Engineer (cloud-specific security: IAM / KMS / WAF / GuardDuty). Stack 2026 (pick ONE deeply, plus basics of the others): AWS — dominates US/EU enterprise + most jobs (EC2 / S3 / Lambda / RDS / EKS / ECS / Fargate / CloudFront / Route 53 / IAM / KMS / VPC / Direct Connect / CloudFormation / CDK / Systems Manager). Certifications: SA Associate → SA Professional. GCP — the best developer experience + ML-friendly (Compute Engine / GKE / Cloud Run / BigQuery / Vertex AI / Cloud Storage / Cloud SQL / Cloud Functions / IAM / VPC). Certifications: Associate Cloud Engineer → Professional Cloud Architect. Azure — Microsoft enterprise + .NET ecosystem (VM / AKS / Azure Functions / Cosmos DB / Active Directory / Azure DevOps / ARM templates / Bicep). Certifications: Solutions Architect Associate → Expert. IaC: Terraform/OpenTofu/Pulumi + cloud-native (AWS CDK / GCP Cloud Deployment Manager / Azure Bicep). FinOps tooling: AWS Cost Explorer + Cost Anomaly Detection + Cost Optimization Hub + GCP Cost Management + Azure Cost Management + Kubecost (K8s costs) + Vantage/Cloudability/Anodot/CloudHealth (commercial). Container orchestration: K8s + cloud-managed K8s (EKS / GKE / AKS) deeply. Python for automation. Top stack: cloud, cloud engineer, aws, azure, ci/cd. Among jobs with a stated work format, 27% are remote.
Data as of:
Key numbers for the Cloud Engineer market: open jobs, median salary, observed talent pool and remote share.
The Cloud Engineer market currently has 1,161 open roles, 999 of them freshly observed. Median salary $9,000/mo.
Among jobs with a stated work format, 27% are remote. Cloud work is fully cloud-based. Outsourcers — almost always remote. Russian banks — hybrid/office due to cloud-data compliance. International tech companies — full-remote standard.
⚠ salary known for 138 of 1161 jobs; remote share from 833 with a stated format; 999 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Cloud Engineer postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 40 |
| 2026-06-08 | 23 |
| 2026-06-15 | 30 |
| 2026-06-22 | 134 |
| 2026-06-29 | 140 |
| 2026-07-06 | 130 |
| 2026-07-13 | 140 |
| 2026-07-20 | 111 |
| 2026-07-27 | 91 |
| 2026-08-03 | 81 |
| 2026-08-10 | 53 |
| 2026-08-17 | 53 |
| 2026-08-24 | 54 |
| 2026-08-31 | 58 |
| 2026-09-07 | 54 |
| 2026-09-14 | 54 |
| 2026-09-21 | 208 |
| 2026-09-28 | 229 |
| 2026-10-05 | 208 |
| 2026-10-12 | 517 |
| 2026-10-19 | 283 |
| 2026-10-26 | 239 |
| 2026-11-02 | 229 |
| 2026-11-09 | 242 |
Active sources per week
Sources over the period: 137. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 11 |
| 2026-06-08 | 9 |
| 2026-06-15 | 12 |
| 2026-06-22 | 22 |
| 2026-06-29 | 33 |
| 2026-07-06 | 33 |
| 2026-07-13 | 29 |
| 2026-07-20 | 36 |
| 2026-07-27 | 30 |
| 2026-08-03 | 30 |
| 2026-08-10 | 23 |
| 2026-08-17 | 19 |
| 2026-08-24 | 28 |
| 2026-08-31 | 24 |
| 2026-09-07 | 22 |
| 2026-09-14 | 23 |
| 2026-09-21 | 35 |
| 2026-09-28 | 35 |
| 2026-10-05 | 39 |
| 2026-10-12 | 43 |
| 2026-10-19 | 49 |
| 2026-10-26 | 46 |
| 2026-11-02 | 47 |
| 2026-11-09 | 55 |
New sources connected: Jun 22 +13 · Jun 29 +21 · Jul 6 +15 · Jul 20 +9 · Nov 9 +11 · all weeks (22) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +3 | 23 |
| Jun 15 | +1 | 30 |
| Jun 22 | +13 | 134 |
| Jun 29 | +21 | 140 |
| Jul 6 | +15 | 130 |
| Jul 13 | +6 | 140 |
| Jul 20 | +9 | 111 |
| Jul 27 | +4 | 91 |
| Aug 3 | +4 | 81 |
| Aug 10 | +1 | 53 |
| Aug 24 | +4 | 54 |
| Aug 31 | +2 | 58 |
| Sep 7 | +4 | 54 |
| Sep 14 | +2 | 54 |
| Sep 21 | +7 | 208 |
| Sep 28 | +2 | 229 |
| Oct 5 | +1 | 208 |
| Oct 12 | +6 | 517 |
| Oct 19 | +6 | 283 |
| Oct 26 | +2 | 239 |
| Nov 2 | +2 | 229 |
| Nov 9 | +11 | 242 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 40 | 11 |
| 2026-06-08 | 23 | 9 |
| 2026-06-15 | 30 | 12 |
| 2026-06-22 | 134 | 22 |
| 2026-06-29 | 140 | 33 |
| 2026-07-06 | 130 | 33 |
| 2026-07-13 | 140 | 29 |
| 2026-07-20 | 111 | 36 |
| 2026-07-27 | 91 | 30 |
| 2026-08-03 | 81 | 30 |
| 2026-08-10 | 53 | 23 |
| 2026-08-17 | 53 | 19 |
| 2026-08-24 | 54 | 28 |
| 2026-08-31 | 58 | 24 |
| 2026-09-07 | 54 | 22 |
| 2026-09-14 | 54 | 23 |
| 2026-09-21 | 208 | 35 |
| 2026-09-28 | 229 | 35 |
| 2026-10-05 | 208 | 39 |
| 2026-10-12 | 517 | 43 |
| 2026-10-19 | 283 | 49 |
| 2026-10-26 | 239 | 46 |
| 2026-11-02 | 229 | 47 |
| 2026-11-09 | 242 | 55 |
Salaries over time
Median Cloud Engineer salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-09-28 | 7,355 | 11 |
| 2026-10-05 | 6,402 | 12 |
| 2026-10-12 | 7,996 | 32 |
| 2026-10-19 | 8,497 | 46 |
| 2026-10-26 | 9,229 | 46 |
| 2026-11-02 | 8,995 | 34 |
| 2026-11-09 | 9,583 | 37 |
The series starts on Sep 28: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | 7,355 |
| 2026-10-05 | 6,402 |
| 2026-10-12 | 7,996 |
| 2026-10-19 | 8,497 |
| 2026-10-26 | 9,229 |
| 2026-11-02 | 8,995 |
| 2026-11-09 | 9,583 |
Remote work over time
Share of Cloud Engineer postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 77.8 |
| 2026-06-08 | 66.7 |
| 2026-06-15 | 56.5 |
| 2026-06-22 | 46.2 |
| 2026-06-29 | 43.5 |
| 2026-07-06 | 51.7 |
| 2026-07-13 | 38.5 |
| 2026-07-20 | 41.3 |
| 2026-07-27 | 53.7 |
| 2026-08-03 | 37.5 |
| 2026-08-10 | 21.4 |
| 2026-08-17 | 19.5 |
| 2026-08-24 | 34.2 |
| 2026-08-31 | 34 |
| 2026-09-07 | 29.3 |
| 2026-09-14 | 22.6 |
| 2026-09-21 | 21.4 |
| 2026-09-28 | 32.7 |
| 2026-10-05 | 32.3 |
| 2026-10-12 | 34.1 |
| 2026-10-19 | 30.2 |
| 2026-10-26 | 30.6 |
| 2026-11-02 | 30.5 |
| 2026-11-09 | 31.4 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 77.8 |
| 2026-06-08 | 66.7 |
| 2026-06-15 | 56.5 |
| 2026-06-22 | 46.2 |
| 2026-06-29 | 43.5 |
| 2026-07-06 | 51.7 |
| 2026-07-13 | 38.5 |
| 2026-07-20 | 41.3 |
| 2026-07-27 | 53.7 |
| 2026-08-03 | 37.5 |
| 2026-08-10 | 21.4 |
| 2026-08-17 | 19.5 |
| 2026-08-24 | 34.2 |
| 2026-08-31 | 34 |
| 2026-09-07 | 29.3 |
| 2026-09-14 | 22.6 |
| 2026-09-21 | 21.4 |
| 2026-09-28 | 32.7 |
| 2026-10-05 | 32.3 |
| 2026-10-12 | 34.1 |
| 2026-10-19 | 30.2 |
| 2026-10-26 | 30.6 |
| 2026-11-02 | 30.5 |
| 2026-11-09 | 31.4 |
Technologies over time
How the share of Cloud Engineer postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | cloud engineer | Azure |
|---|---|---|---|
| 2026-08-10 | 98.1 | 92.5 | 22.6 |
| 2026-08-17 | 90.6 | 83 | 34 |
| 2026-08-24 | 94.4 | 81.5 | 27.8 |
| 2026-08-31 | 100 | 86.2 | 20.7 |
| 2026-09-07 | 92.6 | 75.9 | 24.1 |
| 2026-09-14 | 98.1 | 87 | 22.2 |
| 2026-09-21 | 97.6 | 86.5 | 35.1 |
| 2026-09-28 | 95.2 | 89.5 | 46.3 |
| 2026-10-05 | 94.7 | 89.4 | 51.4 |
| 2026-10-12 | 96.5 | 88.4 | 37.1 |
| 2026-10-19 | 95.4 | 87.3 | 45.9 |
| 2026-10-26 | 96.2 | 91.2 | 51 |
| 2026-11-02 | 97.8 | 90.4 | 41.9 |
| 2026-11-09 | 90.5 | 85.5 | 44.2 |
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | cloud engineer | AWS | Azure | Terraform |
|---|---|---|---|---|---|
| 2026-08-10 | 98.1 | 92.5 | 22.6 | 22.6 | 7.5 |
| 2026-08-17 | 90.6 | 83 | 20.8 | 34 | 5.7 |
| 2026-08-24 | 94.4 | 81.5 | 37 | 27.8 | 13 |
| 2026-08-31 | 100 | 86.2 | 17.2 | 20.7 | 3.4 |
| 2026-09-07 | 92.6 | 75.9 | 24.1 | 24.1 | 5.6 |
| 2026-09-14 | 98.1 | 87 | 16.7 | 22.2 | 7.4 |
| 2026-09-21 | 97.6 | 86.5 | 39.9 | 35.1 | 21.6 |
| 2026-09-28 | 95.2 | 89.5 | 40.2 | 46.3 | 38.9 |
| 2026-10-05 | 94.7 | 89.4 | 35.6 | 51.4 | 31.7 |
| 2026-10-12 | 96.5 | 88.4 | 41.8 | 37.1 | 22.8 |
| 2026-10-19 | 95.4 | 87.3 | 41 | 45.9 | 30 |
| 2026-10-26 | 96.2 | 91.2 | 47.3 | 51 | 44.4 |
| 2026-11-02 | 97.8 | 90.4 | 37.1 | 41.9 | 37.6 |
| 2026-11-09 | 90.5 | 85.5 | 45 | 44.2 | 42.6 |
Countries over time
How the share of Cloud Engineer postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | Poland | UK |
|---|---|---|---|
| 2026-06-01 | 12.8 | 69.2 | 5.1 |
| 2026-06-08 | 17.4 | 56.5 | 4.3 |
| 2026-06-15 | 18.5 | 37 | 0 |
| 2026-06-22 | 6.2 | 43.1 | 2.3 |
| 2026-06-29 | 3.9 | 18 | 2.3 |
| 2026-07-06 | 16.2 | 12.1 | 5.1 |
| 2026-07-13 | 23.8 | 18.9 | 3.3 |
| 2026-07-20 | 13.5 | 14.6 | 21.9 |
| 2026-07-27 | 6.5 | 20.8 | 10.4 |
| 2026-08-03 | 13.6 | 1.5 | 37.9 |
| 2026-08-10 | 12.2 | 4.9 | 24.4 |
| 2026-08-17 | 29.2 | 4.2 | 22.9 |
| 2026-08-24 | 17.8 | 6.7 | 37.8 |
| 2026-08-31 | 16 | 10 | 38 |
| 2026-09-07 | 27.3 | 9.1 | 27.3 |
| 2026-09-14 | 14.3 | 7.1 | 21.4 |
| 2026-09-21 | 17.7 | 5 | 13.3 |
| 2026-09-28 | 21.1 | 16.4 | 8 |
| 2026-10-05 | 17.8 | 17.8 | 10 |
| 2026-10-12 | 18.5 | 11.5 | 11.8 |
| 2026-10-19 | 19.5 | 14.3 | 10 |
| 2026-10-26 | 21.3 | 13 | 9.3 |
| 2026-11-02 | 22 | 10.5 | 9 |
| 2026-11-09 | 25.1 | 13.1 | 10.6 |
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | Singapore | Poland | UK | Australia |
|---|---|---|---|---|---|
| 2026-06-01 | 12.8 | 0 | 69.2 | 5.1 | 0 |
| 2026-06-08 | 17.4 | 0 | 56.5 | 4.3 | 0 |
| 2026-06-15 | 18.5 | 0 | 37 | 0 | 0 |
| 2026-06-22 | 6.2 | 25.4 | 43.1 | 2.3 | 0 |
| 2026-06-29 | 3.9 | 64.1 | 18 | 2.3 | 0 |
| 2026-07-06 | 16.2 | 28.3 | 12.1 | 5.1 | 10.1 |
| 2026-07-13 | 23.8 | 21.3 | 18.9 | 3.3 | 12.3 |
| 2026-07-20 | 13.5 | 12.5 | 14.6 | 21.9 | 12.5 |
| 2026-07-27 | 6.5 | 37.7 | 20.8 | 10.4 | 6.5 |
| 2026-08-03 | 13.6 | 12.1 | 1.5 | 37.9 | 3 |
| 2026-08-10 | 12.2 | 0 | 4.9 | 24.4 | 12.2 |
| 2026-08-17 | 29.2 | 0 | 4.2 | 22.9 | 18.8 |
| 2026-08-24 | 17.8 | 4.4 | 6.7 | 37.8 | 6.7 |
| 2026-08-31 | 16 | 0 | 10 | 38 | 12 |
| 2026-09-07 | 27.3 | 4.5 | 9.1 | 27.3 | 9.1 |
| 2026-09-14 | 14.3 | 4.8 | 7.1 | 21.4 | 26.2 |
| 2026-09-21 | 17.7 | 22.1 | 5 | 13.3 | 5 |
| 2026-09-28 | 21.1 | 25.8 | 16.4 | 8 | 5.6 |
| 2026-10-05 | 17.8 | 10 | 17.8 | 10 | 5.6 |
| 2026-10-12 | 18.5 | 8.5 | 11.5 | 11.8 | 3.8 |
| 2026-10-19 | 19.5 | 12.4 | 14.3 | 10 | 5.6 |
| 2026-10-26 | 21.3 | 13 | 13 | 9.3 | 4.2 |
| 2026-11-02 | 22 | 6.5 | 10.5 | 9 | 5 |
| 2026-11-09 | 25.1 | 6.5 | 13.1 | 10.6 | 5 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Cloud Engineer.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Cloud Engineer jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 1,161 |
| Open demand | 1,161 |
| Observed supply | — not published |
Cloud Engineer — a stable DevOps segment. Growth 2026 is driven by: continued cloud-native adoption, multi-cloud reality (89% of companies use 2+ clouds), FinOps pressure (cloud bills $1M-$1B+ annually demand optimisation), AI/ML infra (cloud GPU / TPU access). Russian — steady flow. EPAM Cloud Practice — the largest outsource channel for US AWS / GCP / Azure projects. International remote via cloud consultancies (Cloudreach / Slalom / Pythian) + tech companies.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Cloud Engineer jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 1 |
| $1–2k | 0 |
| $2–3k | 0 |
| $3–4k | 5 |
| $4–5k | 6 |
| $5–6k | 15 |
| $6–7k | 17 |
| $7–8k | 12 |
| $8–9k | 11 |
| $9–10k | 16 |
| $10–12k | 23 |
| $12–15k | 21 |
| $15–20k | 9 |
| $20k+ | 2 |
- usable for the calculation: 138 (11.9%)
- stated but not converted to USD/month: 235 (20.2%)
- not stated: 788 (67.9%)
One in ten postings offers under $5,208, one in ten over $14,683. Half of the postings offer between $6,500 and $11,666. Sample: 138.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 1 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 0 |
| $3–4k | 3,000 | 4,000 | 5 |
| $4–5k | 4,000 | 5,000 | 6 |
| $5–6k | 5,000 | 6,000 | 15 |
| $6–7k | 6,000 | 7,000 | 17 |
| $7–8k | 7,000 | 8,000 | 12 |
| $8–9k | 8,000 | 9,000 | 11 |
| $9–10k | 9,000 | 10,000 | 16 |
| $10–12k | 10,000 | 12,000 | 23 |
| $12–15k | 12,000 | 15,000 | 21 |
| $15–20k | 15,000 | 20,000 | 9 |
| $20k+ | 20,000 | — | 2 |
Which countries have the most open Cloud Engineer jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 228 | 23.4% |
| Poland | 115 | 11.8% |
| Singapore | 109 | 11.2% |
| United Kingdom | 86 | 8.8% |
| India | 79 | 8.1% |
| Germany | 74 | 7.6% |
| Canada | 24 | 2.5% |
| Netherlands | 23 | 2.4% |
| Hong Kong | 23 | 2.4% |
| Sweden | 15 | 1.5% |
| Other countries | 199 | 20.4% |
The leader by Cloud Engineer job count is the US (228 positions). Poland — Cloud-friendly EU hub. Germany — Berlin / Munich startup cluster + enterprise Microsoft Azure.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 228 |
| PL | 115 |
| SG | 109 |
| GB | 86 |
| IN | 79 |
| DE | 74 |
| CA | 24 |
| NL | 23 |
| HK | 23 |
| SE | 15 |
Which technologies are most often required in the same job as Cloud Engineer.
Used together with
Share — how many of the 1,161 jobs in the Cloud Engineer market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Cloud Engineer stack 2026: ONE cloud deeply (AWS / GCP / Azure) + basics of the other two. AWS deep (EC2 / S3 / Lambda / RDS / EKS / ECS / Fargate / CloudFront / Route 53 / IAM / KMS / VPC / CloudFormation / CDK), GCP deep (Compute Engine / GKE / Cloud Run / BigQuery / Vertex AI / Cloud Storage / Cloud SQL / IAM / VPC), Azure deep (VM / AKS / Functions / Cosmos DB / Active Directory / Bicep), Russian cloud, IaC (Terraform / OpenTofu + cloud-native CDK / Bicep), Kubernetes cloud-managed mastery (EKS / GKE / AKS), FinOps tooling (AWS Cost Explorer / GCP Cost Management / Azure Cost Management + Kubecost + Vantage / Cloudability / Anodot / CloudHealth), Cloud Security (IAM mastery + KMS + GuardDuty / Security Command Center / Sentinel), networking deep (VPC / Transit Gateway / Direct Connect / VPN / DNS / CDN), Python (boto3 / google-cloud / azure-sdk).
Common pairs: AWS + Terraform + Kubernetes + Docker, GCP + Terraform + GKE + BigQuery, Azure + Bicep + AKS + Cosmos DB, Yandex.Cloud + Terraform + Managed K8s, AWS Control Tower + Org Policy + SCPs (multi-account governance), Kubecost + Vantage + Cost Anomaly Detection (FinOps stack), IAM + KMS + Secrets Manager + WAF (security stack). Learning roadmap: DevOps base → pick one cloud → Foundation cert → Associate cert → build production project → Professional cert → networking deep → security deep → FinOps → multi-account governance.
Chart data
| Name | Count |
|---|---|
| cloud | 1,036 |
| cloud engineer | 938 |
| aws | 498 |
| azure | 482 |
| terraform | 242 |
| kubernetes | 212 |
| python | 168 |
| gcp | 166 |
| docker | 148 |
| ansible | 128 |
| cloudformation | 104 |
| google cloud | 98 |
How many Cloud Engineer jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 359 |
| middle | 58 |
| lead | 53 |
| principal | 32 |
| junior | 28 |
Junior — typical entry: DevOps Junior + cloud certs. Career flow: DevOps Junior (1-2 years) → Cloud Engineer (2-3 years) → Senior → either Cloud Architect (strategy), FinOps specialist (cost deep), Cloud Security Engineer (security deep), or a move into a native cloud-provider Solutions Architect role.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 359 |
| middle | 58 |
| lead | 53 |
| principal | 32 |
| junior | 28 |
Who hires the most for Cloud Engineer and how concentrated demand is among the largest companies.
Employers
Demand is spread across 816 employers. The largest accounts for 1.4%, the top ten for 7.5%; the remaining 92.5% is long tail.
| share | value |
|---|---|
| top-1 | 1.4% |
| top-3 | 3.3% |
| top-10 | 7.5% |
| long tail | 92.5% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Cloud Engineer jobs from.
Where Zorky sees this market
Observed across 74 sources; the largest accounts for 9.2% — this market does not rest on a single channel.
Cloud Engineer jobs: hh.ru, Habr Career, getmatch, Djinni, LinkedIn (huge international Cloud segment), NoFluffJobs / JustJoin.it (Poland Cloud-friendly), Telegram, career pages of EPAM Cloud Practice / Luxoft Cloud / Andersen / DataArt / Cloudreach / Slalom, specialised boards cloudnativejobs.com + awsjobs.io + gcpjobs.io + cloud-careers.com, Y Combinator Work at a Startup, native cloud-provider careers.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 657 | 0.5659 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 473 | 0.4074 |
| telegram | Telegram | Telegram | 30 | 0.0258 |
| community | сообщества и публичные профили | community & public profiles | 1 | 0.0009 |
The newest Cloud Engineer jobs from company career sites.
Recent openings
- Cloud Engineer (m/w/x) – Cloud-Betrieb von SaaS-Lösungen · DE
- Cloud Engineer · SE
- Senior Cloud Engineer · GB
- Principal Cloud Engineer · IN
- Junior Cloud Engineer (Azure/AWS) (m/v/x) · RO
- Cloud Engineer · NL
- Microsoft Cloud Engineer - Cayman Islands (Relocation) · GB · $7,092
- Senior AWS Cloud Engineer · GB · $7,092
Latest open Cloud Engineer jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
Cloud Engineer overlaps with DevOps (foundation stack), Cloud Architect (strategy depth), FinOps Engineer (cost specialisation), Cloud Security Engineer (security specialisation), Platform Engineer (cloud platform building), Data Engineer (cloud data warehouse — BigQuery / Snowflake / Redshift). Comparison — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: DevOps / SRE
Related specializations
Inside Cloud Engineer: Cloud Engineer (general — provisions + manages cloud resources), Senior Cloud Engineer (multi-account architecture + cost optimisation + landing zones), Cloud Architect (org-wide cloud strategy), FinOps Engineer / Practitioner (cost optimisation specialist — a growing role in 2026), Cloud Security Engineer (cloud-specific security: IAM / KMS / WAF / GuardDuty). Comparison with devops/sre/kubernetes/devsecops/platform/infrastructure — in the bar below.
Frequently asked questions
The most common questions about Cloud Engineer: pay, AWS vs GCP vs Azure (decision tree + market share 2026), multi-cloud reality 2026 (4 patterns), FinOps as a growing discipline, Cloud Architect difference, remote, how to start (4-8 months from DevOps Middle via the cert track), Senior skills (Pro cert + networking deep + FinOps + multi-account governance). Answers recompute automatically.
What does a Cloud Engineer Junior, Middle, Senior, or Lead earn?
Junior — typical entry: DevOps Junior + cloud certs (AWS SA Associate / GCP ACE / Azure AZ-104). The Junior → Middle jump — after the first production multi-account / multi-region deployment + the first cost-optimisation initiative. Middle → Senior — multi-account landing zones + cost-optimisation mandate + multi-cloud project. Senior → Cloud Architect — org-wide cloud strategy + multi-team coordination. Career flow: DevOps Junior (1-2 years) → Cloud Engineer Junior / Middle (1-2 years) → Senior → either Cloud Architect (strategy), FinOps specialist (cost optimisation deep), Cloud Security Engineer (security deep), or a move into a native cloud provider on solutions-architecture roles.
What stack does a Cloud Engineer most often need?
Top 5: cloud, cloud engineer, aws, azure, ci/cd. One cloud platform deeply + basic knowledge of the other two. AWS deep: EC2 / S3 / Lambda / RDS / DynamoDB / EKS / ECS / Fargate / CloudFront / Route 53 / IAM mastery / KMS / VPC design / Direct Connect / Transit Gateway / Systems Manager / CloudFormation + CDK / CodePipeline / Step Functions / EventBridge. GCP deep: Compute Engine / GKE / Cloud Run / BigQuery / Vertex AI / Cloud Storage / Cloud SQL / Cloud Functions / Pub/Sub / IAM / VPC / Cloud DNS / Cloud Build / Cloud Deploy. Azure deep: VM / AKS / Azure Functions / Cosmos DB / Azure SQL / Storage / Active Directory / Azure DevOps / ARM templates + Bicep / Logic Apps / Service Bus. IaC: Terraform / OpenTofu deep (cloud-agnostic) + cloud-native (AWS CDK for AWS-only, GCP Deployment Manager, Azure Bicep). Kubernetes-cloud-managed: EKS / GKE / AKS mastery (differences from vanilla K8s — managed control plane / integration with cloud-native services). FinOps tooling: AWS Cost Explorer + Cost Anomaly Detection + Cost Optimization Hub, GCP Cost Management, Azure Cost Management, Kubecost (K8s cost attribution), Vantage / Cloudability / Anodot / CloudHealth (commercial multi-cloud). FinOps Foundation certifications. Cloud Security: IAM mastery (least-privilege design), KMS / Secrets Manager, AWS GuardDuty + WAF + Security Hub (or GCP Security Command Center / Azure Sentinel), CIS benchmarks. Networking deep: VPC peering, Transit Gateways, hybrid connectivity (Direct Connect / VPN), DNS strategy (Route 53 / Cloud DNS / Azure DNS), CDN (CloudFront / Cloud CDN / Azure Front Door). Programming: Python (boto3 / google-cloud / azure-sdk SDK mastery) for automation.
AWS vs GCP vs Azure — which cloud to pick?
Strengths: breadth of services (200+), mature IAM / VPC, Lambda — the best serverless, large ecosystem. Weaknesses: developer experience trails GCP, billing complexity ("unreserved surprises" common), long cert path (SA Associate → Pro). Use case: enterprise + breadth matters + most US projects. Strengths: simpler IAM (resource hierarchy + project-level), Cloud Run (best serverless container), BigQuery, strongest K8s heritage (Google invented K8s — GKE most polished). Weaknesses: smaller job market, fewer services than AWS, weaker enterprise integration. Use case: data / ML-heavy workloads + new project with developer experience priority. Strengths: deep Active Directory integration, Microsoft 365 / Office tie-ins, hybrid-cloud (Azure Stack), best for legacy enterprise migration. Weaknesses: ARM templates historically weaker (Bicep fixed that — modern), ecosystem not as rich as AWS. Use case: enterprise with Microsoft stack + hybrid-cloud + .NET legacy. Typical pattern: AWS primary + GCP for data / ML + Azure for enterprise SaaS integrations. A Senior Cloud Engineer owns ONE deeply + basics of the other two.
Multi-cloud reality 2026 — how teams actually work
Reality 2026 — most orgs use 2-3 clouds, but the pattern varies. Typical: AWS primary + GCP for ML / BigQuery. Pattern 2: Multi-cloud by compliance / data residency — different clouds for different regions / customer segments (e.g. AWS for US customers, Azure for EU GDPR-heavy customers). Pattern 3: Vendor-lock avoidance multi-cloud — explicitly multi-cloud architecture (Kubernetes + Terraform for portability, vendor-neutral storage abstractions). Pattern 4: Hybrid-cloud (cloud + on-prem) — banking / healthcare / govt regulated workloads on-prem + cloud for non-sensitive workloads (Azure Stack / AWS Outposts / GCP Anthos). What reality does NOT work in 2026: 1) Pure cloud-agnostic abstraction layers (e.g. Crossplane for all clouds) — too leaky, you lose cloud-native features. 2) 50/50 multi-cloud split — double expertise costs, no volume discounts. 3) Multi-cloud for cost optimisation — data egress costs usually kill the savings. Choose a primary cloud around product requirements. Add another provider for a justified need; Terraform or OpenTofu can help manage infrastructure consistently. The Senior Cloud Architect role — design the right multi-cloud strategy for a specific business need, not "more = better". FinOps aspect: multi-cloud complicates cost attribution + commitment-based discounts (Reserved Instances / Savings Plans / Committed Use Discounts) — each cloud requires separate planning.
What is FinOps and why is it growing in 2026?
FinOps (Cloud Financial Operations) — discipline of financial accountability for cloud spend, the bridge between engineering / finance / business teams. The FinOps Foundation (CNCF-affiliated organisation) defines practices. Senior leadership demands cost optimisation. Career path for FinOps Engineer / Practitioner: typical entry — Cloud Engineer Senior + interest in cost + FinOps Foundation certifications (FinOps Certified Practitioner → Professional). FinOps Engineer responsibilities: 1) Cloud cost tagging strategy (cost allocation by team / project / environment). 2) Cost anomaly detection automation (AWS Cost Anomaly Detection / Azure Cost Management / Vantage / Anodot). 3) Reserved Instance / Savings Plan / Committed Use Discount planning + management. 4) Right-sizing analysis (EC2 / RDS / GCE instances often 2-4× oversized). 5) AWS EC2 Spot: discounts of up to 90% compared with On-Demand; this is an upper bound on compute discounts, not guaranteed savings on the whole bill. Workloads must tolerate interruptions. AWS EC2 Spot. 6) Cloud-native storage tiering (S3 Intelligent-Tiering / Glacier, GCS Coldline / Archive, Azure Cool / Archive). 7) Kubernetes cost attribution (Kubecost / OpenCost). 8) Data egress optimisation (CloudFront / Cloud CDN caching strategies). 9) Chargeback / showback dashboards for product teams. 10) FinOps culture promotion — make engineers cost-aware. Resources: FinOps Foundation (free trainings + community), "Cloud FinOps" J.R. Storment / Mike Fuller (O'Reilly — must-read), Vantage Blog (best practical content).
What share of jobs are remote?
Among jobs with a stated work format, 27% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Cloud Architect different from Cloud Engineer?
Cloud Engineer — implements + maintains cloud infra under guidance / specifications. Day-to-day: Terraform PRs, troubleshooting, cost reviews, IAM updates, on-call rotation. Cloud Architect — designs cloud strategy + landing zone architecture + compliance frameworks. Day-to-day: ADRs writing, design reviews for product-team cloud proposals, multi-account strategy, security architecture review, cost-architecture decisions. Less programming (more strategy + communication). Career path: Cloud Engineer Senior (4-6 years) → Cloud Architect → Principal Cloud Architect / Chief Cloud Officer (CCoE — Cloud Center of Excellence lead). Cloud Solutions Architect — pre-sales + customer architecture work. Often customer-facing — design solutions for prospective customers, technical sales. Career choice: Engineer if hands-on coding every day appeals, Architect (internal) if internal-strategy + multi-team interest, Architect (cloud-provider) if customer-facing + pre-sales interest.
Where to start in Cloud Engineering in 2026?
Roadmap: 1) DevOps base solid — Linux + bash + Docker + Kubernetes + Terraform + Git. Without this base there's no point going into Cloud specialisation. 2) Pick ONE cloud deeply: AWS (default 2026 for US outsource) or GCP (for AI / ML / data workloads) or Azure (for enterprise Microsoft stack). 3) Foundation certification: AWS Cloud Practitioner or GCP Cloud Digital Leader or Azure Fundamentals (AZ-900) — easy entry cert, demonstrates basic understanding. 4) Associate-level certification: AWS SA Associate or GCP Associate Cloud Engineer or Azure AZ-104 (Administrator) + AZ-204 (Developer). 5) Build something real — full-stack app on one cloud with production-grade setup (multi-AZ HA / IaC / observability / CI/CD). Document on GitHub. 6) Professional-level certification: AWS SA Professional (the most valuable cloud cert 2026) or GCP Professional Cloud Architect or Azure Solutions Architect Expert. 7) Deepen networking: VPC design, hybrid connectivity (Direct Connect / VPN / Interconnect), DNS strategy, CDN setup, multi-region architecture. 8) Security deep: IAM mastery (least-privilege patterns), KMS / Secrets Manager, security services (AWS GuardDuty + WAF + Security Hub / GCP Security Command Center / Azure Sentinel), CIS Benchmarks. Optional cert: AWS Security Specialty / Azure Security Engineer (AZ-500). 9) FinOps: cost tagging strategy, Reserved Instances / Savings Plans / Committed Use Discounts, right-sizing automation, Kubernetes cost attribution. FinOps Foundation Certified Practitioner certification. Book: "Cloud FinOps" Storment / Fuller. 10) Advanced pet project: multi-account landing zone setup with AWS Control Tower / GCP Org Policy / Azure Management Groups + automated compliance scanning + cost optimisation automation. RU courses: Otus "Cloud Solution Architect", Slurm Cloud track, Karpov.Courses Cloud Engineer. International (EN): A Cloud Guru (best for cert prep), Cloud Academy, FreeCodeCamp YouTube (free AWS / GCP / Azure courses), AWS Skill Builder (free official). Must-read books: "AWS Certified Solutions Architect Study Guide" Piper / Clinton, "Cloud Native Patterns" Davis, "Designing Cloud Data Platforms" Plewes. DevOps Middle → Cloud Engineer Junior — 4-8 months (with certification track). Backend Senior → Cloud Engineer Junior — 6-10 months.
How many open jobs are in this sample?
The published sample contains 1161 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Cloud Engineer need?
A Senior Cloud Engineer owns the full cloud infrastructure cycle + cost optimisation + technical leadership. One cloud Pro-level: AWS SA Pro / GCP Cloud Architect Pro / Azure Solutions Architect Expert — at real production scale (50+ accounts / multi-region / engineers). Networking deep: VPC design (multi-region / multi-account / Transit Gateways / Direct Connect), DNS strategy, BGP basics, security groups vs NACLs mastery, hybrid connectivity. IaC mastery: Terraform / OpenTofu deep (modules / workspaces / state migration / drift detection) + cloud-native (AWS CDK or Bicep) for cloud-specific advanced features. Kubernetes cloud-managed mastery: EKS / GKE / AKS production-scale, integration with cloud-native services (IRSA for EKS / Workload Identity for GKE), node group strategies. FinOps mastery: cost allocation tagging strategy, Reserved Instances / Savings Plans / Committed Use Discounts planning, right-sizing automation, spot instances strategy, Kubernetes cost attribution (Kubecost / OpenCost). Cloud Security mastery: IAM mastery (least-privilege design + automation), KMS / Secrets Manager rotation, security-services integration (GuardDuty + WAF + Security Hub + Macie / Security Command Center / Sentinel), CIS Benchmark automation, supply chain security. Multi-account governance: Control Tower / Org Policy / Management Groups, SCPs / Org policies, landing zone architecture, account vending automation. Compliance frameworks: SOC 2 / ISO 27001 / HIPAA / PCI-DSS — automation for compliance audits. Disaster Recovery: multi-region failover strategies, RPO / RTO planning, backup strategy, chaos engineering for DR validation. Observability in a cloud context: CloudWatch / Cloud Monitoring / Azure Monitor integration with Prometheus / Grafana / Datadog. Programming: Python deep (boto3 / google-cloud / azure-sdk SDK mastery) + Go basics. System design for cloud: design multi-region multi-AZ HA on whiteboard, well-architected framework principles, cell-based architecture for blast radius. Soft: ADRs writing for cloud decisions, cost-architecture trade-off communication to finance / business, on-call rotation, cross-team collaboration. English for Senior+ MUST — cloud community / docs / certifications in English. Optional bonus: open-source contributions to Terraform providers / cloud SDK projects / cloud-native CNCF projects — sharply increase market value for native cloud-providers hiring.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.