Ashby Posted Its Own Job on HN Between Its Customers' Reqs

On August 1, 2026, Ashby posted itself on the Hacker News "Who Is Hiring" thread at $200k to $275k for engineering leaders, remote. On the same page, dozens of jobs.ashbyhq.com URLs point to reqs from Ashby's own customers. The ATS that YC startups use to reject candidates is publicly fishing in the same pond as the companies paying it.

Read the thread once and it looks like normal August recruiting noise. Read it twice and you notice the vendor has quietly repriced its customers' market band, in public, on one of the highest-signal free sourcing surfaces on the web.

What Ashby actually posted, and why the band matters

Ashby's Aug 2026 HN post reads "Ashby | YC 19 | REMOTE | Hiring Engineering Leaders | $200k - $275k" and explicitly tells readers to cmd+f "Ashby" in the thread to see how many other postings it powers. That is not a job ad. That is a market-making move.

The rules of HN's "Who Is Hiring" (item 49156683) are simple: only hiring companies may post, one post per company. Recruiters and candidates alike scrape these threads for comp bands. Meta-boards like hnhiring.com crawl the ATS URLs (Greenhouse, Lever, Ashby) linked from each post. Every band published there becomes a comp point fast.

By stamping $275k top-of-band on a remote engineering leader role, Ashby did three things at once:

• Set a public ceiling any YC-stage customer competing for the same title now has to answer to.
• Advertised remote-first hiring while Meta, Google, and Databricks are dragging engineers back to campus.
• Marked itself as a peer of the FAANG-tier employers where those leaders currently sit.

If you posted $180k for a Director of Engineering in the same thread, your vendor just repriced you.

The ashby ats hiring signal, decoded

The signal is not "Ashby is hiring." The signal is that a 110-person ATS vendor with OpenAI and Shopify as customers is competing head-on with those customers for the same finite pool of engineering leaders, and doing it on the customers' own recruiting surface.

Ashby was founded in 2018 by Benjamin Encz (ex-Director of Engineering at PlanGrid) and Abhik Pramanik (previously built physics engines at Industrial Light & Magic and Dreamworks). It raised a $50M Series D on an AI-powered talent platform pitch. Named customers include Notion, Linear, Shopify, Figma, and OpenAI. The founding thesis was that 50% of employers do not use an ATS, and that the ones who do get failed by tools built for a different decade.

That thesis is fine. The overlap is the interesting part. Notion's head of talent has publicly called Ashby the tool they rely on most. That means Ashby's product logs know exactly which Notion reqs stall, which sources convert, and which candidates its customers are chasing. Ashby the recruiting team does not need that data to run outreach. Ashby the company sits on top of the funnel of every hire its customers make.

The real engineering leader pool Ashby is fishing

The US engineering-leader pool that Ashby's $200-275k band targets is roughly 67,000 people, and the top current employers of those people are the exact firms YC-stage startups already lose bidding wars to. That is the sourcing reality behind the HN post.

Here is the supply picture, pulled from Refolk's index of professional profiles:

67,489

Two things jump out. First, for every VP of Engineering there are roughly 14 Engineering Managers. That ratio is what makes VP searches so brutal, and why the same 2,900 names cycle through every founder's inbox. Second, Directors of Engineering concentrate in the SF Bay Area at a 6:1 margin over the next city in the sample. If you are remote-first hiring against Ashby, the Bay is still where the density lives, and Figma (an Ashby customer), Palo Alto Networks, Workday, Autodesk, and Temporal already employ most of it.

Sourcing engineering managers when your ATS is your competitor

If your ATS vendor is bidding for the same engineering managers you are, you compete on two axes it cannot easily match: speed to identify off-market candidates, and specificity of pitch. Matching cash bands is a losing game against a $50M Series D remote posture.

Top current employers of US Engineering Managers, per Refolk's index:

1. Meta
2. Google
3. Datadog
4. Rippling
5. Databricks

For Directors of Engineering, the concentration shifts:

1. Palo Alto Networks
2. Figma
3. Workday
4. Autodesk
5. Temporal

That second list has a wrinkle. Figma is an Ashby customer. Ashby's own recruiting team can plausibly build a pitch to Figma engineering leaders informed by product-level context Figma pays Ashby to hold. You cannot match that. You can, however, out-source them: get to the same people faster, with a sharper reason to talk.

This is the exact gap Refolk closes. Instead of building ten Boolean strings against a LinkedIn recruiter seat, you describe the person in plain English ("Director of Engineering in the Bay Area, currently at a FAANG-tier company, has shipped a platform team from 5 to 40, previously ran EM at a Series B") and get a ranked shortlist across GitHub, LinkedIn, and the open web.

Why $200-275k REMOTE is a deliberate FAANG counter

