We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

MLOps: market

Data as of November 19, 2026: 354 open MLOps jobs, 31% remote among jobs that state a work format; median advertised salary $8,315/mo (from 41 postings that state a salary). Source: Zorky, updated daily.

MLOps Engineer — infrastructure for ML/AI teams. At the intersection of DevOps + ML Engineering + Platform Engineering. Builds and operates the ML platform for other DS / ML Engineer / Research teams: feature stores, model registry, training infrastructure, serving stack, monitoring, cost optimisation. Role family: MLOps Engineer (mid — infra for a single product team), Senior MLOps Engineer (multi-team platform + cost optimisation + scaling), ML Platform Engineer (builds a reusable platform for the whole organisation — Feature Store / Model Registry / Training Platform), Staff / Principal MLOps (ML platform architecture for a multi-product organisation), MLOps Tech Lead (team leadership + platform strategy + integration with DevOps / SRE). Stack: Python (primary), Docker+Kubernetes mastery (production ML serving), Helm+Kustomize+ArgoCD (GitOps), Terraform/Pulumi/CloudFormation (infrastructure-as-code for cloud-managed ML resources), MLflow (model registry + tracking — open-source standard), Kubeflow+Kubeflow Pipelines (K8s-native ML orchestration), Airflow/Prefect/Dagster (data + ML pipelines), Feast/Tecton (feature stores), Triton Inference Server+BentoML+TorchServe+vLLM/TGI/SGLang (model serving — LLM-specific), Prometheus+Grafana+Loki (observability), Evidently AI/WhyLabs/Arize AI/Fiddler (ML monitoring + drift detection), DVC+LakeFS (data version control), AWS SageMaker/GCP Vertex AI/Azure ML/Databricks/Domino Data Lab (cloud-managed ML), Spark+Ray (distributed compute platforms), FluxCD+Tekton (CI/CD for ML pipelines), OpenTelemetry (tracing). Top stack: mlops, ci/cd, cloud, aws, python. Among jobs with a stated work format, 31% are remote.

Data as of:

Key numbers for the MLOps market: open jobs, median salary, observed talent pool and remote share.

354
open jobs — by job title, reposts merged
$8,315
median $/mo
31%
remote

The MLOps market currently has 354 open roles, 304 of them freshly observed. Median salary $8,315/mo.

Among jobs with a stated work format, 31% are remote. MLOps work cloud-based standard. Outsourcing shops (EPAM AI Platform / Luxoft AI) — almost always remote. Russian banks (Sber AI banking / VTB) — hybrid/office security compliance. International ML-platform companies — full-remote standard. Big Tech ML Platform — hybrid-standard.

⚠ salary known for 41 of 354 jobs; remote share from 290 with a stated format; 304 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many MLOps postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.

New postings per week

Chart data
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-0125
2026-06-0818
2026-06-1512
2026-06-2256
2026-06-2938
2026-07-0644
2026-07-1367
2026-07-2044
2026-07-2724
2026-08-0325
2026-08-1029
2026-08-1720
2026-08-2424
2026-08-3130
2026-09-0724
2026-09-1434
2026-09-2153
2026-09-2859
2026-10-0556
2026-10-12151
2026-10-1954
2026-10-2670
2026-11-0285
2026-11-0973

Active sources per week

Sources over the period: 124. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-0111
2026-06-088
2026-06-155
2026-06-2211
2026-06-2923
2026-07-0619
2026-07-1328
2026-07-2014
2026-07-2714
2026-08-0319
2026-08-1018
2026-08-1715
2026-08-2412
2026-08-3120
2026-09-0714
2026-09-1418
2026-09-2124
2026-09-2823
2026-10-0522
2026-10-1232
2026-10-1927
2026-10-2629
2026-11-0236
2026-11-0941
New sources connected: Jun 29 +14 · Jul 6 +8 · Jul 13 +15 · Nov 9 +14 · all weeks (23) in the table
WeekNew sourcesNew postings
Jun 8+318
Jun 15+112
Jun 22+556
Jun 29+1438
Jul 6+844
Jul 13+1567
Jul 20+544
Jul 27+324
Aug 3+325
Aug 10+429
Aug 17+620
Aug 24+124
Aug 31+430
Sep 7+224
Sep 14+334
Sep 21+553
Sep 28+159
Oct 5+256
Oct 12+5151
Oct 19+254
Oct 26+370
Nov 2+485
Nov 9+1473

