Dice Jobs Scraper

Hunting for tech roles on Dice means scrolling page after page and copying the same details by hand: who's hiring, where, full-time or contract, and the link to apply. This scraper does the scrolling for you. Type in the keywords you care about, and every matching posting comes back as a clean row with the role title, employer, location, contract type, and a direct listing link already split out. It paginates on its own, runs without code, and you only pay for what you pull.

What you get

Each Dice posting comes back as one row, grouped into three kinds of data:

• The role — roleTitle, contractType, workLocation, summaryText, listedOn, isPromoted
• The employer — employerName, employerLogo, employerProfileUrl
• Identifiers and links — postingId, postingGuid, listingUrl, searchTerm, collectedAt

Quick start

1. Hit Try for free and add one or more queries under Search terms (for example data engineer and cloud architect).
2. Set Search location and Location scope to aim at a country, state, or single city.
3. Pick a Results per term cap to control how much you pull on each run.
4. Press Start, then export the rows as JSON, CSV, Excel, or XML.

Use cases

• Recruiters — build a live feed of openings in your niche and reach out before the role fills.
• Job seekers — sweep several titles at once and export a single shortlist you can sort and filter.
• Market researchers — measure hiring demand by role, employer, and region over time.
• Sales teams — spot companies that are staffing up and time your outreach to their growth.
• Salary and skills analysts — gather a structured sample of postings to study titles, contract mixes, and locations.

Input

Field	Type	Required	Description
searchTerms	array of strings	Yes	Job queries to run on Dice; each term is searched separately. Prefilled with data engineer.
searchLocation	string	No	Place to search within, country-wide or a single city/state. Default United States.
regionCode	string	No	Two-letter ISO 3166-1 alpha-2 country code. Default US.
locationScope	string	No	How wide the location filter reaches: Country, State, or City. Default Country.
resultsLimit	integer	No	Cap on postings gathered per term; the count resets each term. Default 25.
timeoutSeconds	integer	No	Seconds to wait on each request before giving up. Default 45.

Example input

{
    "searchTerms": ["data engineer", "cloud architect"],
    "searchLocation": "Austin, Texas",
    "regionCode": "US",
    "locationScope": "City",
    "resultsLimit": 25,
    "timeoutSeconds": 45
}

Output

Every posting on the search results becomes one row, paginated automatically up to your per-term cap. Fields Dice doesn't show on a given card come back empty rather than guessed.

Example output

{
    "postingId": "a1b2c3d4",
    "postingGuid": "f8e7d6c5-1234-4abc-9def-0123456789ab",
    "roleTitle": "Senior Data Engineer",
    "employerName": "Northwind Analytics",
    "employerLogo": "https://www.dice.com/assets/logos/northwind-analytics.png",
    "employerProfileUrl": "https://www.dice.com/company-profile/northwind-analytics",
    "workLocation": "Austin, Texas",
    "listedOn": "2 days ago",
    "listingUrl": "https://www.dice.com/job-detail/f8e7d6c5-1234-4abc-9def-0123456789ab",
    "summaryText": "Build and own batch and streaming pipelines on AWS, partnering with analytics teams to ship reliable data products.",
    "contractType": "Full-time",
    "isPromoted": false,
    "searchTerm": "data engineer",
    "collectedAt": "2026-06-29T12:00:00.000000+00:00"
}

Output fields

Field	Type	Description
postingId	string	Dice's internal short hash ID for the posting
postingGuid	string	GUID Dice embeds in the posting link
roleTitle	string	Job title as printed on the card
employerName	string	Company doing the hiring
employerLogo	string	Link to the company logo image
employerProfileUrl	string	Link to the company profile page on Dice
workLocation	string	Where the role is based, e.g. Austin, Texas or Remote
listedOn	string	Relative posting age, e.g. Today, Yesterday, 3 days ago
listingUrl	string	Direct link to the full posting page on Dice
summaryText	string	Short description blurb shown on the result card
contractType	string	Engagement badge, e.g. Full-time, Contract, Part-time
isPromoted	boolean	True when Dice flags the posting as Sponsored
searchTerm	string	The keyword query that surfaced this posting
collectedAt	string	ISO 8601 UTC timestamp of when the row was captured

Tips for best results

• Be specific with your terms. Tighter queries like kubernetes platform engineer return cleaner, more relevant rows than broad ones.
• Match locationScope to your goal. Use City for a focused metro search and Country for a nationwide sweep.
• Start small, then scale. Run with a low resultsLimit to confirm the output fits your pipeline before pulling the full set.
• Run several terms in one go. Each term in searchTerms is swept on its own, so you can cover a whole role family in a single run.
• Raise timeoutSeconds if a slow connection produces timeout errors on larger pulls.

How can I use Dice job data?

How can I use the Dice Jobs Scraper to track tech hiring demand? Run the same searchTerms on a schedule and watch how many postings come back per term and region. With roleTitle, employerName, workLocation, and listedOn on every row, you can chart which roles and markets are heating up week to week.

How can I export Dice job listings to a spreadsheet for recruiting? Add your target titles to searchTerms, set searchLocation, and run. Every posting lands as a row with listingUrl, employerName, and contractType, so you can export to CSV or Excel and work your shortlist without copy-pasting from the site.

How can I find companies that are actively hiring on Dice? Search the skills your prospects need and group the results by employerName. Pair employerProfileUrl and workLocation with listedOn to surface companies staffing up right now, then time your outreach to their growth.

Is it legal to scrape data?

Our actors are ethical and do not extract any private user data, such as email addresses or private contact information. They only extract what the user has chosen to share publicly. We therefore believe that our actors, when used for ethical purposes by Apify users, are safe.

However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

You can also read Apify's blog post on the legality of web scraping.

Support

Questions, feature requests, or a field you'd like added? Reach out at data.apify@proton.me and we'll get back to you.