We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

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.

1,161
open jobs — by job title, reposts merged
$9,000
median $/mo
27%
remote

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
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-0140
2026-06-0823
2026-06-1530
2026-06-22134
2026-06-29140
2026-07-06130
2026-07-13140
2026-07-20111
2026-07-2791
2026-08-0381
2026-08-1053
2026-08-1753
2026-08-2454
2026-08-3158
2026-09-0754
2026-09-1454
2026-09-21208
2026-09-28229
2026-10-05208
2026-10-12517
2026-10-19283
2026-10-26239
2026-11-02229
2026-11-09242

Active sources per week

Sources over the period: 137. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-0111
2026-06-089
2026-06-1512
2026-06-2222
2026-06-2933
2026-07-0633
2026-07-1329
2026-07-2036
2026-07-2730
2026-08-0330
2026-08-1023
2026-08-1719
2026-08-2428
2026-08-3124
2026-09-0722
2026-09-1423
2026-09-2135
2026-09-2835
2026-10-0539
2026-10-1243
2026-10-1949
2026-10-2646
2026-11-0247
2026-11-0955
New sources connected: Jun 22 +13 · Jun 29 +21 · Jul 6 +15 · Jul 20 +9 · Nov 9 +11 · all weeks (22) in the table
WeekNew sourcesNew postings
Jun 8+323
Jun 15+130
Jun 22+13134
Jun 29+21140
Jul 6+15130
Jul 13+6140
Jul 20+9111
Jul 27+491
Aug 3+481
Aug 10+153
Aug 24+454
Aug 31+258
Sep 7+454
Sep 14+254
Sep 21+7208
Sep 28+2229
Oct 5+1208
Oct 12+6517
Oct 19+6283
Oct 26+2239
Nov 2+2229
Nov 9+11242

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
Timeline: postings and sources — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-014011
2026-06-08239
2026-06-153012
2026-06-2213422
2026-06-2914033
2026-07-0613033
2026-07-1314029
2026-07-2011136
2026-07-279130
2026-08-038130
2026-08-105323
2026-08-175319
2026-08-245428
2026-08-315824
2026-09-075422
2026-09-145423
2026-09-2120835
2026-09-2822935
2026-10-0520839
2026-10-1251743
2026-10-1928349
2026-10-2623946
2026-11-0222947
2026-11-0924255

Salaries over time

Median Cloud Engineer salary per week, USD per month.

Median salary, USD per month

Chart data
Median salary, USD per month. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodMedianPostings with a salary per week (n)
2026-09-287,35511
2026-10-056,40212
2026-10-127,99632
2026-10-198,49746
2026-10-269,22946
2026-11-028,99534
2026-11-099,58337

The series starts on Sep 28: there is no data before that.

Postings with a salary per week (n)

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
Salaries over time — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekMedian
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-287,355
2026-10-056,402
2026-10-127,996
2026-10-198,497
2026-10-269,229
2026-11-028,995
2026-11-099,583

Remote work over time

Share of Cloud Engineer postings offering fully remote work, per week.

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-06-0177.8
2026-06-0866.7
2026-06-1556.5
2026-06-2246.2
2026-06-2943.5
2026-07-0651.7
2026-07-1338.5
2026-07-2041.3
2026-07-2753.7
2026-08-0337.5
2026-08-1021.4
2026-08-1719.5
2026-08-2434.2
2026-08-3134
2026-09-0729.3
2026-09-1422.6
2026-09-2121.4
2026-09-2832.7
2026-10-0532.3
2026-10-1234.1
2026-10-1930.2
2026-10-2630.6
2026-11-0230.5
2026-11-0931.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
Remote work over time — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-0177.8
2026-06-0866.7
2026-06-1556.5
2026-06-2246.2
2026-06-2943.5
2026-07-0651.7
2026-07-1338.5
2026-07-2041.3
2026-07-2753.7
2026-08-0337.5
2026-08-1021.4
2026-08-1719.5
2026-08-2434.2
2026-08-3134
2026-09-0729.3
2026-09-1422.6
2026-09-2121.4
2026-09-2832.7
2026-10-0532.3
2026-10-1234.1
2026-10-1930.2
2026-10-2630.6
2026-11-0230.5
2026-11-0931.4

Technologies over time

How the share of Cloud Engineer postings mentioning each of the top technologies changed.

Postings mentioning the technology, %

