Key Responsibilities
AI Vibe Coding
AI Researchers use Cursor, Claude Code, and other AI coding tools to build and ship not only research code but also data pipelines and product features directly. You own the path from model to real user experience, and contribute across the whole product, not just inside one lane.
- Write training pipelines, evaluation tools, and product integration code with AI coding tools.
- Lead with sharp ML craft, and contribute with code to backend, frontend, and desktop app surfaces.
- This role starts with working directly in DOR's recording and editing features to create the data you'll train on, and shifts toward world model training and the research built on top of it as that data comes together.
- Work directly in DOR's recording and editing features to decide, at the product level, which signals get captured and at what cadence, and build the data your experiments need.
- Define the alignment rules that handle the frame drops and timestamp drift caused by screen, key input, and voice being captured on different clocks, and turn the footage that comes with recorded actions — out of the 200 million videos accumulating each month — into trainable sequences.
- Design and train game world models that take observations and actions and predict the next state.
- Design latent state representations that compress high-bandwidth signals like the screen, learn transitions conditioned on key inputs on top of that state, and experiment with where signals like voice belong — signals that sit closer to player intent than to the state of the environment.
- Roll the learned model forward many steps to see what's coming, and look back at how things would have gone if a different action had been taken in the same situation.
- Define the criteria for measuring how far a prediction can be trusted, and decide what to validate counterfactual predictions against when no ground-truth trajectory exists.
- Experiment with agents that plan actions or learn policies by rolling the future forward inside the model without touching the real game, and explore applications such as in-game elements and NPC generation that only become possible once the dynamics are learned.
Key Challenges in This Role
The on-device detection models that ship inside the product belong to the AI/ML Engineer role, while this position sits upstream of them and does the research that learns the dynamics of the game itself, which makes the problems below especially important.
- Learning dynamics under partial observability, where the screen is one player's field of view rather than the full game state, and whatever happens off-screen leaves no trace in the observation
- Learning transitions when your own key inputs alone don't determine the next frame, and the actions of the other players that caused the change are never recorded in the data
- Judging how long a trained model stays valid under non-stationarity, since a patch or a shift in the meta changes the dynamics and the screen together
- Defining, from the ground up, where a prediction stops being trustworthy, in a setting where error compounds every time you chain one more step
- Deciding what to predict and in which space: predicting the next frame yields a learning signal without labels, but matching raw pixels spends most of the loss on background and UI
- Deciding what counts as a single step, when the screen and the key inputs are captured on different clocks — a question that is already a model design decision
Products You'll Build
Play Capture and Editing (Record · Edit)
- Improve the recording experience so the moments users don't want to miss are captured more precisely.
- Improve the editing experience so users work with their own gameplay more often and more deeply.
- Design capture along the way so that screen, key input, and voice stay locked to a shared timeline.
Game World Model (World Model)
- Find the layer at which dynamics are shared, even across games with different rules and different screens.
- Validate whether the learned representation can explain the context that the detection models already running in the product miss.
- Make the product better at judging which moments matter as the model gets better.
Prediction and Generation (Predict · Generate)
- Verify in the product how knowing what happens next changes the user experience.
- Explore new product experiences, such as in-game elements and NPCs, that only become possible once the dynamics are learned.
- Make research results carry through into features users actually use inside DOR.
How We Share Our Research
We encourage putting research out into the world. The company supports conference talks, paper submissions, and open-source releases, and where something collides directly with product competitiveness, we scope that part together.
Compute for experiments is provided by the company, sized to the research in flight.
How We Work
- DOR builds products that customers want, not products the CEO wants.
- We repeat problem definition, hypothesis, execution, measurement, and learning in short 1-2 week iterations.
- AI Researchers do research that doesn't end at a paper -- they follow the models they train all the way to the point where those models touch real users' gameplay.
- We build fast, validate fast, and adjust direction fast.
- We focus on creating real impact based on data and user feedback.
- We value results that connect not only to performance metrics but also to user experience.
Tech Stack
We don't expect experience with every stack. However, we expect you to learn and pick things up quickly.
AI / Research
- Python
- PyTorch
- World Model
- Action-Conditioned Prediction
- Latent Dynamics / State Space Model
- Sequence / Video Modeling
- Model-based RL / Planning
- Counterfactual Reasoning
- Generative Model
Data / Infra
- Data Pipeline
- Large-scale Video / Audio Processing
- Multimodal Data Alignment
- Distributed Training
- Experiment Tracking
Qualifications
- Experience designing and training deep learning models yourself, whether in lab research, a course project, or a personal project
- Able to design your own experiments in Python and PyTorch and interpret the results
- Experience reading papers or public code and implementing them yourself to see them run
- Experience turning unstructured data into something a model can train on
- Uses AI coding tools (Cursor, Claude Code, etc.) heavily for experiment pipelines and for writing code
- Able to go beyond research code and fix the product code where the data is created
Preferred Qualifications
- [Top priority] Experience building experiment pipelines or research prototypes yourself with AI tools
- Research experience in world models, latent dynamics, sequence modeling, video generation, reinforcement learning (especially model-based RL), or planning
- Have reimplemented a world model or a sequence · video modeling paper yourself, and written up what reproduced and what didn't
- Published or submitted a paper, or contributed to open-source projects
- Currently in a master's or PhD program in machine learning, or have done research in a lab
- A gamer or someone with a deep understanding of gameplay context
You'd Be a Great Fit If You Are...
- Someone who defines problems that don't have answers yet and digs until they do
- Someone who wants to push their own research agenda on data you can't get at school
- Someone who doesn't separate building the model from building the data it learns from
- Someone who wants their research to live on as papers and public code
- Someone who wants to build game world models on the play data of gamers worldwide
What to Highlight in Your Resume
- Tell us which problems you've solved so far and why you chose them. Course projects and personal research count.
- If you've designed and trained a model yourself, tell us the problem definition, your approach, and the attempts that failed.
- If you've reproduced a paper or public code, tell us what reproduced and what didn't.
- If you've turned unstructured data into something a model can train on, describe it concretely.
- Leave links we can check — papers, open-source contributions, Kaggle, lab internships, personal projects.
- Rather than listing work history and credentials, we'd love to see your problem definition, thought process, actions, learnings, and outcomes.
Hiring Process
01
Application
Submit resume and portfolio
02
Role / Culture Fit Interview
Assess values alignment and working style
03
Task-based Interview
Conducted if needed · Includes reference check
04
Offer Negotiation
Negotiate salary and stock options, then join the team
The entire hiring process is completed within 7 days. During intensive hiring periods, we'll reach out quickly at each stage.
View All Positions →