Researches job postings, hiring signals, and freelance gigs via the Crawlora API — Indeed, Google/Amazon/Apple/Meta/Tesla careers sites, any company's ATS board (Greenhouse, Lever, Workday, SmartRecruiters, Ashby, and more), plus Upwork and Fiverr — returning clean JSON. Use when the user wants to search job postings, see what a specific company is hiring for, aggregate hiring signals for a company, or research freelance gigs and sellers.
Coding
tesla-jobs-research
Try itResearches Tesla job postings via the Crawlora API — search Tesla's careers site (tesla.com/careers) by title, department, or location, and pull a single posting's full description by id — returning clean JSON. Use when the user wants to search Tesla job openings, see what Tesla is hiring for in a location, or pull the full detail of a specific Tesla posting.
What it does
Researches Tesla job postings via the Crawlora API — search Tesla's careers site (tesla.com/careers) by title, department, or location, and pull a single posting's full description by id — returning clean JSON. Use when the user wants to search Tesla job openings, see what Tesla is hiring for in a location, or pull the full detail of a specific Tesla posting.
The skill document
Tesla Jobs search
Search Tesla's public careers site and pull full posting detail — all as normalized JSON from the Crawlora API, no scraping tesla.com/careers by hand.
When to use this skill
- "Search for jobs at Tesla." / "What is Tesla hiring for in ?"
- "Show me all Tesla openings in the department."
- "Get the full description/requirements for Tesla job id ."
- "Is Tesla scaling up hiring in ?" — page through the listing.
Setup (one-time)
- Get a free Crawlora API key (2,000 credits/mo, no card) at https://crawlora.net.
export CRAWLORA_API_KEY=sk_your_key_here- All requests:
x-api-key: $CRAWLORA_API_KEYagainsthttps://api.crawlora.net/api/v1. Missing/invalid key →401.
How it works
- List postings —
/tesla-jobs/listsearches Tesla's careers-state JSON snapshot. Filter withquery(title/department substring) and/orlocation(substring), and page through results withpageandpage_size. Tesla's own upstream endpoint always returns its entire global job dataset regardless of query — this endpoint filters and paginates that snapshot server-side, so listings carry identity/ department/location metadata only (no full description yet). - Job detail — take the numeric
idfield from a list result and pass it to/tesla-jobs/jobto get the full posting: description, responsibilities, and requirements.
Full endpoint list, methods, and params: reference/endpoints.md.
Calling the API
# Search Tesla openings by title/department and location:
scripts/crawlora.sh /tesla-jobs/list query="software engineer" location="Austin" | jq '.'
# Pull the full detail for one posting (id from the list response):
scripts/crawlora.sh /tesla-jobs/job id=204536 | jq '.'
Raw curl fallback:
curl -fsS -H "x-api-key: $CRAWLORA_API_KEY" \
"https://api.crawlora.net/api/v1/tesla-jobs/list?query=production&page=1&page_size=50" | jq '.'
Endpoint reference
See reference/endpoints.md for both Tesla Jobs
endpoints this skill uses.
Examples
- "What is Tesla hiring for in Berlin?" —
/tesla-jobs/listlocation="Berlin", then/tesla-jobs/jobon the ids of interest for full requirements. - "Show me every Tesla data engineering role." —
/tesla-jobs/listquery="data engineer", walkingpage/page_sizeuntil the response is short of a full page.
Notes & limits
- Credits / pay-on-success: billed only on
2xx; free tier 2,000 credits/mo. Key at https://crawlora.net. - Public data only — public postings; respect Tesla's terms.
- Security: key lives in
CRAWLORA_API_KEYonly — never hardcode, query-param, or commit it. query/locationare substring filters, not full-text/geo search — a narrow term (e.g. a city abbreviation) may miss postings; try broader substrings if a search returns nothing.- List results are metadata-only — always follow up with
/tesla-jobs/jobfor the full description, responsibilities, and requirements. - Results are paginated — pass
page(and optionallypage_size, up to 100) to walk the full list.
Related skills
Searches Google's public careers site (careers.google.com) via the Crawlora API and pulls single job postings by id, returning clean JSON. Use when the user wants to search Google Jobs, see what roles Google is hiring for in a location, or pull the full detail of a specific Google Jobs posting.
Researches Apple job postings via the Crawlora API — searches jobs.apple.com and pulls full posting detail (description, qualifications, location, team) — returning clean JSON. Use when the user wants to search Apple careers listings, check what a specific Apple team/location is hiring for, or pull the full detail of a specific Apple requisition or pipeline role.
Searches and pulls postings from Meta's public careers site (metacareers.com) via the Crawlora API — full catalog listing, filtered search by team/technology/location/employment-type, and single-posting detail — returning clean JSON. Use when the user wants to find Meta job openings, track a category or team's open roles over time, or look up one specific Meta posting by id.
Searches Indeed job postings and pulls single job listings via the Crawlora API — keyword + location search, location autocomplete, and job detail by job key — returning clean JSON. Use when the user wants to search Indeed for jobs, look up location suggestions for an Indeed search, or fetch the full detail of a specific Indeed posting.
Fetches any company's job openings straight from its Applicant Tracking System (ATS) via the Crawlora API — Greenhouse, Lever, Workday, Ashby, SmartRecruiters, Workable, Personio, Recruitee, iCIMS, Oracle Recruiting, Rippling, Pinpoint, Eightfold, Gem, UKG, and Teamtailor — returning clean JSON. Use when the user wants every open role from a specific company's ATS-hosted career page, a single job posting's full detail, or a hiring-velocity snapshot for a company, given its ATS platform and company/board slug.