The current week is not over yet and is not shown: an incomplete week would look like a drop.

Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.

Chart data
Timeline: postings and sources — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-012511
2026-06-08188
2026-06-15125
2026-06-225611
2026-06-293823
2026-07-064419
2026-07-136728
2026-07-204414
2026-07-272414
2026-08-032519
2026-08-102918
2026-08-172015
2026-08-242412
2026-08-313020
2026-09-072414
2026-09-143418
2026-09-215324
2026-09-285923
2026-10-055622
2026-10-1215132
2026-10-195427
2026-10-267029
2026-11-028536
2026-11-097341

Salaries over time

Median MLOps salary per week, USD per month.

Median salary, USD per month

Chart data
Median salary, USD per month. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodMedianPostings with a salary per week (n)
2026-10-199,55012
2026-10-269,45716
2026-11-027,75013
2026-11-09—7

The series starts on Oct 19: there is no data before that.

Postings with a salary per week (n)

Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.

Chart data
Salaries over time — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekMedian
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-22—
2026-06-29—
2026-07-06—
2026-07-13—
2026-07-20—
2026-07-27—
2026-08-03—
2026-08-10—
2026-08-17—
2026-08-24—
2026-08-31—
2026-09-07—
2026-09-14—
2026-09-21—
2026-09-28—
2026-10-05—
2026-10-12—
2026-10-199,550
2026-10-269,457
2026-11-027,750
2026-11-09—

Remote work over time

Share of MLOps postings offering fully remote work, per week.

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-06-0164.7
2026-06-0850
2026-06-15—
2026-06-2246.9
2026-06-2954.5
2026-07-0648.3
2026-07-1342.9
2026-07-2063.4
2026-07-2776.5
2026-08-039.5
2026-08-1045
2026-08-1716.7
2026-08-2425
2026-08-3152.2
2026-09-0723.8
2026-09-1426.1
2026-09-2135.7
2026-09-2849
2026-10-0528
2026-10-1232.7
2026-10-1915.4
2026-10-2629.7
2026-11-0230.6
2026-11-0943.9

The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.

Chart data
Remote work over time — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-0164.7
2026-06-0850
2026-06-15—
2026-06-2246.9
2026-06-2954.5
2026-07-0648.3
2026-07-1342.9
2026-07-2063.4
2026-07-2776.5
2026-08-039.5
2026-08-1045
2026-08-1716.7
2026-08-2425
2026-08-3152.2
2026-09-0723.8
2026-09-1426.1
2026-09-2135.7
2026-09-2849
2026-10-0528
2026-10-1232.7
2026-10-1915.4
2026-10-2629.7
2026-11-0230.6
2026-11-0943.9

Technologies over time

How the share of MLOps postings mentioning each of the top technologies changed.

Postings mentioning the technology, %

Chart data
Postings mentioning the technology, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodMLOpscloudPython
2026-08-10961616
2026-08-171002520
2026-08-248717.430.4
2026-08-3196.27.738.5
2026-09-0791.326.18.7
2026-09-14976.13
2026-09-2195.930.636.7
2026-09-2894.944.150.8
2026-10-0594.431.553.7
2026-10-1289.345.630.9
2026-10-1994.360.456.6
2026-10-2686.230.853.8
2026-11-0285.938.546.2
2026-11-0991.849.338.4
Up to 5 on the chart:

Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.

