Mlops Engineer Jobs
Mlops Engineer jobs are open across tech, finance, healthcare, and e-commerce, from junior to staff and principal level, with specializations in model deployment, pipeline automation, and infrastructure reliability. Find a role that fits from the openings below and apply directly.
Find Mlops Engineer JobsLooking for remote work? View remote mlops engineer jobs →Overview
Showing 5 of 58+ Mlops Engineer jobs








About Gallatin
At Gallatin, we are rebuilding logistics infrastructure for the national security missions of the United States and allied partners. We build AI systems that determine how logistics decisions are made — not just how they're executed. From factory to foxhole, we operate at the layer where data becomes decisions, and decisions make the advantage.
What You'll Do
In this role, you will build the systems that move a model out of a notebook and into the hands of a planner. Sometimes, that means deploying to an air-gapped rack in a tent instead of a VPC. You will own the path from training run to deployed capability: the infrastructure it runs on, the release process that ships it, the evaluation harness that proves it works, and the telemetry that tells us when it stops working.
Our AI/ML team works across retrieval-grounded systems for doctrine and logistics data, document and feature extraction, military symbol recognition, optimization and movement models, and an LLM agent platform. This role underpins that work: building the infrastructure, release processes, and evaluation systems that make it shippable and keep it honest in production. You will have plenty of room to shape how we build it.
Training & Serving Infrastructure
Own model training, fine-tuning, and batch inference infrastructure across AWS (SageMaker, EKS) and on-premises GPU hardware.
Stand up and tune LLM inference serving: vLLM-class stacks, quantization, continuous batching, KV-cache and throughput sizing. Make the hosted-vs-local call with numbers behind it.
Build for DDIL: local inference with configurable fallback, degraded-mode behavior, and sane resource envelopes on hardware we do not get to choose.
Release & Reproducibility
Build CI/CD for models and pipelines: versioned datasets, a model registry, promotion gates, and rollback that actually works under pressure.
Own infrastructure as code, containerization, and GitOps deployment across environments ranging from a dev cluster to a disconnected enclave.
Make reproducibility a hard requirement. Any result we put in front of a customer or evaluator must be reproducible from a commit and dataset version.
Evaluation & Observability
Build and own the evaluation harness: regression suites for retrieval and extraction pipelines, LLM-as-judge pipelines with measured judge-human agreement, and adversarial and held-out sets.
Instrument production for drift, latency, cost, retrieval quality, and failure modes, including quiet ones such as a retrieval miss that produces a fluent but wrong answer.
Make our metrics defensible to external test and evaluation reviewers. “We think it’s good” is not a deliverable.
Data & Pipeline Ownership
Own ingestion, versioning, and lineage for logistics and doctrinal data drawn from a heterogeneous set of authoritative sources.
Build and operate embedding and feature pipelines, incremental indexing, and the unglamorous systems that keep a retrieval index fresh.
Build the human-in-the-loop infrastructure: confidence-scored routing, review queues, and feedback capture that improves the next model.
Secure & Accredited Deployment
Deploy and operate ML systems in IL5 and IL6 environments, including air-gapped or restricted-network enclaves. Build the release, observability, artifact-management, and incident-response workflows those environments require.
Support ATO and continuous-authorization work with implementation evidence tied to applicable security controls (NIST SP 800-171, NIST SP 800-53 Rev. 5, CMMC Level 2, FIPS 140-3, and RMF/eMASS).
Handle CUI and classified data correctly without being asked twice.
What We’re Looking For
Strong Platform & Infrastructure Skills
5+ years in MLOps, ML platform, or infrastructure engineering, including meaningful time working on systems with real users.
Strong Python skills and comfort in a production codebase, not just notebooks.
Deep Kubernetes and containerization experience, plus infrastructure as code.
Production experience with AWS ML/Azure infrastructure (SageMaker, EKS, or equivalent).
Hands-on GPU infrastructure experience: scheduling, utilization, memory sizing, and cost.
Hands-on experience deploying and operating production software in IL5 or IL6 environments, including disconnected or restricted-network deployments.
Production ML Judgment
You have shipped an LLM or ML system to production and then had to keep it working. You know what breaks.
You have built evaluation and monitoring for ML systems rather than adopting a vendor dashboard and hoping.
You can reason about where a pipeline’s quality actually comes from and say so when a metric is measuring the wrong thing.
Ownership
You are comfortable with ambiguity and owning a domain end to end. This is a small team; there is no one to hand the pager to.
You are willing to learn the mission domain. The engineers who do best here become genuinely interested in the logistics problem itself.
Nice to Have
Clearance: Preferred
LLM serving and inference optimization (vLLM, TensorRT-LLM, quantization, prefix caching).
Retrieval-grounded systems in production: hybrid retrieval, re-ranking, index freshness, and citation quality.
Edge, on-premises, or disconnected deployment.
Experience supporting ATO, continuous authorization, or production operations in classified environments.
Defense, intelligence, or another accredited or regulated environment.
Palantir Foundry, PostgreSQL/pgvector, NATS/JetStream, or ArgoCD.
A degree in CS, engineering, or a related technical field, or the equivalent built the hard way.
Mission and Identity
We are building the system that enables faster, smarter logistics decisions in contested environments, and we're doing it with a team of seasoned entrepreneurs, operators, and technologists who have built and scaled solutions in this space before. We hold ourselves to an extremely high standard. We value clear thinking, direct communication, and the kind of ownership that doesn't stop until something actually works.
Our mission is to create decision advantage when the stakes are the highest. If we succeed, the system doesn't just run; it gets smarter. We're not building AI for its own sake. We're building it because faster, smarter decisions in the most demanding environments on earth can't wait. If you want to work somewhere the stakes are real and the mission is urgent — you'll fit in here.
Why Gallatin?
The logistics infrastructure that supports America's warfighters and humanitarian disaster responders is overdue for transformation, and we are building it. From defense operations to disaster response, we're solving the hardest problems that keep missions moving when it matters most. Join a team where the mission is the point.
Compensation: Gallatin offers competitive compensation commensurate with experience. Actual compensation may vary based on experience, skills, and location. In addition to base salary, we offer a generous equity grant, full healthcare coverage, 401k, unlimited PTO, and the perks of working in a high-caliber, mission-driven environment.
Gallatin is an equal opportunity employer. We do not discriminate on the basis of race, color, religion, sex, national origin, age, disability, veteran status, sexual orientation, gender identity, or any other characteristic protected by applicable federal, state, or local law.
This position may require the ability to obtain and maintain a U.S. government security clearance. The successful candidate must be able to work in a classified environment when necessary.
We comply with the United States Department of Labor's Pay Transparency provision.
Note: Due to the nature of certain government contracts held by this organization, U.S. citizenship is a requirement for all positions at Gallatin. Proof of citizenship will be required prior to employment if selected.
Compensation Range: $80K - $210K
Mlops Engineer Jobs by Experience Level
See All 58 Mlops Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find Mlops Engineer JobsMlops Engineer Job Market
Who's Hiring



