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 →

AI / LLM Engineer: market

Data as of November 19, 2026: 4,167 open AI / LLM Engineer jobs, 30% remote among jobs that state a work format; median advertised salary $10,833/mo (from 541 postings that state a salary). Source: Zorky, updated daily.

AI / LLM Engineer — the youngest but loudest role inside the AI/ML/DS direction, which split off in 2023 on the wave of ChatGPT / GPT-4 / Claude / Llama 2. Focus: integrating large language models (LLMs) into a product — NOT training foundation models from scratch (that's Research), NOT classical ML pipelines (that's ML Engineer / Data Scientist), but applied LLM engineering: prompt engineering + RAG (Retrieval-Augmented Generation) + fine-tuning via LoRA / QLoRA + agent architectures + tool use + evaluation. Role family: AI Engineer (general — LLM integration into one product feature: chatbot / summarization / classification / Q&A), LLM Engineer (LLM-deep — server-side optimisation: vLLM / TGI / SGLang serving, KV cache tuning, quantization, speculative decoding), Generative AI Engineer (broader — includes image / video / audio: Stable Diffusion / Flux / Suno / ElevenLabs), AI Agent Engineer (rising 2025–2026 — autonomous agents with tool calling, multi-step reasoning, LangGraph / AutoGen / CrewAI / Microsoft Semantic Kernel), Senior AI Engineer (multi-product LLM architecture + cost optimisation). Stack 2026: Python (monopoly). Vector databases: Pinecone (managed leader — premium), Weaviate (open-source — modular), Qdrant (Rust — fast self-hosted), Milvus (enterprise scale), Chroma (lightweight dev), pgvector (Postgres extension — production-friendly), Elasticsearch dense_vector + Redis Stack (hybrid). Fine-tuning: LoRA + QLoRA (PEFT library by Hugging Face), full fine-tuning rare (cost prohibitive). RLHF / DPO: TRL library (Hugging Face). Serving: vLLM (PagedAttention — record throughput), TGI (Text Generation Inference — Hugging Face), SGLang (programming model for serving + caching), Ollama (local), llama.cpp (CPU + edge). Evaluation: RAGAS, DeepEval, lm-evaluation-harness, Inspect AI (UK AISI), Promptfoo, LangSmith (LangChain trace + eval — best UX). Observability: Helicone, LangSmith, Langfuse (open-source), Arize Phoenix, Datadog LLM Observability. Cost: per-token tracking + prompt caching. Top stack: python, llm, cloud, aws, agile. Among jobs with a stated work format, 30% are remote.

Data as of:

Key numbers for the AI / LLM Engineer market: open jobs, median salary, observed talent pool and remote share.

4,167
open jobs — by job title, reposts merged
$10,833
median $/mo
30%
remote

The AI / LLM Engineer market currently has 4,167 open roles, 3,594 of them freshly observed. Median salary $10,833/mo.

Among jobs with a stated work format, 30% are remote. AI work is fully cloud-based (LLM APIs + vector DBs + cloud GPUs). Outsourcers — almost always remote. International frontier-AI labs — full-remote standard for exceptional candidates. Big Tech AI — hybrid standard. Y Combinator AI startups — premium full-remote.

⚠ salary known for 541 of 4167 jobs; remote share from 3515 with a stated format; 3594 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many AI / LLM 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
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-01190
2026-06-08141
2026-06-15113
2026-06-22326
2026-06-29306
2026-07-06351
2026-07-13463
2026-07-20436
2026-07-27254
2026-08-03354
2026-08-10219
2026-08-17262
2026-08-24235
2026-08-31272
2026-09-07278
2026-09-14307
2026-09-211,096
2026-09-28666
2026-10-05752
2026-10-121,640
2026-10-19888
2026-10-26967
2026-11-02928
2026-11-091,041

Active sources per week

