Infrastructure Engineer (ML Compute) - Paris

Hcompany
Europe
Hybrid

Who this role is best for

Best suited to candidates with hands-on GPU and Kubernetes experience working in a hybrid, geographically distributed infrastructure setting.

Best fit for

  • Candidates with experience building and running GPU workloads on Kubernetes and debugging OS-level issues
    — “Have built and run GPU workloads on Kubernetes”
  • Individuals who can design complex GPU clusters from scratch and manage multi-cloud environments
    — “Could design a GPU cluster for training and online RL from scratch”
  • Candidates who have managed distributed infrastructure and have a track record of shipping operational improvements
    — “By month 3, you’ll be handling a share of cluster incidents on your own and will have shipped one change to scheduling or node health”

Things to consider

  • Requires hybrid work arrangement with three days in-office per week in Paris or London
    — “The role is hybrid, with three days a week in our Paris or London office”
  • Involves occasional travel between Paris and London for collaboration
    — “occasional travel between the two”

How to stand out

  • Highlight experience with Kubernetes scheduling tools like Karpenter or Kueue in your resume and interviews
    — “Kubernetes scheduling and autoscaling tools such as Kueue or Karpenter”
  • Demonstrate your ability to debug and resolve GPU, Linux, and network issues through specific examples
    — “Debugging failures in GPUs, Linux, storage and networking”
  • Showcase your Python development skills, particularly in infrastructure automation or system tools
    — “Write strong Python”
  • Emphasize any experience with cloud provider management or capacity planning
    — “Managing capacity with our cloud providers”
Pace · Fast PacedCollaboration · HighAutonomy · MediumDecision Impact · Team

Derived from job-description analysis by Serendipath's career intelligence engine.

What success looks like

  • running gpu clusters
  • improving gpu scheduling
  • managing cloud capacity
  • debugging gpu failures
Typical background
experience with gpu workloads on kubernetes

Skills & requirements

Required

KubernetesGpu ManagementLinuxNetworkingStoragePython

Preferred

SlurmKubernetes Scheduling ToolsMulti-cloud OrchestrationAws ServicesHigh-performance InterconnectsTerraform

Stack & domain

KubernetesGPULinuxPython

About the role

Original posting from Hcompany via Ashby

You’ll own the GPU compute that powers our model training, evaluation and serving systems.

This role sits in our Infrastructure team, which works at the lowest layers of our stack, from Kubernetes down to the GPU hardware. You’ll run the clusters, GPUs and schedulers that our research, product and platform teams depend on, and manage the capacity we buy from our cloud providers.

WHAT SUCCESS LOOKS LIKE

Success is measured by how well we use our GPUs: keeping production reliable and improving the performance of our training and serving stack.

WHAT YOU’LL BE DOING

  • Running Kubernetes clusters for GPU training and inference
  • Improving how GPU work is scheduled and placed
  • Detecting, draining and repairing unhealthy GPU nodes
  • Managing capacity with our cloud providers
  • Debugging failures in GPUs, Linux, storage and networking

THE FIRST YEAR

By month 3, you’ll be handling a share of cluster incidents on your own and will have shipped one change to scheduling or node health, such as automatically detecting and draining unhealthy GPU nodes. By month 6, you’ll own one part of the compute layer outright: scheduling and placement, node health and repair, or capacity and new regions. By month 12, you’ll be responsible for a globally distributed GPU system that shifts capacity between training and inference as needs change.

WHO YOU’LL WORK WITH

Your hiring manager is our VP of Engineering. Day to day, you’ll work with the Platform Infrastructure team, the research and product teams who use our compute, and our cloud providers and other vendors.

WHAT WE THINK IT TAKES

You’re likely a good fit if you:

  • Have built and run GPU workloads on Kubernetes
  • Could design a GPU cluster for training and online RL from scratch
  • Debug confidently at the OS layer and below (Linux, GPU drivers, networking and storage)
  • Write strong Python

It’s a plus if you’ve worked as an SRE or infrastructure engineer, or have used:

  • Slurm
  • Kubernetes scheduling and autoscaling tools such as Kueue or Karpenter
  • Multi-cloud orchestration tools such as SkyPilot
  • AWS services such as EKS or SageMaker HyperPod
  • High-performance interconnects and collective communication libraries such as EFA, InfiniBand, NCCL or Open MPI
  • Terraform

You don’t need ML research experience. If you match most of this but not every point, please apply.

HOW WE HIRE

Four stages, about three hours in total: a 30-minute call with our Talent team, a 60-minute coding interview, a 60-minute system design interview and a closing 30-minute conversation with our VP of Engineering. The coding and system design interviews are modelled on real-world problems you’d face in this role.

PRACTICALITIES

The role is hybrid, with three days a week in our Paris or London office and occasional travel between the two. We offer a competitive package.

Source: Hcompany careers (Ashby)

Similar roles