Senior Platform Engineer

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.

As we scale toward 600 product engineers, the infrastructure layer that powers everything - Kubernetes clusters, VPCs, compute pools, storage, shared services - becomes mission-critical. Right now, that infrastructure is the single point of failure for every developer-facing capability the platform team builds. You'll be the senior IC responsible for designing, deploying and operating that substrate. This is more than infrastructure management; it's production-quality software engineering applied to infrastructure. You'll build abstractions that let service teams specify their infrastructure requirements at a high level, then turn those into reliable, secure, performant deployments. This role sits at the intersection of deep cloud-native expertise and solid software engineering discipline.

• →Lead the design, deployment and operation of platform-layer infrastructure: VPCs, compute pools, storage, Kubernetes clusters, and the networking that connects them - translating configuration data into inputs for IaC modules provided by Cloud Operations.
• →Own the monitoring and operation of managed pub/sub messaging systems (e.g. Kafka) that service teams depend on.
• →Design and evolve abstractions that allow service teams to express infrastructure requirements at a high level, translating those into production-grade deployments with security and high availability baked in by default.
• →Operate platform infrastructure at 99.9% uptime. Own the change management process for infrastructure changes and drive a > 95% change success rate. Build a strong post-incident learning loop.
• →Work with Cloud Operations to consume their IaC modules and feed back operational lessons and enhancement requests. Maintain a clean module-consumer relationship that protects both functions.
• →Anchor the technical standards for the Shared Services and Infrastructure team: code review quality bar, controller patterns, GitOps idioms, IaC consumption patterns and operational runbooks.
  Mentor junior engineers and set the bar for infrastructure software engineering.

• Software or infrastructure engineering experience, including operating production Kubernetes and cloud-native infrastructure.
• Strong software-engineering fundamentals and hands-on experience with Java.
• Deep Kubernetes expertise and comfort with Linux command line.
• Strong networking and cloud architecture fluency: VPCs, subnets, load balancing, security, service mesh interaction.
• Hands-on experience with IaC tools (Terraform) and GitOps tooling (Argo CD, Flux or equivalent).
• Solid experience participating in production incident response. You're comfortable being on-call for critical infrastructure.
• Working knowledge of observability fundamentals (metrics, logs, traces) and experience consuming platform observability backends.
• Experience mentoring junior engineers; you can set and maintain a technical quality bar.
• A Bachelor's or Master's degree in Computer Science, Engineering or related field, or equivalent professional experience.
• Hands-on experience with GCP (primary), AWS or Azure (preferred).
• Experience designing and operating shared services infrastructure at scale (preferred)
• Familiarity with pub/sub messaging systems like Kafka and their operational characteristics (preferred)
• Experience with service mesh patterns and their infrastructure implications (preferred)