Chart data
Postings mentioning the technology, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
Periodcloudcloud engineerAzure
2026-08-1098.192.522.6
2026-08-1790.68334
2026-08-2494.481.527.8
2026-08-3110086.220.7
2026-09-0792.675.924.1
2026-09-1498.18722.2
2026-09-2197.686.535.1
2026-09-2895.289.546.3
2026-10-0594.789.451.4
2026-10-1296.588.437.1
2026-10-1995.487.345.9
2026-10-2696.291.251
2026-11-0297.890.441.9
2026-11-0990.585.544.2
Up to 5 on the chart:

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
Technologies over time — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
Weekcloudcloud engineerAWSAzureTerraform
2026-08-1098.192.522.622.67.5
2026-08-1790.68320.8345.7
2026-08-2494.481.53727.813
2026-08-3110086.217.220.73.4
2026-09-0792.675.924.124.15.6
2026-09-1498.18716.722.27.4
2026-09-2197.686.539.935.121.6
2026-09-2895.289.540.246.338.9
2026-10-0594.789.435.651.431.7
2026-10-1296.588.441.837.122.8
2026-10-1995.487.34145.930
2026-10-2696.291.247.35144.4
2026-11-0297.890.437.141.937.6
2026-11-0990.585.54544.242.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
Postings in the country, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodUSAPolandUK
2026-06-0112.869.25.1
2026-06-0817.456.54.3
2026-06-1518.5370
2026-06-226.243.12.3
2026-06-293.9182.3
2026-07-0616.212.15.1
2026-07-1323.818.93.3
2026-07-2013.514.621.9
2026-07-276.520.810.4
2026-08-0313.61.537.9
2026-08-1012.24.924.4
2026-08-1729.24.222.9
2026-08-2417.86.737.8
2026-08-31161038
2026-09-0727.39.127.3
2026-09-1414.37.121.4
2026-09-2117.7513.3
2026-09-2821.116.48
2026-10-0517.817.810
2026-10-1218.511.511.8
2026-10-1919.514.310
2026-10-2621.3139.3
2026-11-022210.59
2026-11-0925.113.110.6
Up to 5 on the chart:

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
Countries over time — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekUSASingaporePolandUKAustralia
2026-06-0112.8069.25.10
2026-06-0817.4056.54.30
2026-06-1518.503700
2026-06-226.225.443.12.30
2026-06-293.964.1182.30
2026-07-0616.228.312.15.110.1
2026-07-1323.821.318.93.312.3
2026-07-2013.512.514.621.912.5
2026-07-276.537.720.810.46.5
2026-08-0313.612.11.537.93
2026-08-1012.204.924.412.2
2026-08-1729.204.222.918.8
2026-08-2417.84.46.737.86.7
2026-08-31160103812
2026-09-0727.34.59.127.39.1
2026-09-1414.34.87.121.426.2
2026-09-2117.722.1513.35
2026-09-2821.125.816.485.6
2026-10-0517.81017.8105.6
2026-10-1218.58.511.511.83.8
2026-10-1919.512.414.3105.6
2026-10-2621.313139.34.2
2026-11-02226.510.595
2026-11-0925.16.513.110.65

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
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.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
Clean market: hiring index — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open Cloud Engineer jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand1,161
Open demand1,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

P25 $6,500 · P50 $9,000 · P75 $11,666
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k1
$1–2k0
$2–3k0
$3–4k5
$4–5k6
$5–6k15
$6–7k17
$7–8k12
$8–9k11
$9–10k16
$10–12k23
$12–15k21
$15–20k9
$20k+2
Salary in postings: base 1,161
  • 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
Salary distribution — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricLower boundUpper boundCount
<$1k01,0001
$1–2k1,0002,0000
$2–3k2,0003,0000
$3–4k3,0004,0005
$4–5k4,0005,0006
$5–6k5,0006,00015
$6–7k6,0007,00017
$7–8k7,0008,00012
$8–9k8,0009,00011
$9–10k9,00010,00016
$10–12k10,00012,00023
$12–15k12,00015,00021
$15–20k15,00020,0009
$20k+20,000—2

Which countries have the most open Cloud Engineer jobs.

Demand geography

countryjobsshare
United States22823.4%
Poland11511.8%
Singapore10911.2%
United Kingdom868.8%
India798.1%
Germany747.6%
Canada242.5%
Netherlands232.4%
Hong Kong232.4%
Sweden151.5%
Other countries19920.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
Demand geography — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
US228
PL115
SG109
GB86
IN79
DE74
CA24
NL23
HK23
SE15

Which technologies are most often required in the same job as Cloud Engineer.

Used together with

cloud
1,03689.2%
cloud engineer
93880.8%
aws
49842.9%
azure
48241.5%
terraform
24220.8%
kubernetes
21218.3%
python
16814.5%
gcp
16614.3%
docker
14812.7%
ansible
12811%

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
Used together with — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
cloud1,036
cloud engineer938
aws498
azure482
terraform242
kubernetes212
python168
gcp166
docker148
ansible128
cloudformation104
google cloud98

How many Cloud Engineer jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior359
middle58
lead53
principal32
junior28

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
Demand by grade — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior359
middle58
lead53
principal32
junior28

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.

largest 1.4%2nd–3rd 2%4th–10th 4.1%the rest 92.5%
sharevalue
top-11.4%
top-33.3%
top-107.5%
long tail92.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
Where Zorky sees this market — Cloud Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites6570.5659
boardджоб-борды и агрегаторыjob boards & aggregators4730.4074
telegramTelegramTelegram300.0258
communityсообщества и публичные профилиcommunity & public profiles10.0009

The newest Cloud Engineer jobs from company career sites.

Recent openings

All jobs →

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.

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.

DevSecOpsInfrastructure EngineerKubernetes / ContainerPlatform EngineerSRE

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.

By submitting, you agree to the privacy policy.