The band is not generous. It is targeted. Meta, Google, and Databricks (the top current employers of US Engineering Managers in Refolk's index) pay more cash than $275k for equivalent titles, but they are also the loudest voices demanding return-to-office. Ashby's remote $275k top-of-band is arbitrage against FAANG's declining remote posture, dressed up as a comp disclosure.

The non-cash levers Ashby leans on, per its own careers page: remote-first hiring, a 10-year option exercise window, a $100/month education budget, and a generous equipment budget. For an EM with young kids in Austin or Denver considering FAANG cash versus a $275k remote seat with a longer horizon on equity, that trade clears. Ashby knows it. So do Notion and Linear, both remote-friendly, both fishing the same pond.

The band is not a comp disclosure. It is a targeted trade offered publicly to a slice of the ~42,000 US Engineering Managers who would swap FAANG cash for remote optionality today.

What founders and recruiters should actually do

Treat the Ashby HN post as a live case study, then act on three specific things this week. The window closes as soon as your competitors read the same thread.

1. Re-comp your open leadership reqs against the public band

If you posted an EM or Director role in the same Aug 2026 thread below $200k base, you are now the cheap option in a comparison every candidate makes with cmd+f. Either raise the band, add a public equity floor, or lead with the non-cash levers Ashby is leading with (remote, 10-year exercise, equipment budget). Do not leave the number unaddressed.

2. Scrape the thread for jobs.ashbyhq.com URLs, then source the applicants, not the reqs

Every jobs.ashbyhq.com URL in the Aug 2026 thread (Oscilar, Turquoise Health, Everis, SentiLink, and more) is a funnel of engineering candidates who self-identified as open in August. You will not out-post the vendor. You can out-source the pool that applied to the vendor's customers.

3. Move to plain-English sourcing before your ATS vendor does

Ashby claims a 46% reply-rate lift from AI-powered outreach on its own platform. That number cuts both ways. Ashby's customers get warmer intros. So does Ashby, using the same tooling to hire against them. If your outreach is still Boolean and templated, you are the slow lane.

46%

Refolk is built for this exact problem: you ask in plain English for the Databricks Director with a specific team-scaling history, or the VP of Engineering who has actually shipped multi-region infra, and you get real people back, ranked, across GitHub, LinkedIn, and the open web. When an ATS vendor's hiring behavior turns public and aggressive, the counter is not more Boolean, it is faster and more specific search.

The uncomfortable takeaway for YC founders

If your ATS is on the HN "Who Is Hiring" thread bidding for engineering leaders next to your req, the vendor-customer boundary has collapsed. Plan for that, do not complain about it.

Ashby is not doing anything wrong. It is a company hiring 14 engineers in a market where the total addressable senior pool is ~67K, its cash cannot match Databricks, and its remote posture can. The August 2026 HN thread is the honest version of what every ATS vendor already does quietly. The signal for founders is that the free surfaces where you used to find talent (HN, LinkedIn Jobs, Greenhouse-hosted pages) are now competitive terrain owned by companies that also sell you tools. Sourcing off those surfaces, in plain English, at speed, is no longer optional.

Ashby posted itself between its customers' reqs. Read that again. Then go source the pool your vendor is already in.

FAQ

What was Ashby's exact HN "Who Is Hiring" post in August 2026?

Ashby posted "Ashby | YC 19 | REMOTE | Hiring Engineering Leaders | $200k - $275k" on the August 1, 2026 Hacker News "Who Is Hiring" thread (item 49156683). The post explicitly asks readers to cmd+f "Ashby" to count how many other job listings in the thread run on Ashby's ATS, which is a marketing move as much as a hire.

How large is the US engineering leader pool Ashby's band targets?

Roughly 67,000 people in the US carry Engineering Manager, Director of Engineering, Head of Engineering, or VP of Engineering titles, per Refolk's index: 41,968 EMs, 17,253 Directors, and about 8,268 mixed Head and VP roles. Top current employers include Meta, Google, Datadog, Rippling, and Databricks (for EMs) and Palo Alto Networks, Figma, Workday, Autodesk, and Temporal (for Directors), several of which are Ashby customers.

Why does it matter that Ashby's customers post on the same HN thread?

Because Ashby (the vendor) and Notion, Linear, Shopify, Figma, and OpenAI (Ashby customers) are all competing for the same finite pool of ~67K US engineering leaders on the same public page. The vendor-customer boundary collapses when both sides fish the same pond, and Ashby's product logs give it visibility into hiring signals its customers assumed were private. Treat your ATS as a competitor for talent, not just a workflow tool.

How do you source engineering managers against a $275k remote band?

Stop competing on cash and start competing on speed and specificity. Re-comp your published bands, scrape the thread for jobs.ashbyhq.com URLs to identify open funnels, and move from Boolean searches to plain-English sourcing across GitHub, LinkedIn, and the open web. When an ATS vendor publicly repositions the market, the counter is a shortlist your competitors have not seen yet.