Chart data
Technologies over time — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekMLOpscloudAWSPythonDocker
2026-08-10961641612
2026-08-1710025252025
2026-08-248717.48.730.421.7
2026-08-3196.27.7038.534.6
2026-09-0791.326.18.78.78.7
2026-09-14976.10312.1
2026-09-2195.930.618.436.720.4
2026-09-2894.944.137.350.832.2
2026-10-0594.431.522.253.718.5
2026-10-1289.345.631.530.930.2
2026-10-1994.360.432.156.628.3
2026-10-2686.230.827.753.829.2
2026-11-0285.938.532.146.221.8
2026-11-0991.849.332.938.427.4

Countries over time

How the share of MLOps postings in each of the top countries changed, per week.

Postings in the country, %

Chart data
Postings in the country, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodPolandUKRussia
2026-06-0124816
2026-06-08———
2026-06-15———
2026-06-2277.81.91.9
2026-06-2930.62.822.2
2026-07-0613.210.523.7
2026-07-1332.75.51.8
2026-07-2063.42.419.5
2026-07-27504.518.2
2026-08-034.823.84.8
2026-08-10022.225.9
2026-08-17———
2026-08-24043.517.4
2026-08-31011.550
2026-09-07———
2026-09-1415.47.723.1
2026-09-2114.921.314.9
2026-09-2835.315.72
2026-10-0532.722.44.1
2026-10-1222.57.82.3
2026-10-1913.324.46.7
2026-10-2613.817.210.3
2026-11-0213.417.91.5
2026-11-0911.16.312.7
Up to 5 on the chart:

Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.

Chart data
Countries over time — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekPolandUKUSARussiaIndia
2026-06-01248281616
2026-06-08—————
2026-06-15—————
2026-06-2277.81.93.71.93.7
2026-06-2930.62.811.122.25.6
2026-07-0613.210.510.523.710.5
2026-07-1332.75.5201.814.5
2026-07-2063.42.4019.54.9
2026-07-27504.54.518.20
2026-08-034.823.8194.89.5
2026-08-10022.23.725.911.1
2026-08-17—————
2026-08-24043.58.717.44.3
2026-08-31011.53.8503.8
2026-09-07—————
2026-09-1415.47.77.723.115.4
2026-09-2114.921.314.914.92.1
2026-09-2835.315.711.825.9
2026-10-0532.722.422.44.10
2026-10-1222.57.810.12.312.4
2026-10-1913.324.415.66.715.6
2026-10-2613.817.224.110.35.2
2026-11-0213.417.911.91.59
2026-11-0911.16.314.312.711.1

Clean market: hiring index

The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just MLOps.

Hiring index, Oct 16 = 100

Chart data
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.

Chart data
Clean market: hiring index — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open MLOps jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand354
Open demand354
Observed supply— not published

MLOps Engineer — the most "recession-resistant" AI/ML niche (production needs continuously). Growth 2026 driven by: LLM-serving infrastructure (vLLM / TGI / SGLang adoption), foundation model deployment in enterprise, ML platform internal-tooling buildouts, cost-optimisation pressure (GPU costs $10K+/month per team typical). Russian — steady flow. International ML-platform companies (Truefoundry / Bento / Determined AI / Run:AI) — premium remote segment.

⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown

How salaries in MLOps jobs are distributed, in US dollars per month.

Salary distribution

P25 $6,000 · P50 $8,315 · P75 $11,608
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k0
$1–2k1
$2–3k1
$3–4k3
$4–5k3
$5–6k1
$6–7k7
$7–8k3
$8–9k6
$9–10k3
$10–12k4
$12–15k5
$15–20k3
$20k+1
Salary in postings: base 354
  • usable for the calculation: 41 (11.6%)
  • stated but not converted to USD/month: 49 (13.8%)
  • not stated: 264 (74.6%)

One in ten postings offers under $3,894, one in ten over $13,750. Half of the postings offer between $6,000 and $11,608. Sample: 41.

