🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Senior Software Engineer, RL Post-Training Frameworks Experience: Not Available to Not Available years Location: Santa Clara, California, United States Skills: Python, C++, Reinforcement learning, RLHF, PPO, GRPO, DPO, reward modeling, PyTorch, FSDP, tensor parallelism, pipeline parallelism, Kubernetes, NCCL, NVLink, InfiniBand, Megatron-LM, FSDP2, TP, DP, PP, MoE, quantization-aware training, mixed precision, vLLM, SGLang, TensorRT-LLM, Ray, Monarch Company Overview Reinforcement learning post-training is driving some of the most significant capability gains in AI today. It is the process that teaches a model to reason through hard problems, follow complex instructions, and act as an autonomous agent. It is also one of the hardest infrastructure challenges in the field. RL requires inference, rollout generation, and training running in a continuous loop. The rollout step is what makes it hard: the model must interact with environments, tools, and other models to produce the signal that drives learning. Coordinating actor, critic, and reward models across heterogeneous hardware at scale pushes the limits of what distributed systems can do. NVIDIA is building an RL Frameworks engineering team to develop the open-source tools and infrastructure that AI researchers and post-training teams depend on. The team spans the full software stack, from collaborating closely with the researchers and labs pushing the frontier, to contributing to RL frameworks like VeRL, Miles, and TorchTitan, to improving the distributed runtimes they depend on, including Ray and Monarch. Whether your strength is working with researchers to understand and address their need optimizing deep learning frameworks, or building distributed infrastructure, we want to hear from you. Come join us to build the systems that enable the next generation of AI. What you will be doing: You will architect and build RL post-training infrastructure that scales efficiently from experimentation on a single GPU to production across thousands of nodes. This means tuning RL training-inference-rollout loops on GPUs, CPUs, and LPUs for performance where it matters, contributing to and improving the performance and usability of open-source RL frameworks, and partnering with the teams who own them. The role also spans fault tolerance, elastic scaling, and fast restarts so long-running distributed training jobs survive failures, stragglers, and resource contention. Beyond GPU-accelerated training, this work includes partnering with teams building CPU-driven rollout workloads, including tool-use, code execution, and agentic environments, supplying the systems and framework engineering needed to run them efficiently alongside GPU- or LPU-accelerated generation and GPU-accelerated training. It also means advocating for researcher and partner needs with NVIDIA's networking, math library, and compiler teams so the capabilities RL workloads require get prioritized and delivered, and working with hardware teams to take advantage of next-generation hardware capabilities in post-training workloads. What we need to see: MS or PhD in Computer Science, Computer Engineering, or a related field (or equivalent experience) 5+ years of professional experience in distributed systems, high-performance computing, deep learning infrastructure, or ML systems engineering Strong proficiency in Python and C/C++ Demonstrated experience building or contributing to large-scale distributed systems or runtime frameworks in production at a frontier AI lab, hyperscaler, or major technology company Strong verbal and written communication skills and the ability to collaborate across organizational and geographic boundaries Depth in one or more of the following technical areas: Reinforcement learning for LLM post-training (RLHF, PPO, GRPO, DPO, reward modeling), including how algorithms map to distributed execution and the systems challenges they create (heterogeneous placement, rollouts, environment execution, resharding between training and generation) PyTorch internals, including distributed training primitives (FSDP, tensor parallelism, pipeline parallelism) and their composition Kubernetes runtime internals (container lifecycle, pod scheduling, resource quotas, GPU allocation) End-to-end distributed systems design (service boundaries, data flows, consistency models, failure modes, recovery approaches) Experience in any of the following areas is a plus: Deep expertise in networking (NCCL, NVLink, InfiniBand), advanced multi-dimensional parallelisms (Megatron-LM, FSDP2, TP/DP/PP, MoE), or memory optimizations (quantization-aware training, mixed precision) Experience integrating high-performance inference engines (vLLM, SGLang, TensorRT-LLM) into RL training loops for GPU-accelerated rollout Strong background in actor- and task-based distributed programming (Ray, Monarch, or comparable systems) Familiarity with multi-turn training, multi-agent co-evolution, or VLM .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.