Dynamite Jobs Scraper: Remote Jobs + Descriptions (No Login)

$0.2/1K jobs | Extract remote jobs from Dynamite Jobs with the complete original description, employer, posting date and the countries that can apply. Filter by keyword and posting age. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by Dynamite Jobs.

Dynamite Jobs Bulk Scraper for Remote Jobs

Our scraper collects remote job postings from Dynamite Jobs and lets you filter by keyword, work arrangement and posting age. Every row carries the complete original description in text and HTML, the employer, the posting date, the countries where applicants can be based and a link to the posting. It is ideal for remote-job alerts, job-board aggregation and hiring-market research. Optional AI enrichment and English translation run on us: no key to bring and no extra charge.

It serves postings from the public Dynamite Jobs index that have a verified complete description, up to 200 per run. Closed postings and postings without a complete description are left out, so you can see fewer jobs than the website lists.

• Want more remote boards? Our Himalayas Actor puts a salary on most of the rows we sampled, but it only holds a rolling window of recent postings. Our Jobgether Actor covers remote postings from the public Jobgether feed, with eligible countries as ISO codes.
• Need jobs that are not limited to one remote board? Use our LinkedIn Actor.

Key Benefits

• No login or API key: the Actor reads stored postings, so it never asks the Dynamite Jobs website for anything on your behalf and you need no account there.
• Low pricing: $0.20 per 1,000 jobs, with no start fee.
• Quick to try: ten jobs came back in under 10 seconds of run time in our test runs.
• Complete descriptions: every row has the full original text and HTML. Postings without a verified full description are not delivered.
• Checked on a schedule: each run's RUN-SUMMARY shows when the source was last checked (sourceFreshAt).
• No repeats across runs: schedule the same search daily and postings already delivered to you are skipped.

How It Works

1. Provide your search. Every field is optional. Results come newest first, and an empty search returns the newest stored postings:
   • Keyword (e.g., software engineer, customer support): a case-insensitive phrase matched against the title, the employer name and the complete description. Because it also reads the description, a keyword can match jobs that only mention it.
   • Work arrangements (remote, hybrid, onsite): empty means all. Every posting in our test runs was remote.
   • Posted within (e.g., 48h, 7d, 2w, 1m, or any): default is any.
2. Run the Actor. Results go to the dataset, and the key-value store holds RUN-SUMMARY with the data freshness, the candidates, the delivery counts and the final status.
3. Run the same search again and you get only postings you have not received yet; set dedupe.enabled to false to see everything again.

More settings:

• maxItems - Maximum jobs per run. The upper bound is 200, and 0 also means 200. Filters and repeat suppression can return fewer.
• dedupe - Repeat-delivery suppression. On by default. Postings already delivered to your Apify user for the same search are skipped. A non-empty dedupe.key names the alert history, so searches that use the same key share delivery history within your account. If delivery or the ledger cannot be confirmed, the run fails instead of reporting a delivery it cannot prove.
• filters - Advanced filters over the normalized fields. See "Advanced filters" below.
• aiEnrichment and translateToEnglish - Optional processing, both off by default. See "Optional AI enrichment and English translation" below.

Cost: you are billed $0.0002 per job delivered, which is $0.20 per 1,000 jobs. There is no start fee, and Apify platform usage for the run is included in that price.

Dynamite Jobs shows its own date when it is reliable. When it has none, the reported date is the first time the posting was seen, and later refreshes do not make a posting look new.

Titles keep the wording Dynamite Jobs uses, which usually ends in ", Remote Job".

If job data is unavailable or stale, the run fails instead of falling back to scraping the website.

Data You'll Receive

• Job details: title, complete description (text and HTML), posting date.
• Employer: company name. There is no employer link or logo.
• Where you can work: the remote arrangement and the countries where applicants can be based (data.employment.applicantLocationRequirements). The list is long when an employer hires across whole regions.
• On some jobs only: salary range with currency and period, work schedule such as full time, and contract type. In our software engineer test run, salary was on 3 of 10 rows, a work schedule on 8 and a contract type on 2; in an unfiltered run, salary was on 1 of 10.
• Link: the posting URL on Dynamite Jobs (identity.url). The source gives no separate apply link, so data.application.url is empty.
• Identity: identity.source and identity.externalId, a stable key for comparing runs.

