Company Job Board Monitor — Indeed Alternative

Monitor selected company job boards on Greenhouse, Lever, and Ashby. Export current openings with job details, application URLs, source endpoints, and timestamps for employer watchlists and hiring research. For hiring researchers, each dataset row is one current job posting from a selected supported company board.

Workflow: put the results to work

Build a watchlist of supported board sources and company slugs. Filter by job title or location, then export the current openings for employer-level hiring research. Repeat the watchlist on your chosen schedule when you need observations over time.

Output: public job records

One dataset row per validated public posting:

Field	Meaning
source and boardSlug	The public ATS source and caller-supplied employer board identifier.
jobId, title, location, department	Stable source job identity and the public fields available from that board.
applyUrl and jobUrl	Public links supplied by the job board.
descriptionText	Clean public description text when includeDescriptions is enabled.
compensation	A public salary component only when the source exposes it.
sourceApiUrl and collectedAt	Provenance endpoint and the time this record was read.

Missing source data stays null; the Actor does not infer salary, work authorization, company identity, or whether a job remains open after this run.

Input

{
  "boards": [
    { "source": "greenhouse", "slug": "stripe" },
    { "source": "ashby", "slug": "ashby" }
  ],
  "maxResults": 50,
  "titleIncludes": "engineer",
  "locationIncludes": "remote",
  "includeDescriptions": true
}

Supported board slugs are the final identifier in the public board URL: job-boards.greenhouse.io/<slug>, jobs.lever.co/<slug>, or jobs.ashbyhq.com/<slug>. The Actor intentionally requires those identifiers—it does not guess a company board from a brand name or crawl an employer homepage.

Example record shape:

{
  "source": "greenhouse",
  "boardSlug": "stripe",
  "jobId": "42",
  "companyName": "stripe",
  "title": "Platform Engineer",
  "location": "Remote — US",
  "department": "Engineering",
  "applyUrl": "https://boards.greenhouse.io/stripe/jobs/42",
  "jobUrl": "https://boards.greenhouse.io/stripe/jobs/42",
  "sourceApiUrl": "https://boards-api.greenhouse.io/v1/boards/stripe/jobs?content=true",
  "collectedAt": "2026-08-31T12:00:00.000Z"
}

How this bounded workflow compares with Indeed

This is an independent, focused alternative for one job: collecting a known employer watchlist from supported public ATS boards. Indeed is the stronger route for marketplace-wide job discovery, job alerts, applications, candidate matching, employer dashboard, sponsored listings, and other hiring-suite features.

Decision	This Actor	Indeed	Best fit
Starting point	Known public Greenhouse, Lever, or Ashby board slugs	Marketplace search and account experience	Use this Actor when your employer watchlist is already defined.
Effective efficiency	One normalized, source-labeled job record per accepted listing	No current equivalent export/API test was performed	Use the Actor when API/dataset-ready records and endpoint provenance matter.
Scope	Read-only public job-board collection	Broad job marketplace and employer suite	Use Indeed for discovery, alerts, applications, or hiring workflow.
Billing	Intended per-validated-record event price plus platform usage	Dynamic sponsored-job pricing; not the same job	Compare costs only for the same fields, volume, and workflow.
Freshness	Reads supported public endpoints during the run and records collectedAt	Equivalent export provenance was not assessed	Re-run the watchlist when you need a fresh observation.
Automation	Batch input and terminal artifacts are implemented locally	Not compared	Cloud scheduling/API/MCP claims wait for live tests.

Indeed is a trademark of its owner. This independent Actor is not affiliated, associated, or endorsed by Indeed.

API

After private deployment, start a run through the Apify API and read the resulting dataset:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/indeed-alternative').call({
  boards: [{ source: 'greenhouse', slug: 'stripe' }],
  maxResults: 10,
  includeDescriptions: false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Agent prompt card

As an AI agent, collect open engineering roles from these known public employer boards. Use the supplied Greenhouse, Lever, and Ashby slugs, then read back the dataset. Return title, location, public apply URL, source endpoint, collection time, terminal outcome, and the event-cost boundary. Keep the request within this focused watchlist scope.

Best results and source guidance

• Provide the exact public source and board slug for every employer. The public endpoint is read at run time, then the normalized result appears in the dataset.
• Start with a small maxResults value to confirm the board and filters, then schedule the same saved input when a recurring snapshot supports your workflow.
• Use titleIncludes and locationIncludes for literal, case-insensitive narrowing. Verify the returned public application URL before acting on a listing.
• Read OUTPUT for the compact terminal outcome and RUN_SUMMARY for source coverage, record counts, event charges, and guidance for the next targeted input.

Public job boards expose different fields. The normalized contract preserves available values, explicit nulls, source provenance, and the collection time so the next workflow step can make a current, informed decision.

Builder's note

I designed this around the public APIs that career sites use to render their own listings: Greenhouse, Lever, and Ashby. I found that a caller-supplied employer watchlist makes the data boundary and freshness clearer than a fragile global-board scrape, while keeping every record tied to its public source URL.

Responsible use

Use only public employer boards you are authorized to monitor. Respect source terms, rate limits, privacy law, and job candidates' rights. The Actor is read-only and keeps application submission, applicant information, private portals, and hiring decisions with the appropriate authorized system.

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).
job-returned	Validated public job returned	Charged for each validated public job posting written to the dataset with a source identifier, title, and public application URL.

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.