Technical Marketing Engineer — CUDA-Q Developer Enablement
NVIDIA Corporation · Santa Clara, CA
$136,000–$253,000from the description
Jun 30, 2026
Santa Clara, CA
Jul 21, 2026
What this job asks for AI summary
A technical marketing engineering role focused on making a quantum computing platform accessible to developers, researchers, and AI agents. Day-to-day work involves creating documentation, example code, onboarding resources, and agent-consumable tooling such as MCP servers and prompt templates, while also designing evaluation frameworks to measure and improve how quickly developers reach productive use of the platform. Suits someone with a background spanning developer content strategy, quantum computing concepts, and agentic tooling.
Mid level · 5+ 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
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $119,144 (middle half $81,115–$160,963). 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 (11)
The role spans two salary bands: Level 3 ($136,000–$212,750) and Level 4 ($160,000–$253,000); the min/max reported here cover the full advertised range across both levels.
This is a Technical Marketing / Developer Relations / Developer Enablement role — it sits between pure software development and technical writing/advocacy. 15-1299 (Computer Occupations, All Other) is the best fit; 15-1252 (Software Developers) is a plausible runner-up given the MCP server and tooling-build responsibilities.
The title carries no seniority level word; the title states no level. The 5+ years requirement and scope (individual contributor, cross-functional collaboration) support a Mid band — the role does not demonstrate the end-to-end ownership or org-wide authority of Senior.
'Documentation systems' and 'information architecture' are listed under the required 'What we need to see' section but name methodologies rather than specific tools; they are retained because the JD explicitly gates on them as a content-strategy competency.
'Evaluation frameworks' covers the JD's hard requirement for 'experience designing evaluations for developer or ML products — controlled experiments, human eval pipelines, or benchmark harnesses'; no specific tool is named.
CUDA-Q is listed as required with 'familiarity with CUDA-Q or similar quantum computing frameworks'; alternatives populated with well-known peer frameworks (Qiskit, Cirq, PennyLane).
Hands-on CUDA-Q experience, open-source contributions, and data/analytics for developer onboarding appear only under 'Ways to stand out from the crowd' — the explicit preferred/bonus section.
GitHub appears in the required section as a 'developer surface' standard to define, not as a hard technical skill gate; retained as preferred given the ambiguity.
Bachelor's degree is listed as required but immediately qualified with 'or equivalent experience', so the degree requirement is set to None.
Ignored 3 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): information architecture, API documentation, open-source quantum computing.
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.