About the role

THE ROLE: OpenMind is building the operating system for robotics: the models that let robots understand people, context, and norms well enough to work alongside humans safely. Our models run on real robots with real customers, and every deployment produces new data to learn from. You will be the engineer who turns research into models that run reliably on physical robots. You will build the training, evaluation, and inference systems behind our models. You will work with a continuous stream of real-world embodied data, including egocentric video, lidar, audio, state-action logs, and the robot's own reasoning traces, collected from humanoids and quadrupeds operating in public spaces.
WHAT YOU WILL DO: Build multimodal perception models that make robots socially aware, such as active speaker detection, person tracking across camera and lidar, and engagement estimationBuild and scale the pipelines that turn multi-hour, full-stack robot logs into curated, labeled datasets for training, evaluation, and external data partnershipsShip models as containerized services in our OM1 deployment stack, and own their latency, reliability, and regressions in the fieldWork closely with our research lab, robotics engineers, and deployment teams to move models from prototype to production on physical robots within weeksIntegrate, fine-tune, and optimize foundation models for real-time perception and reasoning on embedded computeWHAT WE LOOK FORMS or PhD in machine learning, robotics, computer science, or a related field 1+ years of industry or applied research experience training and shipping machine learning modelsStrong engineering fundamentals in languages such as Python, Go, and/or C++, and fluency in PyTorch or JAXHands‑on experience with multimodal models, perception, or reinforcement and imitation learningExperience running models on edge hardware under real latency and memory constraints, such as the NVIDIA Jetson software stackExperience with TensorRT, ONNX, or other inference optimization toolchainsExperience with ROS2 and Docker‑based deployment on robotsExperience building datasets or benchmarks used outside your own teamPublications at CoRL, RSS, ICRA, NeurIPS, ICML, or ICLRA bias toward models that work in the real world, not only on benchmarks

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this