# Startup Jobs Tracker — YC startup job listings (`agent_muse/startup-jobs-tracker`) Actor

Startup jobs in one structured feed — YC's Work at a Startup board plus remote-friendly startup roles. Filter by keyword, role, location or remote-only; get title, company, salary and direct apply links. Re-run on a schedule and new postings land like an inbox.

- **URL**: https://apify.com/agent\_muse/startup-jobs-tracker.md
- **Developed by:** [John Israel Lofamia](https://apify.com/agent_muse) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.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

## Startup Jobs Tracker — startup job listings

**Startup hiring, tracked in one structured feed: YC's Work at a Startup board plus remote-friendly startup jobs.**

### Who is this for?

**Job seekers** — Stop checking five tabs every morning. Point this Actor at your keywords
(`engineer`, `designer`, `data scientist`) and get a clean, deduplicated table of startup
openings: title, company, location, remote flag, salary range, and a direct apply link.
Run it on a schedule and watch new postings land in your dataset like an inbox.

**Recruiters & sourcers** — Monitor who is hiring, and for what. Track YC batch hiring
waves, spot which startups are scaling engineering teams, and build target-company
lists from real posting data — role categories, job types, locations, salary bands.

### What it scans

| Source | Coverage | Auth |
|---|---|---|
| **YC Work at a Startup** | Every open role at Y Combinator-backed startups — queried newest-first through the board's own public search API, with role/job-type/location facets. The board's rotating public search key is refreshed automatically each run; if the refresh is blocked, this source is skipped gracefully | None |
| **4DayWeek** | Startup and tech roles at companies with reduced-hour / remote-friendly cultures, via its public JSON API | None |

No logins, no API keys, no scraping of login-walled pages.

### Inputs

- **Keywords** (required, default `["engineer"]`) — searched in titles and descriptions.
- **Remote only** — keep only remote jobs.
- **Roles** (YC) — e.g. `["eng", "design", "product", "data", "ops", "marketing", "sales"]`.
- **Job types** (YC) — e.g. `["full-time", "contract", "intern"]`.
- **Location contains** — free-text location filter, e.g. `"San Francisco"` or `"Germany"`.
- **Days back** (default 30) — only jobs posted within the window.
- **Max results** (default 50) — newest first.

### Output

Each row: `title`, `company`, `companyWebsite`, `location`, `remote`, `salaryMin`,
`salaryMax`, `salaryCurrency`, `salaryPeriod`, `url` (direct apply link),
`postedDate`, YC `batch`, `role`, `jobType`, `skills`, `source`, `description`.

Example: *"Senior Backend Engineer — Forge (W24) — San Francisco, CA, US / Remote (US) —
$160K–$220K/yr — https://www.workatastartup.com/jobs/90059"*.

### Pricing

Pay-per-event: **$0.02 per run** + **$0.005 per job listing saved**. A daily
50-job scan costs about **$0.27** — less than a coffee per month.

# Actor input Schema

## `daysBack` (type: `integer`):

Keep only jobs posted within the last N days. 1-365.

## `include4DayWeek` (type: `boolean`):

Include 4DayWeek — public job board of companies with reduced-hour / remote-friendly roles (keyless JSON API).

## `includeYcJobs` (type: `boolean`):

Include YC Work at a Startup — every open role at Y Combinator-backed startups. Uses the board's own public search API; its rotating search key is refreshed automatically each run (if the board blocks the refresh, this source is skipped gracefully and the run still succeeds).

## `jobTypes` (type: `array`):

YC only: keep only these job types, e.g. \["full-time", "contract", "intern"]. Empty = all types.

## `keywords` (type: `array`):

Keywords to search in job titles/descriptions, e.g. \["engineer", "designer", "data scientist"]. At least one is required so the daily auto-test always finds open jobs.

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

Keep only jobs whose location mentions this text, e.g. "San Francisco" or "Germany". Empty = anywhere.

## `maxResults` (type: `integer`):

Maximum job listings to return (newest first).

## `remoteOnly` (type: `boolean`):

Keep only remote jobs.

## `roles` (type: `array`):

YC only: keep only these role categories, e.g. \["eng", "design", "product", "data", "ops", "marketing", "sales"]. Empty = all roles.

## Actor input object example

```json
{
  "daysBack": 30,
  "include4DayWeek": true,
  "includeYcJobs": true,
  "jobTypes": [],
  "keywords": [
    "engineer"
  ],
  "location": "",
  "maxResults": 50,
  "remoteOnly": false,
  "roles": []
}
```

# Actor output Schema

## `results` (type: `string`):

Link to the dataset with all matching startup job listings.

# 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 = {
    "keywords": [
        "engineer"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("agent_muse/startup-jobs-tracker").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 = { "keywords": ["engineer"] }

# Run the Actor and wait for it to finish
run = client.actor("agent_muse/startup-jobs-tracker").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 '{
  "keywords": [
    "engineer"
  ]
}' |
apify call agent_muse/startup-jobs-tracker --silent --output-dataset

```

## MCP server setup

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

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/ooaQpqAclxQXMHtWl/builds/8Paaf5adrkycLihaP/openapi.json