iimjobs Scraper — Jobs with Full JD, Salary & Recruiter Data

Search iimjobs.com — India's leading management and executive jobs board — and get one clean JSON row per job: title, company, the complete job description, salary and experience ranges, skills, locations, apply counts, and recruiter details.

Pure HTTP against iimjobs' own job API. No browser, no login, no cookie, 512 MB of memory — runs are fast and cheap, and the output goes far beyond the listing card.

What you get per job

Field	Description
title, designation, companyName, confidential	The role and who's hiring (confidential postings flagged)
descriptionHtml, descriptionText	The full job description, as HTML and as clean plain text
experienceMinYears, experienceMaxYears	Required experience range
salaryMin, salaryMax, salaryHidden	Salary as listed (INR lakh per annum); salaryHidden: true when the poster hides it
locations, workFromHome, address	Cities, remote flag, and street address where given
skills, mandatorySkills	Skill tags, with the must-haves split out
applyCount, views	Demand signals: how many applied, how many viewed
postedAt	ISO posting date
recruiterName, recruiterId	Who posted it
jobUrl, jobId, companyLogo, premium	Canonical URL and extras
searchTerm, page	Which input produced the row

Rows are deduplicated across pages and terms by jobId.

Example input

{
    "searchQueries": ["product manager", "data science"],
    "location": "bangalore",
    "maxPages": 2,
    "maxItems": 100
}

The location string is resolved through iimjobs' own location mapper — when a city can't be resolved, the search runs country-wide with a warning instead of failing.

Why the full job description matters

Most job scrapers stop at the listing card: title, company, a location string. That's not enough to match candidates, run skills analytics, or feed an LLM. This actor fetches every job's detail record, so each row carries the complete JD text plus the fields only the detail page has (address, company logo). If you only need the cards, switch fetchDetails off for faster listing-only runs.

Use cases

Recruiting intelligence is the obvious one: track which companies hire for which roles at which experience bands, with real apply-count demand signals. Salary benchmarking works on the subset of postings that disclose pay. The skills/mandatorySkills split feeds skills-gap analyses, and the full JD text is ready for embedding pipelines and match models. iimjobs skews senior — management, consulting, finance, product — so the data reads on India's white-collar executive market specifically.

FAQ

Do I need an iimjobs account? No. Search and job details are collected without any login.

Why is salary null on many rows? Most iimjobs postings hide compensation; salaryHidden: true tells you it was withheld rather than missing. Where disclosed, values are as listed — INR lakh per annum.

How many jobs can one term return? Searches report totalJobs in the log (often thousands); pages carry ~50 jobs each, up to 100 pages per term.

Do I need a proxy? Usually no — the default direct connection works. If runs start failing with blocks, switch the proxy input to Apify Proxy.

Explore more scrapers

• Naukri Scraper — India's biggest general jobs board
• Instahyre Jobs Scraper — India tech hiring
• LinkedIn Jobs Scraper — global postings from $0.25/1k

🤖 For AI Agents & LLM Apps

Compact reference for AI agents calling this actor via the Apify MCP server or the Apify API (actor: memo23/iimjobs-scraper).

Purpose: Keyword-searches iimjobs.com (India management/executive jobs) and returns one JSON row per job including the complete job description text.

Minimal input:

{
  "searchQueries": ["product manager"],
  "location": "bangalore",
  "maxPages": 1,
  "maxItems": 25
}

Output: one dataset row per job; key fields: jobId, title, designation, companyName, confidential, descriptionHtml, descriptionText, experienceMinYears, experienceMaxYears, salaryMin, salaryMax, salaryHidden, locations, workFromHome, skills, mandatorySkills, applyCount, views, postedAt, recruiterName, jobUrl.

Behaviors an agent should know:

• Always set maxItems (and/or maxPages, ~50 jobs per page) to cap output; each term in searchQueries runs its own search.
• location accepts a plain city name ("bangalore", "mumbai"); unresolvable cities degrade to a country-wide search with a logged warning, never a failure.
• fetchDetails: false skips the per-job detail call for faster listing-only rows (no descriptionHtml/descriptionText/address).
• Salary fields are null with salaryHidden: true when the poster withholds pay — branch on the flag, not the nulls.
• No login or proxy required by default. Billing: pay-per-event — see the Pricing tab on the actor page.

⚠️ Disclaimer

This actor collects publicly displayed job-listing data from iimjobs.com for legitimate recruiting research, market analysis, and job aggregation. You are responsible for complying with applicable laws and iimjobs' terms. Do not use collected data for spam.

SEO Keywords

iimjobs scraper, iimjobs api, scrape iimjobs, india management jobs data, india executive jobs scraper, iimjobs job description scraper, india jobs api, iimjobs salary data, india recruitment data, management jobs india json, iimjobs export csv, india hiring trends data