Open req

Counting open reqs is harder than it sounds, because the same requisition is published many times over. A role posted once by the employer can reappear on several job boards and across every aggregator that re-lists them, each copy carrying its own date and a slightly different title. Counted naively, one hiring decision becomes a dozen signals.

So an open req is only a useful unit once it is resolved back to the requisition the employer actually opened — one row per real role, attributed to the company that opened it and dated when they opened it. That resolution is what separates a demand figure you can act on from a row count you can only quote.

Which is why SignalsAPI publishes postings, not open reqs: a row records that a requisition was published on a board, and the date it carried when we read it. Whether it survives to any later day is a separate question, and a public posting does not answer it — so every figure on this site is bounded by when a req was posted, never by what a re-check found. The term names the concept; the pages state the observation.