Missing facts stay null, and a known empty list is [].

Sample output data

Here is an example job from this Actor. Descriptions are shortened here; real rows carry the full text.

{
  "llm": {
    "model": null,
    "status": "not_requested",
    "provider": null,
    "completedAt": null,
    "filledFields": [],
    "promptVersion": null,
    "requestedFields": []
  },
  "raw": {
    "description": "Get to Know Us Horizon3.ai is a fast-growing, remote cybersecurity company dedicated to the mission of enabling organizations to proactively find, fix [...]",
    "descriptionHtml": "<h3><strong>Get to Know Us</strong></h3><p><a href=\"http://Horizon3.ai\" rel=\"nofollow\">Horizon3.ai</a> is a fast-growing, remote cybersecurity company dedicated to the mi [...]"
  },
  "data": {
    "title": "Senior Back End Engineer, Remote Job",
    "company": {
      "url": null,
      "name": "Horizon3.ai",
      "logoUrl": null,
      "sourceId": null,
      "department": null
    },
    "domains": null,
    "funding": {
      "programme": null
    },
    "benefits": null,
    "locations": null,
    "seniority": {
      "raw": null,
      "levels": null
    },
    "domainsRaw": null,
    "employment": {
      "startDate": null,
      "hoursPerWeek": null,
      "startDateRaw": null,
      "contractTypes": null,
      "workSchedules": [
        "full_time"
      ],
      "durationMonths": null,
      "hoursPerWeekRaw": null,
      "workArrangements": [
        "remote"
      ],
      "applicantLocationRequirements": [
        "United States"
      ]
    },
    "application": {
      "url": null,
      "email": null,
      "deadline": null,
      "postedAt": "2026-10-13T23:25:04.493000Z",
      "directApply": null,
      "availability": null,
      "applyMethodRaw": null,
      "hiringContacts": null,
      "referenceNumber": null,
      "selectionProcess": null,
      "applicantSnapshot": null,
      "eligibilityCriteria": null,
      "referenceNumberIssuer": null
    },
    "constraints": {
      "visaSponsorship": null,
      "securityClearance": null,
      "workAuthorization": null,
      "locationPreference": null
    },
    "compensation": {
      "raw": "$170k - $235k per year",
      "exact": null,
      "period": "year",
      "maximum": 235000,
      "minimum": 170000,
      "currency": "USD"
    },
    "requirements": {
      "education": null,
      "languages": null,
      "experience": null,
      "certifications": null,
      "requiredSkills": null,
      "preferredSkills": null,
      "skillsQualifications": null,
      "specificRequirements": null
    },
    "classification": {
      "industries": null,
      "jobFunctions": null
    }
  },
  "custom": {
    "data": {
      "jobSlug": "senior-back-end-engineer",
      "objectId": "FdVsL4dY42QM6ClfFBcl",
      "companySlug": "horizon3ai"
    }
  },
  "identity": {
    "url": "https://dynamitejobs.com/company/horizon3ai/remote-job/senior-back-end-engineer",
    "source": "dynamitejobs",
    "externalId": "FdVsL4dY42QM6ClfFBcl"
  },
  "schemaVersion": "nomad-agent-job-v1"
}

Every row follows the same nomad-agent-job-v1 format with six roots: schemaVersion, identity, data, llm, raw and custom. Source-specific facts sit in custom; custom.schemaId identifies the version of the custom.data shape.

Advanced filters

Use the shared nomad-agent-job-filter-v1 expression format for fields other than the ones above. This example keeps jobs that are open to applicants in the United States:

{
  "schemaVersion": "nomad-agent-inventory-search-v1",
  "keyword": "software engineer",
  "postedWithin": "7d",
  "maxItems": 100,
  "filters": {
    "schemaVersion": "nomad-agent-job-filter-v1",
    "expression": {"field": "data.employment.applicantLocationRequirements", "operator": "overlaps", "value": ["United States"]}
  },
  "dedupe": {"enabled": true, "key": ""}
}

