Senior Site Reliability Engineer

Ivo Inc.•San Francisco, CA

6d•$248,000 - $405,000•Onsite

About The Position

Infrastructure Engineers build the foundation for Ivo’s entire platform. Customers are cagey about their contracts, so each customer gets their isolated environment with containers, database, VPC, etc. Things break. Regions go down. Cloud and LLM providers have “incidents.” Customers still expect us to hit our SLAs. We’re looking for an Senior Site level Reliability Engineer as part of Infrastructure team to own uptime, reliability, and performance end-to-end, define and enforce SLI, SLO and SLA targets, design failover + disaster recovery that actually works in real scenarios, turn data residency requirements into real systems (geo-fencing, regional isolation, etc.), implement security controls that pass audits and don’t slow the product to a crawl, build observability that answers: what, why and how often it broke?, and lead incident response + write postmortems that make people actually read. This isn’t a “keep the lights on” role. You’ll be building the system that keeps the company running. In addition to helping us run a solid, high-performance distributed system, we’d love someone who’s as excited about LLMs as we are. You’d be deeply embedded into the engineering team and highly encouraged to push the frontiers.

Requirements

Minimum 5 years of professional experience
Thinks in failure modes
Designs systems that keep working anyway
Can translate “this clause in a contract” into actual infrastructure constraints

Nice To Haves

Experience working in a startup environment is preferred but not required.
Excited about the adventure of building a company!
As excited about LLMs as we are.

Responsibilities

Own uptime, reliability, and performance end-to-end
Define and enforce SLI, SLO and SLA targets
Design failover + disaster recovery that actually works in real scenarios
Turn data residency requirements into real systems (geo-fencing, regional isolation, etc.)
Implement security controls that pass audits and don’t slow the product to a crawl
Build observability that answers: what, why and how often it broke ?
Lead incident response + write postmortems that make people actually read