# Member of Technical Staff - ML Platform Engineer at Preference Model > Onsite · United States · Staff · Backend · open. Source: https://alderhq.app/jobs/ashby%3APreference-Model%3Ab77e59f1-e2ef-43c1-88f2-d05c7264479a (read 2026-11-04). ## Facts (observed) - Company: [Preference Model](https://alderhq.app/companies/preference-model) - Location text: San Francisco - Where it can be done from (inferred): Onsite · United States (evidence: "Location: San Francisco") - Posted: 2026-10-27 (7 days ago) - First seen by alder: 2026-11-02 · last verified: 2026-11-03 - Reposted: 0 times · edited: 0 times - Apply on the employer's site: https://jobs.ashbyhq.com/Preference-Model/b77e59f1-e2ef-43c1-88f2-d05c7264479a - Skills listed (inferred): AWS, GCP, Kubernetes, Docker ## Pay and sponsorship - Posted pay: not posted - Market band for similar posted roles (SF Bay Area, n 49): p25 $218k, median $239k, p75 $260k ## Description (the employer's text) ### About Us Preference Model is a superintelligence data research company. We build RL environments for training capable, better-aligned superintelligences. Almost every aspect of how a model behaves is shaped by the reward signals it's trained on. The biggest problem with AIs today is that they don't always do what we intend. Sometimes that's because they aren't capable enough, and sometimes it's because they aren't aligned. Both problems come down to the training objectives. We're trying to address both of these issues in the most direct, highest leverage way available to us, which today means researching how to build RL environments better, not just for the AIs of today but for the AIs as they will be when they outsmart us. Over the past year, we've built RL environments for several frontier labs, and we're backed by $16M in seed funding led by a16z. Our founding team has previous experience on Anthropic’s data team building data infrastructure, and datasets behind Claude. ### About the Role An RL environment is only useful once it runs reliably inside a lab's training stack. Every environment we build has to be packaged, sandboxed, run at scale, checked against each lab's requirements, and delivered in the format that lab's platform expects. Much of that work is still manual today, and it takes time away from the people designing environments. As an MTS on our ML Platform team, you will own the systems that take an environment from a builder's repo to a lab's training run. That includes Karotte, our open-source framework for defining RL environments, the internal platform that builds, runs, and reviews environments on CPU, GPU, and TPU, and the integrations that deliver them to each lab we work with. This is a senior ML platform engineering role where you will ensure what our Capabilities team builds runs and ships cleanly. You'll join a small Platform team and work directly with environment builders and post-training researchers. In your first six months, success looks like a delivery path to each partner lab that is mostly automated: tasks marked ready get built, validated against that lab's requirements, and packaged without hand work. Our needs change quickly, so you'll also pick up other platform and infrastructure work as priorities shift. ### What You Will Do Own the integrations that deliver our environments to partner labs: build container images, match each lab's submission format, and automate the checks that confirm requirements are met before anything ships. Do the delivery work by hand where you have to, then automate it. Build and maintain Karotte, our open-source environment framework, from API design through releases and migrations that keep existing environments working. Run and scale the infrastructure that builds, runs, and grades environments, including containerized rollouts and grading across CPU, GPU, and TPU, VM-based sandboxing, and the resource limits and isolation that stop a model from gaming its own grader. Build the internal tools environment builders use every day (CLI, docs, data catalog, access controls, and run monitoring) so they spend their time on environment design instead of infrastructure. Partner with environment builders and post-training researchers to turn recurring pain points into platform features, and ship quickly in response to their feedback. ### What We are Looking For 5+ years of experience building and owning ML Platform Engineering, ideally AI related ML Platform Engineering Strong software engineering fundamentals and a track record of building and operating production infrastructure or developer platforms that other engineers depend on. Hands-on experience with containers and orchestration (Docker, Kubernetes, or similar) and at least one major cloud platform (GCP, AWS, or similar). A working understanding of how to run untrusted code safely: isolation, resource limits, and what happens when a process fills the disk or refuses to exit. You've owned something tedious end to end, such as a migration, a release process, or a delivery pipeline, and automated away as much of it as you could. --- Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/ashby%3APreference-Model%3Ab77e59f1-e2ef-43c1-88f2-d05c7264479a and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.