AI & ML Engineer Jobs Scraper (No Login) + 10 Boards

$0.2/1K jobs | AI and ML engineer jobs from 10 boards in one run, including LinkedIn, Foorilla, Hacker News, Y Combinator, Built In and Remote OK, each with the full description. Default search on stored boards only looks at AI and ML titles. No login or API key required. Independent, unofficial tool. Not affiliated with or endorsed by the job boards and sites it reads.

AI & ML Engineer Jobs Bulk Scraper

The scraper pulls AI and ML engineer jobs from 10 boards in one run. You can filter by keyword, location, work arrangement, employment type, and posting age. If you don't pass queries, it searches 19 default AI/ML phrases and only keeps a stored posting if the title contains one (like "AI", "ML", "machine learning", or "data scientist"). LinkedIn is searched live and uses its own ranking. Your custom queries search both title and description. Every row includes the full original description in text and HTML. Good for AI talent feeds, ML hiring analytics, or alerts for ML engineer, data scientist, and applied scientist roles.

• Want every kind of job from 21 boards, not just AI and ML? Use All Jobs Scraper (No Login) + 21 Boards in One.
• Need one AI board with its own page? Foorilla AI Jobs Scraper — ML & Data Roles reads Foorilla alone; this bundle adds nine more boards on top of it.
• Need LinkedIn only, searched deeply? Use LinkedIn Jobs Scraper (No Cookies) + Full Descriptions. Here LinkedIn is searched live for at most 6 query, location and work-arrangement combinations per run.
• Browse all our job-board scrapers: https://apify.com/nomad-agent

Key Benefits

• No login or API key: nothing to set up, no account of yours at risk, and no cookies to hand over.
• Low pricing: $0.20 per 1,000 jobs ($0.0002 per job), with lower rates on Scale and Business plans ($0.15 and $0.1 per 1,000), plus $0.00005 per run start.
• Full descriptions only: a posting with a missing or truncated description is never returned.
• AI and ML in the title by default: if you don't pass queries (the form doesn't), the run searches 19 built-in AI/ML phrases—machine learning, llm, ai, ml, data scientist, etc.—and keeps postings whose job title matches one. LinkedIn handles its own ranking.
• No repeats across runs: schedule the same search daily and get only postings you have not received yet.

How It Works

1. Provide your search. Every filter is optional, and an empty list means no filter:
   • (optional) Search queries (e.g., machine learning). A posting matches when its title or description contains every word of a query, as whole words.
   • (optional) Locations (e.g., Europe, DE, Berlin). Countries match by name, code and native name, and EU and Europe cover their member countries.
   • (optional) Work arrangement (remote, hybrid, onsite) and employment type (Full-time, Part-time, Contract, Internship).
   • (optional) Posted within (e.g., 24h, 7d, 2w). Default is any.
2. Set how many jobs you want with maxItems.
3. Click Start. The form opens with Europe and 20 jobs and leaves queries out, so the 19 built-in AI and ML searches apply.

More settings:

• maxItems - Maximum number of jobs per run. Default is 200; 0, or anything above 200, means 200.
• maxItemsPerSource - Caps how many postings each board contributes. Default is 50, at most 200. maxItems then keeps the newest postings across all boards.
• dedupe - On by default: postings already delivered to your Apify account for the same search are skipped. Set dedupe.enabled to false to get everything again, or set dedupe.key to keep separate alert histories.

Run the same search twice and the second run returns only new postings, possibly none. That is the repeat suppression working; turn dedupe off to see every posting again.

Coverage: Foorilla, Hacker News (Who is hiring), Y Combinator Work at a Startup, Built In, Remote OK, Remotive, We Work Remotely, Welcome to the Jungle and JustJoin.it are served from verified postings, and LinkedIn is read live on every run. Each row keeps its own source.

LinkedIn can be limited or blocked during a run. When that happens its rows are fewer than requested or missing, the other boards are still returned, RUN-SUMMARY.unavailableSources names LinkedIn, and the run is marked partial.

When you set work arrangement or employment type, a posting whose source does not state that fact is left out. Salary and hiring contacts are filled only when the source publishes them (none of the 10 rows in our test run had either), so treat them as bonus fields.

Data You'll Receive

• Job details: title, complete description (text and HTML), locations, posting date, deadline (when published), work arrangement, employment types, salary (when published).
• Employer: company name.
• Links: original posting URL.
• Hiring contacts: the people a source names, when it names any (otherwise an empty list).
• Identity: source and a stable id, so you can deduplicate across runs.

Rows use the nomad-agent-job-row-v3 format, newest postings first. Unknown optional facts are null.

Sample output data

Here is an example job from this Actor (one row of our test run, description shortened):

