Models as research artifacts
Machine learning lived largely in research, specialist products and statistics. Operational concerns existed but were not usually a distinct career.
MLOps Engineer · Builds the systems that train, deploy, monitor and govern machine-learning models in production.
MLOps is a new job name for an old operational problem: a model that works in a controlled experiment can fail when it meets changing data, real users and a production budget. The profession combines machine learning's research culture with the discipline of software delivery and operations.
Its history is therefore shared with data engineering, cloud computing and DevOps. The role became distinct in the late 2010s as organizations moved from isolated models to fleets of models whose data, behavior and compliance had to be managed continuously.
The phrase MLOps spread as cloud platforms and ML teams confronted production maintenance costs. Google researchers' 2015 paper “Hidden Technical Debt in Machine Learning Systems” gave a widely cited vocabulary for the dependencies, feedback loops and operational complexity that turn a model into a long-lived system.
Samuel describes machine learning in work on a self-improving checkers program, helping name the field later put into production.
Web-scale ranking shows how models and data infrastructure can become central product infrastructure.
Amazon Web Services makes elastic compute and storage available as operating services rather than owned hardware.
AlexNet's success on ImageNet makes GPU-based training central to many machine-learning programs.
Google researchers describe why ML systems accumulate dependencies and maintenance burdens beyond their model code.
Kubernetes adoption creates a common operational layer for packaging and running distributed workloads.
Google presents TFX as a production-oriented platform for end-to-end ML pipelines.
Cloud vendors and startups formalize tools for experiment tracking, pipelines, model registries and deployment.
Teams increasingly treat data validation, feature management and model monitoring as production requirements.
Foundation models create new needs for evaluation, retrieval, cost controls, prompt management and AI governance.
Machine learning lived largely in research, specialist products and statistics. Operational concerns existed but were not usually a distinct career.
Elastic infrastructure, distributed processing and open-source frameworks made larger-scale model training and serving possible.
Production teams recognized that data dependencies, monitoring and retraining could cost more than the original model.
Experiment tracking, model registries, feature stores and CI/CD patterns became recognizable MLOps building blocks.
LLM applications widen the work to evaluation, retrieval, access control, observability and responsible deployment.
Neighbouring trades that no longer exist — absorbed, automated or regulated away.
A researcher would email a serialized model and instructions to an application team. Registries, versioned artifacts and deployment pipelines replaced the informal handoff.
Teams recorded runs, parameters and metrics in local files or spreadsheets. Experiment-tracking systems now preserve artifacts, code versions and comparisons centrally.
Operations staff ran periodic scripts to produce predictions. Scheduled workflows, managed platforms and automated quality checks absorbed the repeated execution.
MLOps emerged because the useful life of a model begins after training. The discipline takes the operational questions that prototypes can postpone—versioning, failure, cost, bias and rollback—and makes them first-class engineering work.
The next phase will be defined less by whether organizations can call a model and more by whether they can prove it remains useful, safe and controllable after launch.
Closest neighbours on the six-score profile — not the same field only.
Protects systems, data and people by finding, preventing and responding to digital attacks.
AI-resistant 63 🧫Uses clinical, trial and health-system data to generate reliable evidence for safer care, research and operational decisions.
AI-resistant 68 🔌Designs and fabricates the transistors inside every computer, phone and weapon, using machines precise enough that only a few factories on Earth can run them.
AI-resistant 60 🦾Designs the machines that sense, decide and act in the physical world, where the hard problem was never intelligence but the world itself.
AI-resistant 65 🌿Leads the strategy, measurement and reporting that helps organizations reduce environmental and social harm while meeting business obligations.
AI-resistant 66 👔Advises clients, drafts the documents that bind them, and argues their case when it reaches court — carrying personal legal liability if the advice is wrong.
AI-resistant 58Writes, tests and maintains the code that runs modern life — and is one of the first professions watching AI automate its own daily work.
AI-resistant 35 🤖Designs and tests the algorithms behind machine intelligence, in a field now racing to automate a growing share of its own research process.
AI-resistant 50 🛰️Designs, analyzes and certifies the aircraft, rockets and spacecraft that leave the ground, working to safety margins that leave no room for guessing.
AI-resistant 74 🌉The profession that turns rivers, rock and gravity into bridges, roads and clean water — civilization's quiet load-bearing trade since Imhotep.
AI-resistant 72 🔌Designs and fabricates the transistors inside every computer, phone and weapon, using machines precise enough that only a few factories on Earth can run them.
AI-resistant 60 🦾Designs the machines that sense, decide and act in the physical world, where the hard problem was never intelligence but the world itself.
AI-resistant 65 🔐Protects systems, data and people by finding, preventing and responding to digital attacks.
AI-resistant 63 🌬️Designs, builds and improves wind, solar, storage and grid systems that turn renewable resources into dependable electricity.
AI-resistant 72