Site Reliability Engineer

MyFitnessPal

1d•$120,000 - $160,000

About The Position

MyFitnessPal is seeking a Software Engineer III - Site Reliability to join its Productivity Engineering: Automation & Self-Service (PEAS) team. PEAS provides automation, CI/CD, and self-service platforms that product teams use to build, test, and ship features safely and quickly. The team is part of Technology Operations, which includes IT, Infrastructure, Security, Reliability, and DevOps/DevEx. Its goal is to provide a secure, reliable, low-friction foundation for building and operating software at scale. The role owns reliability across production services and security in the software delivery pipeline. It defines how reliability is measured and protected, leads incident response, and improves the speed and security of CI/CD pipelines. The engineer works with the Security Engineer and broader Security and Reliability disciplines, owning pipeline security while collaborating on other security responsibilities. The role also supports the on-call rotation, develops sustainable operational practices, and coaches engineers across the organization. The reasonably estimated salary range is $120,000–$160,000. Compensation depends on factors including skills, qualifications, and experience. MyFitnessPal describes its workplace as collaborative and inclusive and provides opportunities for in-person team connections, with teams meeting as needed and the company gathering annually.

Requirements

At least 5 years of experience in site reliability, platform, or infrastructure engineering, with senior-level ownership of production systems.
Strong programming skills for automation and tooling in Go, Python, TypeScript, or similar; experience building software or custom tooling, not just scripts.
Hands-on experience with a major cloud platform, Kubernetes, and Infrastructure as Code.
A track record of leading incident response and building SLO-driven reliability practices.
Working fluency with observability tooling.
Practical experience integrating security into CI/CD pipelines, such as SAST/DAST/SCA tools, dependency scanning, or policy-as-code.
Strong understanding of cloud security fundamentals, including identity and IAM, least-privilege patterns, policies and guardrails, and secrets management.
Judgment and communication skills to raise security or reliability findings with senior engineers and work toward shared solutions.

Nice To Haves

Experience with AWS and Terraform.
Experience with Datadog.
Experience with policy-as-code frameworks, especially Kyverno, or OPA/Rego or Conftest, enforced at admission time.
Exposure to regulated or compliance-driven environments such as SOC 2, PCI DSS, or HIPAA.
Chaos engineering or game-day experience.
Experience supporting high-traffic B2C or mobile backend environments with rapid iteration and strong reliability needs.

Responsibilities

Own and evolve service-level indicator (SLI), service-level objective (SLO), and error-budget frameworks, using them to influence prioritization and product decisions.
Lead incident response, conduct postmortems, and turn findings into systemic fixes.
Build and maintain observability across metrics, logs, and traces using Datadog, improving signal quality and reducing alert fatigue.
Design and operate resilient, scalable infrastructure using Infrastructure as Code, including Terraform.
Manage production Kubernetes and container workloads, including capacity planning and cloud-cost optimization.
Own CI/CD pipelines and safe deployment strategies, including canary releases, progressive rollouts, and fast rollbacks.
Own security controls in the delivery pipeline, integrating and tuning SAST, DAST, and SCA scanning so issues surface during code review.
Implement and maintain policy-as-code to block unsafe infrastructure and Kubernetes changes at admission time.
Drive vulnerability triage and remediation SLAs for pipeline- and infrastructure-level findings, prioritizing by risk.
Partner with the Security Engineer and broader Security and Reliability disciplines, owning pipeline security and collaborating on other security responsibilities.
Participate in and improve the on-call rotation; build runbooks and automation to make on-call sustainable.
Coach team members and engineers across the organization on reliability patterns and operational best practices.