Sources over the period: 278. ▲ — 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-0125
2026-06-0824
2026-06-1521
2026-06-2249
2026-06-2968
2026-07-0658
2026-07-1385
2026-07-2075
2026-07-2766
2026-08-0366
2026-08-1040
2026-08-1744
2026-08-2447
2026-08-3149
2026-09-0749
2026-09-1450
2026-09-2175
2026-09-2871
2026-10-0582
2026-10-1273
2026-10-1983
2026-10-2685
2026-11-0282
2026-11-09107
New sources connected: Jun 22 +28 · Jun 29 +36 · Jul 6 +22 · Jul 13 +26 · Jul 20 +19 · all weeks (23) in the table
WeekNew sourcesNew postings
Jun 8+7141
Jun 15+5113
Jun 22+28326
Jun 29+36306
Jul 6+22351
Jul 13+26463
Jul 20+19436
Jul 27+5254
Aug 3+6354
Aug 10+2219
Aug 17+4262
Aug 24+5235
Aug 31+5272
Sep 7+7278
Sep 14+8307
Sep 21+101,096
Sep 28+6666
Oct 5+8752
Oct 12+81,640
Oct 19+14888
Oct 26+3967
Nov 2+9928
Nov 9+101,041

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 — AI / LLM Engineer. 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-0119025
2026-06-0814124
2026-06-1511321
2026-06-2232649
2026-06-2930668
2026-07-0635158
2026-07-1346385
2026-07-2043675
2026-07-2725466
2026-08-0335466
2026-08-1021940
2026-08-1726244
2026-08-2423547
2026-08-3127249
2026-09-0727849
2026-09-1430750
2026-09-211,09675
2026-09-2866671
2026-10-0575282
2026-10-121,64073
2026-10-1988883
2026-10-2696785
2026-11-0292882
2026-11-091,041107

Salaries over time

Median AI / LLM Engineer 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-08-317,35511
2026-09-07—5
2026-09-14—5
2026-09-218,40625
2026-09-289,03649
2026-10-058,33379
2026-10-128,57884
2026-10-199,457156
2026-10-2610,833165
2026-11-0210,625161
2026-11-0911,417167

The series starts on Aug 31: 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 — AI / LLM Engineer. 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-317,355
2026-09-07—
2026-09-14—
2026-09-218,406
2026-09-289,036
2026-10-058,333
2026-10-128,578
2026-10-199,457
2026-10-2610,833
2026-11-0210,625
2026-11-0911,417

Remote work over time

Share of AI / LLM Engineer 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-0130.3
2026-06-0826.1
2026-06-1521.1
2026-06-2227.6
2026-06-2940.9
2026-07-0639.5
2026-07-1340.8
2026-07-2043.1
2026-07-2746.7
2026-08-0327.7
2026-08-1036.2
2026-08-1730.8
2026-08-2431.3
2026-08-3122.9
2026-09-0720.3
2026-09-1417.6
2026-09-2129.6
2026-09-2833.5
2026-10-0536.5
2026-10-1234.5
2026-10-1935.1
2026-10-2634
2026-11-0230.5
2026-11-0930.5

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 — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-0130.3
2026-06-0826.1
2026-06-1521.1
2026-06-2227.6
2026-06-2940.9
2026-07-0639.5
2026-07-1340.8
2026-07-2043.1
2026-07-2746.7
2026-08-0327.7
2026-08-1036.2
2026-08-1730.8
2026-08-2431.3
2026-08-3122.9
2026-09-0720.3
2026-09-1417.6
2026-09-2129.6
2026-09-2833.5
2026-10-0536.5
2026-10-1234.5
2026-10-1935.1
2026-10-2634
2026-11-0230.5
2026-11-0930.5

Technologies over time

How the share of AI / LLM Engineer 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.
PeriodPythonllmcloud
2026-08-1023.436.921.6
2026-08-1739.346.217.9
2026-08-2429.534.117.8
2026-08-3135.746.210.5
2026-09-0734.748.424.2
2026-09-1432.84026.4
2026-09-2138.244.435
2026-09-2856.955.741.8
2026-10-0559.254.340.6
2026-10-1250.350.741
2026-10-1959.860.243.6
2026-10-2659.556.350.6
2026-11-0263.357.940.7
2026-11-0961.45544.9
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 — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekPythonllmcloudAWSAzure
2026-08-1023.436.921.616.27.2
2026-08-1739.346.217.91212
2026-08-2429.534.117.88.511.6
2026-08-3135.746.210.510.58.4
2026-09-0734.748.424.26.512.9
2026-09-1432.84026.45.68.8
2026-09-2138.244.43517.813.5
2026-09-2856.955.741.829.433.6
2026-10-0559.254.340.62627.5
2026-10-1250.350.74123.922.2
2026-10-1959.860.243.628.225.4
2026-10-2659.556.350.631.928.6
2026-11-0263.357.940.726.724.5
2026-11-0961.45544.926.328.6

