Research Engineer

San Jose, California, United States; New York City, New York, United States; New York, New York, United States Full-time On-site 11/19/2026 Job ID: 000611
Apply Now
Training language models Fine-tuning language models Post‑training language models Reinforcement Learning tuning (RLHF, RLAIF, RLVR, GRPO-family, agentic RL) Memory and context for long‑running agents

Summary

What you’ll impact

The Senior Machine Learning Engineer designs, builds, and scales the post‑training stack—including reinforcement learning pipelines, memory/context systems, and inference infrastructure—for enterprise‑grade large language models. They use Python, PyTorch or JAX, and distributed GPU clusters to create synthetic landscape generators, knowledge‑graph pipelines, and high‑throughput RL environments. Responsibilities include developing data generation pipelines, implementing offline evaluation harnesses, optimizing training and inference throughput, and establishing reproducibility and experiment‑tracking standards. Collaboration with research scientists drives end‑to‑end experiments and ensures the platform’s reliability and scalability.

Responsibilities

What you'll do

  • Build and scale the post-training stack: SFT, preference optimization, and reinforcement learning for long-horizon tool use, transformation, and reconciliation over enterprise systems. RL is the center of gravity of this role, not a side interest.
  • Build the memory and context machinery that long-horizon agents run on: what an agent retains across a forty-step run, how it's structured, retrieved, compacted, and revised — and how you train a model to use it well rather than bolting it on at inference.
  • Build the representation layer that agents reason over — ontologies and knowledge graphs derived from real enterprise systems — and the pipelines that construct, validate, and keep them current.
  • Design and implement data generation and curation pipelines — synthetic landscapes, transformation traces, tool-call trajectories, curriculum infrastructure — that teach models to operate systems no public model has seen.
  • Build the RL environments: sandboxed landscapes and execution-and-verification harnesses where a change can be applied, checked, and scored automatically, backed by design-partner traces where synthetic data won't do.
  • Build and run the offline eval harness for long-horizon agentic behavior — trajectory-level scoring, task suites, and the infrastructure that makes a result reproducible six weeks later. You own the harness; the methodology it implements is a shared argument with Research Science.
  • Run experiments end to end — design, launch, debug, analyze — and be honest about which effects are real and which are noise.
  • Optimize training and inference throughput: kernels, parallelism strategies, memory, batching, serving. Long context matters here more than most places; a single enterprise artifact can eat a context window.
  • Take a training result from "the eval moved" to "it's serving traffic" — quantization, serving configuration, rollback path.
  • Establish standards for reproducibility, experiment tracking, and result hygiene, so findings survive contact with the next person who builds on them.

Requirements

What you’ll bring

  • Have significant experience training, fine-tuning, or post-training language models, and can point to results you owned. RL tuning experience — RLHF, RLAIF, RLVR, GRPO-family, or agentic RL — is close to a requirement rather than a bonus.
  • Have thought hard about memory and context for long-running agents, whether through architecture, retrieval, or training.
  • Have strong software engineering fundamentals — the code you write for experiments is code other people can run.
  • Are fluent in Python and PyTorch (or JAX), and comfortable debugging distributed training when the loss curve does something inexplicable.
  • Can design, run, and interpret an experiment with real empirical rigor. You look at data and distinguish an effect from noise from a bug.
  • Have worked with GPU infrastructure at scale and know where the time and the memory go.
  • Want your research to end up in production, and treat that as the interesting constraint rather than the tax.
  • Communicate clearly in writing. We make decisions from documents.

Ready to Move Forward?

Apply now and our recruiting team will reach out with next steps, interview guidance, and client insights tailored to this role.