The Mission

We're looking for a Technical Writer to drive best practices and raise the bar for developer documentation across our Python libraries. You'll be shaping how engineers across industries such as Manufacturing, Aerospace, and Semiconductor understand and adopt our platform. Our tools allow Forward Deployed Engineers (FDEs) and customers to build and deploy deep learning surrogates that solve massive engineering challenges.

Your mission is to establish the standards, patterns, and workflows that enable our engineering teams to produce world-class documentation. You will define what "good" looks like, from API references to tutorials, and partner with engineers to get there.

Core Responsibilities

• Standards & Best Practice: Define and champion documentation standards, style guides, and quality benchmarks across our Python libraries.
• Versioned Docs: Implement a versioning strategy that aligns documentation with library releases, moving beyond "latest only" to support customers on older versions.
• Multi-Persona Architecture: Design an information architecture that serves multiple personas (Data Scientists, Platform Engineers, FDEs) without duplication or confusion.
• Agent-Ready Descriptions: Ensure all content is exposed in a way that is both consumable by Humans and Agents.
• Docs as Tests: Champion executable documentation patterns to ensure code samples are always accurate and runnable.
• CI Integration: Work with engineering to implement automated checks (e.g., blocking internal links in customer-facing docs).

The Tech Stack

• Documentation Tooling: MkDocs (or similar: Mintlify, Zensical), Markdown, Sphinx.
• Languages: Python (primary focus), familiarity with CLI tools.
• Version Control: Git, GitHub.

Who You Are

• Developer-Centric: You write for developers, not marketers. You understand that good docs are the difference between adoption and abandonment.
• A Systems Thinker: You don't just document features, you build coherent information architectures that scale across multiple libraries and personas.
• Technically Curious: You're comfortable reading Python code, running examples locally, and debugging when something doesn't work as documented. Use of LLM coding assistants is both allowed and encouraged.
• Automation-Minded: You believe docs should be tested, versioned, and deployed like code.

Qualifications

• Demonstrable experience in Technical Writing, Developer Relations, or Documentation Engineering.
• Strong proficiency with Python library documentation, MkDocs, and Markdown.
• Familiarity with the Diátaxis documentation framework (tutorials, how-to guides, reference, explanation).
• Demonstrated experience documenting APIs, SDKs, or developer tooling.
• Experience with docs-as-code workflows and CI/CD integration.
• Ability to write clear, concise prose that respects developers' time.

Bonus Points

• Background in simulation or engineering workflows.
• Experience federating documentation across polyrepo architectures.
• Familiarity with scientific computing libraries (NumPy, SciPy, etc.).
• Understanding of how AI agents consume documentation (structured descriptions, tool schemas).