Director of Engineering, Simulation & Rendering

Set technical direction. Own the multi-quarter roadmap for simulation, rendering, and content. Translate company-level objectives into a sequenced plan, and make the prioritization calls when the team can't do everything at once.

Guide technical evolution. Lead the team through the next phase of the platform—incorporating scene reconstruction, neural rendering, and ML-powered content techniques alongside the existing real-time engine stack—without losing sight of the production system our customers rely on today.

Manage and develop the team. Hire when you need to, level up the team you have, and create the conditions where strong technical contributors do their best work.

Drive cross-functional execution. Partner with leaders across ML, platform, SDK, QA, and product to ship coherent, end-to-end capabilities. Own the operating cadence: planning, dependency management, and release readiness.

Stay close to the engineering. You won't be writing production code, but you'll review architecture, weigh in on hard tradeoffs, and have informed opinions about the work.

Leadership track record. 10+ years of engineering experience with at least 5 years leading technical teams, including managing senior individual contributors and ideally other managers.

Domain expertise. A track record of delivering at the intersection of real-time rendering, simulation, or related graphics-heavy domains: video games, computer animation, VFX, virtual production, autonomous simulation, or similar.

Experience leading change. You've taken a team through significant technical change—an engine upgrade, a re-architecture, a tools migration, a shift in content paradigm—and you understand the human side as well as the technical side.

Technical judgment. You can hold your own in a discussion about renderer architecture, asset pipelines, GPU performance, and the tradeoffs between fidelity, performance, and authoring cost.

Communication. You can explain a thorny tradeoff to a non-technical executive in five sentences and write a roadmap the team actually uses.

Unreal Engine. Hands-on background and an opinionated view on its strengths and limitations.

Modern rendering techniques. Familiarity with reconstruction-based methods (gaussian splatting, NeRFs), neural rendering, or diffusion-based content generation.

C++ depth. Track record of leading C++-heavy codebases. Our engineering team works primarily in C++.

Adjacent fields. Direct exposure to machine learning, computer vision, or autonomous systems.