HN Hiring, February 2026: Original Thread and Archive Guide
Historical guide, updated November 2, 2026. This page refers to the February 2026 Hacker News hiring thread. A posting in that thread does not establish that a role is still open today.
Start with the original February thread
The source is Ask HN: Who is hiring? (February 2026). Read the original company comment, its date, any replies and the linked application instructions before contacting an employer.
The thread asks posters to be members of the hiring company, excludes recruiting firms and job boards, and requests location and remote-work restrictions. Those are posting rules, not independent verification of every employer or offer. Readers are asked to contact posters only when personally interested in the job.
How to evaluate an archived listing
Use the thread to find an employer or understand a role, then check the employer's current careers page. Save the original comment link alongside your notes so you can distinguish what the company wrote from your own interpretation.
| Check | What to record | What still needs confirmation |
|---|---|---|
| Role | Job title and advertised responsibilities | Whether the opening still exists |
| Location | Office, remote region and time-zone wording | Your eligibility and the team's current arrangement |
| Employment terms | Full-time, contract or part-time wording | Contract details, benefits and sponsorship |
| Compensation | Any range and currency explicitly stated | Current range and how it applies to your location |
| Application route | The company's linked form or instructions | That the destination belongs to the employer |
If the old application link is unavailable, navigate from the company's own website. Do not assume an archived email address or form remains the preferred channel.
Build a focused shortlist
Pick a few roles that match work you can demonstrate. For each one, write a short note connecting a stated responsibility to a relevant project, including your contribution and a link you are allowed to share. Ask about unclear requirements rather than inventing qualifications or claiming experience you do not have.
For an AI engineering role, useful evidence might include an evaluation you designed, an integration you maintained, or a failure you diagnosed. Describe the actual constraints and measured results of your own work. A list of model names alone gives an employer little evidence of how you build or operate software.
If an application asks about a CCAPI integration, use the CCAPI documentation to describe the endpoint and behavior you implemented accurately. This is a documentation reference, not evidence that any employer in the thread uses CCAPI.
What this thread can tell you about the market
A voluntary monthly discussion can reveal individual openings and the language companies use to describe them. Without a defined sampling method, deduplication and verified outcomes, it cannot support a market-wide hiring-growth rate, a representative salary estimate or a prediction of your chances of being hired.
This revision replaces the earlier general job-market essay and unsupported compensation and growth claims. Use the original February thread as a historical source and verify current openings directly with each employer.