🏔️ Himalayas Remote Jobs Scraper — 100,000+ Remote Tech Jobs to JSON/CSV/Excel

Pull a clean, structured feed of every remote job listed on Himalayas — one of the largest dedicated remote-work boards, with 100,000+ live remote roles across engineering, design, product, marketing, sales, support, data, operations and more. Title, company, salary range, location restrictions, seniority, employment type, categories, apply link — straight from the official Himalayas API, fully paginated, no login, no API key.

Built for recruiters, HR-tech teams, job aggregators, labor-market researchers, talent-intelligence platforms and personal job-hunt automations. Cost-optimised by default — the heavy description field is opt-in and a maxPagesToScan ceiling stops runaway scans when filters are narrow.

🟢 No login. No API key. No proxy. No headless browser. Pure public HTTPS.

---

🧭 What this scraper does

Himalayas indexes tens of thousands of remote-only jobs from companies that hire worldwide, regionally (US-only, EU-only, LATAM) or within a specific timezone window. This Apify Actor talks to Himalayas's public jobs API directly — the same endpoint that powers the site — walks the entire feed page by page, applies your filters (keyword, category, seniority, employment type) and writes one flat JSON record per matching job to the Apify Dataset.

Pull a quick 100-job sample, a focused 500-job recruiter slice, or the full 100k+ feed for an aggregator backend. Either way you get the same clean schema — ready for JSON, CSV, Excel, Google Sheets, Postgres, BigQuery, Snowflake or your ATS.

---

✨ Key features

Feature	What it gives you
🌐 Official Himalayas API	Talks to the same JSON endpoint as the website — fast, stable, fully paginated
📦 100,000+ remote jobs	Engineering, design, marketing, sales, support, data, ops, finance, writing, legal, HR, product
🔎 Keyword search	searchKeyword matches against title, excerpt and company name
🏷️ Category filter	Multi-value categories array matched against each job's categories and parent categories
🎚️ Seniority filter	Filter by Entry-level, Mid-level, Senior, Lead, Executive, Internship
💼 Employment type filter	Narrow to Full Time, Part Time, Contract, Freelance or Internship
💰 Salary data	Min, max and currency captured for every job that publishes a range
🌍 Location & timezone restrictions	Worldwide, US, EU, LATAM, UTC ± 3, etc.
💸 Cost-optimised by default	Heavy description field is opt-in; 200-char excerpt always included
🛡️ maxPagesToScan cost ceiling	Hard cap on pages — prevents runaway scans when filters are narrow
📤 Export-ready	Flat JSON — JSON, CSV, Excel, XML, HTML, RSS via the Apify Dataset
🔄 Schedule-friendly	Daily/hourly recurring runs to keep your feed fresh

---

🎯 Built for these use cases

1. Recruiters & talent sourcing

Maintain a continuously fresh feed of worldwide remote roles in your niche. Filter by category and seniority once, schedule the Actor every morning, wake up to a deduplicated list of new remote engineers, designers or PMs — apply links and salary bands already pulled.

2. HR analytics & workforce dashboards

Pipe listings into Looker, Metabase, Tableau or Power BI for a live picture of remote-hiring demand by category, seniority and salary band. Track week-over-week movement, spot rising sub-niches, benchmark against your own openings.

3. Job market & salary benchmarking

Structured minSalary, maxSalary and currency on a huge share of listings. Aggregate by categories × seniority for one of the cleanest public salary datasets for remote tech work — no proprietary compensation feed needed.

4. Job board & aggregator products

Power a remote-jobs section, a niche category page ("Remote Solidity Jobs"), or a full job-board MVP using Himalayas as your upstream feed. Cross-link the apply URL, store excerpt and tags, refresh nightly.

5. Workforce planning for distributed teams

For remote-first companies, monitor the supply side: how many comparable senior backend roles are live, what salary bands are being offered worldwide vs. US-only, what timezones companies want. Better TA budgeting and offer decisions.

6. Academic labor market research

Track structural shifts in remote work — full-time vs. contract share, regional restrictions trends, category mix. postedAt timestamps and locationRestrictions arrays are researcher-friendly.

