Home · Jobs · Remote DevOps

Remote DevOps Jobs.
The Signal, Not the Noise.

Hand-filtered remote DevOps roles from 9 sources — AWS, Kubernetes, Terraform, CI/CD pipelines. US-friendly only. We reject every generic SWE posting before it reaches the feed.

—Roles right now
9Sources
12hRefresh
0%Generic SWE

Open remote DevOps roles

Loading current roles…

Browse all jobs →

What makes a "remote" job here?

Most job boards label anything fully-remote, hybrid, or "remote-friendly" the same way. We don't. CleanDeploy's strictRemote filter only accepts postings that explicitly say remote, fully remote, or work-from-home with US eligibility. Hybrid roles requiring office days appear separately on the main board so you don't waste time on a "remote" listing that turns out to require Tuesday-in-office.

Postings come from Greenhouse and Lever ATS feeds, plus six aggregators: Adzuna, JSearch, Remotive, RemoteOK, Himalayas, Jobicy, and WeWorkRemotely. Each is run through a deterministic role classifier — DevOps, SRE, Platform, Cloud, Infrastructure are accepted; generic full-stack and frontend roles are rejected before they hit your feed.

Common questions

What counts as a remote DevOps role on CleanDeploy?
A posting that explicitly says remote, fully remote, or work-from-home and accepts US-based candidates. Hybrid roles requiring office days are filtered out.
How fresh are these listings?
The aggregator runs every 12 hours via cron, pulling from 9 sources. Each posting is classified before it appears in the feed.
Do these roles include SRE and Platform Engineering?
Yes — DevOps, SRE, and Platform Engineering share infrastructure scope. The classifier groups them together and tags each posting with its detected role family.
Why don't I see [specific job]?
Either it's not US-friendly, the title fell outside our infra-adjacent allowlist, or it's older than the source's surface window. Source coverage is documented in the main app.