Senior Site Reliability Engineer
Certifyos
| Company | Certifyos |
| Category | Engineering |
| Location | Remote US |
| Remote | Remote |
| Employment | Not stated |
| Level | Senior |
| Salary | Not stated by the employer |
| Posted | 17 Jun 2026 |
| Last verified | 2 Aug 2026 |
| Source | Employer career page (ashby) |
Description
About CertifyOS
CertifyOS is building the data infrastructure that powers modern healthcare.
Today, healthcare organizations rely on fragmented and outdated provider data. This creates unnecessary administrative work, regulatory risk, and higher costs across the system. We’re solving that problem.
Our API-first platform automates provider licensing, enrollment, credentialing, and network monitoring by connecting directly to hundreds of primary data sources. We help healthcare organizations maintain accurate, compliant, and reliable provider networks at scale.
Our vision is simple: One API. One provider ID. Frictionless provider data.
We’re backed by leading investors and built by a team with deep experience in provider data systems. At CertifyOS, we value authenticity, accountability, collaboration, results, and openness to feedback. We’re building a high-ownership team focused on solving real infrastructure problems that impact millions of patients.
ABOUT THE ROLE
We’re looking for a Senior Site Reliability Engineer who takes ownership seriously — someone who designs for reliability, ships the automation, and stands behind it in production. You’ll work across cloud-native infrastructure on systems that process millions of provider records.
This is a role with real scope: you’ll own the operational lifecycle end-to-end and influence platform architecture, reliability standards, and deployment workflows across systems that matter.
HOW WE WORK
We ship fast, but we don’t ship sloppy. SREs at CertifyOS own the full lifecycle of what they support — from infrastructure design and deployment automation through observability, incident response, and postmortems. We use AI-assisted tooling aggressively to reduce toil and accelerate troubleshooting, which raises the floor on the problems we tackle — not an excuse to reduce rigor. If you do your best work reacting to incidents, this probably isn’t the right fit. If you do your best work preventing them, we should talk.
PROBLEMS YOU’LL SOLVE
Healthcare provider data infrastructure is a distributed systems problem at scale. Hundreds of upstream integrations, inconsistent data sources, and evolving workloads all introduce operational complexity and reliability risk.
Reliability and observability at scale. You’re operating a platform hundreds of integrations depend on. How do you maintain uptime, reduce alert fatigue, and build actionable observability across GKE and Cloud Run without drowning in noise? Meaningful SLIs, error budgets, and data quality signals — not just p99 latency.
Scaling infrastructure efficiently. As platform usage grows, infrastructure costs and operational complexity grow with it. You’ll improve autoscaling behavior, resource utilization, and workload efficiency across cloud-native distributed systems.
Incident response and operational maturity. Production incidents are inevitable; operational chaos is optional. You’ll own incident response processes, root cause analysis, escalation workflows, and runbooks — and make hard problems not happen again.
Infrastructure automation and developer velocity. You’ll build and maintain Infrastructure as Code, CI/CD pipelines, and operational tooling that reduce manual work and improve engineering productivity without sacrificing reliability.
Reliability engineering for data platforms. Uptime isn’t enough — you need to know when a provider record is stale, a pipeline is lagging, or a workload is behaving unexpectedly. You’ll instrument data freshness and infrastructure health, not just service uptime.
WHAT WE’RE LOOKING FOR
RELIABILITY ENGINEERING FUNDAMENTALS
- 5+ years in SRE, DevOps, Platform Engineering, or Infrastructure Engineering — operating production systems at scale where your infrastructure is someone else’s dependency and failures have real downstream consequences
- Track record of improving reliability end-to-end: you’ve debugged hard