Senior Cloud/ML Ops Engineer at Ivo Inc.
San Francisco, CA
$250,000–$325,000from the description
Jul 12, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
A Cloud/MLOps Engineer role focused on owning and evolving a multi-cloud Kubernetes platform spanning AWS, GCP, and Azure. Day-to-day work involves designing multi-cluster and multi-region architectures with failover and disaster recovery, building internal tooling for cluster provisioning, enforcing security and compliance controls, and ensuring ML and API workloads are isolated and cost-optimized. Suited to someone with deep production Kubernetes experience and a background in infrastructure-as-code.
Senior level · San Francisco-Oakland-Berkeley, CA · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 650 people in the San Francisco-Oakland-Berkeley, CA area plausibly meet what this posting asks for (software developers). range 480–840
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $190,744 (middle half $167,095–$224,501). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The role is titled 'Cloud/MLOps Engineer' but the primary day-to-day work is clearly building and shipping infrastructure software — cluster provisioning tooling, multi-region architectures, CI/CD pipelines, IaC — rather than operating systems someone else built. This points to 15-1252 (Software Developers) over 15-1244 (Systems Administrators), though the boundary is genuinely close given the operational SRE flavor.
No specific city is stated in the posting, but Ivo is a San Francisco-based startup (consistent with its investor profile and customer base); the CBSA is inferred as San Francisco-Oakland-Berkeley, CA.
The posting lists AWS, GCP, and Azure together as the multi-cloud target ('across AWS/GCP/Azure'). AWS is named first and is the most common primary cloud; GCP and Azure are captured as alternatives since the role spans all three.
Terraform is listed as the primary IaC example with Pulumi also named ('Pulumi, Terraform, etc.'); Pulumi is captured as an alternative since the JD treats them interchangeably.
GitHub CI/CD is explicitly called out in the requirements section ('multi-cluster or multi-region setups with Github CI/CD'); captured as GitHub Actions, the specific CI/CD product within GitHub.
LLMs appear only in the 'nice to have' narrative ('we'd love someone who's as excited about LLMs as we are') and are not gated requirements.
Secrets management and workload identity are mentioned as platform-layer controls but name no specific tool (e.g. Vault, AWS Secrets Manager), so they are omitted per the named-technology rule.
No minimum years of experience are stated at the role level; the '2am debugging' framing and multi-region/multi-cluster scope support a Senior classification.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.