Content Engineer, Developer Documentation

NVIDIA NVIDIA · Semiconductors · Santa Clara, CA

NVIDIA is seeking a Content Engineer/Technical Writer to own developer documentation end-to-end, including building and maintaining the documentation toolchain (docs-as-code, site build, CI checks, automation). This role involves close collaboration with engineers and product managers, influencing tooling and workflows, and ensuring documentation quality scales with product velocity. The ideal candidate will have a proven track record in technical writing or documentation engineering, experience with docs-as-code environments, and strong collaboration and technical skills.

What you'd actually do

  1. Own documentation for assigned products from initial requirements through publication and long-term maintenance, including getting started guides, conceptual docs, SDK and API references, examples, and troubleshooting.
  2. Work closely with engineers, product managers, QA, and support to extract technical knowledge, validate accuracy, and ensure documentation is ready when features ship.
  3. Build and evolve our docs-as-code platform, improving repository structure, build and publish workflows, templates, and CI checks. This includes automating reference documentation where possible and adding guardrails that prevent defects from recurring.
  4. You will continuously identify documentation gaps, broken flows, and quality issues, and drive them to closure through both content fixes and tooling improvements.
  5. This is a unique role spanning Documentation, Developer Experience, and Platform Engineering. Expect a mix of forward-looking design and hands-on execution: writing content, contributing code, improving CI, and refining documentation workflows.

Skills

Required

  • technical writing
  • documentation engineering
  • developer documentation
  • docs-as-code
  • Git-based workflows
  • Markdown or reStructuredText
  • modern documentation platforms
  • collaboration with deeply technical partners
  • independent work
  • balancing priorities
  • full ownership of documentation outcomes
  • excellent editing
  • information architecture
  • content design skills
  • technical depth to validate examples and workflows

Nice to have

  • Experience documenting APIs, SDKs, developer workflows, or infrastructure-level products.
  • Experience extending or maintaining large-scale documentation platforms, static site generators, or custom doc tooling. (Sphinx, Fern, etc)
  • Basic scripting or automation experience, for example, Python or JavaScript, applied to documentation pipelines, validation, or reference generation.

What the JD emphasized

  • documentation end-to-end as a product
  • build/maintain the documentation toolchain
  • documentation quality scales with product velocity
  • influence tooling, workflows, and standards
  • validate accuracy
  • automating reference documentation
  • adding guardrails that prevent defects from recurring
  • continuously identify documentation gaps
  • drive them to closure through both content fixes and tooling improvements
  • documentation outcomes across multiple repositories