7. Lead generation — companies actively hiring

A company hiring 3+ senior remote engineers right now is a high-signal target for ATS vendors, dev-tools, EOR/PEO providers (Deel, Remote.com), payroll, equipment, learning platforms and benefits brokers. Aggregate by company, sort by openings, hand to outbound.

8. Personal job-hunt automation

Run a tightly-filtered nightly scan (React, Senior, Worldwide) and pipe new matches into Slack, Discord, email or Notion. Apply within hours of posting when response rates are highest.

---

📥 Inputs

Field	Type	Required	Description
searchKeyword	string	No	Free-text matched against job title, excerpt and company. Examples: react, data scientist, solidity, fintech. Empty = no keyword filter.
categories	string[]	No	Filter by category. Common values: Engineering, Software Development, Design, Marketing, Sales, Product, Customer Success, Operations, Finance, Data, Human Resources, Writing, Legal. Empty = all.
seniority	string[]	No	Entry-level, Mid-level, Senior, Lead, Executive, Internship. Empty = all.
employmentType	string	No	Full Time, Part Time, Contract, Freelance, Internship. Empty = all.
maxJobs	integer	No	Max matching jobs to save. 100 = quick sample, 500 = focused dataset, 2000 = large, 0 = unlimited. Default 200.
maxPagesToScan	integer	No	Hard cost ceiling on pages (20 jobs/page). 50 ≈ 1,000 jobs scanned, 200 ≈ 4,000, 500 ≈ 10,000. 0 disables (only when you want the entire 100k+ feed). Default 100.
includeDescription	boolean	No	When true, includes full HTML description (1–7 KB per job). excerpt (200 chars) always included. Default false.

Example inputs

Quick 100-job sample across all categories:

{ "maxJobs": 100, "maxPagesToScan": 5 }

Senior React engineers, worldwide remote:

{
  "searchKeyword": "react",
  "categories": ["Engineering", "Software Development"],
  "seniority": ["Senior", "Lead"],
  "employmentType": "Full Time",
  "maxJobs": 500
}

Full board crawl with descriptions (research / backfill):

{ "maxJobs": 0, "maxPagesToScan": 0, "includeDescription": true }

Daily incremental for a design-roles dashboard:

{
  "categories": ["Design"],
  "seniority": ["Mid-level", "Senior"],
  "maxJobs": 200,
  "maxPagesToScan": 50
}

---

📤 Output

Each item is one Himalayas remote job, flat and ready to export.

Example output record

{
  "title": "Senior Backend Engineer (Remote, Worldwide)",
  "company": "Acme Cloud",
  "companySlug": "acme-cloud",
  "companyLogo": "https://himalayas.app/companies/acme-cloud/logo.png",
  "employmentType": "Full Time",
  "seniority": ["Senior"],
  "categories": ["Software Development", "Backend"],
  "parentCategories": ["Engineering"],
  "minSalary": 130000,
  "maxSalary": 180000,
  "currency": "USD",
  "locationRestrictions": ["Worldwide"],
  "timezoneRestrictions": ["UTC ± 4"],
  "excerpt": "We're hiring a senior backend engineer to scale our distributed event-pipeline platform...",
  "url": "https://himalayas.app/companies/acme-cloud/jobs/senior-backend-engineer",
  "postedAt": "2026-05-14T09:12:00.000Z",
  "expiresAt": "2026-06-13T09:12:00.000Z",
  "guid": "himalayas-987654",
  "scrapedAt": "2026-05-15T08:30:00.000Z"
}

Field reference