{
  "schemaVersion": "nomad-agent-job-row-v5",
  "source": "wttj",
  "id": "03bdd832-9087-4a49-9744-44973d23409c",
  "url": "https://www.welcometothejungle.com/en/companies/cgi/jobs/lead-ia-engineer-f-h_paris",
  "title": "Lead IA Engineer F/H",
  "company": "CGI",
  "locations": [
    "Paris, France"
  ],
  "countryCodes": [
    "FR"
  ],
  "applicantLocations": null,
  "postedAt": "2026-10-13",
  "deadline": null,
  "description": "Rejoignez CGI, l'une des plus grandes entreprises de conseil en technologie de l'information et en management au monde. En tant que Tech Lead IA, vous serez responsable de la conception, de l'industrialisation et de la gouvernance des solutions d'IA au sein de l'entreprise. Vous travaillerez sur des… [truncated for display]",
  "descriptionHtml": "Rejoignez CGI, l'une des plus grandes entreprises de conseil en technologie de l'information et en management au monde. En tant que Tech Lead IA, vous serez responsable de la conception, de l'industri… [truncated for display]",
  "workType": "hybrid",
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

AI & ML Engineer Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read on demand through the Apify API. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

• Open an issue on the Actor's Issues tab
• If this Actor saved you time, a short review on the Store helps other users find it.

Run evidence

Start with one input and output

An Apify account is required. Use your Apify API token when calling the API; Console runs do not need that token pasted into the input. No source login or AI-provider key is required for this quickstart. none.

Free-tier event rates checked 2026-10-04: result $0.0002; actor-start $0.00005.

Cost: Total = Actor event charges + platform usage if separately billed + any BYO-provider charges. See “Current costs” for your event rates, plan tiers and a calculation. A sample does not promise future billable volume.

Input and output below were read from the same successful run DyYmLU0VKirHxroPg (2026-10-03, immutable build mZLMTeeYxJ5Z0jqEq). This is an observed example, not a guarantee that repeating it returns this row. The input/output below are from a run before the November 2026 title filter, using the 14 earlier phrases. The output row only mentions AI in its description, so today's default search wouldn't find it.

Input JSON

{
  "queries": [
    "machine learning",
    "deep learning",
    "artificial intelligence",
    "generative ai",
    "large language models",
    "llm",
    "nlp",
    "natural language processing",
    "computer vision",
    "reinforcement learning",
    "mlops",
    "data scientist",
    "applied scientist",
    "ml engineer"
  ],
  "locations": [],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "any",
  "maxItems": 200,
  "maxItemsPerSource": 50,
  "dedupe": {
    "enabled": true,
    "key": ""
  },
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}

Matching output excerpt

Long strings and arrays are shortened for display; this is not a complete dataset fixture.

{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "remote_boards",
  "id": "weworkremotely_gong-io-enterprise-revenue-architect",
  "url": "https://weworkremotely.com/remote-jobs/gong-io-enterprise-revenue-architect",
  "title": "Enterprise Revenue Architect",
  "company": "Gong.io",
  "locations": [
    "Anywhere in the World"
  ],
  "postedAt": "2026-10-02",
  "deadline": "2026-11-01",
  "description": "Headquarters:\nRemote (US)\n\nGong harnesses the power of AI to transform how revenue teams win. The Gong Revenue AI Operating System unifies data, insights, and workflows into a single, trusted system that observes, guides, and acts alongside the world’s most successful revenue teams. Powered by the Gong Revenue Graph, AI-powered intelligence, specialized agen… [truncated for display]",
  "descriptionHtml": "\n\n<p>\n  <strong>Headquarters:</strong> Remote (US)\n</p>\n\n<div class=\"content-intro\"><p>Gong harnesses the power of AI to transform how revenue teams win. The Gong Revenue AI Operating System unifies data, insights, and workflows into a single, trusted system that observes, guides, and acts alongside the world’s most successful revenue teams. Powered by the G… [truncated for display]",
  "workType": "remote",
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

Retained dedupe history can suppress previously returned postings. Keep a stable key and save your own history; an unchanged rerun can return zero new rows.

Recent AI and ML engineer jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are null; an empty locations array means the source names no physical place, and an empty hiringContacts array means the source names nobody. locations is where the job is, countryCodes lists the countries of those places as ISO 3166-1 two-letter codes (null when no place has a known country), and applicantLocations is where an applicant may live, for example a remote job open only to residents of some countries: it is null when the source states nothing and [] when it states no restriction.

Coverage includes these public job sources: Foorilla Hiring (formerly aijobs.net); Hacker News Who is hiring; Y Combinator's Work at a Startup; Built In; Remote OK, Remotive and We Work Remotely; Welcome to the Jungle; JustJoin.it. LinkedIn is also served, fetched live on every run. Each row keeps its own source. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text. LinkedIn results use the requested search filters. Each posting still has its full description or it is left out. LinkedIn may limit or block a run, so its rows can be fewer than requested or missing: the other boards are still returned, RUN-SUMMARY.unavailableSources names LinkedIn, and the run is marked partial.

Without queries (or the older keyword), it searches 19 default AI/ML phrases under Input and only keeps a posting if its job title contains one. A company blurb that just mentions AI doesn't count anymore. LinkedIn is the exception: it's searched live for six of those phrases and keeps its own relevance ranking. Your own queries still match in the title and description. Built In coverage is limited to the supported category, which is narrower than the whole site.

LinkedIn is searched live for at most 6 combinations of query, location and work arrangement per run. With the default queries it searches a curated subset of them, computer vision, artificial intelligence, ml engineer, deep learning, machine learning and generative ai, while the other boards use all of them. Naming several locations or locationTypes shares the six searches, so each location gets fewer of those phrases: two locations get the first three each, three get the first two, and four to six get the first phrase only. With your own queries, or more than six locations and work arrangements together, combinations beyond the sixth are not searched: the last locations you list can get no LinkedIn rows, the run is marked partial, and RUN-SUMMARY.unavailableSources says how many combinations were searched.

Input

{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["machine learning", "deep learning", "artificial intelligence", "generative ai", "computer vision", "natural language processing", "reinforcement learning", "ml engineer", "data scientist", "data science", "applied scientist", "research scientist", "mlops", "llm", "nlp", "genai", "ai", "ml", "ia"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 200, "maxItemsPerSource": 50, "dedupe": {"enabled": true, "key": ""}}

Every filter is optional, and an empty list means no filter. Filters are applied to all available postings before maxItems is counted.

• queries: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches. Default: a run that sets neither queries nor the older keyword searches for AI and ML engineer roles with these queries: machine learning, deep learning, artificial intelligence, generative ai, computer vision, natural language processing, reinforcement learning, ml engineer, data scientist, data science, applied scientist, research scientist, mlops, llm, nlp, genai, ai, ml, ia. On the stored boards it also keeps only postings whose job title contains one of them. Your own queries or keyword replace them and are matched in the title and the description, and an empty list means no query filter.
• locations: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (Germany, DE and Deutschland find the same postings), and EU and Europe cover their member countries.
• locationTypes (remote, hybrid, onsite) and employmentTypes (Full-time, Part-time, Contract, Internship): while one is set, a posting whose source does not state that fact is left out.
• postedWithin: a positive duration in hours (h), days (d), weeks (w) or 30-day months (m), up to 36500 days, or any. Postings without a source date use the date they were first seen, which later refreshes never reset.
• maxItems defaults to 200; 0, or anything above 200, means 200.
• maxItemsPerSource (default 50, at most 200) caps how many postings each source contributes; maxItems then keeps the newest postings across all sources.
• dedupe suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set dedupe.enabled to false to get stateless results, or set dedupe.key to keep separate alert histories.

Output

One flat row per posting in the nomad-agent-job-row-v5 format: schemaVersion, source, id, url, title, company, locations, countryCodes, applicantLocations, postedAt, deadline, description, descriptionHtml, workType, salary, employmentTypes, hiringContacts. employmentTypes lists the types the source states (Full-time, Part-time, Contract, Internship) or is null. countryCodes lists the countries of the job's places as ISO 3166-1 alpha-2 codes (for example DE, FR), in the same order as locations, each once. A code comes from the source if it states one, otherwise from the place label. It's null when no place has a known country (a remote job with no country, or an unidentifiable place) and never an empty list. A place without a known country adds nothing, so the list can name fewer countries than there are places. A posting stored on a single-country board with no place at all carries that board's country, so locations can be [] while countryCodes names one. Postings read live from LinkedIn's public pages always have countryCodes: null. Those pages give a place label but no country code, so only stored postings carry a code. The locations filter matches countries against these codes as well as names and text. applicantLocations lists the regions where the source says an applicant may live (for example United States for a remote job open to US residents), null when it states nothing and [] when it states no restriction. Each hiring contact has a name, and a title and url or null. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the RUN-SUMMARY record of the run's key-value store.

Changes

• November 2026: the default AI and ML search keeps AI and ML job titles. Previously, a run with no specific search matched 14 phrases in either the title or description, so postings where the company text just mentioned AI would show up. Now it searches 19 phrases—including ai, ml, genai, and ia—and only keeps a posting if its job title contains one. Your custom queries still match both title and description, and LinkedIn (searched live for six of the default phrases) is unchanged. Using the default phrases starts a new repeat-delivery history, so postings you've already received might appear once more. Any task, schedule, or integration saved with the old 14 default phrases is now read as the default search.
• October 2026: countryCodes added (row v5). Rows are now nomad-agent-job-row-v5: one new field, countryCodes, lists the ISO 3166-1 alpha-2 country codes of the job's places, in the order of locations, each once (null when no place has a known country, never an empty list). A code is the country the source states, or if it doesn't state one, the country read from the place label. A place whose country can't be determined adds nothing. Postings read live from LinkedIn carry null; its public pages show a place label but no country code. locations and applicantLocations are unchanged. Input, other fields, and pricing are unchanged. Integrations validating against the v4 schema must allow the new field and the new schemaVersion.
• October 2026: applicantLocations added (row v4). Rows are now nomad-agent-job-row-v4: one new field, applicantLocations, lists where an applicant may live as the source states it (null when the source states nothing, [] when it states no restriction). locations is unchanged and still the physical place only; for a remote job open to some regions it is often [] while applicantLocations lists the regions. Input, other fields and pricing are unchanged. Integrations that validate rows against the v3 schema must allow the new field and the new schemaVersion.
• October 2026: new row format. Rows are now nomad-agent-job-row-v3 (15 fields) instead of nomad-agent-job-row-v1. Postings come from the available postings of seven boards (Foorilla, Hacker News, Y Combinator, Built In, RemoteOK/Remotive/We Work Remotely, WTTJ and JustJoin.it), and LinkedIn is read live on every run. Pricing is unchanged.
• Removed from every row: recordType, custom, warnings, docs, snippet (the text is in description and descriptionHtml), seniority, isRemote, remoteType (use workType), location (use locations), salaryMin, salaryMax, salaryCurrency and salaryPeriod (the source's salary text stays in salary), employmentType (now the employmentTypes array, null when unknown), and hiringContactName, hiringContactTitle and hiringContactUrl (now hiringContacts, a list of name, title and url).
• Input: queries, locations, locationTypes, employmentTypes, postedWithin and maxItemsPerSource (default 50, was 36) filter the search, and maxItems defaults to 200 (was 288). keyword becomes queries and replaces the AI/ML default. sources, cacheTtlSeconds, concurrency, runTimeoutSecs and apifyToken are ignored with a note in RUN-SUMMARY. All supported boards remain included.
• Repeats: a posting you already received from this Actor for the same search is no longer returned again by default, where the earlier Actor only removed repeats within one run. Set dedupe.enabled to false for stateless results.
• Source and ID changes: postings from aijobs.net now carry source: "foorilla" (was ai_jobs_net). Remote board ids now start with the board name, for example remoteok_123, so a consumer that keys on (source, id) can receive postings it already has once more.
• Board coverage: Hacker News serves the current "Who is hiring?" thread only, and the full-text searchQuery mode is gone. Built In coverage is limited to the supported category. LinkedIn is fetched live, for a curated subset of the AI/ML phrases and at most 6 query, location and work arrangement combinations per run (see above), and can be limited or unavailable, in which case the run is partial; the other boards are still returned.

Fast setup and source code

Public repository · Agent setup skill.

Use the Actor’s current input form for filters, or start with its documented API example. Select the latest build. Read the dataset together with the run summary: a successful status alone does not show that every source was reached.

Restrictive filters or repeat-delivery suppression can produce zero results.

Observed output example

Selected fields from a real source record inspected on 2026-10-03; consult the output schema for the full contract. Values change with the source.

{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "justjoinit",
  "id": "accenture-industry-x---engineering-platform-integration-agile-product-implementation-analyst-consultant-gn--warszawa-pm",
  "url": "https://justjoin.it/job-offer/accenture-industry-x---engineering-platform-integration-agile-product-implementation-analyst-consultant-gn--warszawa-pm",
  "title": "Industry X – Engineering Platform Integration & Agile Product Implementation Analyst/Consultant (GN)",
  "company": "Accenture",
  "locations": [
    "Warszawa, PL"
  ],
  "postedAt": "2026-10-01",
  "deadline": "2026-11-30",
  "workType": "hybrid",
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}

Product guides and related tools

• Guide and starter input on nomadagent.dev
• Product overview and public links
• Public setup guide
• Job Atlas job-data tools
• Oink personal job alerts
• Search ten job boards with one API call

Current costs

Current Actor event rates, checked 2026-10-16. USD; use the Pricing tab for your plan and later changes.

Event	Free	Bronze	Silver	Gold	Platinum	Diamond
Job result (result)	$0.0002	$0.0002	$0.00015	$0.0001	$0.0001	$0.0001
Actor start (actor-start)	$0.00005	$0.00005	$0.00005	$0.00005	$0.00005	$0.00005

For example, 100 × result, 1 × actor-start totals $0.02005 in Actor event charges on Free. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap.

Your total is the charged Actor events, plus platform usage only if this Actor’s Pricing tab bills it separately, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting.

---

Independent tool. We built and run this Actor ourselves. The job boards and sites it reads do not operate, sponsor or endorse it, and their names are used only to say where the data comes from.