> Markdown version of [/jobs/ext/4505914-ai-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/4505914-ai-infrastructure-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# AI Infrastructure Engineer

- **Company:** Thinking Machines Lab Inc.
- **Location:** New York, NY, United States
- **Experience:** Experienced
- **Salary:** $350,000.0
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, C++ (Programming Language), Software Debugging, Linux, Distributed Computing Environment, Distributed Systems, Fault Tolerance, InfiniBand, Job Scheduling, Python (Programming Language), Machine Learning, Networking Basics, Remote Direct Memory Access, Reliability Engineering, Software Engineering, AI Infrastructure, Reinforcement Learning, Pytorch, Kubernetes, Slurm
- **Published:** November 2, 2026
- **Apply:** https://www.careerbuilder.com/job-details/ai-infrastructure-engineer-new-york-ny--16490cd2-ae0b-4f30-afbe-ca96ca3a289e

## About the Role

Artificial Intelligence (AI), Artificial Intelligence (AI), Reinforcement Learning, Reliability Engineering, Automation, Debugging Skills, Machine Tool, On Call, Rotational Modeling, Production Support, * 4+ years of experience as a production engineer, site reliability engineer, or infrastructure engineer operating large-scale distributed systems in production

 * Track record debugging complex failures across distributed systems - networking, hardware, kernel, or scheduler issues
 * Strong software engineering skills in Python and/or Go/C++, with the judgment to know when to script a fix versus build a system
 * Solid grounding in Linux systems internals and networking fundamentals
 * Comfortable owning production systems, including participating in on-call rotations, * Experience operating GPU or TPU training clusters at scale
 * Familiarity with post-training and RL techniques (e.g., RLHF, PPO, DPO) and the infrastructure challenges specific to them, such as reward model serving, rollout generation, and mixed training/inference workloads
 * Experience with distributed training frameworks (e.g., PyTorch, Ray) and job schedulers (e.g., Slurm, Kubernetes)
 * Experience with high-performance networking (e.g., InfiniBand, RDMA, NCCL) and its role in distributed training performance
 * Experience building observability tooling purpose-built for ML training, not just general infrastructure
 * A track record of thriving in fast-changing, research-driven environments where priorities shift with the science

## Description

Were hiring an AI Infrastructure Engineer to keep our post-training and reinforcement learning (RL) systems fast, reliable, and easy for researchers to iterate on. Think of this as a production engineering or site reliability role built around model training: youll own the health of the training runs, clusters, and pipelines that power post-training and RL at Thinking Machines.

Youll work side by side with research teams during active model runs - debugging failures in real time, hardening infrastructure against the next class of problem, and building the tooling and automation that let researchers spend their time on the science instead of babysitting jobs. This role has real ownership: youll be the person a research team calls when a run stalls at 2am, and the person who makes sure it doesnt happen again.

What You'll Do

 * Own the reliability, performance, and uptime of large-scale post-training and RL training jobs, from launch through completion
 * Partner directly with research teams during active model runs, embedding with them to unblock training and speed up iteration
 * Debug failures across the full stack - accelerators, networking, storage, schedulers, and training frameworks - and drive issues to root cause
 * Build monitoring, alerting, and automated recovery so runs self-heal or fail fast instead of silently stalling
 * Improve checkpointing, fault tolerance, and job scheduling so hardware failures cost minutes, not days of compute
 * Build internal tools that reduce toil and improve cluster utilization across post-training and RL workloads
 * Participate in an on-call rotation supporting production model runs
 * Write postmortems and turn recurring failure patterns into permanent infrastructure fixes