Site Reliability Engineer

About impact.com

impact.com 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, impact.com 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, impact.com 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 impact.com to power more than 225,000 partnerships that deliver measurable business results.

Your Role at impact.com**:**

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 impact.com 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 DevOps 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.

What You'll Do:

• 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 (HashiCorp 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 (SonarQube) 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.
• Build and mature observability for critical services: Become the group's point person for the observability stack (e.g., Grafana). Build and standardize monitoring, dashboards, tracing, and alerting using Open Telemetry that surface the health of systems, services, infrastructure and business/transactional processes — without leaking PII data into logs, traces, or dashboards — while creating reusable patterns that squads can adopt.
• Keep performance and resource metrics within thresholds: Track response latency, JVM heap/GC behavior, thread-pool saturation, CPU/memory consumption, cloud costs, error rates, and uptime across all services (e.g. Java, Spring Boot, NodeJs etc). Turn findings into prioritized improvements in collaboration with the squads.
• Improve batch and orchestration reliability: Help harden batch jobs and support the migration toward durable workflow orchestration to reduce partial-failure windows and manual idempotency.
• Support database performance and query optimization: Monitor the groups databases (e.g. MySql, SingleStore, Elastic, GCP Spanner) for slow queries, indexing, lock contention, and connection-pool health. Flag operational or performance risks in Liquibase migrations before they ship.
• Understand client-generated workloads: Learn how brand, agency, and partner workloads translate into resource consumption. Help confirm that consumption aligns with contract tiers and surface anomalous traffic patterns as both a reliability and a security signal, escalating suspected abuse to the security team.
• Establish alerting and runbook standards: Define the group's conventions for actionable alerts and runbooks to ensure on-call engineers across squads can respond quickly and consistently.
• Troubleshoot across the stack: Address issues in the JVM/application, Spring container, MySQL, Pub/Sub messaging, Feign/REST and legacy RMI/HTTP-Invoker integrations, GKE/GCE, network, and client-generated workloads. This requires growing depth in JVM and database performance (profiling and query optimization). Remediation may include code/query optimizations, JVM/connection-pool tuning, rate-limit or autoscaling configuration, retry/backoff changes, or escalating heavy-request patterns.
• Make the delivery path safer: Partner with squads to improve CI/CD (Jenkins/Github Actions) and GitOps deploys (ArgoCD + Helm), including health checks, readiness/liveness probes, progressive rollouts, and rollbacks for finance services.
• Inform capacity and cost: Help analyze platform usage to attribute costs to customers and workloads, inform capacity planning, and identify efficiency improvements. Partner with Cloud Operations (FinOps).
• Leave things more reliable than you found them: Improve tests, observability, and operability each time a service is touched, and grow the group's reliability guardrails into a shared, durable practice.
• General: Other duties as assigned by the Company. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions.

What You Bring:

• Experience: 3+ years in SRE, software engineering, or systems/operations roles supporting production services, with the appetite to own and grow a reliability practice.
• Systems Design: Solid understanding of systems and application design, with the ability to reason about reliability, failure modes, and performance.
• Java: Able to read, debug, and make changes to Java/Spring code today, wit