← data exports  /  apify actor

Hirist Jobs Scraper: India Tech Jobs, Salary

how to get the data with our Apify actor hirist-jobs-scraper

Scrape India tech jobs from hirist.tech: title, company, locations, experience in years, salary in lakhs when shown, skills, category, remote flag, posting time, the employer's AmbitionBox rating and profile, and the description. Search by keyword, category, location and experience.

on apify
v0iddo/hirist-jobs-scraper
category
jobs, automation
build
0.1.10, built 2026-11-06
billing
Apify bills it per result; the price for your plan is on the actor's page.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

  • title
  • company
  • location
  • Experience from (experienceMin)
  • Experience to (experienceMax)
  • Salary from (lakhs) (salaryMinLakhs)
  • Salary to (lakhs) (salaryMaxLakhs)
  • skills
  • Employer rating (companyRating)
  • Posted (postedAt)
  • Posting (url)

What people use it for

  • India tech salary benchmarks: salary ranges in lakhs by role, skill, city and years of experience.
  • Hiring signals for B2B sales: which companies hire for which stack in Bangalore, Pune or Hyderabad.
  • Skills demand: count the mandatory skills across postings to see which stacks employers ask for.
  • Job boards and alerts: a daily feed of new India tech postings with experience bands and remote flags.

Run it on Apify

  1. Open hirist-jobs-scraper on Apify and sign in, or make an Apify account.
  2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
  3. Click Start. Rows appear on the Output tab while the run works.
  4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
  5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

  • Search terms (keywords): Job titles, skills or words such as Python, React, DevOps or data engineer. One search per term. Leave empty and pick a category to list a whole category.
  • Category (category): Optional. With search terms it keeps the results of this category; alone it lists the category, for example Machine Learning or Backend Development. Options: Any category, Machine Learning, Data Analytics & BI, Data Engineering, Backend Development, Frontend Development, Full Stack, Mobile Applications, Emerging Technologies, DevOps/SRE, CyberSecurity, Quality Assurance, Platform Engineering/SAP/Oracle, Product Management, Business Analysis and Project Management, UI & Design, Semiconductor/VLSI/EDA, Others. Default: any.
  • Locations (locations): Optional cities or states such as Bangalore, Mumbai, Delhi NCR, Pune, Hyderabad, Chennai or Remote. Common other spellings work (Bengaluru, Gurugram, Kochi).
  • Experience from (years) (experienceMin): Optional. Postings whose experience band overlaps the range you give.
  • Experience up to (years) (experienceMax): Optional. Upper end of the experience range in years.
  • Posted within (postedWithin): Only postings from the last 3, 7, 15 or 30 days. Options: Any time, 3 days, 7 days, 15 days, 30 days. Default: any.
  • Only postings that show salary (salaryOnly): Keep only postings whose employer shows the salary range. Most do not. Default: false.
  • Only remote or work from home (remoteOnly): Keep only postings marked work from home or located in Remote. Default: false.
  • Include the job description (includeDetails): Read each posting once more for its description text. Switch it off for a faster run with every other field. Default: true.
  • Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 100.
  • Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

example inputjson
{
  "keywords": [
    "python"
  ],
  "locations": [
    "Bangalore"
  ],
  "includeDetails": true,
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

needs your own Apify tokenpython
# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "keywords": ["python"],
    "locations": ["Bangalore"],
    "includeDetails": True,
    "maxItems": 20,
}
run = client.actor("v0iddo/hirist-jobs-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

  • One search runs per search term; postings are unique by ID across the whole run. Without search terms, a category lists every open posting of that category on hirist.tech.
  • A search shows at most 100 pages of 50 postings. For a broad search, add locations or an experience range.
  • salaryMinLakhs and salaryMaxLakhs are the yearly salary in lakhs of rupees (1 lakh = 100,000 INR), only when the employer shows it; salaryHidden is true otherwise. Most employers hide it.
  • experienceMin and experienceMax are the years of experience the posting asks for. The experience filter keeps postings whose band overlaps your range.
  • companyRating, companyReviews and the other company fields are the employer's public AmbitionBox profile as hirist.tech shows it next to the posting; empty when the employer has none.
  • Recruiter names, applicant and view counts are not collected (the board shows them to signed in users only). E-mail addresses, phone numbers and handles are removed from the description text.
  • Not affiliated with hirist.tech.
  • Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
  • The actor reads only pages that the site's robots.txt leaves open to automated access.
  • Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
  • Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on hirist.tech, cookies or an API key?

No. The actor reads only what every visitor of hirist.tech can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 5,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

every fact here is read from the actor's public data on Apify, every day; it last changed on