Senior Content Engineer, KnowledgeOps
Free to start · No card · 5 credits the moment you sign up
Job description
Build the systems that deliver Simulation Technology knowledge to developers, partners, internal teams, and the AI agents that increasingly sit between them and our documentation. Our KnowledgeOps team sets the information architecture and quality standards for Omniverse, Isaac Sim, and OpenUSD documentation. You'll build the automation, pipelines, and AI-ready infrastructure that apply those standards at scale, and work with documentation leads to refine the architecture based on what you learn.
You're a writer who builds: as comfortable in Git, CI, or Python as in a style guide, and fluent with LLMs in daily work. We build systems where the right way is easier than the wrong way. For you, that means turning documentation, standards, and tribal knowledge into tooling, templates, and self-service paths, so fewer people have to ask "how do I…?"
What you'll be doing:
- Collaborate with documentation leads on knowledge architecture, sharing implementation feedback (what works, breaks, and scales) to refine content models, information architecture, and AI-readiness patterns
- Build and run docs-as-code pipelines: Git authoring, CI/CD builds, linting, link and code-sample validation, and publishing
- Make knowledge AI-ready: structure and package content for RAG, internal assistants, and agentic workflows, including llms.txt, MCP-accessible sources, agent skills and context kits, and evaluation sets for answer accuracy
- Automate the content lifecycle with LLMs and scripting, from drafting and updating to auditing, with checks for freshness, code accuracy, and terminology drift, and human review where judgment matters
- Encode standards (user stories, release readiness, onboarding, security guidance) into templates, validators, and guided workflows rather than static documents
- Capture tribal knowledge from engineering, product, and operations, and turn it into playbooks, decision guides, and self-service paths
- Measure outcomes such as time-to-first-success, support deflection, repeat questions, and AI answer quality, and use the data to decide what to build, fix, or retire
- Partner with Engineering, Product, Security, Developer Relations, and Partner Programs so every release ships documented, discoverable, and supportable
What we need to see:
- Bachelor's degree or equivalent experience, plus 8+ years in technical writing, developer documentation, or developer experience for complex software platforms
- Hands-on docs-as-code experience: Git, pull request review, Markdown/RST, static site generators (Sphinx, MkDocs, Docusaurus, or similar), and CI/CD
- Working proficiency in Python or similar to automate content tasks, transform data, and integrate with APIs
- Practical experience applying LLMs to content workflows (prompting, retrieval and grounding, output evaluation) and sound judgment about where AI can be trusted
- Information architecture skills: content modeling, taxonomy, and metadata for both navigation and machine retrieval
- Enough technical depth to read code and APIs, verify accuracy, and write working examples
- A systems mindset: you fix the class of problem, not just the instance
- A collaborative style: you turn design intent into working systems and give leads clear, constructive feedback grounded in implementation
Ways to stand out from the crowd:
- Experience building RAG pipelines, AI assistants, MCP servers, or agent skill and context libraries backed by documentation
- Documentation experience in graphics, simulation, robotics, or real-time systems; familiarity with USD, Omniverse, Isaac Sim, or ROS
- Content quality automation you've built, such as Vale or custom linters, doc test harnesses, or freshness monitoring
- Measurable reductions in support load or onboarding time through self-service knowledge systems
- Open source contributions or published work on docs-as-code, AI-assisted documentation, or knowledge engineering
You will also be eligible for equity and benefits.
This posting is for an existing vacancy.
NVIDIA uses AI tools in its recruiting processes.
NVIDIA is committed to fostering an inclusive work environment and proud to be an equal opportunity employer. As we highly value diversity in our current and future employees, we do not discriminate (including in our hiring and promotion practices) on the basis of race, religion, color, national origin, gender, gender expression, sexual orientation, age, marital status, veteran status, disability status or any other characteristic protected by law.Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for NVIDIA. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.