datagrit › Jobs & salaries › Hacker News Who Is Hiring: Jobs & Hiring History

Hacker News Who Is Hiring: Jobs & Hiring History

Turn Hacker News Who is hiring threads into job rows with salary, stack, work mode and visa, plus how many months each company has been hiring.

Hacker News Who Is Hiring: Jobs & Hiring History turns the monthly "Ask HN: Who is hiring?" thread into a clean table of job posts. Every top-level comment becomes one row with the company, roles, location, work mode, employment type, stated pay, visa sponsorship, technologies, apply link and the full post text. What other scrapers of this thread do not give you is company history: the Actor compares every company with the earlier monthly threads and tells you how many months it has been hiring, when it first and last posted before, and whether it is posting for the first time. It reads the public Hacker News search API, needs no login or API key, and exports to JSON, CSV or Excel.

Who is it for?

• Job seekers and recruiters who want the current thread filtered by technology, location, remote work, salary or visa sponsorship instead of scrolling 400 comments.
• Sales and lead generation teams selling to startups: companies posting for the first time are young teams that just got funded or started hiring, and companies that post every month are in steady growth.
• Market analysts and investors tracking which technologies and salary levels appear in startup hiring over many months.
• Developers and data teams who need a scheduled feed that delivers only the posts they have not seen yet.

How to use it

1. Choose which thread to read: the latest one, the last few months, or one specific month such as 2026-03.
2. Set how many earlier months each company is compared against. Twelve months is the default. Zero switches history off and makes the run faster.
3. Add filters if you want a narrower list (below), set the maximum number of posts and run the Actor.

Filters

• Post text contains, Role contains, Location contains: keep posts matching any of your words. Role and location are searched in the post header, where companies list them.
• Technologies: keep posts naming at least one of the listed technologies, such as python, rust or kubernetes.
• Work mode and Employment type: remote, hybrid or onsite; full-time, part-time, contract or internship.
• Only posts with a salary and Minimum yearly salary with a currency: pay is converted to a yearly figure, so hourly and monthly rates compare with annual ones.
• Only with visa sponsorship: posts that offer visa or work-permit sponsorship. Posts that refuse it are never returned by this filter.
• Only first-time companies and Minimum months hiring: use the history to find new teams or companies that hire all the time.
• Only posts not delivered before: skip every post an earlier run with the same filters already returned, so a scheduled run delivers each new post once.

Company history

For each post the Actor normalises the company name (lower case, letters and digits only, legal suffixes removed) and, when the post links the company's own website, also keeps the domain (acme.com for Acme, factory.ai for Factory AI). It then looks for the name or the domain in the earlier threads, so a company that links its site in one month and not in the next is still one company. A link to a news article, a LinkedIn short link or a file host inside the post text is never taken for the company's domain. The companyKey column is the normalised name alone (acme, factoryai), so it does not change with the link; two spellings of one company (Factory and Factory AI) give two keys, and the history columns still treat them as one when the website domain is the same. You get monthsHiring (this month included), firstSeenMonth, previousSeenMonth, consecutiveMonths, isNewCompany and postsThisMonth. Posts where no company could be read from the header, or only a placeholder such as Stealth, Confidential or Startup, have no key and carry null history, monthsChecked included, rather than a guess. A header that starts with a place (Boston, MA - Full Time, NYC | Engineer; a name with a place after a comma, such as adapptiv Labs, Switzerland or LiquidFi (Miami, FL), stays a company), a role (Software Engineer | Acme) or an employment phrase gives no company either, and those rows are delivered free of charge, as are rows with a placeholder name. Older threads (before about 2016) were written free-form, so many of their posts have no readable company.

History is only computed from threads whose posts can be read reliably: every thread of the window, and the thread you ask for, must have a standard Company | role | location header in at least 75% of its posts. Before 2016 that is not the case (see "Good to know"), so a run that asks for history on such a month, or on a month whose window reaches one, stops with a message instead of returning rows with empty history. Set Months of history to 0 to read those months as plain posts: you then get the posts without history fields, and rows without a company name are free.

Pricing

You pay per job post returned. Posts removed by your filters, posts skipped as already delivered, posts without a usable company name, placeholders such as Stealth included (the run status counts them) and a run that finds nothing are not charged: a search without matches returns a single status row with found: false that is free. Reading earlier threads for the history costs nothing extra. Set a maximum charge per run in the Apify console to cap spending; the Actor stops cleanly when it is reached.

Good to know

