Glassdoor Scraper — Jobs, Reviews, Salaries & Interviews
Pricing
from $0.80 / 1,000 results
Glassdoor Scraper — Jobs, Reviews, Salaries & Interviews
Scrape Glassdoor without login: jobs with salaries, thousands of employee reviews (all 6 sub-ratings, pros/cons, sentiment), salary percentiles by title, interview questions, and full company profiles. Real logos + shareable visual report. Request-only, fast, reliable.
Pricing
from $0.80 / 1,000 results
Rating
0.0
(0)
Developer
Kelopr
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
Build a joined view of jobs, employee experience, salaries, interviews, and company fundamentals.
Scrape Glassdoor without login: jobs with salaries, thousands of employee reviews (all 6 sub-ratings, pros/cons, sentiment), salary percentiles, interview questions, and full company profiles. Real logos + visual report.
All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.
🚀 What this Actor does
- Flexible collection:
Job discovery,Company reviews,Salary & interview intelligence,Company profile. - Structured output: clean JSON records organized into
overview,jobs,reviews,salaries,interviews,companiesviews. - Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
- Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.
🎛️ Modes and workflows
| Mode or workflow | What it does |
|---|---|
Job discovery | Search by keyword and location or provide exact Glassdoor URLs. |
Company reviews | Collect pros, cons, sub-ratings, recommendations, replies, and sentiment. |
Salary & interview intelligence | Add salary percentiles, interview outcomes, duration, and questions. |
Company profile | Return company ratings and business metadata alongside hiring data. |
💡 Common use cases
- Employer-brand benchmarking
- Salary and interview research
- Hiring-market and employee-sentiment analysis
📥 Input schema
Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.
| Field | Type | Description | Default |
|---|---|---|---|
keywords | array | Job titles or keywords to search on Glassdoor, e.g. "software engineer", "nurse". | — |
location | string | Optional location for the job search — city, state, or country (e.g. "New York, NY"). | — |
startUrls | array | Glassdoor company reviews URLs, e.g. https://www.glassdoor.com/Reviews/Amazon-Reviews-E6036.htm | — |
scrapeReviews | boolean | For each company URL, collect employee reviews (ratings, sub-ratings, pros/cons, employer replies). | true |
maxReviewsPerCompany | integer | Cap on reviews collected per company URL. | 100 |
reviewSort | string | Ordering for collected reviews. Allowed: relevance, recent, lowest. | relevance |
maxJobsPerSearch | integer | Cap on jobs collected per keyword search. | 30 |
scrapeSalaries | boolean | For each company URL, collect salary data by job title (base pay percentiles, count). | false |
maxSalariesPerCompany | integer | Cap on salary rows per company URL. | 50 |
scrapeInterviews | boolean | For each company URL, collect interview experiences (difficulty, outcome, questions). | false |
maxInterviewsPerCompany | integer | Cap on interview rows per company URL. | 50 |
scrapeCompanyProfile | boolean | For each company URL, add a company profile row (industry, revenue, size, HQ, stock). | false |
sentiment | boolean | Add a sentiment score and label to each review. | false |
htmlReport | boolean | Build a shareable HTML report (jobs board + employer intelligence: ratings, sub-ratings, sentiment, salaries, pros/cons) saved to the key-value store as 'report'. | true |
dedupe | boolean | Save each job/review only once per run. | true |
maxItems | integer | Global cap across jobs + reviews. 0 = unlimited. | 200 |
proxyConfiguration | object | Glassdoor requires residential proxies (Cloudflare blocks datacenter). The default is tuned for reliable access. | {"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "US"} |
maxConcurrency | integer | Sources processed at once. | 5 |
maxRetries | integer | Retries for a failed request. | 5 |
requestTimeoutSecs | integer | Maximum time for one request. | 30 |
▶️ Example input
{"keywords": ["data analyst"],"location": "Berlin","maxJobsPerSearch": 25,"scrapeReviews": true,"maxReviewsPerCompany": 20,"scrapeCompanyProfile": true}
📦 Output schema
Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.
overview — Overview
A compact table for fast scanning and export.
Fields: dataType, companyLogo, company, title, summary, companyRating, ratingOverall, location, salaryMedian, url
jobs — Jobs
Normalized job records.
Fields: companyLogo, title, company, companyRating, location, isRemote, easyApply, salaryMin, salaryMedian, salaryMax, salaryCurrency, ageInDays, url
reviews — Reviews
One record or grouped payload for reviews, depending on the source schema.
Fields: companyLogo, company, ratingOverall, summary, pros, cons, jobTitle, employmentStatus, recommendToFriend, ceoApproval, sentimentLabel, employerReply, reviewDate, url
salaries — Salaries
Structured salaries records for this Actor.
Fields: companyLogo, companyName, jobTitle, baseP10, baseMedian, baseP90, totalMedian, currency, salaryCount, mostRecent
interviews — Interviews
Structured interviews records for this Actor.
Fields: companyLogo, companyName, jobTitle, difficulty, experience, outcome, durationDays, source, location, questions, interviewDate
companies — Companies
Company-level identity, enrichment, and aggregate signals.
Fields: companyLogo, companyName, overallRating, reviewCount, recommendToFriendPercent, ceoApprovalPercent, businessOutlookPercent, cultureAndValuesRating, workLifeBalanceRating, careerOpportunitiesRating, compensationAndBenefitsRating, seniorLeadershipRating, diversityAndInclusionRating, industry, revenue, size, type, stock, headquarters, founded, website
📤 Example output
{"title": "Data Analyst","company": "Example Labs","companyRating": 4.2,"location": "Berlin","isRemote": true,"salaryMin": 55000,"salaryMedian": 62500,"salaryMax": 70000,"salaryCurrency": "EUR","url": "https://www.glassdoor.com/job-listing/DEMO-JOB-01"}
Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.
🔌 API example
Replace the placeholder with an Apify token and send the same input used in the Console:
curl -X POST "https://api.apify.com/v2/acts/trakk~glassdoor-scraper/runs?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"keywords": ["data analyst"], "location": "Berlin", "maxJobsPerSearch": 25, "scrapeReviews": true, "maxReviewsPerCompany": 20, "scrapeCompanyProfile": true}'
For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.
🧩 Automation and exports
- Schedule recurring runs from the Apify Console.
- Trigger downstream systems with webhooks when a run succeeds or fails.
- Reuse named monitoring keys or stores where the selected workflow supports change tracking.
- Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.
❓ FAQ
Do I need a login or browser session?
Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.
Why can some fields be empty?
Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.
How should I run this at scale?
Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.
Is the example data real?
No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.