LLM jobs: who is hiring, what they ask for and what they pay
LLM hiring is heavily remote, mostly senior, and led by a small set of large employers, while salary data is strongest in USD and too sparse in several other currencies to generalize.
LLM jobs are concentrated in remote roles, skew senior, and pay well where employers state a salary; these are Jobee's counts of open postings collected on 14 November 2026. The market is led by a few large employers, Python is the most common skill asked alongside LLM work, and salary data is plentiful in USD but thin in several other currencies.
LLM jobs: how much hiring is open right now
Jobee counted 12,613 open LLM jobs from 2,535 employers. That is enough volume to show a real market, but not enough to say it is one neat market. The postings are spread across countries, seniority levels, work patterns, and salary disclosure habits, which matters for anyone applying now.
A useful first read is freshness. 4,313 of 12,613 postings (34.2%) were posted in the last 30 days. That means a little over a third of the visible market is recent, so the listings are not all old holdovers. If you are searching now, you still have active employers to target, but you also need to move quickly on the most relevant roles because the market is broad and competitive.
The spread across employers is also a clue. The top employer in the data is Google with 871 postings, followed by NVIDIA with 689, Salesforce with 468, Amazon.com Services LLC with 463, Bjak with 342, Anthropic with 284, Sezzle with 274, Weloglobal with 189, Adobe with 168, Cloudflare with 156, Welo Global with 150, and Databricks with 119. That mix says two things. First, LLM hiring is not limited to one type of company. Second, the biggest demand is concentrated in employers that can staff many teams at once, so a candidate should expect variation in title, team scope, and product stage even inside the same employer.
For job seekers, that means the best approach is not to search only for the phrase "LLM" and stop there. The title may be about applied AI, machine learning, platform engineering, research, product engineering, or infrastructure, even when the actual work is LLM-related. The employer list shows this especially clearly: the same market includes product companies, cloud companies, infrastructure companies, and AI-native employers.
LLM jobs: who is hiring most often
The employer list is dominated by a handful of names with very large posting counts. That tells you the market is being pulled by organizations that are hiring across multiple functions rather than by one-off niche openings. In practice, that usually means a candidate is more likely to find several adjacent roles at the same employer, which can be useful if one title is not a fit but the skill set is.
Google's 871 postings make it the largest single source of visible LLM hiring in this set. NVIDIA's 689 postings are next, which fits a market where model training, inference, and AI infrastructure all matter. Salesforce's 468 and Amazon.com Services LLC's 463 show that enterprise software and large-scale product organizations are also hiring heavily. Anthropic's 284 postings stand out because the employer is more directly associated with LLM work than many of the others on the list. Adobe, Cloudflare, and Databricks also appear among the largest hiring employers, which suggests demand spans application layers, infrastructure, and data tooling.
The practical lesson is simple: do not assume the same employer is hiring for the same kind of role across every listing. A large employer can have roles for research, deployment, product integration, evaluation, infrastructure, and operations. If your background is stronger on one side of the LLM stack, the employer list still gives you multiple ways in.
LLM jobs: which levels employers want
Most visible LLM hiring is senior. 5,470 of 12,613 postings (43.4%) are Senior. That is the single largest level by far. After that, 2,266 postings (18.0%) do not state a level at all, 1,432 postings (11.4%) are Mid-level, 1,151 postings (9.1%) are Lead, 695 postings (5.5%) are Staff, 651 postings (5.2%) are Director, 370 postings (2.9%) are Junior, 270 postings (2.1%) are Principal, 221 postings (1.8%) are Intern, 49 postings (0.4%) are C-level, and 38 postings (0.3%) are VP.
That shape matters. It says LLM hiring is not mainly an entry-level market. The biggest slice is Senior, and the next biggest slices are still experienced roles. If you are early in your career, the data suggests fewer open doors at Junior and Intern level than at Senior level, so your search will be narrower. You will probably need to target roles that explicitly mention applied AI, software engineering, data engineering, or machine learning foundations rather than only looking for titles that say LLM.
The 18.0% with no stated level is also useful. It means plenty of employers are not being clear about seniority in the title or posting. If you are comfortable with ambiguity, those postings can be worth a look, but they also mean you need to read carefully for the actual scope of ownership, expected experience, and team structure.
For applicants, the level mix also explains why so many postings mention broader engineering ability. Senior and Lead roles usually assume you can work across systems, communicate with product teams, and make trade-offs around deployment, quality, and speed. The posting data supports that expectation.
LLM jobs: where the work happens
Most LLM jobs in this set are remote. 7,547 of 12,613 postings (59.8%) are remote. 624 of 12,613 postings (4.9%) are hybrid. 957 of 12,613 postings (7.6%) are on-site. 3,485 of 12,613 postings (27.6%) do not say where the work happens.
That is a strong remote tilt. More than half the market is remote, while hybrid and on-site together are a much smaller share. For job seekers, that means location flexibility is a major advantage in this market. If you can work remotely, your pool is much wider. If you need to stay local, you are filtering out a very large share of openings.
The 27.6% that do not say where the work happens is almost as important as the remote share. A posting that leaves location unclear is still a posting, but it makes the application process harder. You may have to infer location from the employer, ask in the first conversation, or wait until later in the process to learn whether the role can be done remotely. Since the data already shows that most roles are remote, an unclear posting is worth checking quickly rather than assuming it is flexible.
The advice that follows from this figure is straightforward: if you need remote work, prioritize postings that say remote clearly, because the market has enough of them to make that a realistic filter. If you need on-site work for visa, relocation, or collaboration reasons, the on-site share is much smaller, so your search will be more constrained.
LLM jobs: what they ask for alongside LLM work
The most common adjacent skill is Python. 5,687 of 12,613 postings (45.1%) ask for Python. After that come AWS with 3,288 postings (26.1%), SQL with 2,315 postings (18.4%), CI/CD with 2,179 postings (17.3%), Google Cloud with 1,846 postings (14.6%), TypeScript with 1,793 postings (14.2%), Java with 1,724 postings (13.7%), Azure with 1,721 postings (13.6%), Kubernetes with 1,718 postings (13.6%), Prototyping with 1,553 postings (12.3%), A/B Testing with 1,474 postings (11.7%), and JavaScript with 1,407 postings (11.2%).
This is one of the clearest signals in the whole dataset. LLM jobs are not being written as pure model-research roles. They are being written as engineering jobs that need Python, cloud, deployment, data handling, and product experimentation. Python leads by a wide margin, so a candidate who does not have that language in hand is likely to be screened out often. AWS is also prominent, which suggests the work often touches cloud deployment and managed services. SQL points to data access, analytics, and retrieval. CI/CD and Kubernetes show that deployment and operational quality matter, not just model quality. Google Cloud and Azure show that multi-cloud experience can help. TypeScript and JavaScript suggest the front end or product layer still matters in a lot of these roles. Prototyping and A/B Testing suggest employers want people who can test ideas quickly and measure whether they work.
The application lesson is direct: an LLM candidate who can only talk about prompts and model behavior is missing most of what employers are asking for. The postings say that engineering depth matters. If your background includes Python, cloud tools, deployment, and product iteration, you will match more of the market. If it does not, you may still qualify for some roles, but you will need to show those skills through projects or previous work.
It also helps explain why seniority skews high. Employers want people who can not only build with LLMs but ship systems around them.
LLM jobs: what the salary data shows
Salary disclosure is only partial. 5,942 of 12,613 postings (47.1%) state a salary, while 6,671 of 12,613 postings (52.9%) do not state a salary. That means slightly more than half the postings still leave pay out entirely.
When employers do state pay, the picture varies by currency.
| Currency | Postings with yearly pay | Lower quartile | Median | Upper quartile |
|---|---|---|---|---|
| USD | 4,464 | 166,000 USD | 204,000 USD | 254,000 USD |
| EUR | 263 | 67,000 EUR | 94,000 EUR | 122,000 EUR |
| CAD | 197 | 128,000 CAD | 165,000 CAD | 199,000 CAD |
| GBP | 101 | 101,000 GBP | 170,000 GBP | 232,000 GBP |
| PLN | 50 | 284,000 PLN | 399,000 PLN | 477,000 PLN |
| INR | 24 | 1,962,000 INR | 3,662,000 INR | 5,125,000 INR |
USD is the clearest pay market in the data, with 4,464 postings carrying yearly pay. That is far more than any other currency. EUR has 263 postings with yearly pay, CAD has 197, GBP has 101, PLN has 50, and INR has 24. The sharp drop after USD means most salary comparisons in this market are easiest to make in USD, while the other currencies are still informative but based on much smaller sets of postings.
The safest reading is this: where salaries are stated, LLM jobs can pay well, but the data is uneven across currencies. A candidate applying in a non-USD market should not assume the same breadth of salary disclosure as the USD market. If the posting does not state a salary, the market does not give you enough to infer one. In that case, you need to ask early, especially because salary is missing in more than half of all postings.
The pay bands also suggest why employers often ask for broad engineering skills. Roles that combine LLM work with Python, cloud, CI/CD, and deployment are likely to command stronger pay than a narrowly defined task. The postings do not let us compare one employer against another, but they do show that pay is substantial where it is disclosed.
LLM jobs: what the country mix says about the market
The country list is led by the United States with 5,970 postings. After that come India with 827, Canada with 646, the United Kingdom with 565, Brazil with 322, Poland with 218, Germany with 214, Spain with 192, Argentina with 174, Mexico with 163, Ireland with 152, and Colombia with 146.
The United States dominates the market in absolute count, which also helps explain why USD salary data is the largest by far. The rest of the list shows a wide global spread, but none of the other countries comes close to the U.S. total. For a job seeker, that means the market is international, but it is not evenly distributed. A candidate in the United States will see the most volume. A candidate in Germany, for example, is in a smaller but still visible market with 214 postings.
Because many postings are remote, country counts should be read carefully. A posting can be attached to one country and still be remote, which means the country total does not tell you everything about where the work can be done. Still, it does tell you where employers are actively posting at scale.
LLM jobs: what to do with this market
The data points to a market where the fastest route in is through engineering skills, not only model familiarity. If you are applying now, the postings suggest three priorities.
First, lead with Python if you have it, because 45.1% of postings ask for it. Second, show cloud and deployment experience if you can, because AWS, CI/CD, Kubernetes, and the other infrastructure skills appear often. Third, be ready to talk about shipped systems, not just model ideas, because the seniority mix says employers want people who can own real work.
Salary is worth discussing early because 52.9% of postings do not state it. Where employers do state it, the clearest benchmark is USD, with a median of 204,000 USD. But the data also says not every market is equally transparent, so if a salary is missing, ask sooner rather than later.
The last thing the numbers say is that this is a remote-friendly market. With 59.8% remote and only 7.6% on-site, flexibility is a major feature of LLM hiring. If remote work suits you, that widens your options considerably. If it does not, you will need to search more selectively.
What this rests on
Counted on 14 November 2026 across the openings Jobee had collected. Every figure above comes from this list.
- open LLM jobs
- 12,613
- employers hiring
- 2,535
- posted in the last 30 days
- 4,313 (34.2%)
- are remote
- 7,547 (59.8%)
- are hybrid
- 624 (4.9%)
- are on-site
- 957 (7.6%)
- do not say where the work happens
- 3,485 (27.6%)
- state a salary
- 5,942 (47.1%)
- do not state a salary
- 6,671 (52.9%)
- offer visa sponsorship
- 294 (2.3%)
- say they will not sponsor a visa
- 483 (3.8%)
- say they require work authorization
- 544 (4.3%)