Req-level buying signal
anchor conceptA req-level buying signal is a single open job requisition read as an intent signal: one company, at one moment, committing budget and headcount to a specific role. It is the atomic unit of hiring demand — evidence that a team is being built, a tool is being adopted, or a function is being scaled, before any of that reaches a funding round or a press release.
Most buying-intent data is inferred: a spike in anonymous web traffic, a keyword bid, a firmographic model's guess about who might be in market. A req-level buying signal is the opposite. It is grounded in an action a company has already taken and published — it opened a requisition — so there is nothing to infer about whether the intent is real. The role names the need, the location names the where, and the posting date names the when.
Reading demand at the level of the individual req, rather than the company, is what makes the signal specific enough to act on. "Acme is growing" is a headline; "Acme opened three platform-engineering reqs in Berlin this week" is a reason to reach out today, with the exact hook to open with. The req is the smallest unit that still carries who, what, where and when together.
Every other term in this glossary is a way of working with req-level buying signals at scale: sourcing them from ground truth, packaging them as hiring-intent data, pointing them at a set of competitors, or delivering them through an API.
See hiring-demand data for yourself
Query open requisitions by company, role and location — piped straight into your CRM or warehouse.
Get your free API key →Related terms
- → Hiring-intent data
- → Ground-truth reqs
- → Competitive hiring intelligence
- → Hiring-demand API
- → Watch fire
- → Hiring-demand MCP
Part of the Reqbeat hiring-signal glossary.