Google hiring-trend tracking
Use Google Careers endpoints to turn google hiring-trend tracking into repeatable API requests with documented inputs and JSON responses.
Search Google's own careers site (careers.google.com) — by keyword and free-text location — and get a single posting by id, as structured JSON. Distinct from Crawlora's Google Jobs API, which scrapes Google Search's job-results feature rather than Google-the-employer's own board.
Search Google's own careers site (careers.google.com) by keyword and location and get one posting by id, as structured JSON.
Endpoint families
2
Documented params
6
Examples
2
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
4
Schema refs
2
{
"platform": "Google Careers",
"endpoint": "google-jobs-search",
"method": "GET",
"path": "/google-jobs/search",
"auth": "apiKey"
}Use cases
Search Google's own careers site (careers.google.com) by keyword and location and get one posting by id, as structured JSON.
Use Google Careers endpoints to turn google hiring-trend tracking into repeatable API requests with documented inputs and JSON responses.
Use Google Careers endpoints to turn job posting aggregation and monitoring into repeatable API requests with documented inputs and JSON responses.
Use Google Careers endpoints to turn recruiting and talent-market research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Google Careers endpoint catalog — 2 endpoints, 6 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented Google Careers endpoints, grouped into 2 request families — Job and Search.
6 request parameters are documented across those Google Careers endpoints, 4 of them required — the full input contract is public before you write any integration code.
2 of the 2 Google Careers endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
Google Careers endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the Google Careers endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/google-jobs/job
/google-jobs/search
Endpoint catalog
/google-jobs/searchSearches Google's public careers site (careers.google.com) via its server-rendered search page's embedded job data. Each result includes the description, responsibilities, and qualifications inline. Page size is fixed by Google at 20 results.
Response notes
- A valid query with no matches returns `total: 0` and an empty `jobs` array (not an error). - `jobs[].description`, `responsibilities`, `minimum_qualifications`, and `preferred_qualifications` are HTML-stripped plain text. - `jobs[].minimum_qualifications` / `preferred_qualifications` are split from Google's single combined qualifications block; if a posting only lists minimum qualifications, `preferred_qualifications` is omitted. - `jobs[].locations` lists every location display string for postings open to multiple offices; `jobs[].location` is the first one for convenience. `jobs[].country` is a 2-letter code parsed from the first location. - `jobs[].posted_at` is best-effort parsed from an embedded timestamp; it is omitted if the upstream shape ever drifts. - `jobs[].apply_url` requires a Google account to actually submit an application — same as any job board's apply link. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "software engineer", "location": "Singapore", "page": 1, "total": 102, "jobs": [ { "id": "85207000467546822", "title": "Software Engineer, Embedded Software, Silicon", "company": "Google", "location": "Singapore", "locations": ["Singapore"], "country": "SG", "description": "Google's software engineers develop the next-generation technologies...", "responsibilities": "Design and implement the validation software for Google Tensor...", "minimum_qualifications": "Bachelor's degree or equivalent practical experience. 2 years of experience with software development...", "preferred_qualifications": "Experience in embedded systems design, development, and debugging...", "posted_at": "2026-07-22T14:10:44Z", "url": "https://www.google.com/about/careers/applications/jobs/results/85207000467546822-software-engineer-embedded-software-silicon", "apply_url": "https://www.google.com/about/careers/applications/signin?jobId=..." } ], "source_url": "https://www.google.com/about/careers/applications/jobs/results/?location=Singapore&q=software+engineer" } } ```
MCP tool google_jobs_search
/google-jobs/jobReturns one Google Careers posting by its numeric job id (the `id` field returned by search). Parsed from careers.google.com's server-rendered job detail page.
Response notes
- An unknown or no-longer-listed job id returns `404`. Google's detail page itself always answers `200` for any numeric id (valid or not) and swaps in an internal error payload instead of the job record for an invalid one — this endpoint detects that shape and maps it to a proper `404`. - `description`, `responsibilities`, `minimum_qualifications`, and `preferred_qualifications` are HTML-stripped plain text, split the same way as the search endpoint. - `locations`/`location`/`country` behave the same as in search. Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "85207000467546822", "title": "Software Engineer, Embedded Software, Silicon", "company": "Google", "location": "New Taipei, Banqiao District, New Taipei City, Taiwan", "locations": ["New Taipei, Banqiao District, New Taipei City, Taiwan"], "country": "TW", "description": "Google's software engineers develop the next-generation technologies...", "responsibilities": "Design and implement the validation software for Google Tensor...", "minimum_qualifications": "Bachelor's degree or equivalent practical experience. 2 years of experience with software development...", "preferred_qualifications": "Experience in embedded systems design, development, and debugging...", "posted_at": "2026-07-22T14:10:44Z", "url": "https://www.google.com/about/careers/applications/jobs/results/85207000467546822-software-engineer-embedded-software-silicon", "apply_url": "https://www.google.com/about/careers/applications/signin?jobId=..." } } ```
MCP tool google_jobs_job
Related APIs
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.
Related dataset
Dataset · queryable JSON
Google'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.
Explore the dataset →How to scrape Google Careers
careers.google.com runs its own search API — a different surface from Google Search's job-results feature (Crawlora's separate Google Jobs API). Crawlora's endpoints here return normalized postings directly from Google's own board.
Search Google's own careers board by free-text query, optionally filtered by free-text location.
Pass the query and location to Crawlora's Google Careers search endpoint.
Receive normalized postings — title, location, apply URL — in one JSON shape, or fetch one posting in full by its numeric Google job id.
Monitor Google's own hiring over time, or aggregate alongside the Jobs dataset for talent-market research.
FAQ
Send a keyword and optional location to Crawlora's Google Careers search endpoint and get normalized postings — title, location, apply URL — from careers.google.com directly. Collect only public data and respect Google's terms.
No — Crawlora's Google Jobs API scrapes Google Search's job-results feature (jobs posted anywhere, aggregated by Google Search). This API is Google-the-employer's own careers.google.com board — only Google's own openings.
Yes — pass the numeric Google job id to the single-posting endpoint for the full listing.