Chart data
Salary distribution — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricLower boundUpper boundCount
<$1k01,0000
$1–2k1,0002,0001
$2–3k2,0003,0001
$3–4k3,0004,0003
$4–5k4,0005,0003
$5–6k5,0006,0001
$6–7k6,0007,0007
$7–8k7,0008,0003
$8–9k8,0009,0006
$9–10k9,00010,0003
$10–12k10,00012,0004
$12–15k12,00015,0005
$15–20k15,00020,0003
$20k+20,000—1

Which countries have the most open MLOps jobs.

Demand geography

countryjobsshare
United States5819.7%
Poland5016.9%
India268.8%
United Kingdom237.8%
Germany186.1%
France165.4%
Russia165.4%
Canada124.1%
Romania93.1%
Netherlands51.7%
Other countries6221%

The leader by MLOps job count is the US (58 positions). Poland — AI Platform-friendly EU hub. Germany — Berlin AI cluster. Large international remote via ML-platform companies (Truefoundry / Bento / W&B / Comet / Determined AI) + AI-startup MLOps teams.

⚠ job counts only: salary by country is not published

Chart data
Demand geography — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
US58
PL50
IN26
GB23
DE18
FR16
RU16
CA12
RO9
NL5

Which technologies are most often required in the same job as MLOps.

Used together with

mlops
27778.2%
cloud
14741.5%
aws
12234.5%
python
11933.6%
docker
10529.7%
kubernetes
10228.8%
azure
8323.4%
mlflow
5615.8%
gcp
5214.7%
llm
5014.1%

Share — how many of the 354 jobs in the MLOps market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).

Top MLOps stack 2026: Python + Go bonus, Docker mastery + Kubernetes mastery (production standard), Helm + Kustomize + ArgoCD / FluxCD (GitOps), Terraform + Pulumi / CloudFormation (IaC), MLflow (model registry + tracking — open-source standard) + Kubeflow + Kubeflow Pipelines, Airflow / Prefect / Dagster (workflow), Feast / Tecton (feature stores), Triton Inference Server + BentoML + TorchServe + KServe (model serving), vLLM + TGI + SGLang + Ollama (LLM serving — 2026 must), Prometheus + Grafana + Loki + OpenTelemetry, Evidently AI + WhyLabs + Arize AI + Fiddler (ML monitoring + drift), DVC + LakeFS, AWS SageMaker / GCP Vertex AI / Azure ML / Databricks (cloud-managed ML), Spark + Ray (distributed compute), NVIDIA GPU Operator + Kubeflow Training Operator + Spark Operator + Argo Workflows (K8s ML operators).

Common pairs: Kubernetes + Helm + ArgoCD + Terraform, MLflow + Kubeflow + Feast, Triton + KServe + Prometheus + Grafana, vLLM + TGI + SGLang (LLM serving stack), AWS SageMaker + Terraform + GitHub Actions, GCP Vertex AI + Kubeflow Pipelines, Databricks + MLflow + Spark, Evidently AI + Prometheus + Grafana (ML observability). Learning roadmap: DevOps fundamentals (Linux + Docker + K8s) → Terraform + cloud platform deep → CI/CD + GitOps → ML basics (Python + sklearn + PyTorch) → MLflow + Feast (ML platform foundation) → Triton / vLLM (serving) → Evidently AI (monitoring) → ML platform pet project → open-source contributions.

Chart data
Used together with — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
mlops277
cloud147
aws122
python119
docker105
kubernetes102
azure83
mlflow56
gcp52
llm50
airflow48
databricks37

How many MLOps jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior126
middle30
principal24
lead16
junior11

Junior — typical entry: DevOps Middle + ML interest OR ML Engineer Middle + infra interest OR Backend Senior + ML courses. Career flow: Junior (1-2 years) → Middle (2-3 years) → Senior → either Staff / Principal MLOps (deep technical), MLOps Tech Lead / Platform Engineering Manager, or Founder at an ML-platform startup.

⚠ demand side only: the grade of the observed pool is unknown for most of it

Chart data
Demand by grade — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior126
middle30
principal24
lead16
junior11

Who hires the most for MLOps and how concentrated demand is among the largest companies.

Employers

