# Gem Jobs Scraper: Full Ads, Pay, Offices, Job Alerts (`notarealgamedev/gem-jobs`) Actor

Every open job from any Gem job board (jobs.gem.com/{company}) in clean JSON: full ad, department, every office, workplace type, employment type, requisition ID, posting and update dates, pay as numbers when the ad states it. Filters and only-new-jobs monitoring.

- **URL**: https://apify.com/notarealgamedev/gem-jobs.md
- **Developed by:** [NotAReal GameDev](https://apify.com/notarealgamedev) (community)
- **Categories:** Jobs, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Gem Jobs Scraper do?

It reads the job board of any company that hires through **Gem** and returns every open job as clean, flat JSON: job boards on `jobs.gem.com/{company}`, such as `jobs.gem.com/bilt` or `jobs.gem.com/productboard`.

It reads the public job feed behind each board, one request per company. No login, no API key, no browser. Paste one link or a thousand.

**Typical uses**

- **Job boards and aggregators**: complete, fresh postings straight from the employer's Gem board.
- **Sales and recruiting signals**: which startups and scale-ups hire for which roles, where, and in which teams.
- **Pay research**: pay ranges as numbers from the ads (USD, EUR, CZK and more), by role and place.
- **Alerts**: only the jobs that are new since the last run, plus notice of jobs that closed.

### Why this one

| | What you get |
|---|---|
| **Pay as numbers** | Pay ranges written in the ad ("$160,000 - 215,000", "2,295,000–3,305,000 CZK") become numbers with currency and period. |
| **Every office** | Jobs open in several offices list each of them, with the ISO country code. |
| **Gem's own fields** | Department, workplace type (on-site, hybrid, remote), employment type, requisition ID, office names, posting and update dates. |
| **Filters before you pay** | Title words, locations, remote, posted within N days, ad language. Jobs removed by filters are not charged. |
| **Only new jobs** | Monitoring returns only jobs you have not received, and lists jobs that closed since the last run. |

**Test, 14 November 2026:** Bilt and Productboard, compared with another Gem Actor on the same 20 jobs:

- **Pay as numbers 16 of 20** here (USD for Bilt, CZK for Productboard's Czech roles, read from the ads); 0 of 20 there.
- **Ad language 20 of 20 and seniority 8 of 20** here; the other Actor has neither.
- Both returned the full ad, the country code, the workplace type and every office for the 8 multi-office jobs.

Also tested the same day: BigPanda and Firestorm (found by the name "Firestorm"), 40 jobs in 4 seconds.

### How to use it

1. Paste one or more entries into **Companies**, one per line:
   - **Job board**: `https://jobs.gem.com/bilt` (a link to any job on it works too)
   - **Short form or name**: `gem:bilt`, or just the company name
2. Optionally set filters: title words, location, remote, posted within N days, ad language. **Jobs removed by filters are not charged.**
3. Click **Start**. Download the results as JSON, CSV or Excel, or get them through the API.

#### Input example

```json
{
  "companies": [
    "https://jobs.gem.com/bilt",
    "https://jobs.gem.com/productboard"
  ],
  "titleKeywords": ["engineer"],
  "postedWithinDays": 30,
  "maxJobsPerCompany": 100,
  "onlyNewJobs": true,
  "monitorId": "gem-engineering"
}
```

#### Daily monitoring

Set **Only new jobs** and schedule the Actor, for example daily. Each run returns only the jobs this monitor hasn't delivered before, so you pay for each job once. Each **Monitor name** keeps its own memory, and the run summary (key-value store `OUTPUT`) lists jobs that closed since the last run.

### Output

One row per job. Example (shortened):

```json
{
  "title": "Staff AI Product Engineer",
  "companyName": "Productboard",
  "ats": "gem",
  "board": "productboard",
  "jobId": "8080046002",
  "department": "Product Engineering",
  "location": "Prague, Czechia",
  "locations": ["Prague, Czechia", "Czechia - Remote", "Brno, Czechia"],
  "country": "Czech Republic",
  "countryCode": "CZ",
  "workplaceType": "hybrid",
  "employmentType": "full-time",
  "seniority": "lead",
  "salaryMin": 2295000,
  "salaryMax": 3305000,
  "salaryCurrency": "CZK",
  "salaryPeriod": "year",
  "salaryText": "2,295,000–3,305,000 CZK",
  "postedAt": "2025-07-24T09:29:02Z",
  "updatedAt": "2026-10-26T13:36:57Z",
  "language": "en",
  "url": "https://jobs.gem.com/productboard/8080046002",
  "boardUrl": "https://jobs.gem.com/productboard",
  "description": "Location:\n Czechia (Prague hybrid, or remote within Czechia). Remote within the EU is also possible…",
  "extras": {
    "requisitionId": "E-003",
    "offices": ["Prague (Hybrid)", "Remote Czechia", "Remote Europe", "Brno (Hybrid)"]
  }
}
```

| Field | Meaning |
|---|---|
| `title`, `companyName` | Job title and employer. |
| `department` | Department as the board files it (all departments in `extras` when there are several). |
| `location`, `locations`, `country`, `countryCode` | Main place, every office's place, country and its ISO code. |
| `workplaceType` | `onsite`, `hybrid` or `remote`, as Gem states it. |
| `employmentType`, `seniority` | Full-time, contract, internship…; seniority from the title. |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryPeriod`, `salaryText` | Pay range when the ad states one. |
| `postedAt`, `updatedAt` | First publication and last update (UTC). |
| `language` | Language of the ad. |
| `url`, `applyUrl`, `boardUrl` | Job page (with the application form) and the board. |
| `description`, `descriptionHtml` | Plain text (on by default) and HTML (off by default). |
| `extras` | Requisition ID, office names, all departments. |
| `jobId`, `jobKey` | The job's Gem ID and a unique key for de-duplication. |

The run summary (key-value store `OUTPUT`) lists every company with its status, jobs on the board, jobs matching your filters, jobs delivered and any notes.

### Pricing

**$4.00 per 1,000 jobs delivered** ($0.004 per job), plus Apify's small charge per run start. Jobs removed by your filters are free, and so are jobs already delivered to a monitor.

Examples:

- 10 companies × 20 newest jobs = 200 jobs = **$0.80**.
- Daily monitoring of 50 companies with about 30 new jobs a day ≈ 900 jobs a month ≈ **$3.60 a month**.

### FAQ

**How do I find a company's Gem board?** Open a job on the company's careers page: the address bar or the Apply button often shows `jobs.gem.com/<company>`. Paste that, or just the company name.

**Why is the pay sometimes empty?** Gem's feed has no pay field; the pay comes from the ad text, so it's there when the company writes a range into the ad (common for US, Canadian and many EU roles).

**Is this allowed?** The Actor reads public job ads that companies publish so that people find them, within the site's robots.txt rules, without logging in. Personal e-mail addresses and phone numbers in ads are removed; shared mailboxes such as careers@ are kept. How you use the data is up to you and the laws that apply to you.

**Other job systems?** **Career Page Jobs** by the same author reads more than 20 hiring systems (Greenhouse, Lever, Ashby, Workday, iCIMS, Jobvite and more) in one run, with the same output.

### Integrations

Results work with anything Apify connects to: the API, webhooks at the end of each run, Google Sheets, Slack, email, Make, Zapier and n8n.

# Changelog

This Actor's version history is a separate document: https://apify.com/notarealgamedev/gem-jobs/changelog.md

# Actor input Schema

## `companies` (type: `array`):

One per line: a company's Gem job board (e.g. https://jobs.gem.com/bilt, or a link to any job on it), the short form (gem:bilt) or the company name.

## `maxJobsPerCompany` (type: `integer`):

Newest jobs first. 0 = no limit. You pay per job delivered, so this also caps the cost per company in each run.

## `titleKeywords` (type: `array`):

Keep only jobs whose title contains at least one of these words or phrases (not case-sensitive, whole words). Example: engineer, data, sales. Filtered-out jobs are free.

## `excludeTitleKeywords` (type: `array`):

Drop jobs whose title contains any of these words. Example: intern, senior.

## `locationKeywords` (type: `array`):

Keep only jobs whose location, country or remote type mentions one of these. Example: Oslo, Norway, NO, Remote.

## `workplaceTypes` (type: `array`):

Keep only remote, hybrid and/or on-site jobs. Jobs whose workplace type is unknown are dropped when this is set.

## `postedWithinDays` (type: `integer`):

Keep only jobs published in the last N days. Jobs without a publish date are kept.

## `languages` (type: `array`):

Keep only job ads written in these languages (stated by the job board, or detected from the ad text). Useful for, e.g., English-language jobs in Norway, Germany or the Netherlands. Ads whose language can't be determined (very short ads) are left out.

## `includeDescription` (type: `boolean`):

Full ad text, ready for search or AI. Turn off for smaller exports.

## `includeDescriptionHtml` (type: `boolean`):

The original formatted ad, for re-publishing on your own job board.

## `onlyNewJobs` (type: `boolean`):

Return only jobs this monitor has not delivered before, so you never pay twice for a job. Schedule the Actor (e.g. daily) and you pay only for new jobs. Jobs that have closed since they were delivered are listed for free in the run's OUTPUT record.

## `monitorId` (type: `string`):

Keeps separate memories for separate watch lists, e.g. 'nordic-fintech' or 'client-a'. Letters, numbers, - and \_. Only one run per monitor can work at a time; a second one stops immediately instead of charging twice.

## `skipExistingOnFirstRun` (type: `boolean`):

The first time this monitor reads a company (also companies you add later), save its open jobs as the starting point without delivering them (free). From then on you get only newly posted jobs. Turns on monitoring mode.

## `maxConcurrency` (type: `integer`):

How many companies are read at the same time. The default is polite to the job boards; raise it only for very long lists.

## Actor input object example

```json
{
  "companies": [
    "https://jobs.gem.com/bilt",
    "https://jobs.gem.com/bigpanda"
  ],
  "maxJobsPerCompany": 3,
  "includeDescription": true,
  "includeDescriptionHtml": false,
  "onlyNewJobs": false,
  "monitorId": "default",
  "skipExistingOnFirstRun": false,
  "maxConcurrency": 6
}
```

# Actor output Schema

## `jobs` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        "https://jobs.gem.com/bilt",
        "https://jobs.gem.com/bigpanda"
    ],
    "maxJobsPerCompany": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("notarealgamedev/gem-jobs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "companies": [
        "https://jobs.gem.com/bilt",
        "https://jobs.gem.com/bigpanda",
    ],
    "maxJobsPerCompany": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("notarealgamedev/gem-jobs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companies": [
    "https://jobs.gem.com/bilt",
    "https://jobs.gem.com/bigpanda"
  ],
  "maxJobsPerCompany": 3
}' |
apify call notarealgamedev/gem-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,notarealgamedev/gem-jobs"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/PHEbOrVBiKKRgsEWh/builds/xRIgR87GbtI4Fvlet/openapi.json
