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.
El Segundo, CA · San Francisco, CA · Austin, TX · El Segundo, California, United States
Live, first seen by us 63 days agoLocation type: On-siteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: Engineering › AI EngineeringFrom the employer’s posting
Own model training, fine-tuning, and batch inference infrastructure on AWS and on-prem GPUs
Stand up and tune LLM inference serving, including quantization and throughput sizing
Build CI/CD for models with versioned datasets, a model registry, and rollback
Build and own the evaluation harness, including regression suites and LLM-as-judge pipelines
Instrument production for drift, latency, cost, retrieval quality, and failure modes
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.
Build CI/CD for models and pipelines: versioned datasets, a model registry, promotion gates, and rollback that actually works under pressure.
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
We build AI systems that determine how logistics decisions are made — not just how they're executed.
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 63
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.
7 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd 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 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.
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.
- 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.
- 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).
- 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.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
El Segundo, California, United States
- 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.
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.