Countries over time

How the share of AI / LLM Engineer 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.
PeriodUSAUKPoland
2026-06-0150.82.217.3
2026-06-0851.97.810.9
2026-06-1558.8213.7
2026-06-2229.70.734.7
2026-06-2927.7416.6
2026-07-0631.45.210.8
2026-07-1333.3511.8
2026-07-2034.11718.7
2026-07-2729.611.318.8
2026-08-0335.318.54.8
2026-08-1028.227.63.1
2026-08-1737.320.11.4
2026-08-2432.122.34.3
2026-08-3137.624.51.7
2026-09-0740.917.53.2
2026-09-1437.7201.1
2026-09-2135.912.24.1
2026-09-2837.511.911.9
2026-10-0531.711.715
2026-10-1222.29.210.9
2026-10-192611.213.3
2026-10-2627.8127
2026-11-0228.612.67.4
2026-11-0928.411.47.5
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 — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekUSAUKPolandIndiaGermany
2026-06-0150.82.217.312.31.1
2026-06-0851.97.810.913.27.8
2026-06-1558.8213.76.94.9
2026-06-2229.70.734.773.7
2026-06-2927.7416.67.53.2
2026-07-0631.45.210.813.64.9
2026-07-1333.3511.812.13.7
2026-07-2034.11718.74.72.5
2026-07-2729.611.318.83.85.9
2026-08-0335.318.54.86.81.7
2026-08-1028.227.63.16.13.7
2026-08-1737.320.11.47.71.9
2026-08-2432.122.34.38.22.2
2026-08-3137.624.51.78.32.2
2026-09-0740.917.53.27.91.2
2026-09-1437.7201.112.10.4
2026-09-2135.912.24.174.1
2026-09-2837.511.911.97.45.2
2026-10-0531.711.7155.77.5
2026-10-1222.29.210.99.210
2026-10-192611.213.36.67.8
2026-10-2627.81278.65.3
2026-11-0228.612.67.47.26.1
2026-11-0928.411.47.58.66.4

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 AI / LLM Engineer.

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 — AI / LLM Engineer. 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 AI / LLM Engineer 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 demand4,167
Open demand4,167
Observed supply— not published

AI Engineer — the fastest-growing AI/ML sub-niche (split off in 2023 after the ChatGPT boom). The real market is broader than the visible pool — many AI roles classified as general ML Engineer / Backend in our matcher (titles like "Senior Backend Engineer with AI focus"). Drivers 2026: LLM adoption across all products (chatbots / summarisation / Q&A / code-assist), RAG applications for enterprise knowledge bases, agentic workflows (rising 2025–2026), Foundation Model startups race. International remote via frontier-AI labs + Y Combinator AI startups — premium segment.

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

How salaries in AI / LLM Engineer jobs are distributed, in US dollars per month.

Salary distribution

P25 $7,699 · P50 $10,833 · P75 $15,625
Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
<$1k4
$1–2k10
$2–3k11
$3–4k11
$4–5k11
$5–6k30
$6–7k32
$7–8k37
$8–9k45
$9–10k34
$10–12k80
$12–15k81
$15–20k113
$20k+42
Salary in postings: base 4,167
  • usable for the calculation: 541 (13%)
  • stated but not converted to USD/month: 543 (13%)
  • not stated: 3,083 (74%)

One in ten postings offers under $5,411, one in ten over $19,166. Half of the postings offer between $7,699 and $15,625. Sample: 541.

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

Which countries have the most open AI / LLM Engineer jobs.

Demand geography

countryjobsshare
United States1,05030.3%
United Kingdom3299.5%
Poland3088.9%
India2848.2%
Germany2146.2%
Canada1243.6%
France1103.2%
Singapore1073.1%
Spain651.9%
Russia601.7%
Other countries81923.6%

