NewSearch millions of jobs from your AI agent with MCP
New in JobsPipe

Get told the moment a company starts hiring.

Save the search that describes the companies you care about. We watch millions of live postings and tell you when a new one matches.

Start watching your ICP

Three Signals free. Evaluating them costs no credits.

Signals
3 signals
  • Data teams scaling, USWatchingNew companies

    hiring analytics engineer or data engineer, 200+ employees, in US

    alerts@acme.ioLast checked 12 minutes ago
  • Backend hiring, GermanyWatchingNew companies

    hiring backend engineer, 50-500 employees, in DE

    #gtm-signalsLast checked 12 minutes ago
  • Account executives, SEAWatchingNew jobs

    hiring account executive, in SG

    webhook / crm-syncLast checked 12 minutes ago
Sources

Watching 10 sources

Steps

How it works

Three steps, then it runs without you.

01

Save a search

Build the search once in the dashboard - the roles, the skills, the company size, the industry, the country - and save it as a Signal. If you already run the search by hand, you already have the hard part.

02

We watch it

Every few minutes we re-run your search against postings that entered the corpus since the last time we checked. A posting counts as new the first time we ever see it, so a company reposting an old role does not fire the same alert twice.

03

You get told

Matches arrive as an email, a Slack message, or a signed webhook into your own system. Instant, or batched into one daily digest if you would rather read them together.

Numbers

What it runs on

Millions

of active postings

30+

boards and ATS platforms

5 min

between checks

Use cases

Two ways teams use it

These are real postings that matched each of these Signals.

Senior Analytics Engineer

Super.comUnited States1,145 employees
Sales and GTM

The account just started building the team that buys your product.

Content intent tells you somebody at a company read something. A job posting tells you the company committed budget to a problem and said so in public. If you sell data infrastructure, a company opening two analytics engineering roles has told you more than any bidstream ever will.

Watch: companies over 200 people, hiring analytics engineer or data platform roles, in the US or UK. Fires when a new account enters that set.

Backend Software Engineer (m/f/x)

go-e GmbHBerlin97 employees
Recruiting

The companies that just started hiring in your specialty.

The best time to reach a hiring manager is the week the role opens, before they have committed to an agency or filled the top of the funnel. Watching a specialty across every board means you hear about the opening rather than finding it on a Friday sweep.

Watch: companies of 50-500 people, hiring backend engineers, in Germany. Fires once per company, not once per posting.

Delivery

Where it lands

Email

The matched jobs with company, title, location and a link to the posting. Instant or a daily digest.

Slack

Posted into the channel you choose through an incoming webhook, so the whole team sees the account move.

Webhook

An HMAC-signed alert.matched payload into your CRM, your scoring model, or an agent that acts on it.

Filters

What you can watch for

Signals run on the same corpus the search API serves, normalized into one schema. A Signal can narrow on any of these.

  • Role - Job title, occupation code, or the skills named in the posting.
  • Company size - Minimum and maximum employee count.
  • Industry - ISIC division, so you can scope to a sector rather than guessing from names.
  • Geography - Country, with location resolved from the posting rather than the board's label.
  • Source - Narrow to the boards and ATS platforms you care about - name the ones you want and the rest are left out.

What it cannot narrow on, at least today: funding stage, revenue, and whether a company sells to businesses or consumers. Those are not in the dataset, and a filter that silently matches nothing is worse than one that does not exist.

Prefer to own the loop yourself? The same filters are plain queries in the hiring signals API.

FAQs

Frequently Asked Questions

What counts as a new match?

The first time a posting enters the JobsPipe corpus. We stamp that moment when the posting is first collected and never move it, so a repost, a re-crawl or a backfill does not re-fire an alert you have already seen. In company mode a company fires once for the lifetime of the Signal, however many roles it goes on to post.

How quickly does a Signal fire after a job is posted?

Postings reach the corpus a median of about 80 minutes after we first see them on the source, and the alert evaluator deliberately waits behind that so a slow source cannot cause a match to be missed entirely. In practice a Signal fires within a few hours of the posting appearing, not within seconds. If you need the raw feed with no waiting, poll the search API directly.

Do Signals use my job credits?

No. Evaluating a Signal does not draw down your monthly jobs, and neither does previewing one before you save it. You are billed for the searches you run against the API, not for the ones we run on your behalf.

Can I filter by funding stage, revenue, or whether a company is B2B?

Not today. Signals filter on what the dataset actually holds: role, skills, employee count, industry, geography and source. Funding stage and revenue are not in the data, and we would rather say so than let you build an ICP on a field that is quietly empty.

How many Signals can I run?

Three on the free plan, ten on Builder and fifty on Scale. Email works on every plan; Slack and webhook destinations are on the paid plans.

See what your ICP looks like as a live feed.