Site Reliability Engineer

About

is the world's leading commerce partnership marketing platform, transforming the way businesses grow by enabling them to discover, manage, and scale partnerships across the entire customer journey. From affiliates and influencers to content publishers, brand ambassadors, and customer advocates,  empowers brands to drive trusted, performance-based growth through authentic relationships. Its award‑winning products –
Performance (affiliate),
Creator (influencer), and Advocate (customer referral) – unify every type of partner into one integrated platform. As consumers increasingly rely on recommendations from people and communities they trust,  helps brands show up where it matters most. Today, over 5,000 global brands, including Walmart, Uber, Shopify, Lenovo, L'Oréal, and Fanatics, rely on  to power more than 225,000 partnerships that deliver measurable business results.

As the Site Reliability Engineer for the Content Intelligence & Regulatory Apps Group, you will own and grow our reliability practice for the systems that index, monitor and enrich social and web content on the  platform. This role focuses on building and professionalizing rather than firefighting. Since the platform is stable, your mission is to implement SRE engineering disciplines (service‑level objectives, observability, runbooks, and structured root‑cause analysis) to ensure reliability is measurable, repeatable, and owned.

You will work with Squad leads, Platform Engineering and Cloud Operations and will own the SLO and RCA practice for the group while partnering closely with other internal and external squads. Your job is to provide them with the framework, tooling, and habits needed to run reliable services, and to act as the central point of contact for reliability across those teams.

This is a software‑engineering‑led SRE role where you will read and write Java, instrument Spring services, tune the JVM, help harden infrastructure, batch processes, data and orchestration flows.

Our guiding principle is to prioritize system stability and data integrity above all else. Because these are business‑critical systems, security and compliance are part of the reliability mandate, not an afterthought: you will build observability, audit trails, and operational practices that are secure and auditable by default, working alongside the central security and Dev Ops teams. Reliability, resilience, data integrity, and compliance take precedence over short‑term feature velocity.

This is a strong opportunity for an engineer ready to step into ownership and grow the role and themselves over time, with the support of the group.

• Own the SLO/SLI practice for CIRA: Define meaningful service‑level objectives and indicators for services on GCP with each squad. Establish error budgets and necessary baselines, applying extra rigor to flows that affect critical business processes.
• Build in security and compliance by default. Treat security and auditability as reliability properties: ensure critical business processes and data flows have the necessary audit trails, and if applicable, forensic‑replay history needed for transactional‑correctness and compliance obligations (e.g. SOX, and PCI‑adjacent concerns). Champion secrets hygiene (Hashi Corp Vault, GCP Secret Manager, SOPS), least‑privilege access to production and data, and audited break‑glass procedures.
  
  Partner with the Cloud Security and Cloud Platform teams rather than duplicating their function.
• Manage vulnerability and patch posture for services: Track and drive remediation of vulnerabilities across the JVM, Spring/Spring Boot dependencies, and container images; help establish patching expectations and surface security‑relevant findings from quality gates (Sonar Qube) and secret scanning (ggshield) so they get prioritized alongside reliability work.
• Own and run root‑cause analysis: Establish a consistent, blameless RCA practice for the group. Drive investigations toward durable fixes and preventative actions while partnering with the owning squad rather than working in isolation. Over time, improve the squads' own troubleshooting and post‑incident habits.
• Bu…