The leader by AI Engineer job count is the US (1050 positions) — but the young-niche pool is small, not fully representative. Poland — AI-friendly EU hub (Warsaw / Krakow). Germany — Berlin AI cluster (Aleph Alpha + Black Forest Labs). France — Paris (Mistral + Hugging Face HQ). UK — London. USA — Bay Area (the largest AI hub).

⚠ job counts only: salary by country is not published

Chart data
Demand geography — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
US1,050
GB329
PL308
IN284
DE214
CA124
FR110
SG107
ES65
RU60

Which technologies are most often required in the same job as AI / LLM Engineer.

Used together with

python
1,56237.5%
llm
1,53536.8%
cloud
1,33131.9%
aws
84720.3%
azure
79019%
docker
47711.4%
langchain
44110.6%
langgraph
42510.2%
gcp
4019.6%
mlops
3568.5%

Share — how many of the 4,167 jobs in the AI / LLM 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).

Chart data
Used together with — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
python1,562
llm1,535
cloud1,331
aws847
azure790
docker477
langchain441
langgraph425
gcp401
mlops356
embeddings355
fine-tuning333

How many AI / LLM Engineer jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior1,284
principal316
lead312
junior201
middle184

Junior — typical entry Backend Senior / ML Engineer Middle + LLM portfolio (demonstrable RAG + LangChain experience). Career flow: Backend Senior / ML Middle (2-3 years) + LLM interest → AI Engineer Junior (1-2 years) → Middle (2-3 years) → Senior → either Staff / Principal AI Engineer, AI Tech Lead / Engineering Manager, a move into a frontier-AI lab, or AI startup founder. If grade data is sparse — check the ml-engineer + research pages for broader benchmarks.

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

Chart data
Demand by grade — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior1,284
principal316
lead312
junior201
middle184

Who hires the most for AI / LLM Engineer and how concentrated demand is among the largest companies.

Employers

Demand is spread across 2,497 employers. The largest accounts for 1.1%, the top ten for 5.0%; the remaining 95.0% is long tail.

largest 1.1%2nd–3rd 1.3%4th–10th 2.6%the rest 95%
sharevalue
top-11.1%
top-32.3%
top-105.0%
long tail95.0%

⚠ 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 AI / LLM Engineer jobs from.

Where Zorky sees this market

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

Chart data
Where Zorky sees this market — AI / LLM Engineer. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites2,5300.6072
boardджоб-борды и агрегаторыjob boards & aggregators1,3920.3341
telegramTelegramTelegram2220.0533
communityсообщества и публичные профилиcommunity & public profiles230.0055

The newest AI / LLM Engineer jobs from company career sites.

Recent openings

All jobs →

Latest open AI Engineer jobs — most recent positions in the sample (young niche, sample is small). The full list is in our CRM or via the "see all" link below. For broader view, see the ml-engineer + research pages.

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 AI / LLM Engineer: AI Engineer (general — LLM integration into one product feature), LLM Engineer (LLM-deep — vLLM / TGI serving + KV cache + quantization + speculative decoding), Generative AI Engineer (broader — image / video / audio: Stable Diffusion / Flux / Suno / ElevenLabs), AI Agent Engineer (rising 2025–2026 — autonomous agents with tool use + multi-step reasoning), Senior AI Engineer (multi-product LLM architecture + cost optimisation). Comparison with ml-engineer/data-scientist/research/mlops — in the bar below.

Computer VisionData ScientistML EngineerMLOpsNLP EngineerResearch Engineer

Frequently asked questions

The most common questions about AI / LLM Engineer: pay (premium segment for rare-skill), AI Engineer vs ML Engineer vs Data Scientist (3-way comparison), RAG vs Fine-tuning vs Prompt Engineering (decision tree + cost reality), AI Agent Engineer (rising 2025–2026 sub-specialisation), remote, how to become one (2-4 months from Backend Senior — fastest entry into the ML world), Senior skills (LangChain + advanced RAG + agent architectures + cost optimisation + open-source contributions). Answers recompute automatically.

What does an AI Engineer Junior, Middle, Senior, or Lead earn?

