Dice Employers, Grouped on the Id and Not the Name
Pricing
from $0.01 / 1,000 employer returneds
Dice Employers, Grouped on the Id and Not the Name
Who is advertising on dice.com, with advert counts, locations and pay worked out from employer set figures only. Dice's own salary bands are counted separately rather than averaged in, because they are not what anyone pays.
Pricing
from $0.01 / 1,000 employer returneds
Rating
0.0
(0)
Developer
Gregory Bolshakov
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
Dice employers
Who is advertising on dice.com, with advert counts, locations and pay. Grouped on dice.com's own employer id, not on the name.
This is a sample, and the run says how big
On 16 September 2026 the board reported 111,699 adverts. Asked for 900, it served 741 and then started repeating a page it had already served. There is no empty page and no error at the end.
So an employer list from one search covers roughly 0.7% of what dice.com claims to hold. Those 741 adverts held 47 employers, and one of them, SAIC, had 262 of them.
advertsSeen is named for what it is. It is what this run read, not the employer's total on
dice.com, and no total is claimed anywhere, because none is knowable from the board.
The run summary carries advertsTheBoardClaimedButDidNotServe so the gap is a number you can
read rather than something to infer.
Pay comes from employer figures only
Salary on dice.com mixes at least five things in one field. This run uses only yearly figures the employer set, and counts the rest separately:
advertsWhosePayIsADiceBandare adverts whose salary is one of Dice's five bands, likeUSD 80,001.00 - 120,000.00. About one in five. Averaging those with real pay drags the answer towards a number nobody was offered.advertsPaidHourlyquote an hourly rate.USD 30.00 per hourandUSD 152,749.00 per yearsit in the same field on the same board.advertsWithPayAsWordssay things likeDepends on Experience.advertsWithNoPaypublished nothing.
An employer with no usable figure gets null, never zero.
Grouped on the id
companyProfileId is dice.com's own key and survives a rename. companyName does not. In the
741 advert sample both gave 47 employers, so nothing was split that day, and the id is still
what the grouping uses.
employerTypes is a list because one employer really can advertise both directly and through
an agency. clientBrandIds is a list for the same reason.
What is not here
No employer description, size, industry or logo. Those live on the company profile page, and that page is a 4 KB shell that renders in the browser and carries no data in the HTML. Its API answers two questions, neither of them about the company, and the branding endpoint refuses the keys published in the site's own bundle. Probed on 16 September 2026.
Everything here comes from the adverts instead.
Careful with the city list
dice.com writes the word remote into the city field on remote adverts. So cities can hold
workplace words as well as places.
What it costs
$0.00001 per run and $0.00001 per employer. The employers come from one board walk, one request per 30 adverts, so 47 employers cost about 25 requests. A run that matches nothing costs nothing.
No keyword search
dice.com's robots.txt disallows /jobs?q*, so this Actor never sends a keyword. Narrow with
place, contract type, workplace, who is advertising, posted date or visa sponsorship. Use
Recruiter to list agencies and Direct Hire to list employers.