Hirewatch reads employer career pages directly and returns the open roles as JSON. Poll your 60 named accounts every hour, diff the runs, and you see what opened and what quietly disappeared, before the job boards and three other agencies get there.
The job board shows a role days after the career page does. By the time your alert fires, the hiring manager has a shortlist of suppliers and you are not on it.
Open the bookmark folder. Forty career pages. Scroll, filter by location, compare against yesterday from memory. An hour gone before a single call, and one check a day is all anyone can stand.
Nobody emails you when a role is filled or frozen. It just leaves the page. Your recruiters keep working candidates for a week before someone notices the link is dead.
Reposts, promoted roles and lookalike employers, with a limit on how many alerts you can run.
Millions of postings in a bucket, sold by volume. You care about 60 named accounts.
One endpoint per employer career page. You call it when you want, you get the roles listed right then.
This is the honest inventory, not a logo wall. If your target accounts are not here yet, that is the normal case: send the list and we build their career pages as endpoints.
New employer career pages are built on request. Send the 20, 60 or 200 accounts your desk actually sells into and each one becomes a hosted endpoint with a stable ID. That is the product. The list above is where we started.
Pick an endpoint. Each career page is a hosted function with its own ID. Pass filters such as department or location as variables where the page supports them.
Call it on your schedule. We open the career page in a real browser on our side at call time and read the roles it lists. No scrapers, proxies or headless browsers for you to run.
Diff against your last run. New IDs are roles that opened. Missing IDs are roles that left the page. It is a set difference, shown in the python tab.
Route the signal. Post to the BD channel, create a CRM task, or score the account for your sales team. That part stays in your stack.
Pick employers from today's coverage, choose how often you would poll, and see what a Monday digest could look like, how many runs it takes and how much tab-refreshing it replaces.
Digest counts and sparklines are generated in your browser to show the format, they are not real hiring data. Runs = accounts x polls a day x 30. Hours = accounts x minutes x 22 working days. The digest itself is something you build from the diff; Hirewatch returns the roles.
"We sell into about fifty data and AI employers. I used to hear about a new req from LinkedIn like everyone else. Now the BD channel pings when the career page changes and I am on the phone the same morning."
"The closed-role diff was the surprise. We stopped sourcing against two frozen reqs in the first week. That alone paid for my researcher's time back."
"I did not want a hiring-data lake. I wanted to know when one of 80 target accounts opens a third RevOps role. It is a cron job and a set difference."
No. Hirewatch is a request API. Each call opens the career page at that moment and returns the roles it lists. Opened and closed detection comes from you calling on a schedule and comparing the result with your previous run. Poll hourly and you learn about a new role within the hour. Poll daily and it is within the day. There is no push stream and the feed at the top of this page is a simulation.
You know it left the page. When a role ID is in your last run and missing from this one, the employer is no longer listing it. The page does not say whether it was filled, paused or pulled, so treat it as a prompt to ask your contact, not as a fact about the outcome.
That is expected. Coverage today is about 65 endpoints, 27 of them direct employer career pages. New career pages are built on request: send your account list and each employer becomes its own endpoint. Employers on Lever or Workday are usually the quickest, since those hosts are already covered.
No. This is public job posting data only: titles, teams, locations, links and the text of the posting. No candidate profiles, no applicant data, no contact enrichment.
Because the career page is where a role appears first and disappears first. Boards and aggregators copy it later, with reposts and duplicates mixed in. The job-board endpoints here are for cross-checking and wider sweeps, not the primary signal.
The endpoint is repaired on our side and keeps the same function ID, so your scheduled job does not change. Field names inside the response can differ between employers, so check the response for each endpoint you adopt.
Hirewatch runs on Notte's browser infrastructure. Each endpoint is a hosted Notte function that drives a real browser, which is why it works on career pages that render their listings with JavaScript.
Send the accounts your desk sells into. We turn their career pages into endpoints you can poll every hour.