Junior — typical entry: Backend Middle / ML Engineer Middle / Data Scientist Middle + LLM hobby projects (demonstrable RAG + LangChain experience). The Junior → Middle jump — after the first production LLM-feature deployment (chatbot / summarisation / Q&A in a real product with real users). Middle → Senior — multi-feature LLM ownership + cost optimisation + evaluation methodology. Senior → Staff / Principal — org-wide AI strategy + multi-product LLM platform architecture. Career flow: Backend Senior / ML Engineer Middle (2-3 years) + LLM interest → AI Engineer Junior / Middle (1-2 years) → Senior → either Staff / Principal AI Engineer, AI Tech Lead / Engineering Manager, a move into a frontier-AI lab, or AI startup founder.

What stack does an AI Engineer most often need?

Top 5: python, llm, cloud, aws, agile. Python deep (monopoly — async / typing / FastAPI). Each provider has its quirks (rate limits + retry strategies + cost per token + feature support). LLM Frameworks: LangChain mastery — the largest job market (LCEL — LangChain Expression Language, callbacks, agents, retrievers), LlamaIndex (RAG-focused — data ingestion + indexing strategies), Haystack (deepset), Semantic Kernel (Microsoft for .NET shops), LangGraph (DAG-style agent orchestration — LangChain), AutoGen + CrewAI (multi-agent — rising), DSPy (Stanford — declarative LLM programming, growing). Vector DB mastery: Pinecone (managed leader), Weaviate (open-source modular), Qdrant (Rust-based — fast self-hosted), Milvus (enterprise scale), Chroma (lightweight dev / prototyping), pgvector (Postgres extension — production-friendly for existing Postgres shops), Elasticsearch dense_vector + Redis Stack (hybrid full-text + vector). Fine-tuning: LoRA + QLoRA via PEFT library (Hugging Face — standard 2026), Unsloth (faster LoRA training), Axolotl (config-driven fine-tuning). Full fine-tuning rare (cost prohibitive). RLHF / DPO / KTO: TRL library (Hugging Face — Direct Preference Optimization growth 2024+). Evaluation: RAGAS (RAG-specific — faithfulness + answer relevancy + context precision), DeepEval, lm-evaluation-harness (academic benchmarks), Inspect AI (UK AISI safety-focused), Promptfoo (regression testing for prompts), LangSmith (LangChain trace + eval — best UX). Observability + tracing: Helicone (LLM-specific APM), LangSmith, Langfuse (open-source), Arize Phoenix, Datadog LLM Observability (2024+ feature). Cost optimisation: prompt caching, prompt compression (LLMLingua), model routing (small model for easy queries, large for complex — through providers like Martian / OpenRouter).

AI Engineer vs ML Engineer vs Data Scientist — what's the difference?

Data Scientist — focus on statistical modelling + A/B testing + business problem framing. Stack: pandas + sklearn + XGBoost + Jupyter + SQL + Tableau. See Data Scientist. ML Engineer — focus on production ML pipelines + deployment + scaling. Stack: PyTorch + sklearn + Kubernetes + MLflow + cloud-managed ML. Generalist — works with recsys / fraud / ranking / classical ML. See ML Engineer. AI Engineer (this page) — focus on LLM integration in product. Does NOT train foundation models (that's Research), does NOT build classical ML pipelines (that's ML Engineer). Stack: Python + LLM providers + LangChain / LlamaIndex + vector DBs + vLLM serving + RAG patterns + LoRA fine-tuning + LLM evaluation tools. Key distinction 2026: AI Engineer reuses pre-trained LLMs, ML Engineer often trains models from scratch. AI Engineer works with API/prompts/RAG; ML Engineer — with training loops + feature engineering. Career pivots: Backend Senior → AI Engineer Junior — 2-4 months (fast ramp thanks to API-based work + learnable LangChain). ML Engineer Senior → AI Engineer Senior — 1-3 months (already knows stack basics, needs to deepen LLM-specific). DS Senior → AI Engineer Middle — 3-6 months. AI Engineer Senior → Research — requires deeper math + paper-writing experience + 6-12 months of preparation.

RAG vs Fine-tuning vs Prompt Engineering — what to pick?

