Member of Technical Staff, DevOps
San Francisco, CAFull-timePosted todayStill listed today
Most applications go out cold — see where you stand first. No sign-up to start.
Watch jobs like this. New roles like this one near San Francisco, CA, by email.
Don't just apply. Show up ready.
Olive works from this exact posting.
At a glance
Olive lists jobs from US employers, including remote roles you can work from the United States.
Job overview
Reactor is seeking a DevOps/SRE engineer to own reliability, delivery, and observability for its AI inference platform. The role operates across Kubernetes clusters, cloud providers, and regions, improving automated deployment, infrastructure management, and production operations as the platform scales. The engineer will also participate in on-call and help make incident response and service operation more effective.
Skills & qualifications
Skills
Benefits
Full job description
Member of Technical Staff, DevOps Department: Engineering Employment Type: Full Time Location: San Francisco
Description Reactor is building the inference platform for real-time world models. We run the largest and fastest catalog of world models on the market (15+ and growing), including LingBot World 2, LTX 2.5 Realtime, and HappyOyster. Our founders, Alberto Taiuti (CEO) and Bryce Schmidtchen (CTO), met as technical leads on the early Apple Vision Pro team. Alberto went on to co-found Luma AI, now a $4B company. We've raised $59M, led by Lightspeed, with Amplify Partners, WndrCo, and NVIDIA's NVentures participating. Jeffrey Katzenberg, cofounder of Dreamworks Animation, sits on our board of directors.
We're looking for a DevOps / SRE engineer to own the reliability, delivery, and observability of our AI platform. You'll be the person who ensures models get from a developer's branch to production without anyone losing sleep — and when something does go wrong at 2am, you'll be the one who knows where to look.
We run production across multiple Kubernetes clusters, cloud providers, and regions. Our deployment pipeline is fully automated through CI/CD and GitOps, our infrastructure is managed as code, and our observability stack gives us full visibility across every service and GPU workload. This role is about making all of that faster, more reliable, and easier to operate as we scale.
What You'll Do
- Own and evolve our CI/CD pipelines: dynamic pipeline generation across a monorepo of Go services, Python model containers, and Helm charts
- Operate and improve our GitOps deployment lifecycle: Helm releases, Kustomizations, and image automation across multiple clusters
- Build and maintain our observability stack: distributed tracing, metrics, dashboards, and alerting across all services and GPU workloads
- Define and track SLOs for core platform services, including session latency, model cold start time, and streaming reliability
- Run incident response: triage production issues, write postmortems, build runbooks, and drive reliability improvements
- Manage infrastructure-as-code across multiple cloud providers and regions: plan/apply workflows, state management, drift detection
- Operate secret management: encrypted secrets, external secret syncing, certificate automation
- Improve deployment safety: canary rollouts, health checks, startup probes, rollback automation
- Manage authentication infrastructure: OIDC federation for CI, workload identity for cloud services, cross-cloud credential management
- Participate in on-call rotation and build the tooling that makes on-call less painful
What We're Looking For
- You've run production Kubernetes clusters and been on-call for them. You've debugged node scheduling failures, OOM kills, and mysterious pod evictions at 3am
- Strong CI/CD experience: you've built and maintained pipelines for monorepos, not just single-service repos
- GitOps experience: you understand reconciliation loops, drift detection, and why image automation matters
- Infrastructure-as-code fluency with Terraform or similar across multiple environments and cloud accounts
- You know observability beyond just "set up dashboards". You've defined SLOs, built alerting that doesn't page on noise, and used traces to debug cross-service latency issues.
- Comfortable with secret management patterns (KMS, encrypted configs, external secret operators). You've thought about credential rotation and zero-trust.
- Incident response experience: you've triaged production outages, written postmortems that actually led to improvements, and built runbooks that other engineers could follow
- You write code, not just YAML. Proficiency in Go, Python, or Bash for building tooling, automation, and pipeline scripts
Nice to Have
- Experience with GPU workloads on Kubernetes: device plugins, GPU-aware scheduling, GPU monitoring
- Multi-cloud operations beyond a single provider
- Real-time or streaming workloads: low-latency systems where p99 matters more than average
- Experience with Helm chart authoring and managing complex value layering across environments
- Familiarity with real-time media or relay infrastructure
- FinOps experience: GPU cost optimization, spot/preemptible instance management
What We're Not Looking For
- Engineers who treat infrastructure-as-code as "click around in the console and import later"
- SREs who've only monitored systems but never built the deployment pipelines that ship to them
- Candidates whose CI/CD experience is limited to GitHub Actions for a single-service repo
- People who write alerts that fire every day and then get ignored
Logistics We are based in-person in San Francisco. We are also hiring for this role in Europe for on-call coverage and timezone distribution.
Benefits
- Competitive salary and meaningful early equity
- Visa sponsorship and relocation support
- Generous health, dental, and vision coverage
How this job compares
Set against the 2,370 open DevOps Engineer jobs on Olive Jobs, counted October 30, 2026.
- Pay
- This postingNot listed
- California median$145–220K/yr281 salary ranges
- US median$60–65/hr80 hourly ranges
- Openings
- Olive Jobs lists 362 open DevOps Engineer jobs in California and 2,370 across the US. 9% of them nationwide are listed as remote or flexible.
- Hiring the most in California
- EY22 open
- Apple16 open
- Palo Alto Networks15 open
- Experience
- DevOps Engineer postings that state a minimum ask for 5 years of experience at the median; the middle half ask for 3 to 8 years (2,103 postings).
- Education
- 848 of the 2,370 open DevOps Engineer jobs (36%) ask for a bachelor's degree or higher.
Counted across the open, public US postings on Olive Jobs on October 30, 2026. Pay medians are the middle values of the low ends and of the high ends of postings that list both ends of a range in the same cadence (a yearly salary or an hourly rate); a range's midpoint is halfway between its ends. Pay and experience figures resting on fewer than 20 postings are left out.
You've read the whole posting — now see how you match it.
