Dice Job Scraper
Pricing
from $1.00 / 1,000 results
Dice Job Scraper
Unlock the tech job market! Effortlessly extract job listings, salaries, and company details from Dice.com. This high-performance tool is really fast without proxy! Perfect for recruiters and data analysts needing instant, reliable job board data.
Pricing
from $1.00 / 1,000 results
Rating
5.0
(3)
Developer
Shahid Irfan
Actor stats
5
Bookmarked
138
Total users
27
Monthly active users
0.26 hours
Issues response
6 days ago
Last modified
Categories
Share
Dice Jobs Scraper
Extract Dice job listings with structured, analysis-ready output. Collect current openings by keyword, location, posting date, or a direct Dice search URL, then export the results as a clean dataset for recruiting, market research, and hiring intelligence workflows.
Use this actor to gather job titles, companies, locations, salary text, work setting, job descriptions, and source links at scale. It is designed for repeatable data collection, scheduled monitoring, and fast downstream automation.
Features
- Keyword and location search — Collect Dice jobs using targeted role and geography filters.
- Direct search URL support — Start from a Dice search URL when you already have the exact search page you want.
- Fresh posting filters — Narrow results to recent openings such as the last 24 hours, 3 days, 7 days, or 30 days.
- Detailed job records — Capture job titles, employers, locations, salary text, descriptions, and listing URLs.
- Pagination handling — Continue through result pages until your target count is reached or there are no more jobs.
- Structured output — Export clean data for spreadsheets, dashboards, CRMs, and internal tools.
- Flexible run limits — Control the number of jobs collected and optionally cap the number of pages visited.
Use Cases
Recruiting Intelligence
Track live openings for specific roles, skills, and regions. Build current hiring datasets to support sourcing, outreach planning, and talent pipeline decisions.
Job Market Research
Analyze which roles are being advertised most often, where they are concentrated, and how employers describe them. This is useful for trend monitoring, reporting, and competitive benchmarking.
Salary and Role Benchmarking
Collect salary text, employment type, and work setting data when available. Use the results to compare compensation language, remote demand, and role positioning across employers.
Competitive Hiring Monitoring
Follow which companies are actively hiring and for which job families. Re-run the actor on a schedule to monitor changes over time and identify spikes in hiring activity.
Lead Generation for Staffing Teams
Build structured lists of relevant openings and employer details for staffing, recruiting, or B2B outreach workflows. Export the dataset into the tools your team already uses.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
startUrl | String | No | — | Full Dice search URL to use as the starting point. When provided, it overrides keyword and location. |
keyword | String | No | python | Keyword or phrase to search for on Dice. |
location | String | No | Remote | City, state, region, or remote location filter. |
posted_date | String | No | 24h | Posting date filter. Supported values: all, 24h, 3d, 7d, 30d. |
results_wanted | Integer | No | 20 | Maximum number of jobs to save to the dataset. |
maxPages | Integer | No | Auto | Optional page limit. Leave empty to keep collecting until the target is reached or search results end. |
proxyConfiguration | Object | No | — | Optional Apify proxy settings for improved reliability during larger or repeated runs. |
Output Data
Each dataset item contains the main job listing fields plus search metadata. Common fields include:
| Field | Type | Description |
|---|---|---|
id | String | Internal listing identifier from the source. |
jobId | String | Job ID value when provided by the source. |
guid | String | Unique Dice job GUID. |
title | String | Job title. |
company | String | Normalized company name. |
companyName | String | Company name from the original listing data. |
location | String | Human-readable location. |
jobLocation | Object | Structured location object from the source. |
salary | String | Salary text when available. |
employmentType | String | Employment type such as full-time or contract. |
workSetting | String | Work setting such as Remote, Hybrid, or On-Site. |
employerType | String | Employer category when available. |
easyApply | Boolean | Whether the listing supports easy apply. |
willingToSponsor | Boolean | Sponsorship indicator when available. |
summary | String | Short listing summary. |
description_html | String | Job description in HTML format. |
description_text | String | Plain-text version of the description. |
posted | String | Posted date value. |
updated | String | Last updated date value. |
firstActiveDate | String | First active date value from the listing. |
url | String | Final job detail URL. |
detailsPageUrl | String | Original job detail page URL from the source. |
companyPageUrl | String | Employer profile URL when available. |
companyLogoUrl | String | Company logo URL when available. |
position_id | String | Position identifier derived from the listing data. |
dice_id | String | Dice-specific job identifier. |
searchId | String | Search identifier associated with the result set. |
searchPage | Integer | Result page where the job was collected. |
searchPageSize | Integer | Page size used during the run. |
searchSortBy | String | Sort mode applied by the source search. |
searchIncludeRemote | Boolean | Indicates whether remote jobs were included in the search. |
source | String | Source label for the record. |
Some fields may be empty when the original listing does not provide them.
Usage Examples
Basic Job Search
Collect a small batch of recent remote Python jobs:
{"keyword": "python","location": "Remote","posted_date": "24h","results_wanted": 20}
Regional Hiring Snapshot
Collect more jobs for a specific role and geography:
{"keyword": "data engineer","location": "New York, NY","posted_date": "7d","results_wanted": 100,"maxPages": 3}
Direct Search URL Collection
Use a Dice search URL when you already have the exact search page you want:
{"startUrl": "https://www.dice.com/jobs?q=java&location=Remote&page=1","posted_date": "3d","results_wanted": 75}
Large Scheduled Monitoring Run
Collect a larger dataset for recurring hiring analysis:
{"keyword": "machine learning engineer","location": "United States","posted_date": "30d","results_wanted": 250,"maxPages": 8,"proxyConfiguration": {"useApifyProxy": true}}
Sample Output
{"id": "9f0b440130ec2a87ad06df2631366be8","jobId": "9f0b440130ec2a87ad06df2631366be8","guid": "f147d40f-4328-4fce-bbd4-0d8f880040d4","title": "Sr. Lead of Software Engineering - Back End","company": "Capital One","location": "McLean, Virginia, USA","salary": "USD 229,900.00 - 262,400.00 per year","employmentType": "Full-time","workSetting": "On-Site","summary": "Lead backend engineering initiatives for large-scale systems.","description_text": "Lead backend engineering initiatives for large-scale systems.","url": "https://www.dice.com/job-detail/f147d40f-4328-4fce-bbd4-0d8f880040d4","companyPageUrl": "https://www.dice.com/company-profile/example","dice_id": "f147d40f-4328-4fce-bbd4-0d8f880040d4","position_id": "9f0b440130ec2a87ad06df2631366be8","searchPage": 1,"source": "dice.com"}
Tips for Best Results
Use Specific Keywords
- Search for exact roles such as
java developer,site reliability engineer, ordata analystto reduce noise. - Broader keywords return more jobs, but they usually need more filtering after export.
Use startUrl for Precision
- Use a Dice search URL when you want to preserve a search you already refined in the browser.
- This is useful for recurring monitoring of the same search configuration.
Start Small, Then Scale
- Begin with
results_wantedset to20or50to validate output quickly. - Increase collection size once the query is returning the jobs you expect.
Use Recent Posting Filters
- Choose
24hor3dfor fresh hiring signals. - Use
7dor30dwhen building larger research datasets.
Expect Missing Fields Sometimes
- Some Dice listings do not publish salary, sponsorship, or complete company data.
- Treat empty values as source limitations rather than actor failures.
Proxy Configuration
For larger runs or frequent scheduled monitoring, using Apify Proxy can improve stability:
{"proxyConfiguration": {"useApifyProxy": true}}
Integrations
Connect your dataset with:
- Google Sheets — Review job data in a spreadsheet and share it with your team.
- Airtable — Build searchable recruiting and market research databases.
- Slack — Send scheduled run updates to a channel.
- Webhooks — Push fresh job data into your own systems.
- Make — Build no-code hiring and reporting workflows.
- Zapier — Trigger actions in CRMs, spreadsheets, and internal tools.
Export Formats
- JSON — Best for APIs, scripts, and custom applications.
- CSV — Best for spreadsheet analysis and quick filtering.
- Excel — Best for reporting and stakeholder sharing.
- XML — Best for systems that require XML feeds.
Frequently Asked Questions
How many jobs can I collect in one run?
Use results_wanted to control the maximum number of jobs saved. The actor stops when it reaches your target or when no more matching results are available.
Can I use a Dice search URL instead of entering filters manually?
Yes. Set startUrl to a Dice search results URL and the actor will use it as the starting point.
Can I filter by posting date?
Yes. Use posted_date with all, 24h, 3d, 7d, or 30d.
Why do some jobs have missing salary or company fields?
Not every listing exposes the same information. Missing values usually mean the source page did not publish that field.
Does the actor return job descriptions?
Yes. When available, it returns both description_html and description_text.
Can I limit the number of result pages visited?
Yes. Set maxPages to add a hard ceiling on page traversal. Leave it empty if you want the actor to keep collecting until your target is reached.
Can I schedule recurring runs?
Yes. You can schedule the actor on Apify to monitor job searches automatically and feed the results into downstream workflows.
Support
For issues, feature requests, or actor improvements, use the actor page on Apify to contact support.
Resources
Legal Notice
This actor is intended for legitimate data collection, research, and automation workflows. You are responsible for complying with applicable laws, regulations, and website terms when collecting and using data.