Skip to content
Gallatin

Machine Learning Operations (MLOps) Engineer

El Segundo, CA; San Francisco, CA; Austin, TXOnsite · United States
FullTime · Engineering
POSTED 17 SEPTVERIFIED 1D AGO
Apply Ask
Role
53 days opentrue age
Posted 17 Sept
Payats field
$80k–210kposted
▼ −5% vs market median $152k
$80k$210k
Market p25–p75
$145k–$201k
Gallatin p25–p75
$145kn=5
Los Angeles · n=10 · 365d to 6 Nov
CompanyGallatin →
25open roles
Opened · 30d
+0
Closed · 30d
−0
30d window
Market
3,250open · ML / AI
Opened · 7d
+2267% of open
All ml / ai
6,607open
All tracked boards · live 10 Nov · n=3,250
PythonAWSAzureKubernetesLLMs

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).

Source · GallatinFirst seen 4 NovOriginal ↗