Glassdoor Jobs Scraper

Every job listing, with the employer's full reputation attached.

Most job scrapers hand you a title, a location and a link. This one hands you the job and the company behind it — ratings, salary bands, benefits, revenue, leadership approval, and what people doing that exact role say about working there. Forty fields per listing, in one clean row, ready for analysis.

Search on Glassdoor exactly as you normally would. Paste the URL. Get structured data.

Why this one

The company comes with the job. No second scrape, no matching step, no joining two datasets on a fuzzy company name. Each row already carries the employer's rating, size, sector, revenue, headquarters and CEO approval score.

Salary bands, where Glassdoor publishes them. The employer's estimated range with its median, pay type and currency — and, on listings where Glassdoor has its own estimate, that too, so you can compare the two.

Sentiment from the same role. Listings often carry pros and cons written by people in that job at that company, plus employee benefit reviews. That is qualitative context most job data simply does not have.

Your search, your filters. Role, location, salary band, date posted, remote — whatever you set on Glassdoor is respected. If the search works in your browser, it works here.

What you get

The job — title, location, full job overview, direct application link, posting ID, and the canonical listing URL.

The pay — the employer's estimated range and median, pay type and currency, plus Glassdoor's own estimate and median where it publishes one.

The company — name, ID, rating, size, industry, sector, type, revenue, headquarters, founded year, website, CEO, plus the percentage of employees who approve of the CEO and who would recommend the company to a friend.

The employee verdict — separate ratings for culture and values, career opportunities, compensation and benefits, senior management, and work/life balance, alongside a benefits summary, benefit reviews, and pros and cons from people in the same role.

Sample output

One real row, abridged:

{
  "job_title": "Senior Engineer - Safety & Multimedia / Audio & Camera (iRDK)",
  "job_location": "Santa Clara, CA",
  "job_posting_id": "1010233743600",
  "job_application_link": "https://www.glassdoor.com/partner/jobListing.htm?pos=101...",

  "pay_range_Employer_est": "68911 - 161544",
  "pay_median_employer": 115228,
  "pay_range_currency": "USD",
  "pay_type": "ANNUAL",

  "company_name": "Capgemini",
  "company_rating": 4.1,
  "company_size": "10000+ Employees",
  "company_industry": "Enterprise Software & Network Solutions",
  "company_sector": "Information Technology",
  "company_revenue": "$10+ billion (USD)",
  "company_headquarters": "Issy-les-Moulineaux, France",
  "company_founded_year": 1967,
  "company_ceo": "Aiman Ezzat",
  "percentage_that_approve_of_ceo": 0.69,
  "percentage_that_recommend_company_to_a friend": 0.88,

  "company_culture_and_values_rating": 4.2,
  "company_work/life_balance_rating": 4.2,
  "company_career_opportunities_rating": 4.1,
  "company_comp_and_benefits_rating": 3.8,
  "company_senior_management_rating": 3.9,

  "reviews_by_same_job_pros": ["Good infrastructure and work culture", "..."],
  "reviews_by_same_job_cons": ["Low salaries and slow promotions", "..."],
  "employee_benefit_reviews": ["Cigna insurance which is great", "Good 401k", "..."]
}

Every field above came from a single row of a live run. Export to JSON, CSV, Excel or XML, or pull it straight from the API.

How completely listings are filled in

Glassdoor does not publish every field for every job, so neither does this. From a 25-listing sample run:

Field group	Present on
Job title, location, apply link, company name, overall company rating	~100%
Pay type and currency	~92%
Employer pay range and median	~72%
Company ratings — culture, management, work/life, career, comp	~68%
Employee benefit reviews	~60%
Pros and cons from the same role	~56%
Glassdoor's own pay estimate	~20%

Rates vary by search: well-known employers are documented far more fully than small ones. Fields Glassdoor has no data for come back empty rather than guessed at.

How it works

1. Search jobs on Glassdoor and copy the URL from your address bar.
2. Paste it into Glassdoor search URLs. Add more URLs to run several searches at once.
3. Set a limit if you want one, and run it.

Input

Field	Required	What it does
Glassdoor search URLs	yes	One or more Glassdoor jobs search or listing URLs. Every job behind each one is collected.
Max jobs per URL	no	Stop after this many jobs from each search. Prefilled at 10, so a first run is a quick sample. Raise it up to 1,000 for a full collection, or clear the field to collect 1,000 per URL.
Max jobs in total	no	Stop the whole run after this many jobs, across all searches. Up to 10,000; empty means 10,000.

Both limits are applied during collection rather than to the results afterwards, so a limited run genuinely does less work and finishes sooner. Every run is bounded, so a broad search can never run away with itself.

Run it once to see the shape of the data, then open it up. The prefilled 10 jobs per URL keeps a first run quick and cheap; raise Max jobs per URL when you know the search is the one you want.

Built to be trusted with real work

Stop a run at any time and keep what it found. Aborting stops the collection and delivers every listing completed up to that moment. Nothing is abandoned and nothing half-fetched is passed off as a result.

You are never charged for a job you did not receive. Listings that failed to fetch are reported separately and never reach your dataset.

Runs are self-limiting. Time budgets scale with the size of the request, so a bigger job simply gets longer rather than being cut off at an arbitrary number.

Clean, stable output. Field names come straight from the source schema and are not renamed or reshaped between runs, so whatever you build on top of this keeps working.

No invented data. A field Glassdoor does not publish comes back empty. Nothing is inferred, averaged or filled in to make a row look complete.

What people use it for

• Recruiting intelligence — track who is hiring, for what, where, and at what pay, with employer reputation attached.
• Compensation benchmarking — compare Glassdoor and employer salary estimates across companies, roles and locations.
• Employer brand research — pair open roles with culture, management and work/life ratings to see how companies are actually perceived.
• Market and competitor analysis — watch hiring signals as a leading indicator of where a company is investing.
• Lead generation — find companies hiring for roles that indicate they need what you sell.

Free accounts

On a free Apify plan a run collects up to 10 job listings, whatever the limits above say. Nothing beyond that is collected, so a capped run finishes quickly. Upgrade to a paid plan and the limits above apply in full.

Good to know

• A search URL is checked for shape, not for results. Whether a search returns any jobs is not knowable until collection runs.
• Repeated search URLs are collected once, so a duplicate never costs twice.
• How long a run waits is worked out from how many jobs it could collect — both limits and the number of search URLs. A bigger request gets longer. There is no setting to guess at.
• If a search cannot be crawled, it is reported in the log and counted in the run summary rather than silently dropped.