Decision tree for LLM customisation 2026: 1) Prompt Engineering — first try. Use case: zero-shot or few-shot ENOUGH for the task. Pros: zero cost (no training), instant iteration, model-agnostic. Cons: limited control, prompt fragility, context-window pressure. 2) RAG (Retrieval-Augmented Generation) — best for knowledge-grounded tasks. Use case: chatbot, Q&A, document search, customer support, code documentation, internal knowledge bases. Architecture: query → embed → vector search → top-k documents → augment prompt with retrieved context → LLM generates answer. Pros: factual grounding (anti-hallucination), up-to-date (just update the index, no retraining), source citation possible, cheaper than fine-tuning. Cons: retrieval quality bottleneck, prompt size grows. RAG stack 2026: ingestion (LlamaIndex / LangChain document loaders) → chunking strategy (semantic vs fixed-size vs recursive) → embeddings → vector DB (Pinecone / Qdrant / Weaviate / pgvector) → retrieval (similarity + reranking via Cohere Rerank / BGE Reranker) → prompt augmentation → LLM generation. Advanced RAG: hybrid search (vector + BM25), HyDE (Hypothetical Document Embeddings), query rewriting, multi-hop retrieval, self-reflection (CRAG / Self-RAG). 3) Fine-tuning — use when prompt engineering + RAG aren't enough. Use case: a) domain-specific style / format (medical / legal — specific phrasing patterns), b) reduce token cost (a smaller fine-tuned model replaces a larger general model), c) tasks requiring deep specialised knowledge (where RAG context window doesn't help). LoRA trains adapters while keeping the base weights frozen. The share of trainable parameters depends on the model, adapter rank and selected modules. LoRA. Stack: Hugging Face Transformers + PEFT + TRL + Unsloth (faster) + Axolotl (config-driven). Hardware: 24GB GPU (RTX 4090 / A6000) for 7-13B models, 80GB+ (A100/H100) for 70B+. Cost reality 2026: prompt engineering — minutes, $0. RAG setup — 1-2 weeks engineering, $100-1,000/mo API costs. 4) Combination: real production AI features typically use ALL three. Prompt engineering first (system prompts + few-shot examples) → RAG for grounding → optional LoRA fine-tuning for style/format. 5) Agentic patterns (rising 2025–2026) — LLM + tool use + multi-step reasoning. Use LangGraph / AutoGen / CrewAI / DSPy.

What share of jobs are remote?

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

Where to start in AI Engineering in 2026?

Roadmap: 1) Python deep + Backend basics — async / typing / FastAPI / pytest. Without Backend skill — not an AI Engineer (just a prompt jockey). Book: "Fluent Python" Ramalho. 2) LLM fundamentals understanding — transformer architecture basics (attention + tokenisation + decoding strategies + context windows), but you don't need to implement from scratch. Course: "Building LLMs from scratch" Karpathy YouTube (free — best for intuition). Book: "Hands-On Large Language Models" Jay Alammar / Maarten Grootendorst (2024 — must-read). 3) OpenAI API mastery — chat completions + function calling + structured outputs + streaming + assistants. Build a minimum of 3 real apps. Free credits + cheap experimentation. 4) Anthropic Claude API mastery — best for coding + long-context use cases. Tool use + prompt caching + computer use (if AI Agent track interests you). 5) LangChain mastery — the largest job-market requirement. LCEL (LangChain Expression Language), chains, agents, retrievers, callbacks. Course: "LangChain & Vector Databases in Production" DeepLearning.AI (free). 6) RAG architecture deep — document loaders + chunking strategies (semantic / fixed / recursive) + embeddings choice + vector DB selection + retrieval algorithms + reranking. Build a production RAG app with advanced patterns (hybrid search + reranking + HyDE). 7) Vector DB mastery — at least one deeply (Qdrant — best for self-hosted learning) + one managed (Pinecone). Understanding HNSW / IVF / PQ algorithm basics. 8) Fine-tuning hands-on — LoRA / QLoRA via PEFT library + Unsloth (faster). Fine-tune Llama 3.x 8B on your own dataset. Hardware: Google Colab Pro+ ($50/mo) or RunPod / Vast.ai (cheap GPU rental). 9) vLLM serving — deploy an open model with vLLM + benchmark throughput + compare with OpenAI API. 10) Evaluation mastery — RAGAS + DeepEval + custom evaluation suite. Build a regression test for prompts. 11) LangSmith / Langfuse observability — instrument a production app + analyse traces + identify bottlenecks. 12) Agent frameworks — LangGraph + AutoGen + CrewAI + DSPy basics. Build a multi-agent demo (research agent + writing agent + critic agent). 13) Pet-project portfolio: production-grade AI feature (e.g. document Q&A for an open dataset) with RAG + evaluation + observability + cost tracking. Document as portfolio (GitHub + blog post + demo video). RU courses: Karpov.Courses "AI Engineer" track, Otus "LLM Engineering", HSE School of AI, School21 (Sber) AI Engineer track. Must-read books: "AI Engineering" Chip Huyen (2024), "Hands-On Large Language Models" Alammar / Grootendorst, "Building LLMs for Production" Bouchard / Peng. Backend Senior + LLM interest → AI Engineer Junior — 2-4 months (fastest entry into the ML world). ML Engineer Senior → AI Engineer Senior — 1-3 months. Data Scientist → AI Engineer Middle — 3-6 months.

