Across 1,825 hiring signals from tracked competitors, exactly zero earned a measurable public reaction. Not a handful. Zero. The same check across 2,187 press moves found 323 that drew a reaction, and across 2,490 shipping moves found 197.
A result that clean is usually a bug, so it is worth being precise about what it means.
Do competitor hiring signals ever get public reaction?
No. In our dataset of 6,569 scored competitor moves from 648 companies, no hiring signal drew a single coupled public reaction. The reason is structural rather than interesting: a job posting has no public artefact that anyone discusses. Nobody posts a rival's careers page to Hacker News. There is no launch thread, no comment section, no repository. The event is real and observable, but the surface where reactions happen never sees it.
So this is not the finding that 'nobody cares about hiring'. It is the finding that hiring is invisible to reception measurement by construction — and that distinction changes how you should use it.
Why does that matter if you track competitors?
Because it tells you which questions each signal can answer. Reception measurement tells you whether a market responded to something. Hiring cannot answer that question and never will, no matter how good the instrument gets.
What hiring answers instead is what a company has decided to do next, months before it ships. That is read structurally — volume, role composition, seniority, which team is suddenly growing — not by reaction. Six backend infrastructure roles and a security engineer is a roadmap disclosure. It just is not one the internet is going to react to.
What does the 0% actually rule out?
It rules out a specific mistake we see in competitive intelligence tooling: treating every detected event as though it belongs on the same ranked list. If your feed sorts hires, ships and press together by recency or by a single significance score, hiring signals occupy space in a ranking whose ordering principle cannot apply to them.
In our own product the consequence is that hiring never enters the reception axis at all. It is scored and surfaced on its own terms, in a separate part of the brief, because folding a permanently-zero-reaction category into a reception ranking would just be quietly wrong.
How was this measured?
6,569 deduplicated moves across 648 tracked companies, each one a diff between two consecutive observations of a public surface — changelogs, blogs, pricing pages, job boards, public repositories. Reactions were gathered from Hacker News, Bluesky, GitHub and news, then bound to a specific dated move by exact-phrase and domain-scoped matching rather than loose company-name search. A move counts as having drawn a reaction at one or more coupled reactions.
The honest limitation: this measures public reaction on the surfaces we read. A market that discusses itself in private communities, sales calls or industry Slack groups is invisible to it, and that affects sectors unevenly. It does not affect this particular result, though — hiring draws zero across every sector we have run, including the loudest ones.
Figures are deduplicated. Our own tracking table held several records for a few companies (Linear had seven), and each record independently re-detected the same changelog entry and re-coupled the same public reactions to its own copy — inflating one company's reaction count by 268% before we caught it. A move is now identified by title, category and date, and reactions are counted by distinct source URL, so the same event and the same reaction each count once.
Revised after a coupling audit. Content matching bound reactions to launches without a causality check, so an old forum thread naming a company could attach to a recent, unrelated release — in the worst case a 2007 Hacker News post counted as reaction to a 2026 changelog entry. 1,099 of 2,885 couplings violated causality (Hacker News worst at 80%, because searching a company name surfaces its whole history) and have been removed; the coupler now rejects them. Every finding above survived the correction and two got stronger — but the landed rates here are lower than first published, and that is the honest direction of the error.