About The Position

NVIDIA is seeking a DriveOS Documentation Program Manager to own the documentation strategy and developer experience for DriveOS. The role is responsible for making documentation consistent, unified, organized around customer needs, and accurate and usable at each release. It works with product, engineering, technical writing, safety, security, QA, publishing, and customer-facing teams to set priorities, drive deliverables, track execution, and coordinate reviews and approvals. The position shapes the documentation portfolio across Linux, QNX, and other Automotive variants, connecting content into a coherent developer experience while accounting for product capabilities, review requirements, and delivery paths. It leads planning and execution throughout the release lifecycle, keeping artifact plans, source data, approvals, and published outputs aligned from release plan of record through content freeze, release candidates, delivery, and post-release closure. The role also gathers user feedback and improves documentation workflows, tracking, and automation. NVIDIA notes that clear, connected documentation helps developers evaluate, integrate, and deploy complex Automotive software.

Requirements

  • 8+ years of relevant experience.
  • Bachelor's degree in a technical or related field, or equivalent experience.
  • Strong commitment to technical documentation, demonstrated through hands-on improvements to clarity, consistency, and usability informed by developer feedback and quality signals.
  • Experience organizing developer documentation, defining journeys for different customer types and segments, and designing effective navigation.
  • Strong program management skills, including planning, prioritization, dependency management, risk escalation, and driving complex programs across multiple teams.
  • Familiarity with documentation workflows from content development and review through release and maintenance, including Git/GitLab collaboration, build and publication processes, and CI/CD concepts.
  • Experience with automotive, embedded software, or similarly complex platform products.
  • Clear written and verbal communication, sound judgment, and ability to align technical writers, engineering, product, QA, and customer-facing teams.

Nice To Haves

  • Experience coordinating automotive safety and cybersecurity deliverables and review processes, including ISO 26262 or ISO 21434 contexts.
  • Familiarity with API/ABI documentation, functional or performance test reports, and third-party license reporting.
  • Practical experience using AI/LLMs to map documentation journeys, identify gaps and inconsistencies across documents, or improve content organization, with a clear approach to validating results.
  • Experience with scripting, workflow automation, dashboards, or data validation.
  • Experience with GitLab, Sphinx, reStructuredText, Doxygen, DITA, or related technical documentation toolchains.

Responsibilities

  • Own the DriveOS documentation strategy and information architecture; establish shared content standards, terminology, and organization across teams and product variants, and close gaps, duplication, and inconsistencies.
  • Define documentation journeys for customer types and segments and create navigation maps connecting guides, API references, release notes, and migration information.
  • Plan and drive documentation delivery across DriveOS releases and product variants, aligning scope, owners, milestones, dependencies, customer commitments, and delivery paths.
  • Lead cross-functional execution with writers, engineers, and reviewers; track status, resolve blockers, and manage documentation reviews, approvals, defect closure, and release exceptions.
  • Coordinate publication and release communications, ensuring approved documentation is correctly versioned, mapped to supported variants, and available through appropriate internal and external channels; follow through on late deliverables.
  • Gather feedback from developers and customer-facing teams, assess how easily users find information and complete key tasks, and prioritize improvements with content owners.
  • Improve dashboards, issue tracking, handoff guides, and automation by defining data and workflow requirements with the teams responsible for the tools.
  • Use AI and large language models to propose documentation journeys and navigation maps, identify content gaps and inconsistencies, and support consistent terminology and structure; validate proposed changes with technical writers and subject matter experts before publication.
  • Drive documentation work from release plan of record through content freeze, release candidates, delivery, and post-release closure, making decisions and risks visible.

Benefits

  • Equity and benefits.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service