Pay
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,507 postings in the last year. Stated ranges, not salaries paid.
Washington, District of Columbia, United States
Actively hiring, first seen by us 1 day agoWork setup in the employer’s posting: On-siteFrom the employer’s posting
Employment type in the employer’s posting: Full-timeFrom the employer’s posting
Build reproducible training, validation, and retraining pipelines with versioned data and artifacts
Design model-serving systems and APIs for latency, scaling, and rollback
Build feature pipelines, model registries, and automated release controls
Set up monitoring and alerting for drift, model performance, and cost
Create reusable libraries and delivery pipelines that take models from experiment to production
Reproducible training, validation, tuning, and retraining pipelines with versioned data, code, parameters, environments, and model artifacts.
Model-serving systems and APIs designed for appropriate latency, throughput, availability, scaling, and rollback.
Feature pipelines, feature stores, model registries, lineage records, approval workflows, and automated release controls.
Monitoring and alerting for data quality, drift, model performance, fairness, infrastructure health, latency, and cost.
Reusable libraries, templates, environments, and delivery pipelines that give data scientists a tested path from experiment to production.
An opening may emphasize predictive models, computer vision, natural language models, ranking, anomaly detection, recommender systems, edge inference, generative AI model operations, or an enterprise ML platform. Some openings will focus more on model development, while others will focus more on serving and platform engineering. Specific openings may name Python, SQL, Java, model frameworks, distributed-processing tools, cloud ML services, container orchestration, graphics processing units, feature stores, model registries, experiment tracking, or infrastructure as code. OPEN Data Jobs will identify the required depth for each opening Benefits
OPEN Data Jobs (ODJ) is built to craft data careers.
In the employer’s words · Read in context
Actively hiringFirst seen by us 1 day 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,507 postings in the last year. Stated ranges, not salaries paid.
Day 1
Early. Similar jobs usually come down between day 7 and day 76.
From 6,269 similar postings that came down. Coming down is not always a hire.
23 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordCheck the employer’s posting for the current role and application details.
Already applied? Track this application
About OPEN Data Jobs
OPEN Data Jobs (ODJ) is built to craft data careers. We connect high-potential data, AI, and software professionals with meaningful work on the cutting edge of the federal sector, and our aim reaches beyond any single opening: to help you understand your strengths, find the right role, and grow throughout your career.
ODJ is organized around Roles and Openings. A Role is a durable career type, such as Data Engineer or AI Engineer: it describes the work, the skills that count, and where the path can lead. An Opening is a specific position hiring right now, with a level, a location, and an application. Roles help you see where you fit; from there, there is more than one way to move.
Today, you can apply to any Opening that fits you through our secure application system. You can also register for a Role to express interest in that broader category of work. A Role registration is not an application to every future Opening.
The work
Machine Learning Engineers make machine learning and AI models reproducible, deployable, scalable, and supportable. They build the path from training data and experimentation to a versioned model service that can be released, monitored, retrained, and retired without guesswork.
The role centers on the model lifecycle and the platform beneath it. Machine Learning Engineers automate training and validation, manage features and model artifacts, optimize inference, implement machine learning operations (MLOps), and watch for changes in data, behavior, performance, reliability, and cost. They create the shared tooling that lets data scientists and application engineers move models into production safely.
What you'll build
· Reproducible training, validation, tuning, and retraining pipelines with versioned data, code, parameters, environments, and model artifacts.
· Model-serving systems and APIs designed for appropriate latency, throughput, availability, scaling, and rollback.
· Feature pipelines, feature stores, model registries, lineage records, approval workflows, and automated release controls.
· Monitoring and alerting for data quality, drift, model performance, fairness, infrastructure health, latency, and cost.
· Reusable libraries, templates, environments, and delivery pipelines that give data scientists a tested path from experiment to production.
Who you are
You are comfortable at the seam between modeling and software engineering. You can inspect a model, harden a pipeline, diagnose a production failure, and improve the platform so the same class of problem is easier to prevent next time.
You value repeatability over heroics. You work closely with data scientists on model behavior, data engineers on reliable inputs, AI Engineers on application integration, and platform and security teams on the environment in which the model runs.
What you bring
· Strong programming and software-engineering practice, including testing, version control, packaging, automation, and production debugging.
· Working knowledge of model development, evaluation metrics, feature engineering, data splitting, tuning, and the limits of different modeling approaches.
· Experience with training and inference pipelines, containers, cloud or on-premises compute, artifact management, and automated deployment.
· Practical MLOps experience with model registries, lineage, reproducibility, monitoring, drift analysis, retraining, release controls, and rollback.
· The ability to balance model quality with reliability, interpretability, security, privacy, latency, throughput, and cost.
Register for Machine Learning Engineer Role
Click Apply below to register for Machine Learning Engineer Role.
Requirements
What openings may require
An opening may emphasize predictive models, computer vision, natural language models, ranking, anomaly detection, recommender systems, edge inference, generative AI model operations, or an enterprise ML platform. Some openings will focus more on model development, while others will focus more on serving and platform engineering.
Specific openings may name Python, SQL, Java, model frameworks, distributed-processing tools, cloud ML services, container orchestration, graphics processing units, feature stores, model registries, experiment tracking, or infrastructure as code. OPEN Data Jobs will identify the required depth for each opening
Benefits
Compensation, benefits, work location, and employment terms are set for each specific opening and will be stated with that opening
New ML Engineer postings at the employers we follow are up 12% 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.
Washington, District of Columbia, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting