Skip to main content
PProfileMatch

18 open Cloud Engineer jobs

Real, currently-open Cloud Engineer roles synced directly from company career pages. Upload your resume to see which of these match your skills, or browse all open roles. New to the role? Read our Cloud Engineer guide.

Hiring snapshot for Cloud Engineer

The most common locations right now are New York, NY (2), Boston, MA; Remote-Friendly (Travel-Required) | San Francisco, CA | Seattle, WA | New York City, NY; Washington, DC (1), Gurugram (1). 4 of these 18 roles (22%) list a remote option. 8 were posted in the last two weeks. By team, the biggest groups are Engineering (18).

Computed from the 18 open listings shown below.

Guide: working as a Cloud Engineer

Cloud engineers build and run the infrastructure applications live on: networks, compute, storage, databases and identity in providers such as AWS, Azure or Google Cloud. They define that infrastructure as code, automate deployments, keep costs and permissions under control, and troubleshoot when services fail or slow down.

Core skills employers look for

  • AWS, Azure or GCP core services
  • Infrastructure as code (Terraform)
  • VPCs, subnets and security groups
  • IAM roles and least privilege
  • Docker and Kubernetes
  • CI/CD pipelines
  • Monitoring, logging and alerting
  • Linux and shell scripting

How to stand out when you apply

  • Build a small project entirely in Terraform or a similar tool: a VPC, a container service, a managed database and an alarm. Then destroy it and rebuild it from code to prove it is repeatable.
  • On your resume, describe environments you owned and the changes you made to reliability, security or spend, naming the specific services involved.
  • A vendor certification can help you pass screening, but pair it with a public repository so reviewers see real configuration rather than only exam knowledge.
  • Practise debugging out loud: explain how you would trace why an instance cannot reach the internet or why a deployment suddenly returns permission errors.

What the interviews usually cover

Interviews typically probe networking (routing, DNS, load balancers), identity and access, choosing between managed services, and designing a highly available deployment across zones. Expect hands-on troubleshooting scenarios, questions on infrastructure-as-code workflows and state files, and sometimes a live exercise writing a pipeline or container configuration.

Prepare for free on ProfileMatch

Browse jobs by role

Browse jobs by company