Field	Type	Description
title	string	Job title
company	string	Hiring company name
companySlug	string	Himalayas URL slug for the company
companyLogo	string	Logo image URL
employmentType	string	Full Time, Part Time, Contract, Freelance, Internship
seniority	string[]	Entry-level, Mid-level, Senior, Lead, Executive
categories	string[]	Specific categories (Backend, Frontend, Mobile, etc.)
parentCategories	string[]	Parent groupings (Engineering, Design, etc.)
minSalary	number	Lower bound of published salary range
maxSalary	number	Upper bound of published salary range
currency	string	ISO currency (USD, EUR, GBP)
locationRestrictions	string[]	Worldwide, US, EU, LATAM, Americas
timezoneRestrictions	string[]	UTC ± 3, Americas timezones, etc.
excerpt	string	200-char summary — always included
description	string	Full HTML body — only when includeDescription = true
url	string	Direct apply / listing URL
postedAt	ISO	Original posting date
expiresAt	ISO	Listing expiry when published
guid	string	Stable Himalayas job identifier (dedupe key)
scrapedAt	ISO	When this run captured the job

---

⚙️ How it works

1. Initialise — read input, normalise filters to lowercase, log run config.
2. Paginate — request https://himalayas.app/jobs/api?limit=20&offset=N page by page; Himalayas hard-caps each page at 20 jobs.
3. Track totals — capture totalCount from the first response for progress logs.
4. Parse — map raw records to the canonical schema. Unix-second timestamps → ISO 8601.
5. Filter client-side — keyword (title + excerpt + company), categories, seniority, employment type. Substring matching, case-insensitive.
6. Deduplicate — guid or url based; the scraper keeps a Set so overlapping pages never write the same job twice.
7. Push to dataset — every matching job becomes one row.
8. Stop conditions — first of: maxJobs saved, maxPagesToScan reached, end-of-feed (totalCount), 3 consecutive network errors, persistent HTTP 429, or HARD_CEILING (5,500 pages).
9. Backoff — on HTTP 429: 2 → 4 → 8 → 15 s, give up after 4 retries.
10. Finalise — emit summary and exit cleanly.

---

⚡ Performance

Pure HTTP, 20 jobs per page, ~50 ms courtesy delay between pages.

Run size	Pages	Approx. time	Notes
100 jobs	~5	< 30 s	Quick demo / QA test
500 jobs	~25	1–2 min	Recruiter daily slice
2,000 jobs	~100	4–6 min	Full-category nightly run
10,000 jobs	~500	20–30 min	Weekly aggregator backfill
Full feed (~100k)	~5,000	3–4 h	One-off historical pull

includeDescription = true increases dataset bytes 5–10× but does not change scraping time.

---

💰 Cost model

Standard Apify Actor pricing — you pay only for the compute and dataset storage consumed. No per-result surcharge, no third-party API key. Compute is tiny for filtered runs and moderate for full-feed sweeps; dataset bytes are small with includeDescription = false and much larger when enabled. No proxy spend (pure HTTPS against a public API). Defaults are conservative — loosen them deliberately when you need a bigger pull.

---

🔄 Schedule for continuous monitoring

Apify Schedules run this Actor on any cron interval. Patterns: Daily recruiter feed (narrow filter, maxJobs: 200, morning, append to Google Sheets); Hourly fast-mover scan (narrow keyword, maxJobs: 50, Slack webhook on new rows); Weekly market snapshot (broad filter, maxJobs: 5000, Monday 03:00 UTC, push to Postgres/BigQuery); Quarterly research dump (unlimited, includeDescription: true, archive to S3). Combine with Apify Webhooks to notify your ATS, CRM or Slack when a run finishes.

---

🛠️ FAQ

Is it legal to scrape Himalayas? The Actor reads Himalayas's public jobs API and only collects publicly visible data. Comply with Himalayas's terms and applicable laws (GDPR, CCPA). Don't republish full descriptions verbatim without permission.

Do I need a Himalayas account or API key? No — only an Apify account.

How many jobs can I get in one run? The feed is 100,000+ and the scraper can pull all of them (maxJobs: 0, maxPagesToScan: 0). Full sweep ~3–4 hours; most use cases need 200–2,000 jobs.

Why is description off by default? It's the biggest cost driver — 1–7 KB per job vs. ~1 KB for everything else. Disabling cuts dataset bytes 5–10× without losing title, company, salary, categories, seniority, restrictions, 200-char excerpt or apply URL.

Will it get blocked or rate-limited? Himalayas's public API tolerates the 50 ms-per-page pace. On rare HTTP 429 the scraper backs off (2 → 4 → 8 → 15 s) and retries up to 4 times before stopping cleanly.

