Company Job Opening Finder — Glassdoor Alternative

Find job openings on selected Greenhouse and Lever company boards. Export titles, locations, departments, employment types, direct application URLs, and timestamps for a targeted company-jobs watchlist. For applicants and recruiting teams, each dataset row represents one opening with a direct application link and employer-board source.

Workflow: put the results to work

Choose the employers you want to follow and provide their supported public board URLs. Apply location, keyword, or remote filters, then open the direct application links for relevant roles. This workflow collects employer postings rather than salary surveys or employee reviews.

Best fit and scope

Use this focused workflow when you want to follow openings at selected companies that use Greenhouse or Lever. Start with a short list of public board URLs, export the matching postings, then pass the direct application URLs into your tracker, alerting workflow, or candidate-research process.

This Actor deliberately covers the direct-company job-collection step. Glassdoor remains the broader choice when employee reviews, salary data, employer ratings, anonymous company discovery, or its wider job-search experience matters. Use it for selected-company career-board tracking.

How this bounded workflow compares with Glassdoor

Decision point	This Actor	Glassdoor best fit
Scope	Current openings from the Greenhouse and Lever boards you select.	Broad job discovery, employee reviews, salary data, ratings, and company profiles.
Billing	Pay per event plus platform usage; see the Pricing tab for current rates.	Review current Glassdoor terms for the specific product and workflow.
Output	Direct application URL, selected board URL, provider, and collection time on every saved row.	Broader product experience and data types beyond direct-board collection.
Input	Explicit company career-board URLs, making a repeatable tracker input.	Search and discovery when the employer list is not known yet.
Effective efficiency	One bounded source-linked row is ready to pass to a tracker; a same-job timing comparison awaits an authorized export test.	A full comparison benefits from an authorized same-job export and timing test.
Integrations and automation	Structured dataset/API output supports a repeatable saved input; private cloud schedule and webhook evidence is still pending.	Confirm the integrations and automation available for the required Glassdoor product.
Freshness	The Actor requests each selected public board during the run and records collectedAt.	Confirm the source and freshness needs of the intended Glassdoor workflow.

This is a scope tradeoff, not a universal comparison or a relative-cost claim. It is useful for selected-company monitoring; Glassdoor remains the better route for the broader jobs-and-employer research workflow.

A practical workflow

An applicant tracking engineering roles at a few chosen companies starts with their public Greenhouse and Lever board URLs. They add an optional keyword such as software engineer, select remoteOnly when needed, and set a small result cap for a first run. The Actor fetches each provider’s public posting feed, validates every row, filters it locally, and saves each usable job with its original board and direct apply URL.

Next, they can schedule the same input, compare the new dataset to a previous run, and feed selected job URLs into a personal application tracker. The source URL and collection time let a downstream workflow confirm where and when every record was observed.

Quick start

{
  "sources": [
    { "url": "https://boards.greenhouse.io/stripe", "companyName": "Stripe" },
    { "url": "https://jobs.lever.co/example-company", "companyName": "Example Company" }
  ],
  "keywords": ["software engineer"],
  "location": "",
  "remoteOnly": true,
  "includeDescription": false,
  "maxResults": 25
}

Provide one or more sources with public board URLs in exactly these forms:

• https://boards.greenhouse.io/BOARD
• https://jobs.lever.co/BOARD

Use keywords for a local text filter over title, department, location, and Greenhouse descriptions. Lever listing rows are filtered from their public title and category fields. Leave it empty to collect all available postings from the selected boards. location is a literal text filter; it does not geocode, infer visa eligibility, or expand a city into nearby regions.

Data you receive

Every persisted row is one validated public job posting. When includeDescription is off, the description field remains null so agent and spreadsheet exports stay concise.

Field	Meaning
companyName	Caller-supplied company label or selected board identifier.
title	Public job title.
location / workplaceType	Provider-supplied location and a public remote/hybrid label when present.
department / employmentType	Public team and commitment labels when supplied by the board.
applyUrl	Direct provider-hosted job or application URL.
sourceUrl / provider	The selected public career board and the API route that supplied the record.
collectedAt	ISO 8601 collection time for freshness and provenance.

{
  "jobId": "1234567",
  "companyName": "Stripe",
  "title": "Software Engineer",
  "location": "Remote - US",
  "workplaceType": "Remote",
  "department": "Engineering",
  "employmentType": null,
  "description": null,
  "applyUrl": "https://boards.greenhouse.io/stripe/jobs/1234567",
  "sourceUrl": "https://boards.greenhouse.io/stripe",
  "provider": "greenhouse",
  "collectedAt": "<ISO 8601 collection time>"
}

API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~glassdoor-alternative/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "sources": [{"url":"https://boards.greenhouse.io/stripe","companyName":"Stripe"}],
    "keywords": ["software engineer"],
    "remoteOnly": true,
    "maxResults": 25
  }'

AI agents and automation

The dataset is intentionally small and machine-readable: each job has direct application provenance, a source URL, and a collection timestamp. Via the Apify API and MCP route, an AI agent can call the Actor, inspect OUTPUT, and read the dataset before deciding whether a job should enter a tracker.

Collect remote software-engineering openings from these public Greenhouse and Lever boards. Return the job title, company, public location, direct apply URL, source URL, and collection time. When the filter returns an empty result, report the Actor outcome and use returned rows only.

OUTPUT.outcome is COMPLETE, PARTIAL, VALID_EMPTY, INVALID_INPUT, UPSTREAM_FAILED, or CONFIG_ERROR. A valid board with an empty match set is VALID_EMPTY; a board-provider outage with an empty usable set is UPSTREAM_FAILED; a mix of saved jobs and unavailable boards is PARTIAL. RUN_SUMMARY adds board-level attempts and safe diagnostic messages for retry decisions.

Best results

Provide the employer’s canonical public Greenhouse or Lever board URL and begin with a low maxResults cap. Use the explicit source URL again in a scheduled run when you want a repeatable monitor. Confirm the direct application page before acting because postings can change between collection and review. For public company reviews, salary research, and Glassdoor-specific pages, use a Glassdoor scraper instead of treating this direct-career-board workflow as a substitute for those data types.

Builder's note

I designed this Actor around the part of job hunting that benefits most from an API: watching companies you already care about. The public Greenhouse and Lever feeds have stable enough structured fields to preserve source links and timestamps, while keeping the scope honest: selected employers in, their visible job postings out.

Responsible use

Collect only public career boards you are authorized to access, follow applicable laws and site terms, and respect employer application processes. This Actor is independent and is not affiliated with, associated with, or endorsed by Glassdoor. Glassdoor is a trademark of its owner.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
direct-job-posting	Direct company job posting	One validated public job posting saved from a selected Greenhouse or Lever career board. Diagnostic and invalid rows are not charged.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.