Hacker News Who Is Hiring: Parsed Job Posts by Month

Every job post from the monthly "Who is hiring?" thread, parsed into company, roles, location, remote or onsite, salary text, visa sponsorship and tech stack. Pick a month (or just "latest") and get one structured row per post instead of 250 paragraphs of free text. Turn on monitoring and run it on a schedule through the first days of the month to get only the posts that are new since your last run, charged per post and free on a quiet run.

Who uses it: job-market analysts counting which stacks and roles are hiring, recruiters and sourcers building a list of companies that are hiring right now, founders watching competitors' hiring, and job-seekers filtering for remote or visa-sponsoring posts.

Related actors: to watch Hacker News for mentions of a brand or keyword use Hacker News Mentions Monitor. To read one company's own job board use ATS Jobs Unified Lookup.

How to use

1. In the Apify Console. Open the actor page and click Start — the months field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~hn-who-is-hiring-parser/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"months":["latest"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "months": [
    "latest"
  ]
}

One month per line: latest, 2026-09 or September 2026. Each month is one monthly Ask HN: Who is hiring? thread, and every job post in it is one row. Leave it empty for the latest month. Accepted formats: latest, 2026-09, September 2026, 2019-03.

months takes one month per line: latest, 2026-09, September 2026 (the series starts in April 2011; up to 12 months per run). Each month is read in a single request. Filters (work mode, minimum parse quality, keywords) run before anything is counted or remembered, so a post you filtered out is never charged and never marked as seen. The run itself is free; you are billed per post actually returned.

Output

One row per post, for example:

query	found	status	postCount	monitorStatus	truncated	posts	month	company	companyUrl	roles	location	workMode	remote	employmentTypes	salaryText	visaSponsorship	stack	applyUrls	applyEmail	parseConfidence	headerText	postText	postedAt	postUrl	postId	threadUrl	threadId	isNew	firstSeenAt	scrapedAt
latest	true	OK				<all posts (full list)>									<salary (as written)>													<is this post new?>		1970-01-01T00:00:00.000Z

A month with no thread, or a month where no post matches your filters, comes back as a row with "found": false and is never charged. Missing values are null, never 0 or an empty string.

How the parsing works, honestly. Posts are free text. The first line usually reads Company | Role | Location | REMOTE | Full-time | $salary, but the order varies and some posts use dashes, so each piece of the first line is classified by what it contains, not by its position. On a recent thread, company was found on about 98% of posts, a work mode on about 92%, a location on about 86% and at least one role on about 73%. Anything the parser cannot tell is null, and parseConfidence (high, medium, low) says how much of the first line was understood. headerText and postText are always returned so you can check any row. salaryText is the pay segment exactly as the poster wrote it; it is never converted to a number. visaSponsorship is true/false only when the post says so. The poster's username is not returned, and applyEmail only ever holds a generic role mailbox such as jobs@ or careers@.

Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token and no account of your own beyond an Apify login.

The latest month, first 20 posts. The default shape.

{
  "months": ["latest"],
  "maxResults": 20
}

Remote posts that mention Python, two months side by side.

{
  "months": ["2026-10", "2026-09"],
  "workMode": "remote",
  "includeKeywords": ["python"],
  "minConfidence": "medium",
  "maxResults": 100
}

New-post alert for the current month, monitoring on. Schedule it daily; a day with nothing new returns one free row.

{
  "months": ["latest"],
  "onlyNewSinceLastRun": true,
  "deltaName": "hn-hiring-watch"
}

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~hn-who-is-hiring-parser/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"months":["latest"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~hn-who-is-hiring-parser/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"months":["latest"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~hn-who-is-hiring-parser/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"months":["{{thread}}"]}, mapping the row's thread into the months array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "hacker news who is hiring parser" — the agent will find and run this actor.