• Posts are free text written by people, so parsing is heuristic. The status message at the end of every run reports how many posts had a readable header, how many stated a salary and how many months of the history window were read. It names the threads the posts came from; when Maximum posts is reached before the later threads of a multi-month request, it lists those threads as not read, so a missing month is never mistaken for a month without matches. About three in ten recent posts state pay.
• The share of posts with a standard header depends on the year of the thread, because the Company | role | location format only settled around 2016. Measured on every thread in October 2026: 2011 and 2012 between 2% and 27%, 2013 between 10% and 35%, 2014 between 22% and 41%, 2015 from 35% in January to 77% in December, 2016 between 79% and 92%, 2017 to 2026 between 89% and 96%. With history switched off, posts without a company name are returned but free. With history on, a thread below 75% stops the run (see Company history); with the default 12 months of history that means asking for a month before December 2016 needs Months of history set to 0.
• If Hacker News changes the thread format so that no header can be read in a recent thread, the run fails instead of returning rows with empty fields.
• Company history is only returned when every month of the window is accounted for. The run status says, for example, History window 12 months (12 read). The Actor lists threads from the official whoishiring accounts and then looks up by title every month that list does not contain, or contains only as a thread with fewer than 20 comments, and keeps the thread with the most comments, so threads posted from another account (July 2011) and stub threads next to the real one (December 2011) are read correctly. A month is reported as with no Hacker News thread only when that title search finds nothing; such a month is skipped without breaking consecutiveMonths. If a month cannot be confirmed, the run fails instead of marking companies as new by mistake, and running it again fixes it.
• The newest thread is skipped while it has fewer than 10 comments, which happens in the first hours of a month. Ask for a specific month to read it anyway.
• Only public posts are read. No account, cookies or private data are involved.

Output fields

Every result is one flat record, so it drops straight into a spreadsheet, a database or a CRM.

Sample record

{
  "found": false,
  "month": "2026-09",
  "postId": "49522903",
  "sourceUrl": "https://news.ycombinator.com/item?id=49522903",
  "threadId": "49522897",
  "threadMonth": "2026-09",
  "postedAt": "2026-09-01T15:01:54.000Z",
  "author": "jobposter",
  "company": "Modash.io",
  "companyWebsite": "https://modash.io",
  "companyKey": "modashio",
  "headerLine": "Modash.io | Senior Product Engineer | Remote (Europe) | Full-time | €75k–110k",
  "headerParsed": true,
  "roles": [
    "Senior Product Engineer"
  ],
  "location": "Remote (Europe)",
  "workModes": [
    "remote"
  ],
  "employmentTypes": [
    "full-time"
  ],
  "salaryText": "€75k–110k",
  "salaryMin": 75000,
  "salaryMax": 110000,
  "salaryCurrency": "EUR",
  "salaryPeriod": "year",
  "salaryYearlyMin": 75000,
  "salaryYearlyMax": 110000,
  "visaSponsorship": true,
  "technologies": [
    "TypeScript",
    "PostgreSQL"
  ],
  "applyUrl": "https://jobs.ashbyhq.com/modash/123",
  "links": [
    "https://modash.io",
    "https://jobs.ashbyhq.com/modash/123"
  ],
  "emails": [
    "jobs@modash.io"
  ],
  "descriptionText": "Modash.io | Senior Product Engineer | Remote (Europe) | Full-time\n\nModash helps brands find and manage creators.",
  "monthsChecked": 13,
  "monthsHiring": 7,
  "firstSeenMonth": "2026-01",
  "previousSeenMonth": "2026-08",
  "consecutiveMonths": 3,
  "isNewCompany": false,
  "postsThisMonth": 1,
  "scrapedAt": "2026-10-01T06:00:00.000Z"
}

Input

Call it from your code

Run the Actor and get the results in one request. Replace YOUR_APIFY_TOKEN with the token from your Apify account settings.

curl -X POST "https://api.apify.com/v2/acts/datagrit~hacker-news-hiring-history/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"monthsBack":1,"historyMonths":12,"technologies":["python"],"maxItems":100}'

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('datagrit/hacker-news-hiring-history').call({
  "monthsBack": 1,
  "historyMonths": 12,
  "technologies": [
    "python"
  ],
  "maxItems": 100
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]);

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("datagrit/hacker-news-hiring-history").call(run_input={
  "monthsBack": 1,
  "historyMonths": 12,
  "technologies": [
    "python"
  ],
  "maxItems": 100
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(len(items), items[0] if items else None)

Frequently asked questions

Related Actors