# Hacker News Who Is Hiring: Parsed Job Posts by Month (`accountable_eel/hn-who-is-hiring-parser`) Actor Every job post from the monthly Hacker News Who is hiring thread, parsed into company, roles, location, remote or onsite, salary text, visa sponsorship and tech stack, with a monitoring mode that only returns posts new since your last run. - **URL**: https://apify.com/accountable_eel/hn-who-is-hiring-parser.md - **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community) - **Categories:** Jobs, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 hiring post parseds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. 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 ## 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](https://apify.com/accountable_eel/hackernews-mentions-monitor). To read one company's own job board use [ATS Jobs Unified Lookup](https://apify.com/accountable_eel/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: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~hn-who-is-hiring-parser/run-sync-get-dataset-items?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 ```json { "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 | | | | \ | | | | | | | | | \ | | | | | |
| | | | | | | \ | | 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. ```json { "months": ["latest"], "maxResults": 20 } ``` **Remote posts that mention Python, two months side by side.** ```json { "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. ```json { "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. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~hn-who-is-hiring-parser/run-sync-get-dataset-items?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=`, 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=`, 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. # Actor input Schema ## `months` (type: `array`): 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. You're only charged for the ones we actually find — a miss costs nothing. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Up to 1000. Caps how many posts you get (and pay for) in one run. A busy month has about 250 posts. ## `workMode` (type: `string`): Keep only posts whose header says this. A post whose header says nothing about work mode is dropped when you pick anything but Any. ## `minConfidence` (type: `string`): Posts are free text, so the parse has a real error rate on unusual posts. High keeps only posts where the company, a role and a place or work mode were all found. ## `onlyNewSinceLastRun` (type: `boolean`): On: only posts you have not been given before are returned and charged for. Run it on a schedule through the first days of a month, when most posts arrive. Off: every matching post is returned every time. ## `deltaName` (type: `string`): Optional. Name this monitor's memory so you can tell two schedules apart, or keep one memory across an input change. Leave empty to derive one from your months and filters. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each post found gets its own row instead of being grouped under its thread. You're still only charged once per thread, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## Actor input object example ```json { "months": [ "latest" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "maxResults": 100, "workMode": "any", "minConfidence": "any", "onlyNewSinceLastRun": false, "deltaName": "", "columns": [ "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" ], "expandRows": true, "maxConcurrency": 1 } ``` # Actor output Schema ## `results` (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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "months": [ "latest" ], "includeKeywords": [], "excludeKeywords": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/hn-who-is-hiring-parser").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "months": ["latest"], "includeKeywords": [], "excludeKeywords": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/hn-who-is-hiring-parser").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 '{ "months": [ "latest" ], "includeKeywords": [], "excludeKeywords": [] }' | apify call accountable_eel/hn-who-is-hiring-parser --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/hn-who-is-hiring-parser" } } } ``` 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 ` 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/e5owHgxfwpNIgHP41/builds/pOugJYTQh16fRldcJ/openapi.json