Hacker News Who is Hiring Scraper - Jobs, Salary & Remote

Turn the monthly "Ask HN: Who is hiring?" thread into a clean, structured job dataset you can filter, sort and pipe into a spreadsheet, ATS, job board or AI pipeline.

Every month Hacker News' hiring thread carries 300-500 high-signal job posts from real engineering teams — buried in free-text comments with no structure at all. This Actor finds the right thread automatically and parses every listing into proper fields.

No login. No proxies. No HTML scraping. Built on the official Hacker News API, so it doesn't break when a website changes its markup.

Why not just use the Hacker News API?

The official API hands you each post as a raw HTML comment blob. All the work is left to you. This Actor does that work:

	Official HN API	This Actor
Finds the monthly thread	You hardcode the ID	Automatic
Company / role / location	Raw text blob	Separate fields
Salary	Buried in prose	Detected + normalised
Remote vs onsite	Buried in prose	remote / onsite / hybrid
Tech stack	Buried in prose	Tagged array
Non-job comments	Mixed in	Filtered out
Filtering	None	Remote-only, keyword, tech

Example output

Real rows from a live run:

company	role	location	remote	jobType	techTags
Proxima Fusion	Senior Software Engineer (Dev Platform)	Munich, Germany	onsite	Full-time	ai, python
CodeWeavers	macOS low-level Open Source Developer	St Paul, MN, USA	remote	Full Time	—
Launchpad Technologies	Multiple Roles	LATAM/Remote	remote	Full-time	react, node
Coder	Multiple roles	Multiple locations	remote	Full-time	ai, security
Friendly Captcha	Developer Relations	Munich area, Germany	unspecified	Full-time	—

{
  "company": "Proxima Fusion",
  "role": "Senior Software Engineer (Dev Platform)",
  "location": "Munich, Germany",
  "jobType": "Full-time",
  "remote": "onsite",
  "salary": null,
  "techTags": ["ai", "python"],
  "url": "https://jobs.ashbyhq.com/proxima-fusion/5aebfef0-0c2c-4c87-990d-bbbbd53b94d2",
  "hnUrl": "https://news.ycombinator.com/item?id=49165394",
  "author": "l1am0",
  "postedAt": 1785828570,
  "text": "Proxima Fusion | Senior Software Engineer (Dev Platform) | Munich, Germany | ONSITE | Full-time ..."
}

Output fields

Field	Type	Description
company	string	Company / organisation name
role	string	Job title, semantically identified (not positional)
location	string	Location string as posted
jobType	string	Full-time, Part-time, Contract, Internship…
remote	string	remote, onsite, hybrid or unspecified
salary	string	Detected salary or range, e.g. $200-225K
techTags	array	Detected technologies (rust, python, react, aws…)
url	string	Company / application link
hnUrl	string	Direct link to the original HN comment
author	string	HN username who posted it
postedAt	integer	Unix timestamp
text	string	Full plain-text of the listing

Field coverage

Measured on a real August 2026 run (111 listings):

Field	Filled
location	96%
url	91%
role	85%
techTags	86%
jobType	66%

Coverage is below 100% because some posters simply omit the field. Non-job comments (candidate self-posts, replies) are filtered out, so you are never charged for a non-listing.

How to use it

1. Click Try for free
2. Leave the input empty to get the latest month, or set filters
3. Click Start
4. Export to CSV, JSON, Excel, XML or pull via API / webhook

Runs with an empty input {} — no configuration required.

Input

{
  "month": "latest",
  "remoteOnly": true,
  "keywords": ["rust", "python"],
  "maxResults": 500
}

Field	Type	Default	Description
month	string	latest	latest or a specific month like July 2026
threadId	string	–	Override: parse a specific HN thread item ID
remoteOnly	boolean	false	Only return remote / hybrid listings
keywords	array	[]	Only return listings matching ANY keyword
maxResults	integer	500	Max listings to return (1-1000)

Example: remote Rust and Go jobs only

{ "remoteOnly": true, "keywords": ["rust", "golang"] }