How many open jobs are in this sample?

The published sample contains 4167 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 AI Engineer need?

A Senior AI Engineer owns the full LLM-product engineering cycle + cost optimisation + technical leadership. Python deep + Backend Senior level: async / typing / FastAPI / pytest mastery. Open LLM knowledge: Llama 3.x / Mistral / Qwen 2.5 / DeepSeek V3 + R1 / Phi 3 / Gemma 2 — performance / cost trade-offs, when to use which. LangChain mastery: LCEL deep, callbacks, agents, retrievers, custom chain authoring, debugging through LangSmith. Or equivalent in LlamaIndex / Haystack / Semantic Kernel. RAG architecture mastery: advanced patterns (hybrid search BM25 + vector, reranking, HyDE, query rewriting, multi-hop retrieval, self-reflection patterns CRAG / Self-RAG), chunking strategies (semantic + recursive + hierarchical), embedding model selection. Vector DB mastery deep: one of Pinecone / Qdrant / Weaviate / Milvus / pgvector deeply — index tuning, sharding, replication, hybrid search implementation. Fine-tuning mastery: LoRA / QLoRA via PEFT + Unsloth + Axolotl, dataset preparation (instruction tuning + DPO data), hyperparameter selection, evaluation methodology. RLHF / DPO / KTO basics: TRL library for preference optimisation. Serving mastery: vLLM advanced (PagedAttention + continuous batching + speculative decoding + KV cache optimisation), TGI, SGLang. Agent architectures: LangGraph + AutoGen + CrewAI + DSPy mastery, MCP (Model Context Protocol) implementation, tool use design patterns, multi-agent orchestration. Evaluation mastery: RAGAS + DeepEval + custom evaluation suite design, LLM-as-judge methodology, regression testing for prompts, A/B testing for LLM features. Observability + tracing: LangSmith + Langfuse + Helicone + Arize Phoenix + Datadog LLM Observability mastery. Cost optimisation mastery: prompt caching strategies (native + custom Redis), prompt compression (LLMLingua), model routing (small for easy / large for complex via OpenRouter / Martian), batch API for non-real-time. Safety / guardrails: NeMo Guardrails, Llama Guard, OpenAI Moderation API integration, prompt injection defence, output filtering. System design for LLM products: design a RAG-based product on whiteboard at 100M+ queries/day scale, multi-region considerations, latency budgets (target P95 < 2s for chat). Soft: ADRs writing for LLM architecture decisions, technical writing (LLM feature design docs), cross-team collaboration (Product / Backend / DS / Research teams), mentoring Middle AI Engineers, paper-reading discipline (NeurIPS / ICLR / EMNLP — must follow). English for Senior+ MUST — AI community / docs / papers / conferences are entirely English. Optional bonus: open-source contributions to LangChain / LlamaIndex / vLLM / Hugging Face — sharply increase market value for frontier-AI labs hiring. Twitter AI presence (regular posting about LLM experiments) — important for hiring through community connections.

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.