Infrastructure Engineer

You'll be joining the team responsible for the infrastructure behind all of H's products: clusters, networking and security. It's the foundation that lets the rest of the company deliver value directly to customers.

What you'll own

From your first quarter, you'll own a real piece of our move from AWS to an environment-agnostic platform. The team moves fast and the problems are novel: each model release and each new customer changes what the infrastructure has to support.

What you'll be doing

• Running and scaling Kubernetes clusters and networking

• Building authentication and authorization systems

• Refactoring the stack to be environment agnostic

• Speeding up deployment for our Forward Deployed Engineers (FDEs)

• Building Kubernetes-native services, such as controllers and operators

• Writing and maintaining infrastructure as code

Your team and your users

The role sits in the Infrastructure team, with our VP of Engineering as hiring manager. Your users are H's product and platform engineers and, through our FDEs, our external customers.

What we think it takes

You're likely a good fit if you:

• Write Python or Go well enough to solve real problems with it

• Have built and operated a Kubernetes-based platform at significant scale and can put numbers on its clusters, services and users

• Have worked with more than one cloud provider (AWS, Azure, GCP), or have strong knowledge of fundamental systems engineering (Linux, eBPF)

• Have built and owned infrastructure as code, CI/CD and observability

Stronger still if you have:

• Worked with complex network topologies (multi-cluster, dual-stack) and CNIs such as Cilium or Calico

• Handled petabyte-scale data, or high-frequency, latency-sensitive workloads

• Worked with agentic systems, particularly in security

• Worked with GPUs and tools such as Dynamo, vLLM or SGLang

How we hire

Five stages, about 3.5 hours in all: a 30-minute call with our Talent team, a 30-minute conversation with the lead of the Infrastructure team, a 60-minute coding interview, a 60-minute system design interview and a closing 30-minute conversation with our VP of Engineering.