Built In Jobs Scraper — US Tech & Startup Jobs
Pricing
from $0.70 / 1,000 job results
Built In Jobs Scraper — US Tech & Startup Jobs
Extract live US tech & startup jobs from Built In (builtin.com): software, data, product, design & sales roles. Records include title, company, remote/hybrid, structured salary (min/max/currency), skills, experience level, posted date & apply URL. Delta mode for alert bots.
Scrape current US tech and startup openings from Built In, including remote flags and salary bands where posted.
What Built In jobs data does this scraper extract?
Each result is one flat JSON record per job posting:
| Field | Meaning |
|---|---|
id | Stable source-side identifier |
title | Job title as posted |
company | Hiring company / organisation (null if not shown on the card) |
location | Location / duty station (may include remote hints) |
workplaceType | Normalized work arrangement — "Remote", "Hybrid" or "On-site" — from Built In's own workplace label (null if none) |
url | Direct link to the posting |
postedAt | Absolute UTC ISO 8601 timestamp, parsed from the source's relative age badge (e.g. "3 Days Ago"), null if the badge is absent or unparseable |
salary | Free-text salary string where the source provides it, otherwise null |
salaryMin / salaryMax | Structured pay range as integers, from schema.org baseSalary (authoritative) or parsed from the card salary text; null when no figure is disclosed |
salaryCurrency | Currency code for the range (e.g. "USD"), null when unknown |
salaryPeriod | Pay period — "year", "month", "week", "day" or "hour" — null when unknown |
experienceLevel | Built In's seniority label (e.g. "Senior level", "Mid level", "Internship"). Detail-page field; null on a light run |
employmentType | schema.org employment type (e.g. "FULL_TIME"). Detail-page field; null on a light run |
skills | The detail page's labeled "Skills Required" bullet list (array, up to 25). Detail-page field; null on a light run |
industries | Industry/sector tags from schema.org industry (array). Detail-page field; null on a light run |
validThrough | Posting expiry (ISO 8601) from schema.org validThrough. Detail-page field; null on a light run |
snippet | Short description excerpt from the listing card, otherwise null |
description | Full job-description text from the detail page (schema.org JobPosting JSON-LD, with a class-matched HTML fallback). Only populated when includeDescription: true; null otherwise |
isNew | true when returned by delta mode (onlyNewSinceLastRun); absent on ordinary runs |
source | Always "builtin" |
The detail-page fields (experienceLevel, employmentType, skills, industries, validThrough, description, and the authoritative salary*) require includeDescription: true (the default). Missing/absent fields are always null — never an empty string.
How to scrape Built In jobs with this Actor
- Click Try for free / Run — no login to the target site, no cookies, no proxies to configure.
- Pick job categories (or leave empty for the curated default in
categoryPages— see Input below) and adjustmaxItems. - Run it and export the dataset as JSON, CSV or Excel, or read it over the API.
Run it from your own code:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("nomad-agent/builtin-scraper").call(run_input={"maxItems": 50})for item in client.dataset(run["defaultDatasetId"]).iterate_items():print(item["title"], "—", item["company"], item["url"])
Or a single HTTP call that runs the Actor and returns items in one response:
curl -X POST \"https://api.apify.com/v2/acts/nomad-agent~builtin-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \-H "Content-Type: application/json" \-d '{"maxItems": 50}'
Input
| Field | Type | Default | Notes |
|---|---|---|---|
categories | array (multi-select) | (empty) | Friendly Built In job categories to scrape — 21 verified categories including Software Engineering, Frontend, JavaScript, DevOps, Data & Analytics, Data Science, Machine Learning, Data Engineering, Product, Design, Marketing, Sales, Operations, HR, Finance, Legal, Content, Customer Success, Project Management, Cybersecurity + IT, and Internships. Leave empty to use the default shown in categoryPages below. Merges with categoryPages if both are set. |
maxItems | integer | 50 | Maximum number of listings to return across all category pages. Set to 0 for no limit. |
maxPagesPerCategory | integer | 1 | How many pagination pages to fetch per category URL. Page 1 is always fetched; subsequent pages use the ?page=N parameter. |
includeDescription | boolean | true | Fetch each job's detail page to populate the full description plus the authoritative structured salary*, skills, experienceLevel, employmentType, industries and validThrough. Turn off for faster, lighter runs — those fields stay null; salaryMin/Max still come from the card text where present, and snippet/workplaceType are unaffected. |
postedWithinDays | integer | 0 | Only return listings posted within this many days (from each card's relative age badge). 0 disables the filter. Listings with no parseable age are kept, not dropped. |
onlyNewSinceLastRun | boolean | false | Delta / monitoring mode: only output listings not seen on a previous run that also had this flag on. Already-seen listings are dropped before push (never billed) — the cheapest way to run on a schedule and pay only for genuinely new postings. See "Delta mode" below. |
categoryPages (Advanced) | array | /jobs/remote/dev-engineering/front-end, /jobs/remote/dev-engineering/javascript, /jobs/remote/data-analytics/machine-learning, /jobs/remote/dev-engineering/devops, /jobs/remote/data-analytics/data-engineering | Legacy/low-level form: raw Built In category page paths or full URLs. Pre-filled with this Actor's actual default coverage (previously a hidden code-level default with no UI visibility) so you can see and edit exactly what a default run fetches. Prefer categories for common cases; use this for one-off or niche categories not covered by the enum. Merges with categories, doesn't replace it. |
cacheTtlSeconds (Advanced) | integer | 1800 | Reuse a page fetched this many seconds ago instead of hitting builtin.com again on rapid re-runs. Set 0 to always fetch live. |
Output example
{"id": "2237714","title": "Senior Data Engineer","company": "Motive","location": "Remote · United States","workplaceType": "Remote","url": "https://builtin.com/job/senior-data-engineer/2237714","postedAt": "2026-06-30T12:00:00Z","salary": "150K-180K Annually","salaryMin": 150000,"salaryMax": 180000,"salaryCurrency": "USD","salaryPeriod": "year","experienceLevel": "Senior level","employmentType": "FULL_TIME","skills": ["5+ years of data engineering experience", "Expert SQL", "Spark / Airflow"],"industries": ["Artificial Intelligence", "Software"],"validThrough": "2026-08-05T00:00:00+00:00","snippet": "Motive is hiring a Senior Data Engineer...","description": "Motive is hiring a Senior Data Engineer to build the data platform powering our fleet analytics... (full JD, up to 5000 chars)","source": "builtin"}
Delta mode / monitoring (onlyNewSinceLastRun)
Set onlyNewSinceLastRun: true to only emit postings not seen on a previous flagged run. State is tracked per Actor in a dedicated key-value store keyed by each listing's id; already-seen listings are dropped before push, so you are never billed for them. Returned listings carry isNew: true. This is the cheapest way to run this Actor on a cron schedule and pay only for genuinely new postings — ideal for job-alert bots. Combine with postedWithinDays for a tight freshness window.
Integrations
Export the dataset as JSON, CSV or Excel from the Console, pull it over the Apify API (including run-sync-get-dataset-items for a single blocking call), wire it into Make/Zapier/n8n, or drive it from an AI agent via the Apify MCP server.
Pricing
Pay per event: $0.005 per Actor start and $0.0009 per job returned. 100 jobs ≈ $0.095. No subscription, no rental — you pay only for what you fetch.
Use cases
- US tech job boards and alert bots
- Startup-hiring market research
- Sourcing pipelines for US tech roles
- Salary benchmarking by city
FAQ
Is it legal to scrape Built In jobs? This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case.
Do I need an account on the target site? No. Postings are fetched from public pages/APIs — no login, cookies or session tokens.
How fresh is the data?
Every run fetches live listings. Results are cached for cacheTtlSeconds (default 30 min, set 0 to always hit the source live).
How many jobs can I get?
maxItems caps the run (set 0 where supported for no cap). Most sources paginate from newest to oldest.
What's the difference between categories and categoryPages?
categories is a friendly multi-select of common Built In job categories — pick from a list, no need to know the site's internal URL structure. categoryPages (Advanced) is the raw underlying mechanism: literal Built In category page paths or URLs, for categories not covered by the friendly list. Both feed the same fetch and can be combined.
Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and reliability fixes ship fast.
Related Actors
- Web Developer Jobs Scraper — 10 Boards in One
- AI & ML Engineer Jobs Scraper — 8 Boards in One
- Y Combinator Jobs Scraper — Work at a Startup
- LinkedIn Jobs Scraper — No Login, No Cookies
From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.