Glassdoor Jobs Scraper - Pay and Ratings avatar

Glassdoor Jobs Scraper - Pay and Ratings

Pricing

from $0.25 / 1,000 results

Go to Apify Store
Glassdoor Jobs Scraper - Pay and Ratings

Glassdoor Jobs Scraper - Pay and Ratings

Scrape Glassdoor job listings by keyword and location. Each row carries the title, company, employer rating, pay as numbers with its period and currency next to the range Glassdoor displays, easy-apply and sponsored flags, a description snippet, days since posting and the apply URL.

Pricing

from $0.25 / 1,000 results

Rating

0.0

(0)

Developer

String

String

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Glassdoor Jobs Scraper — salary, company rating, location

The Glassdoor Jobs Scraper collects job listings from Glassdoor search results. Give it search terms and a location, and it returns each listing with the employer's Glassdoor rating, the pay range as numbers rather than a display string, the location, the apply URL and how many days ago the job was posted.

To scrape Glassdoor jobs, put one or more job titles or keywords in queries and a location such as "United States" or "New York, NY". No Glassdoor account, login or cookies are used; this Actor reads what a logged-out visitor sees. Around 22 jobs per search.

What it returns

FieldTypeNotes
jobIdstringGlassdoor's own listing ID — stable, use it to de-duplicate
titlestring
companystringThe employer named on the search row
employerRatingnumberGlassdoor overall employer rating out of 5
salaryEstimatestringThe pay range as Glassdoor displays it on the card, e.g. "$136K - $184K"
salaryMin, salaryMaxnumberThe same range as numbers — 136000 and 184000, not a string to clean up
salaryPeriodstringThe period the pay is quoted over, e.g. "ANNUAL"
salaryCurrencystringCurrency of salaryMin and salaryMax, e.g. "USD"
salarySourcestringGlassdoor's own label for where the figure came from, e.g. "EMPLOYER_PROVIDED"
locationstring
ageInDaysnumberWhole days since the listing was posted, as Glassdoor states it
postedAtstringISO 8601 timestamp derived from ageInDays — day precision, not hour
easyApplybooleanWhether the listing takes Glassdoor's one-click apply
sponsoredbooleanWhether the listing is a paid placement
descriptionSnippetstringThe first description fragment Glassdoor shows on the card — a snippet, not the full description
employerIdnumberGlassdoor's employer ID, stable across that employer's listings
jobUrlstringDirect link to the Glassdoor posting
query, searchLocation, sourceUrl, collectedAtstringProvenance for every row

Input

{ "queries": ["software engineer", "product manager"], "location": "New York, NY" }
FieldDescription
queriesJob titles or keywords. Required, 1–50. Duplicates collapse to one fetch.
locationCity, state or country. Default "United States". One location per run.
maxItemsCap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below.
concurrencySearches run in parallel. Default 5.

Every search in a run shares one location. The Glassdoor Jobs Scraper resolves that free-text location through Glassdoor's own autocomplete before searching, which costs one extra request per run and is what lets you write "New York, NY" instead of Glassdoor's internal location ID.

Use cases

  • Compensation benchmarking from Glassdoor's numeric pay ranges rather than scraped display strings
  • Employer-brand analysis — pairing employerRating with what a company is hiring for
  • Competitor hiring signals by role and city
  • Recruiting lead lists filtered by employer rating
  • Tracking Glassdoor postings over time by re-running on a schedule, joined on jobId

Reliability

The Glassdoor Jobs Scraper reads the search page's own data payload rather than asking a model to interpret the rendered HTML, so a field is either present and correct or null.

Pay is reported twice on purpose: salaryEstimate is the exact string Glassdoor renders, and salaryMin/salaryMax are the underlying numbers, joined back to their listing by Glassdoor's own listing ID rather than by card order. salarySource records whose figure it is, so an employer-stated range and a Glassdoor estimate are distinguishable in the dataset instead of being flattened together.

Glassdoor dates a listing only as a whole-day age, so ageInDays is carried as the source's own value and postedAt is derived from it — the timestamp is accurate to the day, not the hour.

A Glassdoor search that cannot be read is recorded in the run's SUMMARY under failures, and a run where every search failed exits with an error. A location that Glassdoor cannot resolve fails the run outright, because searching on without it would silently widen every query to nationwide results.

Frequently asked questions

Do I need a Glassdoor account, login or API key? No. The Glassdoor Jobs Scraper uses no account, login, cookies or API key — only public Glassdoor search pages are read.

Does the Glassdoor Jobs Scraper return salary as a number? Yes. salaryMin and salaryMax are numbers with salaryPeriod and salaryCurrency alongside, and salaryEstimate keeps the formatted string Glassdoor displays.

Is the Glassdoor salary the employer's or Glassdoor's estimate? Both occur, and salarySource tells you which — a listing whose employer stated the range carries "EMPLOYER_PROVIDED". The label is passed through unchanged rather than being flattened away.

How many Glassdoor jobs does one search return? Around 22, which is what one Glassdoor results page carries. Ten search terms therefore return roughly 220 jobs.

Can I get the full Glassdoor job description? No. descriptionSnippet is the fragment Glassdoor shows on the search card. Follow jobUrl for the full description.

Can I search several locations in one run? No — one run searches one location across all of its queries. Start one run per location.

What happens on a free Apify plan? The run stops at 250 requests and 250 results and reports that it hit the limit. Any paid plan runs the full input.

Limitations

The Glassdoor Jobs Scraper reads one results page per search, so it collects the first page rather than paginating a whole market; run several narrower queries to widen coverage. Full job descriptions, company reviews, interview reports and salary-report pages are out of scope, as is searching more than one location per run.

Free plan limit

Runs started from an Apify free plan stop at 250 requests and 250 results, and the run reports that it reached the limit. Any paid plan runs the full input and maxItems you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not cover for free-plan runs. It binds on requests as well as results so that a large input list cannot spend those fetches for rows the run will not return.