Pay
$166K–$240K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,279 postings in the last year. Stated ranges, not salaries paid.
US - Remote
Live, first seen by us 14 days agoEmployment type in the employer’s posting: FULL_TIMEFrom the employer’s posting
Fetch is built on real purchase data shared by millions of users scanning their receipts.
As a Senior MLOps Engineer, you’ll own the systems and practices that make Fetch’s models production-ready, observable, reproducible, and resilient.
Own model lifecycle from validation and deployment through retraining, rollback, and retirement
Build monitoring for data quality, drift, prediction quality, latency, and infrastructure cost
Build reusable training, evaluation, and deployment pipelines for multiple models
Develop orchestration workflows with scheduling, retries, backfills, and failure recovery
Build and maintain a model hub linking documentation, evaluation, releases, and monitoring
Fetch is built on real purchase data shared by millions of users scanning their receipts. Data Science turns that signal into predictive models that generate valuable user intelligence for our stakeholders and partners. Those models need a reliable operational foundation to move confidently from experimentation into production and continuously improve over time.
As a Senior MLOps Engineer, you’ll own the systems and practices that make Fetch’s models production-ready, observable, reproducible, and resilient. You’ll partner closely with Data Science and Engineering across the full model lifecycle, including training, validation, deployment, versioning, monitoring, retraining, and retirement.
Own the complete model lifecycle from experimentation through validation, deployment, versioning, retraining, rollback, and retirement.
Build monitoring for data quality, drift, prediction quality, service reliability, latency, and infrastructure cost.
Build reusable training, evaluation, and deployment pipelines that support multiple models and modeling approaches.
Develop dependable orchestration workflows covering dependencies, scheduling, retries, backfills, and failure recovery.
Build and maintain an accessible model hub connecting model documentation, evaluation results, release history, versioning, and monitoring.
5+ years managing production ML systems beyond initial deployment, including monitoring, retraining, incident response, and continuous improvement.
Hands-on experience using Spark for distributed data processing.
Experience with a workflow orchestration engine for scheduling, dependency management, retries, backfills, and recovery.
Hands-on experience building infrastructure with Terraform.
Experience deploying and operating containerized production workloads on Kubernetes.
Experience building reusable training, evaluation, or deployment infrastructure used by multiple models, scientists, or teams.
Experience developing platform services, infrastructure, or internal tooling in Go.
Experience building or owning a model registry, model hub, or similar system used by technical and nontechnical stakeholders.
Experience supporting ML systems where outcome labels are delayed or model quality cannot be measured immediately.
Experience designing configurable ML infrastructure that supports several modeling frameworks or approaches.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$166K–$240K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,279 postings in the last year. Stated ranges, not salaries paid.
Day 14
Similar jobs usually come down between day 6 and day 69.
From 4,296 similar postings that came down. Coming down is not always a hire.
29 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.
- 5+ years managing production ML systems beyond initial deployment, including monitoring, retraining, incident response, and continuous improvement. - Strong production software development skills in Python and proficiency with SQL. - Hands-on experience using Spark for distributed data processing.
- Hands-on experience building infrastructure with Terraform. - Experience deploying and operating containerized production workloads on Kubernetes. - Experience building reusable training, evaluation, or deployment infrastructure used by multiple models, scientists, or teams.
- Strong production software development skills in Python and proficiency with SQL. - Hands-on experience using Spark for distributed data processing. - Experience with a workflow orchestration engine for scheduling, dependency management, retries, backfills, and recovery.
- Experience with a workflow orchestration engine for scheduling, dependency management, retries, backfills, and recovery. - Hands-on experience building infrastructure with Terraform. - Experience deploying and operating containerized production workloads on Kubernetes.
Complete your application on jobs.gem.com. The employer’s form will show what is required.
Already applied? Track this application
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.
US - Remote
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.