Demand is spread across 280 employers. The largest accounts for 1.2%, the top ten for 9.3%; the remaining 90.7% is long tail.

largest 1.2%2nd–3rd 2.2%4th–10th 5.9%the rest 90.7%
sharevalue
top-11.2%
top-33.4%
top-109.3%
long tail90.7%

⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier

Which company sites and job boards Zorky collects MLOps jobs from.

Where Zorky sees this market

Observed across 71 sources; the largest accounts for 9.6% — this market does not rest on a single channel.

Chart data
Where Zorky sees this market — MLOps. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites1810.5113
boardджоб-борды и агрегаторыjob boards & aggregators1460.4124
telegramTelegramTelegram250.0706
communityсообщества и публичные профилиcommunity & public profiles20.0056

The newest MLOps jobs from company career sites.

Recent openings

All jobs →

Latest open MLOps jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.

How this is measured
Vacancy
an open job that cleared the quality gate and lists at least two technologies
Observed candidate
a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
Matchable candidate
not counted yet
Window
jobs open at the moment the snapshot was built

About the data

  • Some breakdowns are hidden: their data coverage is not yet sufficient.
  • Statistics are shown only where the sample clears a quality gate.
  • A missing block does not mean a value of zero.

Breakdowns currently hidden: 8.

Direction: AI / ML / Data Science

Related specializations

Inside MLOps: MLOps Engineer (mid — infra for a single product team), Senior MLOps (multi-team platform + cost optimisation), ML Platform Engineer (reusable platform-as-product for organisation), Staff / Principal MLOps (architecture for multi-product organisation), MLOps Tech Lead (team management + platform strategy). Comparison with ml-engineer/data-scientist/research — in the bar below.

AI / LLM EngineerComputer VisionData ScientistML EngineerNLP EngineerResearch Engineer

Frequently asked questions

The most common questions about MLOps Engineer: pay, MLOps vs DevOps vs Platform Engineer, MLflow vs Kubeflow vs Vertex AI vs SageMaker (decision tree of 7 options), ML Platform Engineer differences, remote, how to become (4-10 months from DevOps Middle / ML Engineer Middle), Senior skills (LLM serving + cost optimisation + multi-team platform). Answers recompute automatically.

What does an MLOps Junior, Middle, Senior, or Lead earn?

Junior MLOps — typical entry: 1) DevOps / SRE Middle + ML interest, 2) ML Engineer Middle + infra interest, 3) Backend Senior + ML knowledge (via courses). Junior → Middle jump — after the first end-to-end ML platform deployment (Feature Store + Model Registry + Serving stack + Monitoring). Middle → Senior — multi-team platform ownership + cost optimisation. Senior → Staff / Principal — ML platform architecture for multi-product organisation + integration strategy with DevOps / SRE / Data Platform teams. Career flow: DevOps Middle / ML Engineer Middle → Junior MLOps (1-2 years) → Middle (2-3 years) → Senior → either Staff / Principal MLOps (deep), MLOps Tech Lead (management), or Founder at an ML-platform startup.

What stack does an MLOps most often need?

