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 · United States
Live, first seen by us 22 days agoLocation type: HybridFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: Research & EngineeringFrom the employer’s posting
Design experiments that show whether a data change helps: baselines, small-scale proxies, scaling ladders, held-out loss and targeted evals.
Build and run production pipelines that feed real training runs at scale, and make them reproducible and traceable.
Work with pre-training, post-training and eval teammates to understand what they need from data, and propose the next most useful thing to work on.
Own a part of the pre-training data stack end to end, for example a quality filter, a dedup or decontamination pass, a synthetic or distillation data source, or a mixture or curriculum experiment, from question to shipped result. Design experiments that show whether a data change helps: baselines, small-scale proxies, scaling ladders, held-out loss and targeted evals. Report null and negative results as clearly as wins. Keep the loop scientifically valid: check for contamination and benchmark leakage, watch for benchmark noise, and flag when a quality gain costs diversity.
Keep the loop scientifically valid: check for contamination and benchmark leakage, watch for benchmark noise, and flag when a quality gain costs diversity. Build and run production pipelines that feed real training runs at scale, and make them reproducible and traceable. Work with pre-training, post-training and eval teammates to understand what they need from data, and propose the next most useful thing to work on.
Build and run production pipelines that feed real training runs at scale, and make them reproducible and traceable. Work with pre-training, post-training and eval teammates to understand what they need from data, and propose the next most useful thing to work on. Experience & Capabilities
Strong Python, experience with large-scale data processing, and practical experience training or fine-tuning models (PyTorch preferred).
Experience with small or efficient models and with how architecture changes should affect data strategy.
From the employer’s posting.
Spun out of MIT CSAIL, we build general-purpose AI systems that run efficiently across deployment targets, from data center accelerators to on-device hardware, ensuring low latency, minimal memory usage, privacy, and reliability.
In the employer’s words · Read in context · Company website ↗
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 22
Similar jobs usually come down between day 7 and day 76.
From 6,389 similar postings that came down. Coming down is not always a hire.
4 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add 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.
- Evidence you've connected a data change to a model outcome, through an experiment you designed and can explain, including what you'd do differently. - Strong Python, experience with large-scale data processing, and practical experience training or fine-tuning models (PyTorch preferred). - Agency paired with judgment. For example, you spotted a problem nobody assigned, explained why it mattered, and fixed it. Or you killed your own approach when the data said so. Or you chose not to build something and saved the team time.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Spun out of MIT CSAIL, we build general-purpose AI systems that run efficiently across deployment targets, from data center accelerators to on-device hardware, ensuring low latency, minimal memory usage, privacy, and reliability. We partner with enterprises across consumer electronics, automotive, life sciences, and financial services. We are scaling rapidly and need exceptional people to help us get there.
You'll join the Pre-Training Data team, which decides what Liquid Foundation Models learn from: which data we source, filter, synthesize, and mix, and in what order. Public data sources are plateauing, so model quality increasingly depends on purpose-built datasets and on knowing which data changes actually help.
We treat data as a research problem, not an infrastructure problem. You'll work alongside our pre-training researchers on a small team, run the experiments that settle data questions, and build the pipelines that carry the answers into training runs.
We need someone who:
Thinks like a researcher, ships like an engineer: You build the pipelines and you make the model-facing calls about what goes into them. You don't hand off either half.
Leads with a hypothesis: Before changing a dataset, you can say what it should do to the model, what you'll measure, and what could fool you, such as contamination or a noisy benchmark. You hold views on pre-training pitfalls, and you test them.
Owns problems end to end: You take ambiguous work from open question to shipped result with little direction or process, do the unglamorous parts that get it there, and don't care whose job it was.
Own a part of the pre-training data stack end to end, for example a quality filter, a dedup or decontamination pass, a synthetic or distillation data source, or a mixture or curriculum experiment, from question to shipped result.
Design experiments that show whether a data change helps: baselines, small-scale proxies, scaling ladders, held-out loss and targeted evals. Report null and negative results as clearly as wins.
Keep the loop scientifically valid: check for contamination and benchmark leakage, watch for benchmark noise, and flag when a quality gain costs diversity.
Build and run production pipelines that feed real training runs at scale, and make them reproducible and traceable.
Work with pre-training, post-training and eval teammates to understand what they need from data, and propose the next most useful thing to work on.
What you'll need:
Hands-on depth in at least one substantial area of pre-training or mid-training data, for example web-scale curation, quality filtering, dedup or decontamination, mixtures or curricula, or synthetic data and distillation. We don't expect mastery of every technique.
Evidence you've connected a data change to a model outcome, through an experiment you designed and can explain, including what you'd do differently.
Strong Python, experience with large-scale data processing, and practical experience training or fine-tuning models (PyTorch preferred).
Agency paired with judgment. For example, you spotted a problem nobody assigned, explained why it mattered, and fixed it. Or you killed your own approach when the data said so. Or you chose not to build something and saved the team time.
A clear account of your own contribution: what you decided, what tradeoff you made, and what changed because of you.
Pragmatism: you size experiments to the compute, time and team you have, and build just enough process.
Helpful, not required:
Experience with small or efficient models and with how architecture changes should affect data strategy.
Long-context data, knowledge distillation, or eval-framework work.
Open-source data tools or datasets with real adoption, or published data research.
You own a critical pre-training data pipeline end to end
Data systems you built or improved have measurably moved model performance
You've identified and integrated at least one external dataset that moved the needle
Upstream of every model: Pre-training data shapes every Liquid Foundation Model. On a small team, the mixtures, filters, and synthetic data you build go straight into the models we ship.
Compensation & Equity: Competitive base salary plus equity, so you share in what we build. Final offers reflect skills, experience, and location.
Time Off: Unlimited PTO, plus company-wide Refill Days, long weekends when the whole company rests together.
Health & Wellbeing: Comprehensive health coverage, with details varying by location.
Paid Leave: Paid leave for pregnancy, parenting, medical needs, and caring for family.
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.
United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.