On this board, countries are written out in full, such as United States. With AI turned off, filters check source facts only, and unknown values do not satisfy ordinary comparisons. Most Dynamite Jobs rows publish no salary, so a salary rule such as data.compensation.minimum gte returns few jobs.

With AI enrichment on, rows that visibly fail your filter are removed before any AI call, and unknown values are checked again after enrichment.

Optional AI enrichment and English translation

Both are independent opt-ins, off by default, funded by us. You do not supply an API key, and they are not billed separately.

{
  "schemaVersion": "nomad-agent-inventory-search-v1",
  "keyword": "software engineer",
  "maxItems": 50,
  "aiEnrichment": {"enabled": true, "accuracy": "silver"},
  "translateToEnglish": true,
  "dedupe": {"enabled": true, "key": ""}
}

• AI enrichment fills supported unknown fields and records its provenance in llm. It cannot overwrite a known source fact. Jobs whose requested enrichment fails are withheld, so you can get fewer rows.
• Translation turns selected display text into English. raw.description and raw.descriptionHtml always keep the original text, and filters run on the normalized values before translation.
• Only when you turn them on, description text goes to OpenRouter for extraction, and selected display text goes to DeepL for translation. The configured routes deny provider data collection but do not guarantee zero retention or EU-only processing. Extracted facts and translations may be cached by us.
• Without enrichment, llm.status is not_requested. When enrichment runs, the key-value store also holds OWNER-USAGE, which separates actual provider costs from unpriced token counts.
• The top-level accuracy field is a compatibility override for aiEnrichment.accuracy. It never turns enrichment on by itself.

Dynamite 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. Use latest as the build and keep the build number your run returns if you need to reproduce a result.

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.

Good to know

• Coverage follows what Dynamite Jobs shows in its public index and what we could verify with a complete description. The Actor does not read the website at run time.
• One employer can post many roles at once. An unfiltered run is newest first and can be dominated by a single employer (7 of 10 rows in one of our test runs), so add a keyword for a mixed result.
• Restrictive filters, repeat suppression or a narrow postedWithin can produce zero results. A successful run status alone does not prove complete coverage, so check the dataset and RUN-SUMMARY together.

Migrating from the previous release

• schemaVersion must be nomad-agent-inventory-search-v1. Inputs from the previous release, which used source-specific fields, fail with migration guidance. Replace them with keyword or filters.
• identity.externalId is the source's own posting ID as represented in this output, and it may be spelled differently from earlier releases. The stable key is the pair (identity.source, identity.externalId). Update stored comparison keys; existing delivery history can permit a one-time repeat.
• custom now carries source facts under a new custom.schemaId. The other five roots keep the nomad-agent-job-v1 contract.
• Relative posting-age windows are limited to 36500 days. Use any for an unrestricted search.

Run evidence

• Test run on 2026-10-16, build 1.0.5, run j8A08W1RsWzhd9dBB: keyword software engineer, 10 jobs, 8 different employers, all 10 with a complete description. Run time 6.6 seconds.
• In that run the source had been checked 29 minutes before the run started (sourceFreshAt 16:18 UTC, run at 16:47 UTC).
• Salary was present on 3 of those 10 rows, a work schedule on 8, a contract type on 2, and data.application.url on none. An unfiltered run (dP1967DPVdpnQT8ja) returned 10 jobs from 4 employers, 7 of them from one employer, newest first.
• Filter test, run n5iaDAcUQHETob2yD: keyword software engineer with the United States rule from "Advanced filters" returned 10 jobs, every one listing United States among the eligible countries.
• Cost per run = jobs delivered x $0.0002.

Job Atlas

Explore the Job Atlas job-data and matching Actors. Use latest and keep the build number each run returns.

• LinkedIn
• EURAXESS
• Y Combinator
• AI job fit scorer

Product guide | Source and client examples | Setup skill | Setup guide

• Product overview and public links
• Job Atlas job-data tools

---

Independent tool. We built and run this Actor ourselves. Dynamite Jobs does not operate, sponsor or endorse it, and its name is used only to say which site the data comes from.