# startup.jobs Category & Keyword Job Scraper (`vexaloom-labs/startup-jobs-category-and-keyword-job-scraper`) Actor

Collect startup job listings from startup.jobs by category and keyword, with title, company, work mode, salary, job type, listing text, tags, and the listing link.

- **URL**: https://apify.com/vexaloom-labs/startup-jobs-category-and-keyword-job-scraper.md
- **Developed by:** [vexaloom-labs](https://apify.com/vexaloom-labs) (community)
- **Categories:** Jobs, Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## startup.jobs Category & Keyword Job Scraper

Scrape live job listings from **[startup.jobs](https://startup.jobs)** by category, role, keyword, company, location, salary, experience and work mode. Each row includes the full job description, company logo, workplace type and posting date, plus structured salary, company website and tags whenever the listing publishes them. No login, cookies or API key required.

### What this actor does

- Searches live startup.jobs listings by category, 65-role taxonomy, keyword or company (up to 500 matches per query)
- Filters by remote/hybrid/on-site, full-time/part-time/contract/internship, experience range, minimum or maximum salary, and posting age
- Collects full plain-text descriptions, structured salary ranges (currency and interval), company logo/website, tags and posted dates
- Validates each listing against the live source and skips closed, removed or temporarily unavailable jobs
- Empty fields are omitted from records

### Output per job

- `id` - startup.jobs job ID
- `title` - job title
- `company` - hiring company name
- `companySlug` - company page slug
- `companyLogoUrl` - company logo image URL
- `companyWebsiteUrl` - company website, when published
- `location` - display location (for example `London, United Kingdom` or `United States`)
- `city`, `state`, `country`, `countryCode` - structured location parts
- `workplaceType` - `remote`, `hybrid` or `on-site`
- `employmentType` - `full-time`, `part-time`, `contractor` or `internship`
- `jobType` - human-readable employment label (for example `Full-time`)
- `experienceLevel` - `0-1`, `1-3`, `3-6` or `6+`, when published
- `salary` - formatted salary range and interval, when published
- `salaryMin`, `salaryMax` - published salary bounds
- `salaryCurrency`, `salaryInterval` - currency code and pay period
- `salaryMinUsd`, `salaryMaxUsd` - USD-converted values from the listing; `salaryInterval` gives the pay period (hourly values are not annualised)
- `hasSalary` - whether the listing publishes pay
- `tags` - role, skill and seniority tags, when published
- `description` - full plain-text job description
- `postedAt` - original posting date and time (ISO 8601)
- `url` - the job page on startup.jobs, where you can apply
- `recordType`, `source`, `scrapedAt` - record metadata

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `category` | string | `remote` | `all`, `engineering`, `design`, `marketing`, `sales`, `product`, `operations`, `data`, `finance`, `hr`, `legal`, `customer-success` or `remote` |
| `role` | string | - | Specific role from the startup.jobs taxonomy; when set, `category` is ignored |
| `keyword` | string | - | Matches job titles, company names and tags (not full description text) |
| `company` | string | - | Company name, slug or startup.jobs company URL |
| `location` | string | - | City/country name or startup.jobs location URL; `Remote` is accepted |
| `workplaceType` | string | - | `remote`, `hybrid` or `on-site` |
| `employmentType` | string | - | `full-time`, `part-time`, `contractor` or `internship` |
| `experienceLevel` | string | - | `0-1`, `1-3`, `3-6` or `6+` |
| `minSalaryUsd` | integer | - | Only jobs whose published maximum salary is at least this amount (USD); jobs without pay are excluded |
| `maxSalaryUsd` | integer | - | Only jobs whose published minimum salary is at most this amount (USD) |
| `postedWithin` | string | - | `1`, `7`, `30` or `90` days |
| `maxItems` | integer | `50` | Maximum number of jobs to return (1-500) |

#### Example: engineering jobs mentioning Python

```json
{
  "category": "engineering",
  "keyword": "python",
  "workplaceType": "remote",
  "maxItems": 100
}
```

#### Example: design roles in London

```json
{
  "category": "design",
  "location": "London",
  "maxItems": 50
}
```

#### Example: well-paid product roles posted this week

```json
{
  "category": "product",
  "minSalaryUsd": 120000,
  "postedWithin": "7",
  "maxItems": 50
}
```

#### Example: everything at one company

```json
{
  "company": "stripe",
  "maxItems": 100
}
```

### Use cases

- **Recruiting and sourcing** - build a fresh pipeline of startup openings by role, location and pay
- **Job-board aggregation** - feed startup-specific listings into your own search product or newsletter
- **Compensation research** - compare published salary ranges across roles, companies and markets
- **Remote-work tracking** - monitor remote, hybrid or on-site startup hiring
- **Market intelligence** - follow which roles and skills startups are hiring for right now

### Cost and runtime

A warm 2-row prefill finishes in a few seconds; a cold run adds one ~32 s connection setup. A recent-heavy 50-row run measured about **$0.084** because 47 of the 50 newest jobs needed a detail-page fallback, while a 500-row keyword slice measured about **$0.146** and **39 minutes** (492 rows). A 500-row all/remote slice is projected at roughly **$0.86-0.88** because nearly every one of the first 500 hits is recent and needs that fallback; older or narrower slices need fewer fallbacks. Closed or temporarily unavailable listings are skipped, so a run can return fewer rows than requested; each skipped candidate gets one bounded re-check, so stale-heavy slices can take longer.

### FAQ

**Does this actor require login, cookies or an API key?**
No. It reads publicly visible startup.jobs listings and needs no account or credential.

**What does the keyword search match?**
Job titles, company names and tags, matching the site's own search index. It does not scan the full description text.

**Why is salary missing on some jobs?**
Only some employers publish pay. `hasSalary` says whether the listing includes it; jobs with no published salary are omitted from salary fields.

**Why are some jobs skipped?**
startup.jobs can keep closed or stale listings in its search index for a while, and individual source requests can fail. The actor checks each candidate against the live source and skips listings that are closed or temporarily unavailable.

**How many jobs can I get in one run?**
Up to 500. The site's search exposes at most 500 matches per query, so use narrower filters to reach different slices of the board.

**Why is `applyUrl` not included?**
The employer application link is protected by the site's apply flow. The `url` field opens the job page, where you can apply.

**Does the output include equity?**
startup.jobs does not publish structured equity data, so equity is not a separate field. Equity mentions may appear inside the description.

**How fresh is the data?**
Live. Each run reads startup.jobs at request time; posting dates reflect the original publication date.

**Is this affiliated with startup.jobs?**
No. This is an independent, third-party actor that reads startup.jobs' public listings.

**Do I need to set up a proxy?**
No. The actor chooses a working connection to startup.jobs automatically. Just fill in the input and run it.

# Actor input Schema

## `category` (type: `string`):

Broad job category. Choose All categories to search everything, or Remote jobs for remote-only listings.

## `role` (type: `string`):

Specific role from the startup.jobs role taxonomy. When set, the category is ignored.

## `keyword` (type: `string`):

Matches job titles, company names and tags on startup.jobs. It does not search full description text.

## `company` (type: `string`):

Company name, slug or startup.jobs company URL (e.g. stripe or https://startup.jobs/company/stripe).

## `location` (type: `string`):

City or country name, or a startup.jobs location URL (e.g. United States, London, https://startup.jobs/locations/germany). Use Remote for remote jobs.

## `workplaceType` (type: `string`):

Filter by remote, hybrid or on-site work.

## `employmentType` (type: `string`):

Filter by full-time, part-time, contract or internship roles.

## `experienceLevel` (type: `string`):

Filter by the experience range published on the listing. Jobs without an experience level are excluded when this is set.

## `minSalaryUsd` (type: `integer`):

Only jobs whose published maximum salary is at least this amount in USD. Jobs without a published salary are excluded.

## `maxSalaryUsd` (type: `integer`):

Only jobs whose published minimum salary is at most this amount in USD. Jobs without a published salary are excluded.

## `postedWithin` (type: `string`):

Only include jobs published within this period.

## `maxItems` (type: `integer`):

Maximum number of jobs to return (1-500).

## Actor input object example

```json
{
  "category": "remote",
  "role": "",
  "workplaceType": "",
  "employmentType": "",
  "experienceLevel": "",
  "postedWithin": "",
  "maxItems": 2
}
```

# Actor output Schema

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

Dataset containing all scraped startup.jobs listings with full details.

# 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 = {
    "category": "remote",
    "role": "",
    "workplaceType": "",
    "employmentType": "",
    "experienceLevel": "",
    "postedWithin": "",
    "maxItems": 2
};

// Run the Actor and wait for it to finish
const run = await client.actor("vexaloom-labs/startup-jobs-category-and-keyword-job-scraper").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 = {
    "category": "remote",
    "role": "",
    "workplaceType": "",
    "employmentType": "",
    "experienceLevel": "",
    "postedWithin": "",
    "maxItems": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("vexaloom-labs/startup-jobs-category-and-keyword-job-scraper").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 '{
  "category": "remote",
  "role": "",
  "workplaceType": "",
  "employmentType": "",
  "experienceLevel": "",
  "postedWithin": "",
  "maxItems": 2
}' |
apify call vexaloom-labs/startup-jobs-category-and-keyword-job-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/startup-jobs-category-and-keyword-job-scraper"
        }
    }
}
```

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/ApfeZpSE8udFjcclX/builds/J2ttUxi3zsAMAny4j/openapi.json