Tesla hiring-trend tracking
Tesla Jobsエンドポイントを使えば、「Tesla hiring-trend tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Search Tesla's own careers site (tesla.com/careers) — by title, department, or location — and get a single posting by id, as structured JSON. No login, no brittle DOM scraping.
Search Tesla's own careers site (tesla.com/careers) by title, department, or location and get one posting by id, as structured JSON.
エンドポイントファミリー
2
ドキュメント化されたパラメータ
7
サンプル数
2
ライブカタログスナップショット
稼働エンドポイント
2
メソッド
GET
必須パラメータ
3
スキーマ参照
2
{
"platform": "Tesla Jobs",
"endpoint": "tesla-jobs-list",
"method": "GET",
"path": "/tesla-jobs/list",
"auth": "apiKey"
}ユースケース
Search Tesla's own careers site (tesla.com/careers) by title, department, or location and get one posting by id, as structured JSON.
Tesla Jobsエンドポイントを使えば、「Tesla hiring-trend tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Tesla Jobsエンドポイントを使えば、「Job posting aggregation and monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Tesla Jobsエンドポイントを使えば、「Recruiting and talent-market research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のTesla Jobsエンドポイントカタログから取得しています（エンドポイント2件、ドキュメント化されたリクエストパラメータ7個、公開レスポンススキーマ2件）。DocsとPlaygroundが参照しているカタログと同じものです。
Tesla Jobsのエンドポイントは2件、2つのリクエストファミリーに分類されています（Job、List）。
これらのTesla Jobsエンドポイントには7個のリクエストパラメータがドキュメント化されており、うち3個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
2件のTesla Jobsエンドポイントのうち2件が実際のサンプルレスポンスを、2件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Tesla Jobsのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Tesla Jobsのエンドポイントは2個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/tesla-jobs/job
/tesla-jobs/list
エンドポイントカタログ
/tesla-jobs/listSearches Tesla's public careers site (tesla.com/careers) via its own careers-state JSON endpoint. Tesla's own endpoint always returns its entire global job dataset regardless of query parameters; this filters and paginates that snapshot server-side. Listings carry identity/department/location metadata only — call the job endpoint for the full description, responsibilities, and requirements.
レスポンスに関する注記
- Tesla sits behind Akamai Bot Manager, so this endpoint renders through a stealth browser backend rather than a plain HTTP client. First requests after a cold start can take noticeably longer while a session warms up; results are cached briefly afterward. - A valid query/location combination with no matches returns `total: 0` and an empty `jobs` array (not an error). Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "software engineer", "location": "Palo Alto", "page": 1, "page_size": 20, "total": 112, "jobs": [ { "id": "221961", "title": "Software Engineer, Generalist, AI Inference", "department": "Tesla AI", "location": "Palo Alto, California" } ] } } ```
MCPツール tesla_jobs_list
/tesla-jobs/jobReturns one Tesla Careers posting by its numeric job id (the `id` field returned by the list endpoint). Parsed from tesla.com's own job detail JSON endpoint.
レスポンスに関する注記
- An unknown or no-longer-listed job id returns `404`. - Tesla sits behind bot protection, so this endpoint renders through a browser backend rather than a plain HTTP client. A posting that has not been read recently can take noticeably longer on its first request; once fetched it is served from cache on subsequent reads. - If that first fetch runs longer than the request budget, the endpoint returns `503` with a `Retry-After` header rather than holding the connection open until your client times out. The fetch continues in the background, so a retry after the advertised delay normally returns `200` straight away. Treat this `503` as "ask again shortly", not as a failure. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "224501", "title": "AI Engineer, Manipulation, Optimus", "department": "Tesla AI", "job_family": "AI", "location": "Palo Alto, California", "state": "CA", "country": "US", "employment_type": "Full-time", "description": "Tesla AI is solving robust embodied intelligence through humanoid robots...", "responsibilities": "Design and develop our learned robotic manipulation software stack and algorithms...", "requirements": "Production quality modern C++ or Python...", "url": "/careers/search/job/ai-engineer-manipulation-optimus-224501" } } ```
MCPツール tesla_jobs_job
関連API
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
関連データセット
データセット · クエリ可能なJSON
Tesla's open postings are also queryable in bulk alongside 18 other providers — filter by department, location, employment type, or remote flag over one REST call.
データセットを見る →Tesla Jobsのスクレイピング方法
Crawlora's Tesla Jobs endpoints read tesla.com/careers, which publishes its whole global job list as a single dataset. The listing endpoint filters and paginates that snapshot server-side. On 2026-09-18, 2,764 postings matched engineer. Listing rows are deliberately thin: id, title, department, and location. The full job, including compensation text and Tesla's Avature apply link, comes from /tesla-jobs/job.
/tesla-jobs/list takes query (matched against title or department), location, page, and page_size up to 100. Both filters are case-insensitive substring matches, so location=texas matches every Texas site.
department values are Tesla's own, such as Tesla AI, Engineering & Information Technology, Manufacturing, Energy Engineering, and Energy - Solar & Storage. For engineer, Tesla AI roles for Optimus clustered in Palo Alto, with factory roles in Brookshire, Texas and Grünheide, Germany.
/tesla-jobs/job adds job_family, state, country, employment_type, description, responsibilities, requirements, compensation_text, and an apply_url on tesla.avature.net, which is Tesla's application system.
Tesla sits behind Akamai, so the first request after a cold start renders through a browser and can take noticeably longer. Results are then cached briefly.
FAQ
The job endpoint returns Tesla's compensation_text for each posting. Listing rows don't include it, so fetch /tesla-jobs/job for roles where pay matters.
Both query (title/department) and location are case-insensitive substring matches, not exact or faceted filters.