SECAI Core · phase 9 of 15 · noun
MLOps engineer
A role that automates the lifecycle on the platform by establishing continuous integration and delivery for AI models and prompts, managing versioning and lineage, orchestrating retraining workflows, and setting up monitoring
The Explain card
- Plain English
- An MLOps engineer automates the AI lifecycle on the platform: continuous integration and delivery for models and prompts, versioning and lineage, retraining workflows, and monitoring.
- Example
- They build a pipeline where every change to a prompt template or model weights is versioned, tested against an evaluation suite, and deployed only if it passes. Lineage records show exactly which data and code produced each model in production.
- Why it matters
- Lineage and versioning are how defenders answer "which model was live when that happened?" and roll back a poisoned or misbehaving version fast.
- Hook
- CI/CD for models, with a receipt for every version.
Word knowledge
How the word is built, where it came from, and what it sits beside in memory.
In a sentence
When the canary's 95th-percentile latency rose on the GPU serving pool, the MLOps engineer halted the Argo promotion and restored the last signed weights from the model registry.
Why these words
- MLOps English blend of ML (machine learning) and Ops, a clip of operations from Latin operatio, after DevOps names the practice half, so the title-holder is claimed to run machine-learning work the way a DevOps engineer runs software work
- engineer Old French engigneor, constructor of military engines, from Latin ingenium, inborn talent names the craftsperson, so the phrase claims that practice is a thing a person builds
Where it came from
- Origin
- English job-title collocation from MLOps, a blend of ML (machine learning) and Ops (operations) after DevOps, and Old French engigneor, constructor of military engines, from Latin ingenium, inborn talent
- Entered the language
- late 2010s
- What changed
- ML had been the short form of machine learning since the late twentieth century. Ops is a clip of operations, first fused to Dev in 2009 as DevOps. Teams grafted ML onto that Ops half in the mid-2010s, then added engineer so the blend named a person on call, not only a practice.
How it is spelled
- Pattern
- a two-letter all-caps initialism fuses to a capitalised clip, as in DevOps and GitOps
- Pattern
- -eer is the French -eur agent suffix, as in volunteer and pioneer
- Breaks the pattern
- MLOps keeps mixed case; it is not written MLOPS or mlops in formal titles
- Breaks the pattern
- the noun phrase stays two words
Spelled like
- DevOps
- GitOps
- volunteer
- pioneer
Broken into chunks
-
Ops
- DevOps
- DataOps
- GitOps
-
oper
- operate
- operator
- operation
-
engine
- engineering
- reengineer
- engine
-
eer
- volunteer
- pioneer
- musketeer
What it sits beside
Same subject
Same shape
- DevOps engineer
- DataOps engineer
- software engineer
- site reliability engineer
Engineer titles
Ops blends
- DevOps
- DevSecOps
- DataOps
- GitOps
Where it sits in the deck
Phase 9: Roles, Teams, and Organisational Accountability
Governance frameworks are executed by people — introduce the human roles and organisational structures responsible for building, operating, and auditing AI systems.