🔔 Hirist New Tech Jobs Alert Monitor

Watch any Hirist (hirist.tech) tech job search and get alerted the moment a new job is posted. Point this monitor at a job keyword — java, devops, data scientist, react, product manager, anything on Hirist — put it on a schedule, and each run returns only the jobs newly posted since the last run. Quiet runs return nothing, so you can watch a search every few minutes, all day, and only ever see fresh openings.

Built for automation: drop it into Apify Schedules, n8n, Make or Zapier and turn every new tech job into an email, a Slack message, a Google Sheet row or a webhook.

Why a monitor instead of a scraper?

A scraper gives you everything every time — and you then have to figure out what's new. This monitor remembers what it saw last time and hands you a clean feed of just the new jobs:

• 🆕 New jobs — the moment a posting matching your search goes live.
• 🗑️ Removed jobs — optional. Jobs that were present before but have now been filled, withdrawn or expired.

Perfect for tech job seekers who want to apply first, IT recruiters tracking a market, job boards aggregating fresh roles, and anyone building automated job alerts for India's technology hiring.

How it works

1. Give it a search — one or more keywords like java, devops or data scientist. You can also paste a Hirist search URL from your browser.
2. Put it on a schedule (e.g. every 30 minutes) in Apify or your automation tool.
3. First run quietly records the current jobs as a baseline and returns nothing — so a fresh schedule doesn't dump the whole board at you. (Prefer the full list up front? Turn on Emit all jobs on the first run.)
4. Every run after that returns only the jobs posted since the previous run.

Each monitor keeps its own separate memory, so you can run several different searches side by side without them interfering — just give each one a Monitor name.

What you get

One row per newly-posted job:

Field	Description
changeType	new (newly posted) or removed (no longer in results).
jobId	Hirist job ID.
title	Job title (e.g. "Senior Java Developer").
designation	Role designation.
company	Hiring company name.
location	Job location (e.g. "Bengaluru").
experience	Required experience (e.g. "5-8 yrs").
salary	Salary when disclosed.
skills	Key skills for the role.
postedDate	When the job was posted.
url	Link to the job on Hirist.
firstSeenAt	When this monitor first saw the job.
lastSeenAt	When the job was last seen (on removals).
detectedAt	When this change was detected.

Example new-job row

{
  "changeType": "new",
  "jobId": 1543210,
  "title": "Senior Java Developer",
  "company": "Acme Technologies",
  "location": "Bengaluru",
  "experience": "5-8 yrs",
  "skills": ["Java", "Spring Boot", "Microservices"],
  "postedDate": "2026-09-05T09:12:00.000Z",
  "url": "https://www.hirist.tech/j/senior-java-developer-1543210",
  "firstSeenAt": "2026-09-05T12:34:56.000Z",
  "detectedAt": "2026-09-05T12:34:56.000Z"
}

How to use it

1. Add Hirist New Tech Jobs Alert Monitor to your Apify account and open its input.
2. Enter one or more Job keywords (e.g. java, devops, data scientist).
3. Optionally set a Monitor name so this search keeps its own memory.
4. Save it, then create a Schedule (e.g. every 30 minutes) — or trigger it from n8n, Make or Zapier.
5. Connect the output to email, Slack, a spreadsheet or a webhook and let the new-job alerts come to you.

Input

{
  "queries": ["java", "devops"],
  "maxItems": 200,
  "monitorName": "backend-jobs-watch",
  "emitBaselineOnFirstRun": false,
  "detectRemoved": false
}

Field	Description
queries	One or more tech job keywords to watch. Each is monitored as its own search.
maxItems	How many jobs from the top of each search to check each run. 0 = no limit.
monitorName	Optional label so this search keeps its own separate memory.
emitBaselineOnFirstRun	Output every current job as new on the first run instead of seeding silently.
detectRemoved	Also report removed jobs (default off).

FAQ

How often should I run it? As often as you like — every 15 or 30 minutes works well. Runs with no new jobs return nothing, so frequent checks stay cheap.

Will the first run flood me with results? No. By default the first run silently records a baseline and returns nothing; you only start getting rows from the second run onward. Turn on Emit all jobs on the first run if you'd rather get the full list up front.

Can I watch several searches at once? Yes. Give each one a different Monitor name and each keeps its own independent memory of what it has seen.

What export and integration options are there? JSON, CSV, Excel and XML, plus the Apify API, webhooks and native integrations with n8n, Make, Zapier and more.