Senior / Staff Documentation Engineer (AI & Docs Tooling)

TetraScience

13d•Remote

About The Position

TetraScience is the Scientific Data and AI Company building Tetra OS, the operating system for scientific intelligence. We help the world’s leading life sciences firms turn fragmented scientific data into AI-native assets and scientific workflows that accelerate discovery, development, and manufacturing. TetraScience’s growing ecosystem of strategic partners includes NVIDIA, Databricks, Thermo Fisher Scientific, Snowflake, Google, and Microsoft. The Role TetraScience is the scientific data and AI company. Our documentation is how customers, from bench scientists to platform engineers, learn to build on the platform, and increasingly it is how AI agents consume the platform too. We are looking for a Documentation Engineer to own documentation as a system: the pipelines that build and publish it, the AI-augmented workflows that generate drafts for human review and refinement, the review and publish process, and the infrastructure that makes it reliably consumable by AI agents. This is primarily a documentation systems role, not only a writer who uses tools. The differentiator is building and owning the systems that produce, validate, publish, and AI-enable our documentation. Strong writing and editorial judgment are still required, but the center of gravity is tooling and systems, and a large portion of the day to day is building. You will lead, not just maintain. You will take our existing docs-as-code foundation and AI-assisted documentation workflows and grow them into a docs-as-AI-agents capability that is differentiated for a life-sciences AI platform. You will still own editorial quality and the release-notes cadence, but you will spend most of your time building leverage rather than absorbing work.

Requirements

5+ years owning documentation tooling, content engineering, or developer documentation for a developer-platform or enterprise B2B product.
Engineering ability in a scripting or web stack (for example Python, TypeScript, or JavaScript) and real fluency with docs-as-code: Git, pull-request review, CI/CD, and a static-site or CMS publishing pipeline.
Hands-on experience building AI-augmented or LLM-backed workflows: integrating LLM APIs, AI-assisted authoring, and structuring content for AI consumption.
Ability to read and reason about a real codebase and API surface well enough to document it accurately and to build tooling against it.
Strong editorial judgment: you can take a dense engineering change and make it clear, correct, and customer-safe.
Bachelors or Masters degree in a technical field, or equivalent practical experience.

Nice To Haves

Experience making documentation consumable by AI agents (llms.txt, content negotiation, RAG pipelines, MCP servers)
Experience in BioPharma or scientific software, or in regulated and validated (GxP) environments.
Experience generating reference docs from OpenAPI or related specifications with two-way Git sync.
Developer-relations or developer-education exposure.

Responsibilities

Own the documentation site and its publishing as software: the docs-as-code repo, the CI/CD publishing pipelines, build performance, and automated link, structure, and quality checks.
Build and grow AI-augmented documentation workflows: AI-assisted drafting, summarization, classification, consistency and staleness checks, and a feedback loop that improves generation quality over time, all with human oversight.
Build our docs-as-AI-agents position: structure and transform content so AI systems can reliably chunk, index, and reason over it, and stand up and maintain MCP-style interfaces so agents and assistants consume our docs accurately.
Generate reference documentation from source (OpenAPI and related specs) and keep docs in lockstep with the platform as code changes.
Lower the barrier for internal contributors (PMs, squad leads, engineers) to ship their own docs through the docs-as-code workflow, and reduce repetitive work through automation.
Own the release-notes and customer-communications cadence that goes out with every platform release, and run the SME review that keeps it accurate and on time.
Own the documentation style guide, hold the review-and-publish gate, and keep the team runbook current so the function is not dependent on any one person.