Time since we first saw it
Day 94
Up longer than most. 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.
AI/ML Engineer (MLOps-Focused) Location On-site, San Francisco · Experience 5–7 years · Compensation $150,000–$275,000 + equity About BurntRead the full posting
Employment type in the employer’s posting: FULL_TIMEFrom the employer’s posting
Build and deploy demand forecasting models, backtested on real order books
Design the ontology and knowledge graph that resolves product and vendor SKUs
Fine-tune LLMs with LoRA and PEFT, and build the evals that decide what ships
Build drift detection and retraining pipelines that keep models current
Engineer Spark data pipelines over messy multi-tenant supply chain data
Build and maintain time series forecasting models that serve production traffic and hold up under backtest against real order books.
Design and maintain the ontology and knowledge graph our agents reason over.
Fine-tune LLMs with LoRA and PEFT on our own data, and build the evals that decide what ships.
Build the versioning, drift detection, and retraining pipelines that keep models honest after launch.
Engineer data pipelines at scale with Spark, over messy multi-tenant supply chain data.
Burnt isn't building software on top of ERPs.
In the employer’s words · Read in context
Open 3 monthsWe first saw this posting 94 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 94
Up longer than most. 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.
1 open job
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.
You should be fluent in most of this and able to ramp fast on the rest: - Core: Python at expert level. This is the whole job, not a nice-to-have. - Data: Apache Spark and the surrounding data engineering ecosystem.
If you do not clear every line below, this is not the right role. We screen on these first, no exceptions: - Python at an expert level. Demonstrable, not claimed. - ML models, not agents, deployed and maintained in production.
- Knowledge graph: Neo4j, RDF, OWL, SPARQL, or similar. - Application layer: enough TypeScript and React to be useful in our codebase. You don't need to have shipped a frontend last quarter, but you do need to be willing to. What we expect you've done
- Build the versioning, drift detection, and retraining pipelines that keep models honest after launch. - Run the AWS ML stack: SageMaker at the core, with S3, Glue, and Step Functions around it. - Architect the systems your models live inside, not just the models, and own those design decisions.
- Data: Apache Spark and the surrounding data engineering ecosystem. - Platform: AWS SageMaker as the core platform, plus S3, Glue, Step Functions and the rest. - MLOps: MLflow, Kubeflow, or equivalent.
- Worked inside systems backed by ontologies and knowledge graphs. - Operated across the AWS ecosystem beyond SageMaker. - Engineered data pipelines at scale with Spark.
- ML models, not agents, deployed and maintained in production. - AWS SageMaker hands-on. - A time series forecasting model in production. Hard filter, no exceptions.
- Platform: AWS SageMaker as the core platform, plus S3, Glue, Step Functions and the rest. - MLOps: MLflow, Kubeflow, or equivalent. - Fine-tuning: LoRA and PEFT libraries such as HuggingFace PEFT or TRL.
- Forecasting: Prophet, NeuralForecast, statsmodels, or similar. - Knowledge graph: Neo4j, RDF, OWL, SPARQL, or similar. - Application layer: enough TypeScript and React to be useful in our codebase. You don't need to have shipped a frontend last quarter, but you do need to be willing to.
- Core: Python at expert level. This is the whole job, not a nice-to-have. - Data: Apache Spark and the surrounding data engineering ecosystem. - Platform: AWS SageMaker as the core platform, plus S3, Glue, Step Functions and the rest.
- MLOps: MLflow, Kubeflow, or equivalent. - Fine-tuning: LoRA and PEFT libraries such as HuggingFace PEFT or TRL. - Forecasting: Prophet, NeuralForecast, statsmodels, or similar.
Complete your application on jobs.gem.com. The employer’s form will show what is required.
Already applied? Track this application
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.
AI/ML Engineer (MLOps-Focused) Location On-site, San Francisco · Experience 5–7 years · Compensation $150,000–$275,000 + equity About Burnt
Burnt HQ
AI/ML Engineer (MLOps-Focused) Location On-site, San Francisco · Experience 5–7 years · Compensation $150,000–$275,000 + equity About Burnt
No clear work-authorization passage found. Eligibility is unconfirmed.