The Rendering Infrastructure team owns the foundational systems the broader Rendering team builds on top of: asset and scene ingestion, GPU memory and resource management, acceleration structure construction, packaging and deployment, profiling infrastructure, and the core engine abstractions of our physically-based sensor simulation system. We also own how the renderer connects to the AV stack and world simulator, as a library or a service, and how consumers configure it — what it produces, at what fidelity, and how it behaves when something goes wrong.
We sit between the rendering algorithms team and everyone who consumes simulated sensor data — perception training, closed-loop validation and reinforcement learning. We care about determinism, throughput per GPU, iteration speed, and infrastructure that stays comprehensible as it scales.
Why Join Us?
Work on hard systems problems with an unusually clear definition of success — reproducibility, timing fidelity, frames per second per GPU, and worker spin-up time are all measurable, and all of them matter. Own meaningful surface area: the AV stack integration and transport layer, the sensor scheduling and timing model, multi-world rendering on a single GPU, or the runtime deployment and asset delivery path, depending on your strengths.
Sit at the center of the simulation stack, where rendering, perception, and infrastructure meet, and see your work used across the organization for perception training, closed-loop simulation, and reinforcement learning. Join a team that pairs rigor — design documents, reproducibility, profiling, and regression testing — with pragmatic engineering and short feedback loops.