Naukri Job Scraper

Scrape Naukri job listings by keyword and location with no login and no API key required. Search any role, skill, or company across Indian and Gulf locations and get clean structured rows: job title, company, salary, experience, skills, location, posting date, and a direct apply link.

What it does

• Keyword job search by role, skill, or company name (for example python developer, react, Acme Co).
• Location filtering across Indian cities and Gulf locations (for example bangalore, mumbai, dubai).
• Many searches in one run. Queue multiple keyword and location pairs and process them in parallel.
• Automatic pagination. Walks page after page until your per-search limit is reached or results run out.
• Salary and experience parsing. Returns both the human label (14-24 Lacs PA, 5-10 Yrs) and numeric min/max values you can filter and sort on. Undisclosed pay returns null instead of a misleading zero.
• Company ratings. Includes company rating and review counts when the company has a public profile.
• Openings count. Reports the number of advertised vacancies for a role when the listing exposes it.
• Clean structured output. Every row follows one stable schema with skills as an array and a deduplicated job id.

No account, no password, no API key. Give it keywords and locations and it returns clean structured job rows.

Use cases

• Job board / aggregator - power a niche, city, or skill-specific job feed with fresh listings.
• Recruitment lead generation - source companies actively hiring for a role and build an outreach list.
• Hiring market research - track demand for a skill, role, or technology across cities over time.
• Competitor hiring monitoring - watch which roles your competitors are recruiting for.
• Salary benchmarking - collect advertised salary ranges for a role to benchmark compensation.

Input

Field	Type	Description
searches	array	One entry per search. Each entry is an object with a keyword (role, skill, or company) and an optional location.
keyword	string	A single keyword, as a shortcut when you only need one search. Combined with location below.
location	string	Location for the single-search keyword. Leave blank to search everywhere.
maxItemsPerSearch	integer	Maximum jobs returned per search. Default 100. Pagination walks as many pages as needed to reach it.
concurrency	integer	How many searches to process in parallel. Default 5.
proxyConfig	object	Proxy configuration. Defaults to Apify residential proxy for reliable large runs.

Example input

{
  "searches": [
    { "keyword": "python developer", "location": "bangalore" },
    { "keyword": "accountant", "location": "dubai" }
  ],
  "maxItemsPerSearch": 200
}

Output

Each job is one dataset row with a stable schema. Sample row:

{
  "type": "job",
  "jobId": "160626017917",
  "title": "DevOps Engineer",
  "url": "https://www.naukri.com/job-listings-devops-engineer-acme-co-160626017917",
  "companyName": "Acme Co",
  "companyId": 15624,
  "companyRating": 3.4,
  "companyReviewsCount": 1516,
  "salaryLabel": "14-24 Lacs PA",
  "minSalary": 1400000,
  "maxSalary": 2400000,
  "currency": "INR",
  "experience": "5-10 Yrs",
  "minExperienceYears": 5,
  "maxExperienceYears": 10,
  "location": "Hyderabad, Bengaluru",
  "openings": 4,
  "skills": ["Docker", "Terraform", "AWS", "CI/CD"],
  "description": "Develop and manage container images...",
  "logo": "https://example.com/logo.png",
  "postedLabel": "1 Day Ago",
  "postedAt": "2026-06-16T00:32:17.000Z",
  "scrapedAt": "2026-06-18T04:10:00.000Z"
}

Key fields

• jobId, url - stable unique id and the direct apply link for each listing.
• salaryLabel + minSalary / maxSalary - the advertised salary as a readable label and as numeric bounds for filtering and sorting. When a listing does not disclose pay, salaryLabel reads "Not disclosed" and the numeric fields (and currency) are null rather than a misleading zero.
• experience + minExperienceYears / maxExperienceYears - required experience as a label and as numeric bounds.
• openings - number of advertised vacancies for the role, when the listing exposes it.
• skills - the listing's tagged skills as a clean array.
• companyRating, companyReviewsCount - included when the company has a public profile, null otherwise.
• postedAt - ISO timestamp of when the job was posted (null for listing types that do not expose it); postedLabel always carries the human-readable freshness ("1 Day Ago").

FAQ

Do I need a login or API key? No. The scraper needs no account, no password, and no API key. Just provide keywords and locations.

How much does it cost? You are billed per job result returned, on top of standard Apify platform usage. There is no per-run start fee. See the Pricing tab on the actor page for the current rate.

How many jobs can I get? Set maxItemsPerSearch to your target (up to 50,000 per search). The scraper paginates automatically until it reaches that number or the search is exhausted. Run multiple searches in one go to cover more roles and cities.

Which locations are supported? Indian cities (for example bangalore, mumbai, delhi, pune, hyderabad) and Gulf locations (for example dubai, abu dhabi) all resolve through the same search. Leave location blank to search everywhere.

How fast is it? Searches run in parallel (controlled by concurrency), and each search streams pages back as it goes. A typical search of a few hundred jobs completes in seconds; large multi-search runs scale with the number of pages walked.

Why are some salary or rating fields empty? Some listings do not advertise a salary, and some companies have no public rating profile. Those fields are returned as null rather than guessed, so your data stays accurate.

Can I filter by salary or experience? Yes. Each row includes numeric minSalary / maxSalary and minExperienceYears / maxExperienceYears alongside the readable labels, so you can filter and sort downstream.