Site Reliability Engineer, K8s (Remote International)

PulsePoint operates large-scale data and advertising platforms that power business-critical services used every day across the company.

Our Platform Engineering team owns the foundation that enables engineering teams to move quickly and safely. We build and operate the infrastructure that supports Kubernetes workloads, data platforms, developer tooling, observability and production operations at scale.

Unlike many cloud-only environments, we own the full lifecycle of the infrastructure - from bare-metal hardware and networking to Kubernetes, observability and developer experience.

The environment supports large-scale Kubernetes workloads, multi-petabyte data systems and business-critical services used across multiple engineering organizations.

We're looking for an experienced engineer to help shape its next stage of growth.

This is a hands-on role focused on architecture, reliability, automation and operational excellence. You will work on complex distributed systems, drive platform improvements and help shape the technical direction of infrastructure across the company.

You'll help design, build and operate the Kubernetes platform used across PulsePoint.

Examples of challenges you may work on include:

• Platform architecture and Kubernetes lifecycle management

• Reliability, observability and incident response

• Infrastructure automation and GitOps workflows

• Platform tooling and automation in Go, Python and Bash, including AI-assisted engineering workflows

• Networking, service connectivity and platform security

• Developer experience and self-service platform capabilities

• Large-scale distributed systems running on bare-metal infrastructure

You'll work in an environment that includes:

• Kubernetes and platform services

• Multi-petabyte data infrastructure

• Bare-metal and cloud environments

• GitOps and infrastructure automation

• Modern observability and reliability engineering practices

Technologies commonly used across the environment include Kubernetes, ArgoCD, Puppet, Terraform, OpenTelemetry, Prometheus, Alertmanager, Kafka, Redis and Ceph.

Experience with every technology is not required.

Success in this role is not measured by the number of tickets closed or clusters operated. Success means building platform capabilities that make engineering teams more reliable, productive and autonomous.

We're especially interested in engineers who:

• Have operated production infrastructure at meaningful scale

• Understand how distributed systems fail and recover

• Prefer automation over repetitive operational work

• Enjoy simplifying systems rather than adding complexity

• Take ownership beyond the boundaries of a single component

We also expect solid fluency with code. This is not a software developer role, and we won't ask you to solve algorithm puzzles. But code is a daily working tool here, and we expect you to use it the way an engineer does. Our infrastructure tooling is written in Go, Python and Bash, so we're looking for comfort with these rather than with application-level stacks.

• Read and understand code you didn't write: Helm charts, operators and controllers, Terraform modules, Puppet code, internal Go/Python tooling, and upstream open-source projects when debugging a production issue

• Write automation and tooling in Go, Python or Bash (scripts, CLIs, controllers, pipelines) that is simple, tested, observable and maintainable by the rest of the team

• Use LLM assistants to speed up writing code, configs and investigations, while staying fully accountable for the result: you review, test and understand every change before it reaches production

• Recognize when generated code is wrong, unsafe or over-complicated, and when not to use it at all

• Treat code as part of the system: review it, version it, roll it out and roll it back safely

This is not a ticket-driven operational role.

You'll help define platform architecture, influence engineering standards and work on infrastructure that supports multiple engineering organizations.

The engineer joining this role is expected to become a key technical contributor shaping the future of the platform.

Location and Hours:

You'll be required to work 9am-6pm ET U.S. hours because it is necessary for on-call rotation.

We can hire FTEs in the U.S., UK, Germany, India, and the Netherlands. In other countries, we can hire as long-term contractors via Deel (payment is monthly, 40 hours/week).

We try to keep the process focused and practical:

1. Introductory conversation (~60m)
   Learn about your background and discuss the role.

2. Technical discussion (~60m)
   Deep dive into systems engineering, Kubernetes and operational experience.

3. Code and tooling discussion (~60m)
   Work through reading, reviewing and writing infrastructure code, including AI-assisted workflows.

4. Leadership conversation (~30m)
   Meet engineering leadership and discuss team, strategy and long-term direction.