Top 5: mlops, ci/cd, cloud, aws, python. Python (primary — for custom infrastructure), Go bonus (for performance-critical infra components — e.g. serving proxies). Docker mastery (multi-stage builds for optimised ML images, GPU containers). Kubernetes mastery (production standard for ML serving — Deployment / StatefulSet / DaemonSet / Job / CronJob, RBAC, Network Policies, Resource Quotas, HPA / VPA / Cluster Autoscaler). GPU operator (NVIDIA GPU Operator for K8s GPU scheduling). K8s operators for ML: Kubeflow Training Operator + Spark Operator + Argo Workflows. Helm + Kustomize + ArgoCD / FluxCD — GitOps standard. Terraform / Pulumi / CloudFormation (IaC for cloud-managed ML — AWS / GCP / Azure resources). MLflow mastery (open-source standard for model registry + tracking — Senior owns MLflow Plugins customisation). Kubeflow + Kubeflow Pipelines (K8s-native ML orchestration — large enterprise often requires). Workflow orchestrators: Airflow + Prefect + Dagster (one deeply — Dagster rising 2026). Feature stores: Feast (open-source) or Tecton (managed) — must for Senior MLOps. Model serving: Triton Inference Server (NVIDIA — multi-framework + dynamic batching) + BentoML (Python-friendly) + TorchServe + KServe (K8s-native serving). LLM-specific serving: vLLM (PagedAttention — record for high-throughput LLM serving), Text Generation Inference (TGI) from Hugging Face, SGLang (programming model for LLM serving + caching), Ollama (local LLM serving). Observability: Prometheus + Grafana + Loki + OpenTelemetry. ML monitoring + drift detection: Evidently AI + WhyLabs + Arize AI + Fiddler (one deeply). Data version control: DVC + LakeFS. Cloud-managed ML: one of AWS SageMaker / GCP Vertex AI / Azure ML / Databricks deeply. Distributed compute platforms: Spark + Ray mastery. Cost optimisation: spot instances strategy, GPU sharing (NVIDIA MIG), quantisation integration, caching strategies (Redis for inference results), batch vs real-time inference cost analysis.

MLOps vs DevOps vs Platform Engineer — what's the difference?

DevOps Engineer — focus on general application infrastructure (CI/CD + monitoring + cloud + Kubernetes + IaC). Stack: Docker / K8s / Terraform / Prometheus / Grafana / Ansible / Jenkins / GitHub Actions / cloud (AWS / GCP / Azure). See DevOps Engineer (general) (when the page ships). Platform Engineer — DevOps + internal-tooling focus. Builds a developer platform for engineers (K8s clusters management + ArgoCD + IDP — Internal Developer Platform — Backstage / Port / Cortex). MLOps Engineer (this page) — DevOps + ML-specific focus. Builds an ML platform for DS / ML Engineer / Research teams. On top of the DevOps stack: MLflow / Kubeflow / Feature Stores / Model Serving (Triton / vLLM) / ML Monitoring (Evidently / WhyLabs) / cloud-managed ML (SageMaker / Vertex AI). ML Platform Engineer — Senior MLOps with focus on reusable platform-as-product (for the whole organisation, not a single team). Career overlap: DevOps Middle → MLOps Junior — 6-12 months (learn ML stack + Kubeflow / MLflow + cloud-managed ML). MLOps Senior ↔ Platform Engineer Senior — easy lateral move (much shared stack). ML Engineer Middle → MLOps Junior — 4-8 months (already knows ML stack, need to deepen Kubernetes + Terraform + observability). DevOps → MLOps — more distant than Platform Engineer pivot (ML knowledge gap).

MLflow vs Kubeflow vs Vertex AI vs SageMaker — what to pick?

