Cloud hiring is distributed across architecture, application delivery, security, data, reliability, and cost control. Provider names matter, but employers usually hire for the operating decisions behind them.
168 live roles10 hiring companies1% remote-friendly
Vacancy evidence map
Where Cloud carries hiring weight
Each segment represents roles where Cloud was parsed at that evidence tier. This keeps a required production skill separate from contextual stack language.
28 Core79 Required33 Supporting28 Optional
107core + required64% of mentions
16.8roles per company10 employers
Market interpretation
What Cloud demand means in practice
Cloud is a broad market signal, so the evidence tiers are especially important. A required mention may imply hands-on deployment and operations, while supporting mentions can simply describe where a product runs. Companion technologies reveal the actual workload behind the label.
A credible profile translates cloud experience into scale, reliability, security, and spend: traffic handled, recovery targets, deployment frequency, isolation boundaries, or cost reduced. Those facts transfer across AWS, Azure, and GCP more reliably than memorized service lists.
Cloud platformBackend and distributed systemsDevOps / SRECloud security
Reading the market
Signals to look for
Containers, Kubernetes, Terraform, CI/CD, networking, and observability commonly define the delivery path.
Security and identity requirements often carry more weight than the generic cloud label.
Multi-cloud wording may signal customer deployment constraints rather than equal depth in every provider.
Should candidates list every cloud service they have used?
No. Prioritize services tied to production ownership and explain the architecture or outcome. A shorter evidenced stack is more credible.
Can experience transfer between cloud providers?
Yes, especially for networking, identity, containers, observability, distributed systems, and infrastructure-as-code. Role-specific services may still require a ramp-up.
How Cloud appears in job requirements
Inferred from the title and requirement wording in 168 active roles; each role is counted once. Read the methodology.
Posting evidence, not a company-wide stack claim
Main / core
17%(28)
Required
47%(79)
Supporting / context
20%(33)
Nice-to-have
17%(28)
Skills mentioned with Cloud
A shared posting does not always require both skills. Explicit alternatives are counted separately.