Senior Site Reliability Engineer

Juniper Square; United States; On-site; USD 140,000 - 190,000; Full time

Job summary

Juniper Square is seeking a Senior Site Reliability Engineer II to scale our infrastructure and reliability practices as our engineering organization expands by 90+ engineers this year.

You will own reliability and observability for your team's systems, working hands-on across Kubernetes, AWS, and CI/CD, partnering with 16+ engineering teams to roll out standards and automation that reduce friction org-wide.

Qualifications

• 8–10 years of experience as a Senior SRE, DevOps, or Infrastructure Engineer.
• Hands-on with Kubernetes (EKS/ECS), CI/CD pipelines, and Helm/Argo.
• Experience with AWS services and database technologies (Postgres, DocumentDB).
• Familiarity with Infrastructure as Code tools (Terraform, Crossplane).
• Comfortable driving change across cross-functional teams and leading incident response.

Responsibilities

• Own reliability and observability across the organization, SLAs/SLOs, instrumentation, and on-call health.
• Design, deploy, and maintain Kubernetes infrastructure (Helm, EKS/ECS) and core AWS services.
• Build and maintain CI/CD pipelines (GitHub Actions, Argo, Helm).
• Drive adoption of IaC standards across multiple teams and lead cross-team rollouts.
• Lead incident response and root-cause analysis for cross-team issues.
• Use AI tools to improve workflow and assist teammates.

Skills

Kubernetes

AWS

CI/CD

Helm

Argo

Terraform

Crossplane

GitHub Actions

Datadog

Tools

Postgres

DocumentDB (Mongo)

RDS/Aurora

Job description

• We're looking for a Senior Site Reliability Engineer II to help us scale our infrastructure and reliability practices as we grow our engineering org by 90+ people this year
• You'll take ownership of reliability and observability for your team's systems, work hands-on across Kubernetes, AWS, and CI/CD, and partner with 16+ engineering teams to roll out standards and automation that reduce friction org-wide
• This role is for someone who's proactive by nature - you see a problem and go fix it without waiting to be asked
• You're comfortable working across teams with different workflows and priorities, and you're already using AI tools as part of how you build, debug, and ship
• You won't be working in a vacuum: you'll partner with a Staff-level architect and engineering leadership on the biggest calls, while owning execution and cross-team rollout yourself
• Own reliability and observability across the organization - SLAs/SLOs, instrumentation, and on-call health
• Design, deploy, and maintain Kubernetes infrastructure (Helm, EKS/ECS) and core AWS services (RDS/Aurora Postgres, networking, scaling)
• Build and maintain CI/CD pipelines in GitHub Actions and Argo/Helm
• Drive adoption of Infrastructure as Code standards (Terraform, and increasingly Crossplane) across multiple teams
• Partner with 16+ engineering teams to roll out new standards, tools, and processes - adapting the rollout to how each team actually works
• Participate in on-call rotation and lead incident response/root-cause analysis for issues that cross team boundaries
• Use AI tools daily to work faster and more effectively, and help less AI-fluent teammates pick up the same habits
• Represent SRE's perspective in planning conversations with engineering leadership

Real database experience with Postgres and DocumentDB (Mongo) across RDS/AuroraDeep hands-on experience with Kubernetes (EKS or ECS), GitHub Actions, Terraform, CI/CD pipelines, and Helm/Argo8-10 years of experience as a Senior SRE, DevOps, or Infrastructure EngineerAlready using AI as part of your actual workflow (coding, debugging, design)Background at smaller-to-mid-size, high-growth SaaS companies (Series A/B through C/D) - you know how to move fast and own ambiguity, not navigate a large, slow-moving orgA track record of working cross-functionally - managing timelines, setting expectations, and collaborating with other teams' engineers, not just your ownCrossplaneDatadogProactivity and bias to action - you don't wait for permission to fix what's brokenComfort driving change across teams with different priorities and some natural resistanceGenuine fluency talking through your own technical decisions in depth - the "how" and "why," not just the "what"