Remote AI Jobs: 378 Open, 56% Based in the US (September 2026)

On 7 September 2026 the board listed 378 fully remote AI roles, which is 13% of the 2,852 live AI roles we track. That number is real, but it needs two qualifiers before anyone plans a job search around it: more than half of those remote roles name the United States as the base country, and three of the nine AI functions hold almost all of them. This is the first monthly remote edition, frozen at publication, with the live version always at remote AI jobs.

Remote, hybrid, on-site, unknown

The market dashboard classifies every live posting from its location and title fields:

• On-site - 939
• Unknown - 916
• Hybrid - 618
• Remote - 378

The second line matters. Almost a third of AI postings do not say, in any field we can read, whether the job is remote. So 13% is the floor for remote work in AI, and the true share sits somewhere between 13% and the roughly 40% you would get if every unknown turned out to be remote. It will not, but the band is wide, and any headline remote percentage for AI hiring, ours included, should be read with that in mind.

Where remote roles are based

"Remote" in an AI posting almost always comes with a country attached, for payroll, work authorisation or time-zone overlap. On the day of the read the 378 remote roles were based in:

• United States - 211 (56%)
• Canada - 22
• United Kingdom - 20
• India - 11
• Australia - 7
• Germany - 5
• Netherlands - 4
• France - 3

Those eight are the markets the page names; the remaining roles carry no primary country or one outside that list. If you are outside the United States, the practical starting set is the country pages: remote AI jobs in the UK, Canada, India, Europe and Asia-Pacific, plus the postings that name no country at all. Some employers say the time-zone requirement out loud, such as a live CrowdStrike Lead AI Engineer posting scoped to 2.00 pm to 11.00 pm IST. Most do not, and it is the first thing to ask on a screening call.

Which functions go remote

Remote AI work is concentrated in three functions. The 378 remote roles by function:

• Applied AI - 116
• ML Engineering - 97
• Data & MLOps - 81
• Research Science - 40
• AI Infrastructure - 34
• AI Product - 8
• AI Governance & Policy - 1
• Evals & Red Teaming - 1
• AI Safety & Alignment - 0

The top three hold 294 roles, 78% of all remote AI work. Measured against each function's total on the board (Data & MLOps 403, ML Engineering 505, Applied AI 955, Research Science 492), the remote share is about one in five for Data & MLOps and ML Engineering, about one in eight for Applied AI, and about one in twelve for Research Science. Safety, evals and governance, which together hold 91 roles, have two remote seats between them; the full picture of those three functions is in our scarcity index.

The reading is simple: remote lives where the work is shipping code against a cluster. Function-specific pages exist for the three that matter, remote Applied AI, remote ML engineering and remote Data & MLOps, and they are a better starting point than the all-functions list.

What remote roles say about pay

The remote listings that publish a band do not look discounted. Among the newest remote postings on the day of the read: Shield AI's Senior Staff Engineer, ML Ops at $280,000 to $420,000; AssemblyAI's Senior Research Engineer at $270,000 to $310,000; Torc Robotics' Staff Machine Learning Engineer at $215,500 to $258,600 and its Senior Machine Learning Engineer at $177,300 to $212,800; KoBold Metals' Staff Applied Scientist at $125,000 to $235,000; and, at the other end, Cohere Health's Senior Forward Deployed Automation Strategist at $100,000 to $115,000. Five of the six name a US location; the KoBold Metals listing names none at all. Disclosed bands skew senior and skew toward US states with pay-transparency law, so treat this as the upper view rather than a median.

What to do with this

• Filter by function before location. Three functions hold 78% of remote supply. A remote search across all of AI hides that.
• Read "remote" as "remote plus a country". 211 of 378 are US-based. Start from your own country's page and from the postings that name none.
• Ask about the time zone on the first call. The overlap requirement is the real constraint, and most postings leave it unstated.
• Do not wait for a remote safety or evals role. Two exist. Hybrid in London or San Francisco is the realistic shape of those functions right now.

Method and caveats

Counts are live roles on 7 September 2026, read hourly from each company's own applicant tracking system. Remote status is classified from the location and title fields, which is why 916 postings are "unknown": they carry a city with no remote or hybrid signal we can read. The remote hub and the market dashboard both showed 378 on the day of the read, against 2,852 live AI roles from the stats API minutes earlier, so the percentages here can move by a fraction depending on which cache you check. Enterprise Workday feeds are capped at 100 postings per tenant, which under-counts large multinationals. It is a large sample of companies that publish a feed, not a census, so treat every count as a floor. Pay bands are quoted exactly as published. Every figure is free to quote with attribution to AI Hiring Board.