Pay
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,537 postings in the last year. Stated ranges, not salaries paid.
San Francisco, California, United States
Actively hiring, first seen by us 3 days agoEmployment type in the employer’s posting: FullTimeFrom the employer’s posting
You'll build and maintain the ML systems and pipelines that our research runs on top of data pipelines, training infrastructure, evaluation tooling, deployment, observability.
Build and maintain training, evaluation, and deployment pipelines for research
Take research code from prototype to production: refactor, harden, instrument, test
Design observability into ML systems (metrics, logs, traces, eval dashboards)
Own data pipelines for training and evaluation: ingest, dedup, version, validate
Set engineering standards across the ML stack (testing, reviews, runbooks)
You'll build and maintain the ML systems and pipelines that our research runs on top of data pipelines, training infrastructure, evaluation tooling, deployment, observability. The work bridges research and production, and you'll be the person who makes "we ran an experiment" actually mean "we ran it correctly, at scale, with results we trust."
Build and maintain the training, evaluation, and deployment pipelines that our research runs on
Take research code from prototype to production: refactor, harden, instrument, test
Design observability into our ML systems (metrics, logs, traces, eval dashboards) so failures surface fast
Own data pipelines for training and evaluation: ingest, dedup, version, validate
Set engineering standards across our ML stack (testing, reviews, runbooks)
6+ years building production-grade ML systems
Track record across the full lifecycle: data, training, evaluation, deployment, monitoring
Strong distributed systems experience
Fluent Python, fluent with at least one of (PyTorch, JAX)
Comfortable with experimentation infrastructure (Ray, Slurm, Kubernetes, or similar)
We're building autonomous research agents for recursive self-improvement (multi-agent systems that propose, run, and analyze machine learning experiments).
In the employer’s words · Read in context
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,537 postings in the last year. Stated ranges, not salaries paid.
Day 3
Early. Similar jobs usually come down between day 7 and day 76.
From 6,398 similar postings that came down. Coming down is not always a hire.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
be on - Fluent Python, fluent with at least one of (PyTorch, JAX); comfortable at the systems-level when needed - Comfortable with experimentation infrastructure (Ray, Slurm, Kubernetes, or
- Fluent Python, fluent with at least one of (PyTorch, JAX); comfortable at the systems-level when needed - Comfortable with experimentation infrastructure (Ray, Slurm, Kubernetes, or similar)
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
ABOUT THE COMPANY
We're building autonomous research agents for recursive self-improvement (multi-agent systems that propose, run, and analyze machine learning experiments). We're a small, well-funded team that works onsite in San Francisco.
ABOUT THE ROLE
You'll build and maintain the ML systems and pipelines that our research runs on top of data pipelines, training infrastructure, evaluation tooling, deployment, observability. The work bridges research and production, and you'll be the person who makes "we ran an experiment" actually mean "we ran it correctly, at scale, with results we trust."
This is a senior ML engineering role. You'll own systems end-to-end. You'll work with researchers daily and translate research code into infrastructure that the team can rely on. You'll move fast and you'll be measured on whether your systems make the team faster.
WHAT YOU'LL DO
- Build and maintain the training, evaluation, and deployment pipelines that our research runs on
- Take research code from prototype to production: refactor, harden, instrument, test
- Design observability into our ML systems (metrics, logs, traces, eval dashboards) so failures surface fast
- Own data pipelines for training and evaluation: ingest, dedup, version, validate
- Work closely with researchers to understand what they need, what's slow, and what's brittle
- Set engineering standards across our ML stack (testing, reviews, runbooks) so the team scales
- Contribute to architectural decisions that shape how research and
production interacts
WHAT WE'RE LOOKING FOR:
- Senior ML engineer with 6+ years building production-grade ML systems
- Track record across the full lifecycle: data, training, evaluation, deployment, monitoring
- Strong distributed systems experience; you've shipped systems that have to
be on
- Fluent Python, fluent with at least one of (PyTorch, JAX); comfortable at the systems-level when needed
- Comfortable with experimentation infrastructure (Ray, Slurm, Kubernetes, or
similar)
- Bias toward shipping; you prefer working code over working diagrams
- Strong written communication
NICE TO HAVE:
- Experience building experimentation platforms or research infrastructure
at a frontier ML lab
- Background in distributed training systems
- Open-source contributions to ML infrastructure
- History of working effectively with small senior teams
THIS ROLE IS PROBABLY NOT FOR YOU IF:
- You want to do research with engineering as a side activity: this is engineering as the main thing
- Cross-functional work with researchers (translation, scoping, education) doesn't appeal
- Long-running ownership of running systems isn't appealing: this role has it
SPONSORSHIP SUPPORT
We sponsor visas to help exceptional talent join our team and support long-term immigration pathways where applicable.
New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under ML Engineer, by the work the posting describes.
ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.
Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.
A data scientist often works out which model to build; an ML engineer makes it run reliably in production.
The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
- Long-running ownership of running systems isn't appealing: this role has it SPONSORSHIP SUPPORT We sponsor visas to help exceptional talent join our team and support long-term immigration pathways where applicable.