Every remote DevOps role currently open on RemoteAI, sourced continuously from remote-first companies. Search within this category or explore related roles below.
Remote DevOps jobs cover the engineering work that sits between writing code and running it reliably in production — infrastructure engineering, site reliability engineering (SRE), platform engineering, release engineering, and cloud infrastructure roles all fall under this umbrella. The work itself is defined by tools that are cloud-native and remote-friendly almost by design: infrastructure-as-code, container orchestration, CI/CD pipelines, and monitoring/observability platforms are all managed through the same dashboards and command-line tools whether an engineer is on-site or three continents away from the servers they're managing.
Demand for remote DevOps talent tends to track closely with how much infrastructure a company runs, which means it spans company sizes and stages more evenly than some other technical categories — early-stage startups often need their first DevOps hire the moment they outgrow a single deploy script, while larger companies run entire distributed platform teams responsible for the infrastructure dozens of product engineers depend on. Because reliability and uptime are inherently continuous concerns, DevOps and SRE roles are also more likely than most to mention on-call rotations explicitly in the listing — worth checking specifically if that's a dealbreaker for you.
Core expectations across most listings include comfort with a major cloud provider (AWS, GCP, or Azure), containerization and orchestration (Docker and Kubernetes show up constantly), infrastructure-as-code tools like Terraform, and CI/CD pipeline experience. Beyond that baseline, roles diverge: SRE-leaning positions weight incident response, monitoring, and reliability engineering more heavily, while platform engineering roles focus more on building the internal tools and paved paths other engineers use day to day. Security-adjacent DevOps roles (sometimes labeled DevSecOps) layer in compliance and security tooling on top of the same infrastructure skill set.
Because this work directly affects whether production stays up, listings tend to weight real operational experience — incidents handled, systems scaled, outages prevented — more heavily than credentials or certifications alone, though cloud certifications can still help a resume clear an initial screen. Below are the current remote DevOps and infrastructure roles pulled continuously from companies hiring now.
DevOps is the broader practice of streamlining how software gets built, deployed, and operated, while SRE is a more specific discipline focused on reliability, incident response, and uptime — many companies use the titles somewhat interchangeably in practice.
A major cloud provider (AWS, GCP, or Azure), Docker and Kubernetes for containerization, and an infrastructure-as-code tool like Terraform show up in the large majority of listings, alongside CI/CD pipeline experience.
Often, yes, especially for SRE-leaning roles — reliability work is inherently continuous, so it's worth checking a specific listing for on-call expectations if that matters to your decision.
They can help a resume clear an initial screen, but most listings weight real operational experience — incidents handled, systems scaled — more heavily than certifications alone.
Platform engineering usually refers more specifically to building the internal tools and self-service infrastructure other engineers use day to day, while DevOps is the broader umbrella term covering that plus deployment, reliability, and operations work generally.
This is likely temporary. Try again in a moment.
Reload jobs