Myworkdayjobs APInvidia.wd5.myworkdayjobs.com ↗
Search NVIDIA job postings by keyword, location, and department. Retrieve full job details including description, requirements, and application URLs.
What is the Myworkdayjobs API?
This API provides access to NVIDIA's current job listings through 2 endpoints, returning up to 10 results per page with fields like title, department, locations, and work_location_option. The search_jobs endpoint accepts keyword queries, location filters, and category filters to narrow results across NVIDIA's full open-role catalog, while get_job_details returns the complete posting for a specific position including its apply_url and job_family.
curl -X GET 'https://api.parse.bot/scraper/e5cfae17-8775-4522-bedd-f18bbf73036a/search_jobs?query=software+engineer&start=0&location_type=onsite' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace nvidia-wd5-myworkdayjobs-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: NVIDIA Jobs SDK — search listings and drill into details."""
from parse_apis.nvidia_jobs_api import NvidiaJobs, LocationType, JobNotFound
client = NvidiaJobs()
# Search for remote AI jobs, capped at 5 results
for job in client.jobsummaries.search(query="AI", location_type=LocationType.REMOTE, limit=5):
print(job.title, job.department, job.work_location_option)
# Drill into the first result for full details
summary = client.jobsummaries.search(query="software engineer", limit=1).first()
if summary:
detail = summary.details()
print(detail.title, detail.department)
print("Location:", detail.location)
print("Job family:", detail.job_family)
print("Apply:", detail.apply_url)
# Handle a not-found case with typed error
try:
bad = client.jobsummaries.search(query="nonexistent_xyz_000", limit=1).first()
if bad:
bad.details()
except JobNotFound as exc:
print(f"Job not found: {exc.position_id}")
print("exercised: jobsummaries.search / summary.details / JobNotFound error handling")
Search NVIDIA job listings by keyword, location, and filters. Returns paginated results with 10 jobs per page. Pagination advances via the start offset in increments of 10. Each job summary includes identifiers, title, locations, department, and work type.
| Param | Type | Description |
|---|---|---|
| query | string | Search keyword (e.g. 'software engineer', 'data scientist') |
| start | integer | Pagination offset (0-based, increments of 10) |
| category | string | Job category filter (e.g. 'engineering', 'sales', 'marketing') |
| location | string | Location filter (e.g. 'Santa Clara', 'California') |
| location_type | string | Work location type filter: 'onsite', 'remote', or 'remote_local' |
{
"type": "object",
"fields": {
"jobs": "array of job listing summaries with id, job_id, title, locations, department, posted_date, work_location_option, and url",
"count": "number of jobs returned on this page",
"start": "current pagination offset",
"total": "total number of matching jobs"
},
"sample": {
"data": {
"jobs": [
{
"id": 893392590814,
"url": "https://jobs.nvidia.com/careers/job/893392590814",
"title": "Senior System Software Engineer - Software Development Kit",
"job_id": "JR2010588",
"locations": [
"US, CA, Santa Clara"
],
"department": "Engineer, Sys SW",
"posted_date": 1778112000,
"work_location_option": "onsite"
}
],
"count": 10,
"start": 0,
"total": 1953
},
"status": "success"
}
}About the Myworkdayjobs API
Searching NVIDIA Job Listings
The search_jobs endpoint accepts five optional parameters: query for keyword matching (e.g. 'machine learning', 'systems engineer'), location to filter by city or state, location_type to restrict results to onsite, remote, or remote_local roles, category to target a functional area like engineering or marketing, and start for pagination in increments of 10. Each response includes a total count of matching jobs alongside the current page's count and start offset, making it straightforward to walk through large result sets. Each job in the jobs array carries a numeric id, a human-readable job_id (e.g. JR2010588), title, locations array, department, posted_date, work_location_option, and a direct url to the public posting.
Retrieving Full Job Details
The get_job_details endpoint takes the position_id (the numeric id from search results) and returns the complete posting record. Beyond the summary fields, this includes a full job description, time_type (e.g. Full time), job_family categories, primary location string, and an apply_url that points directly to the application form. This is the endpoint to call when you need to render a full job page or extract the detailed requirements text.
Pagination and Filtering Notes
Results are returned in pages of 10. To retrieve the next page, increment start by 10. The total field in the search_jobs response tells you how many matching jobs exist across all pages. Combining query with location and location_type produces more targeted result sets; omitting all parameters returns the full open-role feed sorted by recency.
The Myworkdayjobs API is a managed, monitored endpoint for nvidia.wd5.myworkdayjobs.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nvidia.wd5.myworkdayjobs.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official nvidia.wd5.myworkdayjobs.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a job board widget that surfaces NVIDIA openings filtered by location and work_location_option for remote-first candidates.
- Track new NVIDIA engineering roles by polling search_jobs with a category filter and comparing posted_date against previous results.
- Aggregate NVIDIA job counts by department field to analyze hiring trends across business units.
- Enrich a recruiting CRM by pulling full job descriptions via get_job_details for positions that match a sourcing keyword list.
- Alert hiring managers when NVIDIA posts roles in a specific job_family by monitoring search_jobs results.
- Generate a structured dataset of NVIDIA job titles, locations, and time_type values for labor market analysis.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.