Dice Jobs Scraper

Extract job listings from Dice with structured output for hiring analysis, lead generation, and market monitoring. Collect current job data like title, company, location, salary, work setting, and job descriptions in one run. Built for fast, repeatable collection with flexible search filters.

Features

• Targeted search inputs — Filter by keyword, location, and posted date.
• Direct search URL support — Start from a full Dice search URL when needed.
• Rich job records — Includes identifiers, company links, salary text, and description fields.
• Pagination support — Collects records across result pages until your limit is reached.
• Clean structured dataset — Output is ready for dashboards, spreadsheets, and automation.
• Run-time controls — Control record count and optional page limits for faster runs.

Use Cases

Job Market Research

Track role demand, salary patterns, and location trends for specific skills.

Recruiting Intelligence

Build up-to-date datasets of open roles for sourcing and outreach planning.

Competitive Hiring Monitoring

Follow hiring activity by company, role type, and geography over time.

Lead Generation for Staffing Teams

Collect role and company details for outbound recruiting or business development.

Career Opportunity Tracking

Monitor newly posted jobs by keyword and location with repeatable searches.

---

Input Parameters

Parameter	Type	Required	Default	Description
startUrl	String	No	—	Full Dice search URL. If provided, it overrides keyword and location.
keyword	String	No	python	Search keyword for jobs.
location	String	No	Remote	Location filter for jobs.
posted_date	String	No	24h	Date filter: all, 24h, 3d, 7d, 30d.
results_wanted	Integer	No	20	Maximum number of jobs to save.
maxPages	Integer	No	1 (prefill)	Optional cap on the number of pages to process.
proxyConfiguration	Object	No	—	Optional proxy configuration for reliability and region control.

---

Output Data

Each dataset item can include:

Field	Type	Description
id	String	Internal job record identifier.
guid	String	Dice job GUID.
jobId	String	Job ID from source data.
title	String	Job title.
company	String	Company name.
companyName	String	Raw company name value from source data.
location	String	Formatted location text.
jobLocation	Object	Structured location details (city, state, country, display name).
salary	String	Salary text when available.
employmentType	String	Employment type label.
workSetting	String	Work setting, for example Remote, Hybrid, or On-Site.
employerType	String	Employer category value.
easyApply	Boolean	Indicates whether easy apply is enabled.
willingToSponsor	Boolean	Sponsorship flag when provided.
description_html	String	Job description with HTML tags preserved.
description_text	String	Plain text description.
summary	String	Short listing summary.
posted	String	Posted date value.
updated	String	Last updated date value.
firstActiveDate	String	First active date value.
url	String	Job detail URL.
detailsPageUrl	String	Source details page URL.
companyPageUrl	String	Company profile URL.
companyLogoUrl	String	Company logo URL.
position_id	String	Position identifier.
dice_id	String	Dice-specific ID derived from job URL/GUID.
searchId	String	Search identifier from run metadata.
searchPage	Integer	Page number where the item was collected.
searchPageSize	Integer	Page size used during collection.
searchSortBy	String	Sorting mode value from metadata.
source	String	Source label (dice.com).

---

Usage Examples

Basic Keyword Search

{
  "keyword": "python",
  "location": "Remote",
  "posted_date": "24h",
  "results_wanted": 20
}

More Results Across Pages

{
  "keyword": "data engineer",
  "location": "United States",
  "posted_date": "7d",
  "results_wanted": 200,
  "maxPages": 5
}

Start From a Direct Dice Search URL

{
  "startUrl": "https://www.dice.com/jobs?q=java&location=Remote&page=1",
  "results_wanted": 100,
  "maxPages": 3
}

With Proxy Configuration

{
  "keyword": "machine learning engineer",
  "location": "New York, NY",
  "posted_date": "3d",
  "results_wanted": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}

---

Sample Output

{
  "id": "9f0b440130ec2a87ad06df2631366be8",
  "guid": "f147d40f-4328-4fce-bbd4-0d8f880040d4",
  "title": "Sr. Lead of Software Engineering - Back End (Java, Python, Golang, AWS)",
  "company": "Capital One",
  "location": "McLean, Virginia, USA",
  "salary": "USD 229,900.00 - 262,400.00 per year",
  "employmentType": "Full-time",
  "workSetting": "On-Site",
  "description_html": "<strong>Who We Are:</strong><br /><ul><li>...</li></ul>",
  "description_text": "Who We Are:\n...",
  "url": "https://www.dice.com/job-detail/f147d40f-4328-4fce-bbd4-0d8f880040d4",
  "dice_id": "f147d40f-4328-4fce-bbd4-0d8f880040d4",
  "position_id": "9f0b440130ec2a87ad06df2631366be8",
  "source": "dice.com"
}

---

Tips for Best Results

Use Focused Keywords

Use role-specific terms like java developer, data engineer, or cloud architect for cleaner results.

Keep results_wanted Realistic

Start with 20 to validate output quickly, then scale to larger volumes.

Limit Pages for Faster Runs

Set maxPages when you need speed or when testing new query combinations.

Prefer Recent Filters for Fresh Data

Use 24h or 3d when monitoring active hiring trends.

Use Proxy for Higher Stability

Enable proxy settings for long or repeated production runs.

---

Integrations

Connect your dataset with:

• Google Sheets — Share and analyze job data quickly.
• Airtable — Build searchable recruiting or research databases.
• Slack — Send updates from scheduled runs.
• Webhooks — Push records to internal systems.
• Make — Build no-code workflows around collected job data.
• Zapier — Trigger downstream automations.

Export Formats

• JSON — Best for APIs and custom applications.
• CSV — Best for spreadsheet workflows.
• Excel — Best for stakeholder reporting.
• XML — Best for legacy system integrations.

---

Frequently Asked Questions

How many jobs can I collect in one run?

Use results_wanted to control the maximum number of items saved.

Can I scrape by exact location?

Yes. Set location to a city, state, or broader region.

Can I start from a URL instead of keyword and location?

Yes. Provide startUrl to begin from a specific Dice search URL.

Why are some fields missing on some jobs?

Some source listings do not publish every field, so output may vary by job.

Does the actor include description fields?

Yes. It outputs both description_html and description_text when available.

Can I schedule recurring runs?

Yes. Use Apify schedules to run this actor automatically.

---

Support

For issues or feature requests, use the actor page on Apify and open a support request.

Resources

• Apify Documentation
• Apify API Reference
• Apify Schedules

---

Legal Notice

This actor is intended for legitimate data collection and analysis workflows. You are responsible for complying with website terms, local laws, and applicable regulations when collecting and using data.