Member of Technical Staff (Software Engineer, Inference & Training Platform)
Apply at source. Perplexity handles the application directly; Houtini doesn't take a fee from candidates or companies. We curate which companies appear; the listings come from yubhub.
What the team is looking for.
We are looking for a Member of Technical Staff (Software Engineer, Inference & Training Platform) to join our AI Research & Systems team.
The successful candidate will be responsible for building a self-serve compute platform, operating a large GPU fleet, solving for GPU scarcity, supporting two different workloads, owning Kubernetes for GPU orchestration, making failure boring, and setting technical direction across teams.
The compensation range for this position is $250K - $485K.
Responsibilities
- Build a self-serve compute platform. Design and own the systems that let inference engineers and researchers launch training jobs and operate inference services without managing GPU provisioning, cluster configuration, or provider-specific infrastructure.
- Operate the GPU fleet. Own provisioning, lifecycle management, reliability, and capacity integration across providers, giving teams a consistent way to use compute regardless of where it runs.
- Solve for GPU scarcity. Build the scheduling and placement logic that finds available capacity across providers, packs it efficiently, and gets the right workload onto the right hardware under real constraints.
- Support two very different workloads. Keep long-running distributed training jobs healthy while simultaneously guaranteeing the availability and latency of production inference services on the same fleet.
- Own the Kubernetes for GPU orchestration. Write the operators and CRDs, and manage many clusters across providers so the platform behaves the same everywhere we run.
- Make failure boring. Build the fault tolerance, autoscaling, and observability that keep the fleet utilized and let workloads survive node loss, provider hiccups, and capacity shifts without human intervention.
- Set technical direction across teams. Partner with inference and cloud infrastructure engineers to turn operational constraints into a coherent platform architecture and roadmap.
Qualifications
- Deep Kubernetes experience , custom operators, CRDs, and multi-cluster federation, not just running kubectl apply.
- You've managed GPU clusters at scale: NVIDIA hardware, CUDA, and the networking that makes them fast (InfiniBand or RoCE).
- You've orchestrated compute across multiple clouds (CoreWeave, AWS, GCP, or similar) and understand how different each one really is.
- Strong distributed systems fundamentals: scheduling, resource allocation, and fault tolerance under load.
- You write infrastructure and systems-level code in Go, Rust or C++.
- You've supported both long-running training jobs and high-availability inference services, and you know why they pull infrastructure in opposite directions.
- You own problems end-to-end and do well when the path forward isn't laid out for you.
Additional experience we value
- Inference serving stacks: vLLM, SGLang, or TensorRT-LLM.
- Slurm or other HPC schedulers.
- GPU kernel work in CUDA or Triton , not required, but notable.
- High-speed interconnects: InfiniBand, RoCE, or RDMA in production.
- Observability for ML workloads: Prometheus, Grafana, or Weights & Biases.
- Kubernetes
- GPU clusters
- distributed systems
- Go
- Rust
- C++
- cloud computing
- Inference serving stacks
- Slurm
- GPU kernel work
- high-speed interconnects
- observability for ML workloads
Other roles you might consider.
Filtered through the same AI-companies allowlist.
Research Scientist, Life Sciences (Computational)
Anthropic
Product Manager, Safeguards (Verticals)
Anthropic
Power Systems Engineer (Data Center Infrastructure)
SpaceXAI
Electrical Reliability Engineer (Data Center Infrastructure)
SpaceXAI
Harness Engineer
OpenAI
Backend Software Engineer, API Enterprise Controls
OpenAI
New to AI work? Start with these.
Six pieces of orientation. Most AI-company job specs assume you've done this kind of hands-on work already. If you haven't, an afternoon with one of these is the cheapest way to close the gap.
Claude Desktop, from zero.
The agentic-AI assistant most of the people you'd be working alongside use every day. Install, configure, first useful prompts.
What MCPs areThe best MCPs for Claude Desktop.
MCP servers extend an AI assistant with tools and data. The catalogue most teams use. Useful technical context for any AI-engineering role.
Code with AIClaude Code, the complete beginners' guide.
The CLI for AI-paired development. Required reading if you're applying for any engineering role that mentions agents, or any role full stop.
Run a local modelHow to set up LM Studio.
Running a model on your own machine teaches you more about how AI products work in three hours than a year of using ChatGPT will.
The hardware realityBeginner's guide to AI hardware.
What the infrastructure under the model actually looks like. Useful context for infrastructure, applied-AI and hardware roles.
Browse the stackMCP catalogue.
Eleven MCP servers Houtini maintains or recommends. Each detail page describes a real piece of working AI infrastructure.