Y Combinator Jobs Scraper
Pricing
from $0.02 / 1,000 result extracteds
Y Combinator Jobs Scraper
Scrape public YC Work at a Startup jobs with roles, locations, remote flags, salary, equity, company details, apply links, and descriptions.
Export public YC Work at a Startup job listings with role, company, batch, location, compensation and source-link context. Filter visible listing text by keyword, role, location, remote signal or experience, with optional long job descriptions. Public jobs support separate recruiting and market research rather than verified hiring growth, complete compensation benchmarks or access to applications.
Quick start
Begin with the existing engineering and remote filters under a small saved-result cap, then inspect source links and missing values:
{"searchQuery": "engineer","roles": ["Engineering"],"locations": ["Remote"],"remoteOnly": true,"maxResults": 25,"includeCompanyDetails": false}
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose an example to start with a small, preconfigured input.
- Find remote engineering jobs at YC startups — Collect up to five remote engineering listings with source links and location context.
- Collect YC startup job descriptions — Add available long descriptions to a small engineering-job sample.
- Find experienced-hire jobs at YC startups — Apply the numeric experience filter while retaining source requirement text.
What you get
One saved job row with jobId, jobUrl, company and batch context, available role and employment labels, source compensation strings and collection time. includeCompanyDetails adds the long job description rather than a separate company-enrichment dataset. Missing salary, equity or experience fields remain unavailable rather than becoming inferred offers.
Who is it for?
- Recruiting researchers reviewing selected startup role and location samples.
- Labor-market analysts retaining source compensation and experience context.
- Company research teams inspecting public hiring observations before separate analysis.
- Job-data developers building source-linked search, reporting or matching tools.
How you can use the data
- Review remote engineering candidates. Use the existing Engineering/Remote recipe and keep location, remote and jobUrl together. The filter follows source remote labels or text, without guaranteeing where an applicant may legally or practically work.
- Inspect experience requirements honestly. Apply the existing optional minimum-experience filter, retaining the original requirement. Listings with no numeric value, such as Any or new grads ok, remain included rather than silently satisfying a strict numeric threshold.
- Compare disclosed compensation within a defined sample. Retain salaryRange, equityRange, role and location for selected jobs. Treat source strings as published claims, avoiding invented annualization, missing salary values or conclusions about a full market distribution.
- Maintain your own startup hiring observations. Store jobId, company, batch, source URL and scrapedAt before recurring exports. Feed your own spreadsheet, Slack or Notion workflow, CRM, warehouse or search index, producing alerts and analysis downstream rather than treating postings as proof that a company is growing.
Input settings
Use a small result cap for your first run. Console prefills are examples, not API defaults.
| Setting | What it does |
|---|---|
searchQuery | Optional keyword across visible listing text, up to 500 characters. |
roles | Up to 20 role labels, such as Engineering, Product or Sales. |
locations | Up to 20 location-text filters, such as Remote, San Francisco or India. |
remoteOnly | Keep jobs marked remote or containing remote location text. Defaults to false. |
minExperience | Optional minimum numeric years, from 0 to 20. Nonnumeric requirements remain included. |
maxResults | Save up to 1–1000 matching jobs. Defaults to 50 for omitted API input. The Console prefills 20. |
includeCompanyDetails | Fetch available long descriptions for matching jobs. Defaults to false. |
resumeJobs | Advanced: continue with an unchanged PENDING_JOBS checkpoint from this Actor. |
resumeSourceUrls | Advanced: add PENDING_SOURCES URLs to the normal filtered selection. Deduplicate by jobId across runs. |
Without filters, API input collects the public listing sample. The Console prefills engineer, Engineering and Remote. Clear those examples if you want a broader sample. A run may finish below the result cap when the charge budget or available matching records are exhausted.
Output data
The existing illustrative job row contains historical values and abbreviated links, not a new available-role measurement:
{"jobId": "97116","title": "Product Marketing","role": "Marketing","companyName": "Text Blaze","ycBatch": "W21","location": "San Francisco / Remote (US)","remote": true,"type": "Full-time","salaryRange": "$80K - $150K","equityRange": "0.50%","minExperience": "Any (new grads ok)","applyUrl": "https://account.ycombinator.com/...","jobUrl": "https://www.ycombinator.com/companies/text-blaze/jobs/...","scrapedAt": "2026-07-06T08:52:05.171Z"}
Each dataset row is one YC job posting.
| Field | Description |
|---|---|
jobId | YC job identifier |
title | Job title |
role | Broad role label |
roleSpecificType | Specific role subtype when available |
companyName | YC company name |
companyUrl | YC company profile URL |
ycBatch | YC batch, such as W24 or S23 |
location | Listed job location |
remote | Whether the job appears remote |
type | Job type, such as Full-time |
salaryRange | Listed salary range |
equityRange | Listed equity range |
minExperience | Listed experience requirement |
description | Long description when detail enrichment is enabled |
applyUrl | Application URL |
jobUrl | YC job detail URL |
scrapedAt | ISO timestamp for the run |
visa | Source visa information when available |
skills | Source skill labels, or an empty array |
companyLogoUrl | Available company logo URL |
companyOneLiner | Available short company description |
createdAt | Source creation timestamp when available |
lastActive | Source activity timestamp when available |
sourceUrl | Public YC jobs source URL |
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
The start event is charged when an accepted run starts. It can apply even when no jobs match or extraction later fails.
The result event is charged per saved job record. Detail enrichment adds work to the same record rather than creating a separate charge event. Use a modest result cap and enable descriptions only when needed.
Platform compute, storage or transfer can also apply. See the live Pricing tab for current rates and account discounts.
Tips for best results
- Begin with a broad role and small cap. Narrow by keyword after reviewing the visible sample.
- Keep remote context. A source remote label is different from applicant-location eligibility.
- Inspect nonnumeric experience. Such listings remain included by the documented minimum-experience behavior.
- Select descriptions deliberately. Detail enrichment is useful for your own search index or text review but adds work.
- Retain compensation strings and source times. Missing values are not zero pay or equity.
- Keep recurring filters consistent. Your own retained exports support comparisons rather than an automatic historical archive.
Limits and caveats
The actor can only return public jobs visible on YC pages.
Requests stop if a decompressed page exceeds 2 MiB. Parsing is limited to 200,000 visited/queued nodes and 64 nesting levels. Retained matching jobs and supplied job checkpoints are limited to 8 MiB. These safety limits preserve useful rows and report incomplete extraction rather than claiming no matches. Split large checkpoints into smaller runs. The shipping memory allocation remains 512 MiB.
Some listings may omit salary, equity, role subtype, or experience details.
Application links may point through YC account pages.
Long descriptions require detail enrichment and therefore take longer. A description can remain unavailable even when enrichment is enabled.
Processing is limited to five minutes from the original run start, including shutdown time. Deadline-limited runs may save PENDING_JOBS or PENDING_SOURCES checkpoints. Inspect RUN_SUMMARY for incomplete sources and pending work before treating a dataset as complete. Useful rows remain available when another source fails. An automatic restart does not repeat already charged results. Inspect the existing dataset and start a new run with any pending checkpoint when needed.
Results reflect public jobs visible at collection time, and postings can change or be removed later. Salary and equity strings, experience text and remote flags are source information rather than a verified offer, legal eligibility or a representative benchmark.
Application links can lead through a YC account page, but this Actor does not submit applications or gain account access. Keyword and role filters bound the observed sample rather than proving that every YC company or role was covered. Long descriptions remain optional, and a missing description requires enrichment when available rather than generated replacement text.
This actor extracts publicly available information from YC job pages.
Use the data responsibly and respect applicable laws, platform terms, and privacy obligations.
Do not use scraped data for spam, harassment, discrimination, or prohibited employment practices.
Privacy and data handling
This Actor only requests the permissions needed to run the input you provide. It uses your input (such as URLs, search terms, identifiers, filters, and limits) only to fetch the requested public data from the relevant source site or API for this Actor, then writes results to your Apify dataset/key-value store.
Data may pass through Apify platform services and Apify Proxy during the run, and requests are sent only to the target site or public data provider required for this Actor's results. FetchCat does not send your inputs or outputs to advertising networks, data brokers, or model-training services, and does not retain run data outside Apify storage after the run except when you explicitly share run details for transient support debugging.
You are responsible for using this Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs. Review the output before storing, sharing, or combining it with other data.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
Your own destinations can include Airtable, Slack, Notion, HubSpot, Salesforce, internal recruiting dashboards, warehouses or vector-search tools after export. Configure any messaging or analysis in your own workflow and retain source rows behind generated claims.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The existing Node.js and Python examples wait for completion and print the dataset ID. Use that ID to read saved rows with the Dataset API or client, with pagination for larger exports. The cURL example starts a run and returns its details. Wait for completion before reading its dataset.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~y-combinator-jobs-scraper/runs?token=MY-APIFY-TOKEN' \-H 'Content-Type: application/json' \-d '{"roles":["Engineering"],"locations":["Remote"],"remoteOnly":true,"maxResults":25}'
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/y-combinator-jobs-scraper').call({roles: ['Engineering'],locations: ['Remote'],remoteOnly: true,maxResults: 25});console.log(run.defaultDatasetId);
Python
from apify_client import ApifyClientclient = ApifyClient('MY-APIFY-TOKEN')run = client.actor('fetch_cat/y-combinator-jobs-scraper').call(run_input={'roles': ['Engineering'],'locations': ['Remote'],'remoteOnly': True,'maxResults': 25,})print(run['defaultDatasetId'])
MCP and AI agents
You can ask your AI assistant to collect data with Y Combinator Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Y Combinator Jobs Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/y-combinator-jobs-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Y Combinator Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/y-combinator-jobs-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s Y Combinator Jobs Scraper to collect up to 5 Engineering jobs with Remote in the location and remote-only enabled, with long descriptions off. Keep source links and location qualifiers without assuming applicant eligibility.”
- “Collect up to 5 YC job listings matching founding with long descriptions enabled. Keep role, company, batch and source text without inferring company growth or inventing missing compensation.”
- “Retrieve up to 5 Sales roles from YC public job pages with descriptions off. Preserve salary and equity strings and nonnumeric experience requirements before I make my own comparison, without applying to jobs.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Can I scrape remote-only YC jobs?
Yes. Set remoteOnly to true and optionally add Remote to locations.
Can I get long job descriptions?
Yes. Enable includeCompanyDetails, which adds detail-page descriptions for matching jobs.
Troubleshooting
Why did I get zero results?
Your filters may be too narrow.
Remove searchQuery, reduce role/location filters, or increase maxResults.
Why is description null?
Enable includeCompanyDetails to request available long descriptions. A missing description can also reflect unavailable source text or a failed detail request. Check the run diagnostics rather than assuming every listing has one.
Why are some compensation fields empty?
YC companies do not always publish salary or equity ranges for every job.
Why do I see fewer results than maxResults?
The source may have fewer jobs matching your filters at run time.
Related Actors
More Y Combinator scrapers
- Y Combinator Companies & Founders Scraper — Collect public Y Combinator company records and optional available founder details.
- Y Combinator Companies Scraper — Collect public Y Combinator company-directory records with available company details.
Explore related Apify actors from the same publisher:
- Dice Jobs Scraper — Collect public Dice technology job listings and available job details.
- Ashby Jobs Scraper — Collect public Ashby job-board openings and available job details.
- ATS Jobs Scraper — Collect public job-board openings and available job details from supported applicant-tracking systems.
- Craigslist Classifieds Scraper — Collect public Craigslist classified listings with available prices, locations and links.
Release history
11 Jul 2026
- Feature: Added ready-to-run Y Combinator Jobs Scraper examples for startup hiring research.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