Instahyre & foundit Jobs Scraper — India tech jobs

Two India job boards in one run: Instahyre and foundit (ex Monster India). Title, company, locations, skills and the link from both; salary range, years of experience, employment type and industry from foundit.

No login, no cookies, no proxy.

The ceiling, and how this run gets past it

Instahyre holds 13 419 open jobs (the count moves daily), but plain paging cannot reach them all. Measured by binary search on 18 Sep 2026: offset 9959 works, 9979 fails — so a scraper that only walks offsets stops at about 9 994 jobs and silently leaves a quarter of the board behind.

This run slices by company size instead. Measured live from the Apify cloud:

Bucket	Jobs
1	3 915
2	7 272
3	2 221
Together	13 419 of 13 419

Each bucket is below the ceiling, and together they cover the whole board.

Every bucket is verified before it is used. Instahyre silently ignores a parameter name it does not know and returns the full set: company_sizes=1, size=small, employee_count=small and location=Bangalore all came back with the same 13 419. A scraper that trusted the name would walk the same list three times and bill you three times for it. Here a bucket whose count equals the whole is dropped, and the run says so in its report.

You are not charged for repeats

foundit repeats one pinned job on every page. Measured: of 487 rows the source handed over, 87 were repeats — 18%. They are merged before delivery, so they never reach your dataset and never appear on your bill.

foundit also stops advancing at start=10000 and quietly serves the same page again (checked at 10 000, 20 000 and 99 000 — identical job IDs). This run stops at the measured ceiling instead of paying for circles.

What a row holds

Common to both boards: board, job_id, title, company, locations, skills, url.

Instahyre adds: candidate_title, company_tagline, company_founded, company_size, company_logo, posted_at.

foundit adds: min_salary, max_salary, salary_currency, salary_hidden, min_experience, max_experience, employment_types, industries, functions, designations, is_urgent, is_fresh, posted_ago, created_at, last_updated, job_source, company_id.

Types are the same on both boards on purpose: IDs are strings, skills are a list. Mixing types makes a CSV unusable and made the very first cloud run of this Actor fail outright.

Honest limits

• Salary and years of experience come from foundit only. Instahyre does not publish them at all, so a salary or experience filter with foundit switched off would drop every row — the run says that by name instead of finishing green and empty.
• foundit needs a search word. It has no browse-everything endpoint. Instahyre browses everything without one.
• Both boards rate-limit. The run paces itself and backs off; a full sweep of Instahyre takes a few minutes.

Watch mode

Turn on Only changed and the run returns only jobs that are new or changed since its previous run, labelled NEW or UPDATED with the changed fields listed.

Empty runs

A run that collects nothing charges nothing and says why by name in the run log and in the REPORT record: no board selected, foundit without a search word, a salary or experience filter without foundit, every row removed by filters, nothing changed since the last run, or every board unreachable.