How we recognise an AI engineer on GitHub

We count someone as an AI engineer when their public work builds products on top of models rather than training them: LLM applications, retrieval (RAG), agents and tool calling.

In practice, their repositories, descriptions or bio carry at least two such signals: frameworks like LangChain, LlamaIndex or DSPy, vector stores like Qdrant, pgvector or FAISS, model APIs, evaluation and tracing tools like Langfuse or promptfoo. Training-side work (PyTorch, JAX, computer vision) is classified as AI research instead, and one profile can carry both roles.

The stack inside the role

Model APIs come and go; the retrieval and orchestration layer is where the role is decided. The technologies most present in their repositories:

#TechnologyShare of AI engineers
1AI agent48%
2Python38%
3RAG37%
4LLM36%
5TypeScript28%
6Node.js13%
7PyTorch12%
8React8%
9AWS8%
10LLM inference7%

Which countries have the most AI engineers?

Volume follows the large tech hubs, where most LLM products are built. The index column shows where AI product work weighs most among local developers.

#CountryDevelopersShare of local developersvs index
1United States19,000+32%1.4x
2United Kingdom3,300+25%1x
3India2,900+32%1.3x
4France2,500+22%0.9x
5Germany2,000+23%1x
6China1,700+33%1.4x
7Canada1,500+29%1.2x
8Japan1,300+29%1.2x
9Brazil1,000+20%0.8x
10South Korea870+24%1x

Min. 1,000 indexed developers and 30 AI engineers per country; counts rounded down. Method: by-country study.

China stands out: 33% of its indexed developers, 1.4x the index average.

Cities

#CityShare of located AI engineers
1San Francisco10%
2London5%
3New York5%
4Seattle4%
5Paris3%
6Boston2%
7Tokyo2%
8Los Angeles2%

Where the role overlaps with others

A profile can carry two roles. 19% of AI engineers also qualify for AI research: a spec asking for both describes a real, if narrower, profile.

#Also classified asShare of AI engineers
1Software engineering51%
2AI research19%
3Infrastructure, DevOps and SRE19%

How reachable are they?

SignalAI engineersIndex average
Public email31%27%
Available for hire20%15%
Pushed code, last 90 days69%54%

Ask for the evidence rather than the title. A repository that wires retrieval, evaluation and a model API together says more than "5 years of AI", a claim nobody can have made about LLM applications for long.

Who employs AI engineers today?

#Company
1Microsoft
2Red Hat
3Google
4NVIDIA
5IBM
6AWS
7Amazon
8Carnegie Mellon University

What they build themselves

#RepositoryStars
1obra/superpowers★ 281,184
2mattpocock/skills★ 277,760
3affaan-m/ECC★ 239,759
4getify/You-Dont-Know-JS★ 184,937
5msitarzewski/agency-agents★ 149,954

For the language side of the same search, see the guides to hiring Python developers and hiring TypeScript developers. To write the query by hand first, use the GitHub user search builder.

Frequently asked questions

How many AI engineers are on GitHub?

At least 78,000: that is how many StarHunt's index places in the role as of October 2026, counting only work visible in public repositories.

Is an AI engineer the same as a machine learning engineer?

Not in how the work shows on GitHub. AI engineers build applications on top of existing models: retrieval, agents, evaluation. Machine learning engineers and researchers train and serve the models themselves, with PyTorch, JAX or inference servers. StarHunt classifies the second group as AI research.

Where are AI engineers concentrated?

San Francisco is the largest hub among those we can place on a map, and China has the highest concentration relative to its size.

Search this pool yourself.

Describe the product you are building and get engineers who have shipped retrieval, agents or evaluation in public, ranked on the last twelve months.

Find AI engineers