Decision tree for ML platform choice 2026: 1) MLflow (open-source, vendor-neutral) — best for experiment tracking + model registry + simple deployment. Lightweight. Self-hosted or managed (Databricks). Use case: foundation of ML platform for most organisations. Default 2026 for team-level ML tracking. 2) Kubeflow + Kubeflow Pipelines (open-source, Kubernetes-native) — best for enterprise K8s-first organisations that want a full ML-platform stack without vendor lock. Heavier setup. Includes: Pipelines (workflow) + Training Operator (distributed training) + Serving (KFServing → KServe) + Notebooks. Use case: large enterprise + Kubernetes-mature team + multi-cloud / on-prem requirement. 3) AWS SageMaker (managed) — best for AWS-native organisations. Comprehensive: SageMaker Studio (IDE) + Training Jobs + Hyperparameter Tuning + Pipelines + Endpoints (real-time + batch) + Model Registry + Feature Store + Clarify (bias detection). Vendor lock to AWS. Use case: AWS-first organisation + small ML team — pays off thanks to feature count in one platform. Cost-heavy at scale (expensive). 4) GCP Vertex AI (managed) — Google's SageMaker equivalent. Strong on: Vertex AI Workbench (Jupyter cloud), Pipelines (Kubeflow-based — portable), AutoML, TPU access (for research / large training), Model Garden (pre-trained models). Use case: GCP-first organisation + Kubeflow portability matters. 5) Azure ML (managed) — Azure equivalent. Strong on: Designer (visual ML pipeline builder), AutoML, MLOps capabilities, Azure-native integration. Use case: Azure / Microsoft-first organisation. 6) Databricks (managed multi-cloud) — best for Spark-first ML workloads + Lakehouse. MLflow creators. Premium pricing. Use case: data-heavy organisations with Spark / Lakehouse pattern. 7) Specialised platforms: Weights & Biases (best UX for experiment tracking — research favourite), Comet (W&B alternative), Neptune, Determined AI (distributed training platform), Run:AI (GPU orchestration — acquired by NVIDIA), Truefoundry + Bento (modern model serving). Default 2026 for new ML team: MLflow self-hosted (or Databricks managed if Spark-heavy) + Kubernetes serving (Triton / vLLM) + Feast (feature store) + Prometheus + Grafana + Evidently AI. Default for AWS-native enterprise: SageMaker (if cost-acceptable + small team) or MLflow on EKS + custom services (cheaper at scale). Default for Kubernetes-mature enterprise: Kubeflow + MLflow.

What share of jobs are remote?

Among jobs with a stated work format, 31% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.

How is ML Platform Engineer different from MLOps Engineer?

MLOps Engineer (general) — can work in any ML team (product team / research lab / AI consultancy). Stack: universal MLOps. ML Platform Engineer — Senior MLOps with focus on reusable platform-as-product for the whole organisation (not for a single team). On top of that: internal API design (for other ML Engineers / DS), self-service tools (templates / scaffolding / CLI tools — like generate-new-model-project), SLA management for platform components (uptime / latency / throughput targets), cost-chargeback systems (per-team compute usage tracking + billing), onboarding documentation + training programmes for other ML team members, backwards-compatibility management for shared platform components, open-source contribution to platform components (e.g. Feast / Kubeflow contributions). Staff / Principal MLOps — even higher, typically managing an ML platform team (3-7 MLOps engineers + integrations with DevOps / SRE / Data Platform leads). Career choice: MLOps Engineer if you like being hands-on with a new problem every day, ML Platform Engineer if you like building reusable systems and working with multiple consumer teams. All three are legitimate Senior+ paths.

Where to start in MLOps in 2026?

Roadmap: 1) Strong DevOps base — Linux + networking + bash mastery, Docker mastery (multi-stage builds + layer optimisation + security scanning), Kubernetes mastery deep (Deployment / Service / Ingress / PVC / RBAC / Network Policies / HPA + custom CRDs basics). Books: "Kubernetes in Action" Lukša, "The Kubernetes Book" Poulton. 2) IaC mastery: Terraform deep (modules / state management / workspaces) + understanding cloud-provider-specific patterns. HashiCorp Learn course (free). GitOps patterns with ArgoCD / FluxCD. 4) Cloud platform deep — pick one of AWS / GCP / Azure and pass Solutions Architect Associate / Professional cert. 5) ML basics — minimum: Python + pandas + scikit-learn + PyTorch (basics) + understand training / inference loops. fast.ai "Practical Deep Learning" Part 1 course. "Designing Machine Learning Systems" Chip Huyen — MLOps must-read 2026 (for understanding the ML workflow from training to deployment). 6) Experiment tracking + model registry: MLflow mastery deep (Tracking + Registry + Projects + Models). Set up self-hosted MLflow on EKS / GKE / AKS. 7) ML serving stack: Triton Inference Server (multi-framework + dynamic batching) + BentoML + KServe. LLM serving: vLLM mastery (PagedAttention + continuous batching) + TGI + SGLang. 8) Feature Store: Feast (open-source) — set up end-to-end on a test project (offline + online + retrieval). 9) Orchestration: one of Airflow / Prefect / Dagster + Kubeflow Pipelines basics. 10) ML monitoring: Evidently AI (drift detection + data quality) + WhyLabs or Arize AI or Fiddler — one deeply. 11) Pet project: full ML platform deployment (K8s cluster + MLflow + Feast + Triton + Prometheus + Grafana + Evidently AI) with simple model lifecycle (train → register → deploy → monitor → retrain). Document in GitHub README. 12) Open-source contribution — Feast / Kubeflow / MLflow / vLLM / Triton — sharply increases MLOps resume value. Russian courses: Karpov.Courses "MLOps", Otus "MLOps", SkillFactory MLOps track, Slurm MLOps intensive. International (EN): "Made with ML" MLOps course Goku Mohandas (free, comprehensive), Hugging Face MLOps course, Coursera "MLOps Specialization" DeepLearning.AI, Databricks Academy MLOps. Must-read books: "Designing Machine Learning Systems" Chip Huyen, "Machine Learning Design Patterns" Lakshmanan, "Reliable Machine Learning" Cathy Chen. DevOps Middle / ML Engineer Middle → Junior MLOps — 4-10 months. Backend Senior → Junior MLOps — 8-14 months (need to learn ML stack).

