Software Engineer, GPU Design Automation
NVIDIA Corporation · Santa Clara, CA
$152,000–$287,500from the description
Jul 1, 2026
Santa Clara, CA
Jul 21, 2026
What this job asks for AI summary
A software engineering role focused on modernizing the internal development infrastructure used to build GPU chips. Day-to-day work involves designing automation, building and extending code generation pipelines, and refactoring large legacy codebases to be more parameterized and data-driven. The role suits engineers with a background in build systems or design automation who are comfortable working at the intersection of software tooling and hardware development workflows.
Mid level · 3+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 221,500 people nationally plausibly meet what this posting asks for (software developers). range 65,000–332,500
Applicant volume Heavy — This req sits in a large pool with little in its requirements to thin it, and auto-apply tools fire at everything in the occupation. Applying early and leading with the rare skills below is what gets read.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (9)
The posting covers two internal levels (L3 and L4) with distinct salary bands: $152,000–$241,500 for L3 and $184,000–$287,500 for L4. The pay band fields reflect the full combined range across both levels.
Python and C++ are listed together as interchangeable examples ('Python, C++, or similar') under the required qualifications; they are captured as a single requirement with alternatives rather than two separate hard gates.
Degree requirement is None: the JD explicitly accepts 'equivalent experience' in lieu of a formal degree.
Hardware development workflow familiarity (modeling, verification) is listed under required qualifications but is framed as 'familiarity with' — a softer gate; however, it sits in the requirements block. It is captured implicitly through the build systems and code generation requirements rather than as a standalone skill, since it names no specific tool or technology.
All 'Ways to Stand Out' items (hardware build automation at scale, parameterized/template-driven code generation, GPU/ASIC development experience, configuration management) are treated as preferred, as they appear under an explicitly secondary heading.
The role title carries no seniority level word; the title states no level. The 3+ years requirement and scope (team-level automation work, no org-wide authority) support a Mid classification, consistent with the L3/L4 framing.
Remote status is set per caller declaration; no metro is inferred.
Ignored 4 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): hardware build automation, template-driven build systems, GPU development, configuration management.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.