Top Industries Hiring
- Technology & Software11
- Retail1
- Human Resources1
- Biotechnology & Pharmaceuticals1
What Employers Look For
The qualifications that appear most often in mlops engineer jobs.
- Proficiency in Python and experience building and maintaining ML pipelines at scale
- Hands-on experience with containerization and orchestration tools such as Docker and Kubernetes
- Familiarity with at least one major cloud platform including AWS, GCP, or Azure ML services
- Experience with ML experiment tracking and model registry tools such as MLflow or Weights and Biases
- Understanding of CI/CD principles and tooling applied to machine learning model deployment workflows
- Bachelor's degree in computer science, data engineering, or a closely related technical field
Tips for Your Mlops Engineer Job Search
Tailor your resume to deployment pipelines
Hiring managers scan for specific orchestration tools like Kubeflow, MLflow, or Airflow. List each tool with the scale you operated at and the problem it solved, not just the name. Vague 'used ML tools' lines get skipped.
Apply early to roles that fit
Migrate Mate lists mlops engineer openings from across the United States in one place, so you can find roles that match and apply directly to each listing.
Highlight model monitoring and observability work
Many mlops engineer candidates oversell training pipelines and undersell production monitoring. Emphasize experience with drift detection, alerting, and retraining triggers because those are the gaps most teams are actually trying to fill.
Filter openings by cloud platform overlap
AWS, GCP, and Azure mlops tooling diverge sharply. When targeting roles, prioritize postings that name the cloud stack you know deepest so your hands-on experience answers the interview's first technical question before you walk in.
Prepare a live demo of a deployed model endpoint
Interviewers for mlops roles frequently ask you to walk through a real system you built. Having a publicly accessible endpoint or a recorded walkthrough of a CI/CD model pipeline makes that conversation concrete and memorable.
Negotiate scope before you negotiate salary
In mlops offers, clarify whether the role owns infrastructure decisions or only executes on them. A title of 'mlops engineer' can mean staff-level architecture ownership or pure tooling maintenance, and that distinction shapes long-term growth more than base pay.
Mlops Engineer Jobs: Frequently Asked Questions
Which companies are hiring the most mlops engineers?
The companies hiring the most mlops engineers right now include Molex, TikTok, and TRM Labs, with the largest share of openings in California, Georgia, and Texas, based on current listings on Migrate Mate as of September 2026. Demand is concentrated in organizations scaling production ML systems beyond the experimentation phase.
How many mlops engineer jobs are remote?
About 71% of mlops engineer openings are fully remote or hybrid as of September 2026, making it one of the more remote-accessible infrastructure roles in tech. Model deployment, pipeline development, and monitoring work tend to be the most remote-friendly sub-areas, while roles requiring close collaboration with on-prem GPU clusters more often require on-site presence.
How do you become a mlops engineer?
Start by building a strong foundation in software engineering and data engineering before layering on ML system knowledge. Learn to containerize models with Docker, automate deployments with a CI/CD tool, and instrument a live model endpoint with monitoring. Contributing to open-source mlops tooling or publishing a documented end-to-end pipeline project accelerates hiring conversations significantly.
Can you get hired as a mlops engineer with little experience?
Yes, but you need a portfolio that proves production thinking, not just experimentation. Build and document a complete pipeline that trains, versions, deploys, and monitors a model in a cloud environment. Roles titled 'associate mlops engineer' or 'mlops platform engineer' at growth-stage companies often hire candidates who show systems thinking even without years of prior mlops-specific experience.
What does the mlops engineer interview process look like?
Most mlops engineer interview processes include a recruiter screen, a technical phone interview covering Python and infrastructure concepts, a take-home or live system design exercise focused on a deployment or pipeline problem, and a final round with engineering and data science stakeholders. Expect at least one question asking you to debug or improve an existing pipeline rather than build from scratch.
Where can I find and apply to mlops engineer jobs?
You can find and apply to mlops engineer jobs on Migrate Mate, which lists current openings from across the United States. Find roles that match your experience and tools, then apply directly to each listing. New openings are added regularly, so checking back frequently helps you catch roles before they close.
See All 58 Mlops Engineer Jobs
Find roles that match your experience and apply in just a few clicks.
Find Mlops Engineer Jobs