How many open jobs are in this sample?

The published sample contains 354 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.

What skills does a Senior MLOps need?

A Senior MLOps owns the full ML-platform engineering cycle + technical leadership. Programming mastery: Python deep + Go bonus for performance-critical infra. Docker mastery: multi-stage builds, layer optimisation, GPU containers, security scanning (Trivy / Snyk). Kubernetes mastery deep: Deployment / Service / Ingress / PVC / RBAC / Network Policies / HPA / VPA / Cluster Autoscaler, custom CRDs basics, GPU Operator + Kubeflow Training Operator + Spark Operator + Argo Workflows. IaC mastery: Terraform deep (modules / state / workspaces), one of Pulumi / CloudFormation bonus. GitOps mastery: ArgoCD / FluxCD + Kustomize / Helm patterns. Cloud platform deep: one of AWS / GCP / Azure at Solutions Architect Professional level. MLflow mastery: deep customisation + Plugins + multi-tenancy patterns. Kubeflow Pipelines: enterprise-scale deployment + custom components + multi-tenancy. Feature Store mastery: Feast deep (offline + online + retrieval + monitoring + multi-tenancy) or Tecton (managed). Model serving mastery: Triton Inference Server deep (ensembles + dynamic batching + model repositories) + BentoML + KServe. LLM serving mastery (2026 must): vLLM deep (PagedAttention + continuous batching + speculative decoding + KV cache optimisation) + TGI + SGLang + Ollama. Distributed compute platforms: Spark + Ray mastery (Spark Operator on K8s, Ray Train + Ray Serve). Observability deep: Prometheus + Grafana + Loki + OpenTelemetry + custom metrics + alerting strategies. ML monitoring: Evidently AI + WhyLabs / Arize AI / Fiddler integration patterns. Cost optimisation mastery: spot instances strategy + GPU sharing (NVIDIA MIG) + quantisation integration (INT8 / FP16 / FP4) + caching strategies (Redis for inference results) + batch vs real-time inference cost analysis + reserved instance planning. Security mastery: secrets management (Vault / cloud KMS), network policies, supply chain security (signed images), data privacy (PII handling in ML pipelines). System design for ML platforms: design ML platforms on a whiteboard at scale 100M+ predictions/day + multi-tenant + multi-region. Soft: ADRs writing for platform decisions, technical writing (platform documentation + onboarding materials), code review for multiple teams, mentoring Middle MLOps, cross-team collaboration (DevOps / SRE / Data Platform / ML Engineer / DS / Research teams). English for Senior+ MUST — MLOps involves intensive cross-team work in English. Optional bonus: open-source contributions to Feast / Kubeflow / MLflow / vLLM / Triton — sharply increase market value for frontier-AI labs + ML-platform companies.

Leave a request

Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.

By submitting, you agree to the privacy policy.