ML Engineer: market
Data as of November 19, 2026: 2,291 open ML Engineer jobs, 32% remote among jobs that state a work format; median advertised salary $13,666/mo (from 309 postings that state a salary). Source: Zorky, updated daily.
ML Engineer — the largest role inside the AI/ML/DS direction (the biggest pool among ML sub-niches). Production ML — takes a model (own or from a Data Scientist), drives it to a production service with stable SLA. Role family: ML Engineer (general — feature engineering + training + deployment), Senior ML Engineer (end-to-end ML pipelines + scaling), Staff ML Engineer/Principal ML Engineer (ML platform architecture for the whole organisation), ML Tech Lead (team leadership + ML infrastructure decisions), Applied ML Engineer (product ML focused on business metrics). Stack: Python (monopoly), PyTorch/TensorFlow/JAX (deep learning — PyTorch dominates 2026), scikit-learn+XGBoost+LightGBM+CatBoost (classical ML — mandatory), pandas+NumPy+Polars (data manipulation), Hugging Face Transformers+LangChain+LlamaIndex (LLM/NLP), MLflow+Weights & Biases+Neptune (experiment tracking), DVC (data version control), Airflow/Prefect/Dagster (orchestration), Docker+Kubernetes (deployment), FastAPI+Triton Inference Server+BentoML+TorchServe (model serving), ONNX (cross-framework inference), Feast/Tecton (feature stores), Spark+Ray+Dask (distributed compute), AWS SageMaker/GCP Vertex AI/Azure ML (cloud-managed). Top stack: python, cloud, pytorch, llm, aws. Among jobs with a stated work format, 32% are remote.
Data as of:
Key numbers for the ML Engineer market: open jobs, median salary, observed talent pool and remote share.
The ML Engineer market currently has 2,291 open roles, 2,024 of them freshly observed. Median salary $13,666/mo.
Among jobs with a stated work format, 32% are remote. ML work is cloud-based (training on cloud GPUs, serving in K8s). Outsourcers (EPAM AI / Luxoft AI) — almost always remote. Russian banks (Sber AI banking ML) — hybrid/office compliance. International AI companies — full-remote standard.
⚠ salary known for 309 of 2291 jobs; remote share from 1926 with a stated format; 2024 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many ML Engineer 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
| Period | New postings per week |
|---|---|
| 2026-06-01 | 104 |
| 2026-06-08 | 142 |
| 2026-06-15 | 77 |
| 2026-06-22 | 175 |
| 2026-06-29 | 332 |
| 2026-07-06 | 286 |
| 2026-07-13 | 353 |
| 2026-07-20 | 283 |
| 2026-07-27 | 170 |
| 2026-08-03 | 215 |
| 2026-08-10 | 128 |
| 2026-08-17 | 115 |
| 2026-08-24 | 132 |
| 2026-08-31 | 115 |
| 2026-09-07 | 127 |
| 2026-09-14 | 186 |
| 2026-09-21 | 612 |
| 2026-09-28 | 370 |
| 2026-10-05 | 373 |
| 2026-10-12 | 794 |
| 2026-10-19 | 492 |
| 2026-10-26 | 519 |
| 2026-11-02 | 406 |
| 2026-11-09 | 463 |
Active sources per week
Sources over the period: 217. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 17 |
| 2026-06-08 | 23 |
| 2026-06-15 | 15 |
| 2026-06-22 | 32 |
| 2026-06-29 | 53 |
| 2026-07-06 | 44 |
| 2026-07-13 | 54 |
| 2026-07-20 | 57 |
| 2026-07-27 | 46 |
| 2026-08-03 | 46 |
| 2026-08-10 | 31 |
| 2026-08-17 | 29 |
| 2026-08-24 | 35 |
| 2026-08-31 | 40 |
| 2026-09-07 | 41 |
| 2026-09-14 | 35 |
| 2026-09-21 | 56 |
| 2026-09-28 | 52 |
| 2026-10-05 | 61 |
| 2026-10-12 | 63 |
| 2026-10-19 | 66 |
| 2026-10-26 | 66 |
| 2026-11-02 | 63 |
| 2026-11-09 | 76 |
New sources connected: Jun 29 +30 · Jul 6 +18 · Jul 13 +18 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +11 | 142 |
| Jun 15 | +2 | 77 |
| Jun 22 | +15 | 175 |
| Jun 29 | +30 | 332 |
| Jul 6 | +18 | 286 |
| Jul 13 | +18 | 353 |
| Jul 20 | +11 | 283 |
| Jul 27 | +8 | 170 |
| Aug 3 | +2 | 215 |
| Aug 10 | +7 | 128 |
| Aug 17 | +2 | 115 |
| Aug 24 | +5 | 132 |
| Aug 31 | +9 | 115 |
| Sep 7 | +4 | 127 |
| Sep 14 | +4 | 186 |
| Sep 21 | +10 | 612 |
| Sep 28 | +3 | 370 |
| Oct 5 | +10 | 373 |
| Oct 12 | +3 | 794 |
| Oct 19 | +9 | 492 |
| Oct 26 | +4 | 519 |
| Nov 2 | +5 | 406 |
| Nov 9 | +10 | 463 |
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
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 104 | 17 |
| 2026-06-08 | 142 | 23 |
| 2026-06-15 | 77 | 15 |
| 2026-06-22 | 175 | 32 |
| 2026-06-29 | 332 | 53 |
| 2026-07-06 | 286 | 44 |
| 2026-07-13 | 353 | 54 |
| 2026-07-20 | 283 | 57 |
| 2026-07-27 | 170 | 46 |
| 2026-08-03 | 215 | 46 |
| 2026-08-10 | 128 | 31 |
| 2026-08-17 | 115 | 29 |
| 2026-08-24 | 132 | 35 |
| 2026-08-31 | 115 | 40 |
| 2026-09-07 | 127 | 41 |
| 2026-09-14 | 186 | 35 |
| 2026-09-21 | 612 | 56 |
| 2026-09-28 | 370 | 52 |
| 2026-10-05 | 373 | 61 |
| 2026-10-12 | 794 | 63 |
| 2026-10-19 | 492 | 66 |
| 2026-10-26 | 519 | 66 |
| 2026-11-02 | 406 | 63 |
| 2026-11-09 | 463 | 76 |
Salaries over time
Median ML Engineer salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-09-21 | 12,545 | 16 |
| 2026-09-28 | 10,238 | 28 |
| 2026-10-05 | 9,457 | 39 |
| 2026-10-12 | 9,805 | 56 |
| 2026-10-19 | 13,919 | 92 |
| 2026-10-26 | 13,134 | 93 |
| 2026-11-02 | 13,750 | 85 |
| 2026-11-09 | 12,929 | 110 |
The series starts on Sep 21: there is no data before that.
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
| Week | Median |
|---|---|
| 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 | 12,545 |
| 2026-09-28 | 10,238 |
| 2026-10-05 | 9,457 |
| 2026-10-12 | 9,805 |
| 2026-10-19 | 13,919 |
| 2026-10-26 | 13,134 |
| 2026-11-02 | 13,750 |
| 2026-11-09 | 12,929 |
Remote work over time
Share of ML Engineer postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 44.4 |
| 2026-06-08 | 19.1 |
| 2026-06-15 | 11.5 |
| 2026-06-22 | 22 |
| 2026-06-29 | 25.5 |
| 2026-07-06 | 34.2 |
| 2026-07-13 | 28.4 |
| 2026-07-20 | 47.3 |
| 2026-07-27 | 36.5 |
| 2026-08-03 | 31.2 |
| 2026-08-10 | 34.3 |
| 2026-08-17 | 41.8 |
| 2026-08-24 | 41.7 |
| 2026-08-31 | 34.6 |
| 2026-09-07 | 28.4 |
| 2026-09-14 | 25 |
| 2026-09-21 | 28 |
| 2026-09-28 | 35.7 |
| 2026-10-05 | 37.6 |
| 2026-10-12 | 38.8 |
| 2026-10-19 | 37.8 |
| 2026-10-26 | 46.9 |
| 2026-11-02 | 35.1 |
| 2026-11-09 | 35.3 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 44.4 |
| 2026-06-08 | 19.1 |
| 2026-06-15 | 11.5 |
| 2026-06-22 | 22 |
| 2026-06-29 | 25.5 |
| 2026-07-06 | 34.2 |
| 2026-07-13 | 28.4 |
| 2026-07-20 | 47.3 |
| 2026-07-27 | 36.5 |
| 2026-08-03 | 31.2 |
| 2026-08-10 | 34.3 |
| 2026-08-17 | 41.8 |
| 2026-08-24 | 41.7 |
| 2026-08-31 | 34.6 |
| 2026-09-07 | 28.4 |
| 2026-09-14 | 25 |
| 2026-09-21 | 28 |
| 2026-09-28 | 35.7 |
| 2026-10-05 | 37.6 |
| 2026-10-12 | 38.8 |
| 2026-10-19 | 37.8 |
| 2026-10-26 | 46.9 |
| 2026-11-02 | 35.1 |
| 2026-11-09 | 35.3 |
Technologies over time
How the share of ML Engineer postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | Python | cloud | llm |
|---|---|---|---|
| 2026-08-10 | 40 | 20 | 17.8 |
| 2026-08-17 | 37.7 | 26.4 | 30.2 |
| 2026-08-24 | 32 | 20 | 25.3 |
| 2026-08-31 | 48.1 | 23.1 | 26.9 |
| 2026-09-07 | 34.5 | 13.8 | 29.3 |
| 2026-09-14 | 37.2 | 26.9 | 21.8 |
| 2026-09-21 | 55.5 | 36.1 | 32.3 |
| 2026-09-28 | 59.9 | 33.7 | 28.2 |
| 2026-10-05 | 63.1 | 39.7 | 35.9 |
| 2026-10-12 | 55.6 | 35.4 | 28.6 |
| 2026-10-19 | 63 | 41.2 | 44.3 |
| 2026-10-26 | 66.6 | 37.9 | 35.1 |
| 2026-11-02 | 65 | 29.1 | 35.6 |
| 2026-11-09 | 68.9 | 37.7 | 36.6 |
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
| Week | Python | cloud | llm | pytorch | AWS |
|---|---|---|---|---|---|
| 2026-08-10 | 40 | 20 | 17.8 | 8.9 | 8.9 |
| 2026-08-17 | 37.7 | 26.4 | 30.2 | 17 | 9.4 |
| 2026-08-24 | 32 | 20 | 25.3 | 18.7 | 6.7 |
| 2026-08-31 | 48.1 | 23.1 | 26.9 | 17.3 | 11.5 |
| 2026-09-07 | 34.5 | 13.8 | 29.3 | 20.7 | 13.8 |
| 2026-09-14 | 37.2 | 26.9 | 21.8 | 19.2 | 6.4 |
| 2026-09-21 | 55.5 | 36.1 | 32.3 | 32.9 | 16 |
| 2026-09-28 | 59.9 | 33.7 | 28.2 | 36.9 | 22.6 |
| 2026-10-05 | 63.1 | 39.7 | 35.9 | 33.8 | 27.5 |
| 2026-10-12 | 55.6 | 35.4 | 28.6 | 32.2 | 20.2 |
| 2026-10-19 | 63 | 41.2 | 44.3 | 34.3 | 26.7 |
| 2026-10-26 | 66.6 | 37.9 | 35.1 | 32.9 | 27.2 |
| 2026-11-02 | 65 | 29.1 | 35.6 | 37.4 | 16.3 |
| 2026-11-09 | 68.9 | 37.7 | 36.6 | 36.3 | 29.5 |
Countries over time
How the share of ML Engineer postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | UK | Singapore |
|---|---|---|---|
| 2026-06-01 | 64.6 | 2 | 0 |
| 2026-06-08 | 68.9 | 0.8 | 3.8 |
| 2026-06-15 | 65.8 | 5.5 | 1.4 |
| 2026-06-22 | 33.1 | 1.2 | 18.4 |
| 2026-06-29 | 18.2 | 0.7 | 47.9 |
| 2026-07-06 | 52.2 | 6.5 | 6.1 |
| 2026-07-13 | 45.6 | 3.3 | 11.8 |
| 2026-07-20 | 38.8 | 8.6 | 15.5 |
| 2026-07-27 | 50.7 | 3 | 11.9 |
| 2026-08-03 | 40.2 | 15.6 | 6.1 |
| 2026-08-10 | 38.2 | 14.7 | 2.9 |
| 2026-08-17 | 38 | 14.1 | 0 |
| 2026-08-24 | 33.6 | 24.3 | 0 |
| 2026-08-31 | 21.1 | 30 | 1.1 |
| 2026-09-07 | 30.9 | 28.7 | 2.1 |
| 2026-09-14 | 38 | 27.2 | 2.5 |
| 2026-09-21 | 43.6 | 14 | 7.5 |
| 2026-09-28 | 30.2 | 19.9 | 6.9 |
| 2026-10-05 | 31.8 | 18.2 | 4.5 |
| 2026-10-12 | 32.1 | 11.2 | 2 |
| 2026-10-19 | 29.1 | 14.3 | 4.4 |
| 2026-10-26 | 29.2 | 12 | 3.9 |
| 2026-11-02 | 35.9 | 14 | 8.6 |
| 2026-11-09 | 44.9 | 11 | 2.2 |
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
| Week | USA | UK | Singapore | Poland | India |
|---|---|---|---|---|---|
| 2026-06-01 | 64.6 | 2 | 0 | 16.2 | 6.1 |
| 2026-06-08 | 68.9 | 0.8 | 3.8 | 6.8 | 6.8 |
| 2026-06-15 | 65.8 | 5.5 | 1.4 | 6.8 | 2.7 |
| 2026-06-22 | 33.1 | 1.2 | 18.4 | 21.5 | 3.7 |
| 2026-06-29 | 18.2 | 0.7 | 47.9 | 4.3 | 5.9 |
| 2026-07-06 | 52.2 | 6.5 | 6.1 | 4.9 | 4.9 |
| 2026-07-13 | 45.6 | 3.3 | 11.8 | 3.6 | 9.2 |
| 2026-07-20 | 38.8 | 8.6 | 15.5 | 13.5 | 5.7 |
| 2026-07-27 | 50.7 | 3 | 11.9 | 10.4 | 4.5 |
| 2026-08-03 | 40.2 | 15.6 | 6.1 | 4.5 | 5.6 |
| 2026-08-10 | 38.2 | 14.7 | 2.9 | 2 | 9.8 |
| 2026-08-17 | 38 | 14.1 | 0 | 0 | 4.3 |
| 2026-08-24 | 33.6 | 24.3 | 0 | 3.7 | 8.4 |
| 2026-08-31 | 21.1 | 30 | 1.1 | 1.1 | 8.9 |
| 2026-09-07 | 30.9 | 28.7 | 2.1 | 2.1 | 9.6 |
| 2026-09-14 | 38 | 27.2 | 2.5 | 3.8 | 5.7 |
| 2026-09-21 | 43.6 | 14 | 7.5 | 2.2 | 4.9 |
| 2026-09-28 | 30.2 | 19.9 | 6.9 | 8.5 | 6.9 |
| 2026-10-05 | 31.8 | 18.2 | 4.5 | 9.9 | 6.4 |
| 2026-10-12 | 32.1 | 11.2 | 2 | 8.2 | 8 |
| 2026-10-19 | 29.1 | 14.3 | 4.4 | 9.9 | 6.2 |
| 2026-10-26 | 29.2 | 12 | 3.9 | 5.6 | 7.2 |
| 2026-11-02 | 35.9 | 14 | 8.6 | 4 | 6 |
| 2026-11-09 | 44.9 | 11 | 2.2 | 6.8 | 4.9 |
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 ML Engineer.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.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
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open ML Engineer jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 2,291 |
| Open demand | 2,291 |
| Observed supply | — not published |
ML Engineer — the largest AI/ML role, demand growth 2026 driven by the LLM/Generative AI boom: Foundation Model deployment, RAG applications, AI agents, voice/multimodal products. Russian product companies — a steady flow. EPAM/Luxoft AI Practice — the largest outsource channel for US AI projects.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in ML Engineer jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 4 |
| $1–2k | 2 |
| $2–3k | 7 |
| $3–4k | 7 |
| $4–5k | 9 |
| $5–6k | 14 |
| $6–7k | 11 |
| $7–8k | 4 |
| $8–9k | 9 |
| $9–10k | 16 |
| $10–12k | 31 |
| $12–15k | 68 |
| $15–20k | 83 |
| $20k+ | 44 |
- usable for the calculation: 309 (13.5%)
- stated but not converted to USD/month: 372 (16.2%)
- not stated: 1,610 (70.3%)
One in ten postings offers under $5,027, one in ten over $20,916. Half of the postings offer between $9,600 and $17,416. Sample: 309.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 4 |
| $1–2k | 1,000 | 2,000 | 2 |
| $2–3k | 2,000 | 3,000 | 7 |
| $3–4k | 3,000 | 4,000 | 7 |
| $4–5k | 4,000 | 5,000 | 9 |
| $5–6k | 5,000 | 6,000 | 14 |
| $6–7k | 6,000 | 7,000 | 11 |
| $7–8k | 7,000 | 8,000 | 4 |
| $8–9k | 8,000 | 9,000 | 9 |
| $9–10k | 9,000 | 10,000 | 16 |
| $10–12k | 10,000 | 12,000 | 31 |
| $12–15k | 12,000 | 15,000 | 68 |
| $15–20k | 15,000 | 20,000 | 83 |
| $20k+ | 20,000 | — | 44 |
Which countries have the most open ML Engineer jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 882 | 45.9% |
| United Kingdom | 160 | 8.3% |
| India | 120 | 6.2% |
| Poland | 117 | 6.1% |
| Singapore | 86 | 4.5% |
| Canada | 63 | 3.3% |
| Germany | 58 | 3% |
| France | 38 | 2% |
| Russia | 34 | 1.8% |
| Netherlands | 26 | 1.4% |
| Other countries | 338 | 17.6% |
The leader by ML Engineer job count is the US (882 positions). Poland — AI-friendly EU hub (Warsaw/Krakow). Germany — Berlin AI-startup cluster.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 882 |
| GB | 160 |
| IN | 120 |
| PL | 117 |
| SG | 86 |
| CA | 63 |
| DE | 58 |
| FR | 38 |
| RU | 34 |
| NL | 26 |
Which technologies are most often required in the same job as ML Engineer.
Used together with
Share — how many of the 2,291 jobs in the ML Engineer 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 ML Engineer stack 2026: Python (monopoly), PyTorch / TensorFlow / JAX (PyTorch dominates), scikit-learn + XGBoost + LightGBM + CatBoost (classical), pandas + NumPy + Polars (data), Hugging Face + LangChain + LlamaIndex (LLM/NLP), sentence-transformers + Pinecone / Weaviate / Qdrant / Milvus (vector DBs / RAG), MLflow + W&B + Neptune (experiment tracking), DVC, Airflow / Prefect / Dagster, Docker + Kubernetes, FastAPI + Triton Inference Server + BentoML + TorchServe + vLLM / TGI / SGLang (LLM serving), ONNX, Feast / Tecton (feature stores), Ray + Spark + Dask, AWS SageMaker / GCP Vertex AI / Azure ML, Optuna, Evidently AI (drift). Senior add-ons: LoRA / QLoRA fine-tuning, quantization, distillation.
Common pairs: Python + PyTorch + Hugging Face, Python + scikit-learn + XGBoost + LightGBM, MLflow + DVC + Airflow, Docker + Kubernetes + Triton Inference Server, FastAPI + Triton + ONNX, LangChain + Pinecone + OpenAI API, Ray + PyTorch DDP (distributed training), Feast + Spark + Snowflake. Learning roadmap: Python + math → classical ML (sklearn / XGBoost) → Deep Learning (PyTorch) → MLOps (MLflow + Docker + K8s) → LLM specialisation (Hugging Face + LangChain + RAG) → distributed training (Ray) → cloud-managed ML (SageMaker / Vertex AI).
Chart data
| Name | Count |
|---|---|
| python | 935 |
| cloud | 572 |
| llm | 521 |
| pytorch | 514 |
| aws | 384 |
| mlops | 313 |
| tensorflow | 259 |
| docker | 258 |
| azure | 250 |
| fine-tuning | 225 |
| kubernetes | 225 |
| gcp | 181 |
How many ML Engineer jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 794 |
| principal | 341 |
| junior | 102 |
| lead | 90 |
| middle | 87 |
Junior — rare, typical entry via Data Analyst → ML Junior or Backend Middle → ML Junior. Career flow: Junior (1-2 years) → Middle (2-3 years) → Senior → either Staff / Principal ML Engineer (deep technical), ML Tech Lead / Engineering Manager, a move into Research (with PhD), or ML CTO/Founder at an AI startup.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 794 |
| principal | 341 |
| junior | 102 |
| lead | 90 |
| middle | 87 |
Who hires the most for ML Engineer and how concentrated demand is among the largest companies.
Employers
Demand is spread across 1,312 employers. The largest accounts for 1.7%, the top ten for 8.6%; the remaining 91.4% is long tail.
| share | value |
|---|---|
| top-1 | 1.7% |
| top-3 | 3.9% |
| top-10 | 8.6% |
| long tail | 91.4% |
⚠ 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 ML Engineer jobs from.
Where Zorky sees this market
Observed across 109 sources; the largest accounts for 20.7% — this market does not rest on a single channel.
ML Engineer jobs: hh.ru, Habr Career, getmatch, Djinni, LinkedIn (huge international AI segment), NoFluffJobs / JustJoin.it (Poland AI-friendly), Telegram, career pages of EPAM AI / Luxoft AI / Andersen AI, specialised boards aijobs.net + ai-jobs.net + builtin.com/jobs/ai, Y Combinator Work at a Startup, AI-startup careers pages.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 1,546 | 0.6748 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 616 | 0.2689 |
| telegram | Telegram | Telegram | 115 | 0.0502 |
| community | сообщества и публичные профили | community & public profiles | 14 | 0.0061 |
The newest ML Engineer jobs from company career sites.
Recent openings
- Junior LLM / ML Engineer в Москве · RU
- Senior Machine Learning Engineer · GB
- Machine Learning Engineer · ZA
- Senior Machine Learning Engineer, Content Intelligence · GB
- Senior / Staff ML Engineer (Routing & Optimisation) · GB
- Proxify AB: Senior Machine Learning Engineer
- AI/ML Engineer
- ML Engineer · UA
Latest open ML Engineer jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
ML Engineer overlaps with Data Scientist (statistical modelling + business framing), Research Engineer (novel architectures + papers), MLOps Engineer (ML platform infrastructure), Backend Engineer (production discipline + system design). Comparison with data-scientist/research/mlops — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
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 ML Engineer: general ML Engineer (universal, recsys/NLP/CV/fraud), Applied ML Engineer (product focus + business metrics), Senior ML Engineer (end-to-end pipelines + scaling), Staff / Principal ML Engineer (ML platform architecture for the organisation), ML Tech Lead (team leadership), ML Platform Engineer (infrastructure for other ML teams). Comparison with data-scientist/research/mlops — in the bar below.
Frequently asked questions
The most common questions about ML Engineer: pay, ML Engineer vs DS vs Research vs MLOps, production ML pipeline stack (10 components), how it differs from Applied ML, remote, how to start (8-14 months from Data Analyst / Backend Middle), Senior skills (LLM mastery + MLOps + distributed). Answers recompute automatically.
What does an ML Engineer Junior, Middle, Senior, or Lead earn?
Junior ML Engineer — rare (the market starts with Data Analyst or Backend → ML). The Junior → Middle jump — after mastering the first production ML pipeline end-to-end (feature engineering → training → deployment → monitoring). Middle → Senior — multi-pipeline ownership + LLM/RAG experience + scaling distributed training + cost optimisation. Senior → Staff/Principal — ML platform architecture, multi-team ML strategy. Career flow: Data Analyst (1-2 years) → Junior ML Engineer (1-2 years) → Middle (2-3 years) → Senior → either Staff ML Engineer (deep technical), ML Tech Lead (management), a move into Research (PhD track), or ML Founder/CTO at a startup.
What stack does an ML Engineer most often need?
Top 5: python, cloud, pytorch, llm, aws. Python is the monopoly (R is barely seen in production ML 2026). Classical ML: scikit-learn + XGBoost + LightGBM + CatBoost — base, must for tabular data. Data manipulation: pandas + NumPy + Polars (modern, rising 2026 — 10-100× faster), PyArrow for cross-framework data. Computer Vision: OpenCV, torchvision, Detectron2, MMDetection, Ultralytics YOLO. Experiment tracking: MLflow (open-source standard) or Weights & Biases (premium UI) or Neptune. Data version control: DVC. Orchestration: Airflow + Prefect + Dagster (one deeply). Deployment: Docker + Kubernetes mastery, FastAPI + Triton Inference Server + BentoML + TorchServe (one deeply). Cross-framework inference: ONNX. Feature stores: Feast (open-source) or Tecton (managed). Distributed compute: Spark + Ray + Dask. Cloud-managed ML: AWS SageMaker / GCP Vertex AI / Azure ML (one deeply). Senior extras: quantization (PyTorch quantization, bitsandbytes), distillation, LoRA/QLoRA fine-tuning, vLLM/TGI/SGLang for LLM serving, Optuna for hyperparameter tuning.
ML Engineer vs Data Scientist vs Research vs MLOps — what's the difference?
Data Scientist — focus on business problem framing + statistical modelling + A/B testing + insights communication. Stack: pandas + sklearn + Jupyter + SQL + Tableau/Looker. Less infrastructure-heavy. See Data Scientist. ML Engineer (this page) — focus on production ML pipelines + deployment + scaling. Stack like DS + Docker/K8s + MLflow + Airflow + cloud-managed ML. Research Engineer / Scientist — focus on new models, papers, novel architectures. Often PhD track. Stack: PyTorch deep + JAX + experiment-heavy infrastructure. See Research Engineer / Scientist. MLOps Engineer — focus on ML platform infrastructure (feature stores, model registry, monitoring, observability, cost optimisation). Stack: K8s + Terraform + MLflow/Kubeflow + Prometheus/Grafana + cloud. See MLOps Engineer. Career switch ML Engineer ↔ DS — 1-3 months. ML Engineer ↔ MLOps — 2-4 months (if K8s base exists). Research path requires PhD or 3+ years of deep specialisation.
What does the production ML pipeline stack look like in 2026?
Reference stack for production ML 2026: 1) Data ingestion — Airflow/Prefect/Dagster pulls raw data from source systems (DB/Kafka/S3). 2) Feature engineering — Spark/Pandas/Polars transforms → Feature Store (Feast or Tecton — centralised storage, point-in-time correctness, online+offline serving). 3) Experimentation — Jupyter + W&B/MLflow tracking + DVC for data version control + Optuna for hyperparameter search. 4) Training — Ray Train or PyTorch Lightning + distributed (multi-GPU/multi-node), checkpointing in S3/GCS, quantization (INT8/FP16) for inference cost. 5) Model registry — MLflow Model Registry or SageMaker Model Registry (versioning + stages: staging/production/archived). 6) Validation — automated tests (data drift, prediction quality), shadow deployment, A/B test setup. 7) Serving — Triton Inference Server (NVIDIA, multi-framework + dynamic batching) or BentoML or TorchServe or vLLM (for LLM). FastAPI wrapper for API contract. 8) Deployment — Kubernetes (production standard) + Helm + ArgoCD for GitOps. 9) Monitoring — Prometheus + Grafana (latency/throughput/error rate) + custom drift detection (Evidently AI/WhyLabs) + cost dashboards. 10) Feedback loop — log predictions + ground truth → retraining trigger. ML platform for the whole organisation — Kubeflow or Metaflow or SageMaker Pipelines. LLM-specific stack: vLLM/TGI/SGLang for serving + prompt engineering (LangChain/LlamaIndex) + RAG (vector DBs Pinecone/Weaviate/Qdrant) + fine-tuning via LoRA/QLoRA + evaluation (RAGAS, DeepEval, custom benchmarks).
What share of jobs are remote?
Among jobs with a stated work format, 32% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is ML Engineer different from Applied ML Engineer?
ML Engineer (general) — can work in any ML domain (recsys, NLP, CV, fraud detection, ranking). Stack is universal. Applied ML Engineer — focus on a specific product ML task + business-metrics ownership (CTR, conversion, revenue lift). Stack is the same, but adds product thinking + A/B testing mastery + stakeholder communication. Pay comparable (median), but at product companies Applied ML is usually somewhat higher at Senior thanks to business-impact ownership. ML Platform Engineer (a separate sub-niche — closer to MLOps) — builds infrastructure for other ML Engineers (Feature Store, MLflow infrastructure, training platform). Career choice: ML Engineer if universality and portability matter most, Applied ML Engineer if product impact is interesting, ML Platform Engineer if infrastructure and tooling. All three are legitimate Senior+ paths, not better/worse.
Where to start in ML Engineering in 2026?
Roadmap: 1) Python deep to Backend Middle level (clean code, design patterns, async). Books: "Fluent Python" Ramalho, "Effective Python" Slatkin. 2) Math — linear algebra + calculus + probability/statistics at the level of "understanding what's under the hood of backprop". MIT 18.06 Linear Algebra (Strang), 3Blue1Brown "Essence of Linear Algebra". 3) Classical ML — scikit-learn + XGBoost + LightGBM mastery. Andrew Ng "Machine Learning Specialization" (Coursera). Book "Hands-On Machine Learning" Géron (must-read 2026). 4) Deep Learning — PyTorch deep (forward/backward/optimisers/training loops from scratch). "Deep Learning Specialization" Andrew Ng. "Deep Learning with PyTorch" Stevens. 5) NLP/LLM track: Hugging Face course (free) → fine-tuning small LLMs (Mistral 7B/Llama 3 8B) with LoRA/QLoRA → build a RAG application with LangChain + Qdrant. 6) Computer Vision track (alternative): torchvision + Detectron2 + Ultralytics YOLO + custom dataset training. 7) MLOps basics: MLflow + DVC + Airflow + Docker + Kubernetes for ML serving. "Designing Machine Learning Systems" Chip Huyen — must-read for production ML. 8) Cloud ML: one of AWS SageMaker / GCP Vertex AI / Azure ML — go through one e2e tutorial. 9) Distributed training: Ray Train + PyTorch DDP. 10) Pet project: full e2e ML system (data pipeline + feature store + training + MLflow tracking + Kubernetes deployment + monitoring) on an open dataset (Kaggle). International (EN): fast.ai "Practical Deep Learning", Hugging Face NLP Course, DeepLearning.AI (Andrew Ng). Classic books: "Pattern Recognition and Machine Learning" Bishop, "The Hundred-Page Machine Learning Book" Burkov. Conferences: NeurIPS, ICML, ICLR (papers — must reading for Senior). Data Analyst or Backend Middle → ML Engineer Junior — 8-14 months.
How many open jobs are in this sample?
The published sample contains 2291 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 ML Engineer need?
A Senior ML Engineer owns the full production ML cycle + technical leadership. Programming mastery: Python Backend Senior level (clean code, async, profiling, memory optimisation). Math foundations: linear algebra + calculus + probability at the level of "reading papers without blocks". Classical ML mastery: deep feature engineering, model selection rationale, calibration, evaluation metrics trade-offs, business-aligned model design. Deep Learning mastery: PyTorch deep (custom Layers/Modules/Optimizers), distributed training (DDP, FSDP), mixed-precision, quantization (INT8/FP16), distillation, ONNX export. LLM mastery (2026 must for Senior): fine-tuning via LoRA/QLoRA, prompt engineering, RAG architecture (vector DBs Pinecone/Weaviate/Qdrant), evaluation (RAGAS, DeepEval), vLLM/TGI/SGLang for serving. MLOps: MLflow / W&B mastery, DVC, Airflow / Prefect / Dagster, Feature Stores (Feast / Tecton), Docker + Kubernetes mastery for ML serving, Helm + ArgoCD. Cloud ML: one of AWS SageMaker / GCP Vertex AI / Azure ML deeply. Distributed compute: Ray + Spark mastery. Monitoring: Prometheus + Grafana + Evidently AI (drift detection) integration. Cost optimisation: GPU utilisation, batch sizing, model quantization, caching strategies. System design for ML: design ML systems on whiteboard at 100M+ user scale (recsys / fraud / ranking / chatbot). Soft: papers reading (NeurIPS / ICML / ICLR), technical writing (ADRs, design docs), code review for multiple teams, mentoring Middle ML Engineers, communication with product/data/backend teams, A/B test design + statistical analysis. English for Senior+ MUST — the ML/AI community and papers are in English. Bonus: open-source contributions (PyTorch / Hugging Face / LangChain) — sharply increase market value.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.