Site Reliability Engineer — Miami, FL

About The Role

The role owns the reliability of production infrastructure serving millions of requests per day - Kubernetes clusters, distributed data stores, and the CI/CD pipelines that ship to them. When systems degrade, this is the person who gets paged.

The SRE team sits at the intersection of software engineering and operations, writing code that eliminates toil, building observability that catches incidents before customers do, and setting the SLOs that define what 'reliable' actually means.

Key Responsibilities

• Design, build, and operate production infrastructure on Kubernetes and cloud platforms (AWS/GCP), including autoscaling, multi-region failover, and capacity planning

• Own SLO definitions and error budgets for core services; drive reliability reviews with engineering teams when budgets are burned

• Build and maintain observability tooling - Prometheus, Grafana, OpenTelemetry, distributed tracing - with actionable alerting that minimizes pager noise

• Lead blameless postmortems for production incidents, identifying root causes and driving remediation work to completion

• Automate infrastructure as code using Terraform and Helm; eliminate manual provisioning and configuration drift across environments

• Improve CI/CD pipelines for safe, fast deployments - canary releases, feature flags, automated rollback strategies

• Contribute to on-call rotation and participate in chaos engineering exercises to validate resilience assumptions

What We Are Looking For

• 3–7 years of experience in SRE, DevOps, or infrastructure engineering, running production systems at scale

• Deep hands-on expertise with Kubernetes - cluster operations, troubleshooting, and production incident response

• Strong scripting and software skills in Go, Python, or Bash for building internal tooling and automation

• Production experience with at least one major cloud (AWS, GCP, Azure) and IaC tooling (Terraform)

• Solid understanding of Linux systems, networking fundamentals, and distributed systems failure modes

• Experience defining and operating against SLOs/SLIs, and running postmortem processes

• Bonus: Experience with service meshes (Istio/Linkerd), cost optimization (FinOps), chaos tooling (Litmus, Gremlin), or platform engineering/internal developer platforms