Senior Site Reliability Engineer II

Ovii's Interpretation of the Role

Senior Site Reliability Engineer II responsible for organization‑wide reliability, observability, and infrastructure automation. Works hands‑on with Kubernetes, AWS, Terraform and CI/CD pipelines while partnering across dozens of engineering teams.

Role Snapshot

• Own reliability & observability (SLAs/SLOs, on‑call)
• Design & operate Kubernetes & core AWS services
• Build CI/CD pipelines with GitHub Actions & Argo
• Drive IaC standards (Terraform, Crossplane)
• Partner with 16+ engineering teams for rollout
• Lead incident response and root‑cause analysis
• Leverage AI tools daily

Must-Have Requirements

• Kubernetes (EKS/ECS)
• AWS services (RDS/Aurora, networking)
• Terraform
• GitHub Actions
• Helm & Argo CD
• PostgreSQL & DocumentDB (Mongo)
• AI tools usage
• Senior SRE/DevOps/Infrastructure engineering
• Kubernetes
• AWS
• CI/CD pipelines
• Postgres & DocumentDB

Nice-to-Have Signals

• Crossplane
• Datadog

Work Setup

• Location: USA, USA
• Work mode: REMOTE
• Remote scope: COUNTRY_RESTRICTED
• Remote countries: USA
• Employment type: Full-Time

Not Specified in JD

• Visa sponsorship
• Relocation
• Security clearance
• Travel
• Shift
• Notice period
• Coding test
• Portfolio
• GitHub
• Writing sample
• Cover letter

What You'll Likely Work On

• Define and maintain reliability targets, monitoring, and on‑call health across the platform
• Architect, deploy and sustain Kubernetes clusters and associated AWS services
• Create and evolve CI/CD pipelines using GitHub Actions and Argo/Helm
• Champion Infrastructure‑as‑Code practices, expanding Terraform usage and introducing Crossplane
• Collaborate with 16+ engineering squads to adopt standards, tools and processes
• Participate in on‑call rotation and lead cross‑team incident investigations
• Integrate AI tools into daily workflows and mentor teammates on their use
• Advocate the SRE perspective in planning and leadership discussions

Good Fit If You Have

• Proactive bias to action – fixes problems without waiting for direction
• Comfort driving change across teams with differing priorities
• Strong communication of technical decisions, explaining both how and why