How do I get only new jobs each day? Schedule the Actor and dedupe downstream using the stable guid field, or sort by postedAt desc and keep rows newer than your last run's max timestamp.

Can I filter by salary? Not in input, but minSalary / maxSalary / currency are in output. Filter downstream (WHERE minSalary >= 100000 AND currency = 'USD').

Can I filter by location or timezone? Output has locationRestrictions and timezoneRestrictions arrays. Filter downstream. Himalayas only lists remote roles, so the question is geographic restriction rather than physical office.

What output formats are supported? JSON, JSONL, CSV, XLSX, XML, HTML, RSS. Pull via the Apify API or push to Google Sheets, S3, webhooks.

Can I integrate with an ATS / CRM? Yes — use Apify Webhooks on ACTOR.RUN.SUCCEEDED to pipe rows into Greenhouse, Lever, Workable, Ashby, HubSpot, Salesforce. Map guid to your unique-key column so re-runs upsert.

What if Himalayas changes its API? The scraper is defensive — missing fields → null, malformed JSON triggers a clean stop. Report breakage via the Actor's Issues tab.

Can I run it from my own script? POST your input JSON to https://api.apify.com/v2/acts/logiover~himalayas-remote-jobs-scraper/runs?token=YOUR_TOKEN, poll the run, fetch dataset items.

---

📚 Related scrapers

Pair Himalayas with the rest of the job-board collection: Remote OK (tech-heavy remote), Remotive (curated remote feed), Jobicy (tech & marketing remote), Welcome to the Jungle (European employer branding), Web3 & Crypto Jobs (web3.career), Arbeitnow (German-speaking + European remote), Hacker News Who Is Hiring (monthly HN thread), Lever Postings (Lever-hosted pages), Greenhouse Job Board (Greenhouse-hosted pages), The Muse (career platform), Built In Tech Jobs (US-city tech ecosystems), USAJobs (US federal), Internshala (Indian internships), Hirist Tech (Indian senior tech), WorkIndia (Indian mass hiring), Naukri (India's largest board), Lagou Tech Jobs (Chinese tech).

---

🔑 Keyword cloud

Core: himalayas scraper, himalayas remote jobs scraper, himalayas.app scraper, remote jobs api, remote jobs scraper, worldwide remote jobs, remote job board scraper, remote tech jobs feed, remote jobs dataset, remote-first hiring data, structured job listings, jobs apify actor.

Niche / role / region: remote react engineer jobs, remote backend engineer jobs, remote python developer, remote senior engineer jobs, remote staff engineer, remote product manager jobs, remote designer jobs, remote UX UI jobs, remote data scientist jobs, remote DevOps SRE jobs, remote QA engineer jobs, remote marketing jobs, remote sales jobs, remote customer success jobs, remote operations jobs, remote finance jobs, remote HR people ops jobs, remote legal counsel jobs, US-only remote jobs, EU remote jobs, LATAM remote jobs, APAC remote jobs, timezone-restricted remote jobs.

Use case: remote hiring trends, remote-work labor market data, remote salary benchmark, remote jobs aggregator backend, recruiter sourcing automation, ATS data pipeline, talent intelligence dashboard, remote-jobs alert bot, job-hunt automation, EOR PEO market intelligence, dev-tools lead generation, remote-work academic research.

Audience: recruiters, talent acquisition, sourcers, HR-tech founders, ATS vendors, dev-tool marketers, EOR PEO sales teams, payroll software, equipment providers, job board operators, career platforms, labor market economists, journalists, indie developers, job seekers, career coaches.

---

Changelog

• 2026-06-01 — Maintenance & reliability pass: pulled the latest source and rebuilt the Actor on the current base image; build verified.

• 2026-05-25 — Maintenance & reliability pass: pulled the latest source and rebuilt the Actor on the current base image; build verified.

• 2026-05-20 — Maintenance pass: reviewed the input schema and default values for a smooth one-click start, and rebuilt the Actor on the latest base image.

Last reviewed: 2026-06-01.