Example: a specific past month

{ "month": "June 2026", "maxResults": 1000 }

Use cases

• Job boards — fill a niche board from HN's highest-signal hiring source
• Recruiters — filter remote + stack in seconds instead of scrolling 400 comments
• Job seekers — a filterable spreadsheet of every listing matching your stack
• Market research — track hiring trends, salary bands and in-demand tech month over month
• Lead generation — companies hiring engineers are companies with budget
• AI / RAG datasets — real, well-formed job postings

Integrations

Works with everything Apify supports: Zapier, Make, n8n, Slack, Google Sheets, Airbyte, LangChain, plus REST API and webhooks. Schedule it monthly to catch each new thread automatically.

Pricing

Pay Per Event: $0.01 per structured job listing returned.

You pay only for listings actually returned after your filters. Filtered-out comments and non-job posts cost nothing. A typical full month is 300-500 listings ($3-5); a filtered remote-Rust query is usually under $0.50.

FAQ

Do I need a Hacker News account or API key? No. The data is public and read through the official API.

Is this legal? It reads publicly available data from Hacker News' official public API — no login, no paywall, no personal data beyond the public HN username the poster chose to post under.

How fresh is the data? The thread is posted on the 1st of each month and fills up over the following days. month: "latest" always resolves to the newest thread. Schedule monthly for continuous coverage.

Why is role or salary empty on some rows? Because the poster didn't include it. The thread is free text and follows a loose convention. Fields are identified semantically, so a missing field means it genuinely wasn't posted rather than a parsing failure.

Can I get past months? Yes — set month to e.g. "May 2026", or pass a specific threadId.

Will it break? It uses the official Hacker News API rather than HTML scraping, so it's immune to site redesigns. Requests retry with exponential backoff.

Historical selection and coverage limits

• Omit month or use the literal "latest" to select the newest matching thread indexed by Algolia (not necessarily the current calendar month).
• Historical input must use a full English month and four-digit year, exactly like "January 2020". Abbreviations, lowercase month names, surrounding whitespace, empty strings and null are rejected; they are not corrected.
• Historical discovery searches the requested month in titles and paginates the matching search results. The exact thread type and month/year in the title are checked again against HN Firebase before comments are parsed. An unavailable month raises a clear error, never a fallback to latest. Algolia indexing gaps and API errors can prevent resolution of a real thread.
• threadId remains an explicit override and takes precedence over month (and thread type where applicable). It bypasses automatic month selection; verify the ID you supply. Each output row includes threadId, threadTitle and threadMonth (resolved from the source title, or null for a custom title without a recognised monthly suffix).
• These are heuristic parsers of top-level comments, not a complete archive. Deleted/dead comments are omitted. Failed comment reads are logged and skipped, so a successful run can still contain fewer profiles/listings than the thread. Check warnings before treating a backfill as complete. Filters, result limits, posting activity and parsing rules also reduce coverage.

Local regression checks (no Apify runs)

From this actor directory, with httpx and apify installed:

python -B -m unittest -v test_main.HistoryTests
HN_LIVE_TESTS=1 python -B -m unittest -v test_main.LiveTests

The first command uses mock HTTP responses and an Actor stub, including failure and no-delivery assertions. The opt-in second command only reads public Algolia and HN Firebase to verify January 2020 thread resolution; it does not publish rows or verify Cloud billing.

Troubleshooting

Problem	Fix
Empty dataset	Your filters may be too narrow — try keywords: [] and remoteOnly: false
Fewer results than expected	Check comment-read warnings, filters and limits; early in the month the thread is still filling up
Month not found	Use the exact format "July 2026", or pass threadId directly
Need more than 1000	Run per month and combine datasets

Notes

• Source: official Hacker News Firebase API + Algolia HN Search for thread discovery. No HTML scraping, no proxies.
• Parsing follows the community Company | Role | Location | REMOTE | Salary | URL convention and degrades gracefully when a post doesn't. Fields are classified by content, not by position, so a missing role doesn't shift the location into the wrong column.