Dice Jobs Scraper

Dice Jobs Scraper: US tech job listings with the apply link, no login

Give it keywords and a location and it walks Dice's search results, returning one row per job: the title, the company, where it is, whether it is remote or hybrid, the employment type, the date it was first posted and the URL you apply on. You can also hand it job URLs or job ids directly.

Dice's own filters run on internal codes rather than the words printed on the cards. Ask its search for "Full-time" and you get nothing back. This translates the everyday wording for you, so Full-time, contract and corp-to-corp all work.

🔍 What Dice Jobs Scraper does

Every query is run against every location, so three keywords and two cities is six searches. Each one pages through Dice's results up to the page limit you set, and stops early when a page brings nothing new.

Filters go into the Dice URL, so the narrowing happens on their side rather than by throwing rows away afterwards. Workplace type, employment type, Easy Apply and the today, 3d and 7d windows all work that way. Dice stopped applying its 30-day window, so 30d is checked here against each job's own posting date, and older jobs are left out and not charged.

employerTypes goes to Dice too: pick Direct Hire to skip agencies, or Recruiter for agency roles only.

Every results page also lists a few similar jobs beside the results. They ignore your search and its filters, so they are always left out.

By default you get what the search card carries, which is fast. Switch on Fetch full details and each job's own page is opened for the complete description. That takes a request per job, so it is noticeably slower on a big run.

When details are on, the filters are checked a second time against the detail page. Dice cards sometimes label a job one way and the job page another, and a job that turns out not to match what you asked for is dropped rather than delivered.

📥 What you give it

{
  "searchQueries": ["python developer", "data engineer"],
  "locations": ["New York, NY", "Remote"],
  "employmentTypes": ["Full-time"],
  "postedDate": "7d",
  "maxItems": 300,
  "includeDetails": true
}

Run it with nothing filled in and you get one free sample row instead of an error. It is there so you can see the shape before committing to a real run.

📤 What you get back

A real row from a recent run:

{
  "ok": true,
  "_sample": false,
  "_diagnostic": false,
  "source": "dice",
  "jobId": "7015377a-0d8c-4367-86c2-c8de29fa55b8",
  "title": "Senior Python Developer",
  "company": "Randstad Digital",
  "location": "Jersey City, New Jersey",
  "workplaceType": null,
  "employmentType": "Contract",
  "postedAt": "Today",
  "postedDate": "2026-09-28T21:04:03Z",
  "description": null,
  "url": "https://www.dice.com/job-detail/7015377a-0d8c-4367-86c2-c8de29fa55b8",
  "searchQuery": "python developer",
  "searchLocation": "New York, NY"
}

🧾 Reading the output

Three kinds of row can land in your dataset.

Filter on _sample and _diagnostic, not on ok. The sample row carries ok: true as well.

To sort or filter by age, use postedDate, not postedAt.

One failed search never stops the others, and a diagnostic row never fails the run.

▶️ How to run it

1. Open Dice Jobs Scraper and click Try for free. 2. Put your keywords into Search queries and your cities into Locations. Use Remote as a location for remote roles. 3. Set Maximum jobs. Start around 50 to see the row shape. 4. Narrow it with Posted date, Workplace and Employment types if you want, then click Start. 5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

Switch on Fetch full details when you need the description text. Leave it off when you only need titles, companies and apply links.

💰 How much does it cost?

$0.90 per 1,000 jobs. Flat on every Apify plan, no volume tiers.

You pay per job row delivered. The sample row, diagnostic rows, jobs already seen in the same run, jobs dropped by your filters and the similar jobs beside the results are all free, and turning on full details does not change the price.

💡 What people use it for

• Watching a role and a city on a schedule, with postedDate on today so each run is only new

postings.

• Pulling contract and corp-to-corp roles separately from permanent ones, which is the filter Dice

makes awkward.

• Building a list of companies hiring for a skill, then working the list rather than the jobs.
• Feeding descriptions into a model that has to match candidates to postings, with full details on.
• Checking what a competitor is hiring for, by searching their name as a keyword.

🚧 What it does not do

• US tech roles. That is what Dice is. It is not a general job board.
• No salary field. Dice does not publish one consistently, so there is nothing reliable to give

you.

• No guessed dates. If Dice gives no posting date for a job, postedDate is null.
• Reposts are not merged. A job relisted under a new id looks like a new job, because to Dice it

is one.

• Workplace type from a card is inferred from the card's wording, so a title with "Remote" in it

can be read as a remote job. Turn on full details when that distinction matters.

• The 30-day window is ours, not Dice's. Each job's postedDate decides, whatever its card says.
• 1,000 jobs per run.
• Nothing is delivered until the searches finish. A run stopped partway through writes no job

rows.

• No applying, no contact details, no recruiter emails.

🧭 Which jobs scraper do you need?

❓ Questions people ask

Do I need a Dice account? No. It reads the public search and the public job pages.

Why did asking for full-time jobs used to return nothing? Because Dice's search wants its own internal code, not the label on the card. Type the label here and it is converted before the request goes out.

Should I turn on full details? Only if you need the description. It adds a page fetch per job and makes a large run much slower, though it does not change what you pay.

Can I get just one job? Yes. Paste its URL into Direct job URLs, or its id into Direct job IDs.

Why is description empty? Full details were off. Card previews frequently carry no usable text.

Is scraping job listings legal? These are public postings on public pages. Job ads can contain personal data, which GDPR and similar laws cover, so have a reason for collecting it. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the run ID and the query and location you used. The errorCode on the diagnostic row usually names the problem on its own.