ParseForge
We Work Remotely Jobs Scraper
parseforge/we-work-remotely-scraper
JobsAutomationDeveloper tools
Scrapes remote job listings from We Work Remotely filtered by category. Returns each job as a flat row with title, company, URL, and full description.
- Total users
- 1
- Monthly active
- 1
- Total runs
- 100
- Bookmarked
- 0
- Rating
- Not rated yet
- Last modified
- 12 days ago
Overview
We Work Remotely Jobs Scraper
Scrape remote job listings from We Work Remotely by category, up to a million per run. Each job comes with its title, company, URL, and full description. No login or API key. Export to CSV, JSON, Excel, or XML.
Finding a remote job means checking dozens of boards and filtering through noise. This Actor reads the public job feed from We Work Remotely, the largest remote work community, and returns every listing in a clean, flat schema. Pick a category like Front-End Programming or DevOps and Sysadmin, set a limit, and get structured data ready for analysis or your own job board.
| Who uses it | What they scrape We Work Remotely for |
|---|---|
| Job board operators | Populate a niche remote job board with fresh listings from a specific category. |
| Recruiters | Monitor new remote job postings in their domain to source candidates proactively. |
| Data analysts | Track remote hiring trends across programming, design, and marketing categories over time. |
| Job seekers | Build a personal feed of relevant remote openings without browsing the site daily. |
What it does
This Actor collects remote job listings from We Work Remotely filtered by category and returns each one as a flat row.
- 🏷️ Category filter: scrape all remote jobs or narrow to one category like Full-Stack Programming, Design, or Sales and Marketing.
- 🔢 Flexible volume: collect anywhere from a single listing to a million jobs per run, controlled by a simple number input.
- 📄 Structured output: every job returns as a flat row with title, company, URL, and full description, ready for spreadsheets or databases.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with We Work Remotely data
📊 Monitor remote hiring trends.
A market analyst scrapes all categories weekly, loads the CSV into a dashboard, and reports which remote roles are growing fastest.
🎯 Build a niche job alert.
A developer scrapes the Front-End Programming category daily, filters for React roles, and pushes new matches to a Telegram channel.
🏢 Power a white-label job board.
A startup founder scrapes the Design category, enriches the listings with salary data from other sources, and displays them on a curated remote design jobs site.
🔍 Source passive candidates.
A recruiter scrapes DevOps and Sysadmin jobs each morning, extracts company names, and cross-references them with LinkedIn to find hiring managers.
Why choose this scraper
| What you get | |
|---|---|
| No API key needed | Reads the public job feed directly with no registration or rate-limit headaches. |
| Fixed schema | Every run returns the same fields so your downstream pipeline never breaks. |
| Category precision | Choose from ten specific remote job categories instead of noisy keyword searches. |
How it compares
No other Store actor targets We Work Remotely the same way, so the honest comparison is with the alternatives teams actually weigh.
| We Work Remotely Jobs Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When We Work Remotely changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor by selecting a job category and setting a maximum number of listings; the category filter runs as each job is read so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
{
"maxItems": 10
}
A larger pull:
{
"maxItems": 200
}
Pricing
Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the We Work Remotely Jobs Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to We Work Remotely through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/we-work-remotely-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that the category you selected has active listings. Some niche categories may have fewer postings. Try running without a category filter to see all available jobs.
The run finished but I got fewer jobs than my maxItems setting.
The Actor stops when it exhausts all available listings in the category. If the category has fewer total jobs than your limit, you will receive all of them.
Why are some job descriptions truncated?
The Actor captures the full description as displayed on the listing page. If a description appears cut off, the original posting on We Work Remotely may be brief.
The Actor is running slowly.
The Actor respects the website's response time. For large scrapes, increase the run timeout in your Actor settings rather than adjusting request rates.
Can I resume a run that was interrupted?
The Actor does not support resuming from a checkpoint. If a run fails, start a new run. For large jobs, consider breaking them into smaller category-specific runs.
FAQ
| Question | Answer |
|---|---|
| Does this scraper require a We Work Remotely account or API key? | No. It reads the public job listings directly from the website. You do not need an account, an API key, or any authentication. |
| Can I scrape multiple categories in one run? | The Actor scrapes one category per run. To collect jobs from multiple categories, run the Actor once per category and merge the datasets. |
| How many job listings can I scrape? | You can set the maximum from 1 up to 1,000,000 listings per run. The Actor stops when it reaches your limit or when no more listings exist in the category. |
| What fields does each job record contain? | Each row includes the job title, company name, the full We Work Remotely URL, and the complete job description text as it appears on the site. |
| How often is the data updated? | The Actor reads the live We Work Remotely site on every run, so you always get the current listings. Schedule it to run hourly or daily for fresh data. |
| Can I filter by job type like full-time or contract? | The Actor filters by the ten We Work Remotely categories. Job type filters are not available as a separate input, but the full description text often contains this information. |
| What output formats are supported? | You can export your dataset to CSV, JSON, Excel, or XML from the Apify platform after the run completes. |
| Is it legal to scrape We Work Remotely? | This Actor reads publicly available job listings. You are responsible for complying with We Work Remotely's terms of service and applicable laws in your jurisdiction. |
| Can I search for specific keywords within job listings? | The Actor does not have a built-in keyword filter. Scrape a category and then filter the resulting dataset by searching the job title or description fields in your spreadsheet or script. |
| Does this Actor handle pagination automatically? | Yes. It navigates through all available pages in the selected category until it reaches your maxItems limit or the end of the listings. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by We Work Remotely Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
Input
| Field | Type | What it does | Default |
|---|---|---|---|
| maxItems | integer | How many job listings to collect per run. | 10 |
| category | string (11 options) | Filter jobs by category. Leave empty to scrape all categories. | not set |
Pricing
from $19.00 per 1,000 results
| Charged for | What it is | Price each |
|---|---|---|
| result | Single result in the default dataset. | $0.019 to $0.021 |
Tiered: the lower figure is the price on a higher Apify plan. Billing and the free credit live on Apify.
API
One POST returns the dataset directly. Same shape for every scraper in the library, so swapping the slug is the only change.
curl -X POST "https://api.apify.com/v2/acts/parseforge~we-work-remotely-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"helloWorld": 123
}' Examples
Input that runs as-is.
{
"helloWorld": 123
} Reviews
No reviews yet. Be the first.
Issues
We build and maintain this scraper, so a problem with it comes to us. Report it on the Apify listing and the thread stays attached to the scraper where the next person can find it: open an issue.
Broken and urgent, or you would rather not post in public? Write to parseforge@protonmail.com and it reaches the people who wrote it.