Head of Documentation / Lead Documentation Engineer

We are looking for a Head of Documentation / Lead Documentation Engineer to own the documentation system, tooling, and processes for Mujin OS - a complex software product in the industrial automation/robotics domain.

This role is responsible not only for writing and editing documentation, but for designing, implementing, and maintaining a sustainable documentation ecosystem that is deeply integrated into our engineering workflows. It owns documentation as a system and acts as the central point of accountability for documentation structure, tooling, and quality.

The ideal candidate has extensive writing experience as well as hands-on experience setting up docs-as-code systems, partnering closely with engineers, and enabling documentation to be authored, reviewed, and maintained across teams.

This role is intended to evolve into building or leading a documentation team over time.

Responsibilities:

Documentation Strategy & Ownership

• Own the end-to-end documentation strategy, including structure, standards, tooling, and long-term maintainability
• Define documentation audiences, document types, and information architecture (e.g. developer docs, operator manuals, API references, conceptual guides, internal docs)
• Act as the single accountable owner for documentation quality, consistency, and discoverability

Docs-as-Code & Tooling

• Design and maintain a docs-as-code workflow (e.g., Markdown/AsciiDoc, git-based authoring, CI-driven builds and previews)
• Select, configure, and evolve documentation tooling (static site generators, linters, preview environments, versioning strategies)
• Integrate documentation into the software development lifecycle, including PR-based documentation changes, release documentation, and versioned documentation tied to product releases

Automation & Generated Documentation

• Define what documentation should be:
  • Written manually
  • Authored by engineers
  • Automatically generated from source (APIs, schemas, configs, code)
• Set up and maintain pipelines for generated documentation (e.g. OpenAPI, Sphinx, Doxygen, or custom tooling)
• Ensure generated documentation is usable, curated, and integrated into the overall documentation set

Collaboration with Engineering & Product

• Work closely with engineers, product managers, and UX designers to extract and validate technical information as well as define documentation responsibilities per component or feature
• Enable and guide engineers to contribute documentation through templates, contribution guidelines, review processes
• Establish clear expectations for documentation ownership and updates as part of feature development

Writing, Editing, and Review

• Write and edit high-impact documentation where structure, clarity, or system-level understanding is critical
• Review and improve API documentation, tutorials and onboarding materials, troubleshooting guides, release notes
• Review and improve UI text, warnings, labels, and onboarding flows for the web-based controller UI

Standards, Quality, and Governance

• Define and maintain documentation standards, style guides, terminology, and voice/tone guidelines
• Establish review and quality assurance processes for documentation changes
• Balance modern software documentation practices with industrial documentation expectations, including safety-related content where applicable

Internationalization & Scaling

• Design documentation workflows that support internationalization and localization
• Collaborate with localization teams or vendors to ensure technical accuracy across languages
• Prepare the documentation system to scale with product complexity and team growth

Requirements:

• Significant experience owning or leading documentation for a complex software product
• Excellent writing and editing skills, with the ability to explain complex systems clearly and precisely
• Hands-on experience with docs-as-code workflows (git-based authoring, CI-based publishing)
• Strong understanding of software development concepts, APIs, and modern development workflows
• Ability to work as a peer with engineers and discuss architecture, interfaces, and trade-offs
• Awareness of how classical industrial automation systems (PLC-based environments, hardware-centric systems, industrial HMIs) are traditionally documented
• Ability to translate between classical industry expectations (procedural, safety-oriented, hardware-first documentation) and modern software-style documentation (conceptual models, APIs, workflows, examples)
• Experience documenting systems used by engineers, integrators, and operators with differing expectations
• Experience defining documentation standards and enforcing them across teams
• Ability to drive adoption of documentation practices without relying on formal authority
• Comfortable acting as a process designer and change agent, not just a content producer

Preferred Skills and Competencies:

• Professional experience in robotics, manufacturing automation, logistics systems, or adjacent industrial software domains
• Experience designing or maintaining documentation platforms rather than only contributing content
• Experience with Markdown, AsciiDoc, static site generators
• Experience with CI/CD systems
• Experience editing or curating automatically generated documentation
• Understanding of compliance-oriented or safety-adjacent documentation and how it intersects with software documentation
• Experience with information architecture, content strategy, or developer experience (DX)
• Ability to read and understand code (e.g. Python, C++, JavaScript/TypeScript)
• Experience working with Linux and command-line tools
• Familiarity with Docker, CI/CD pipelines, and software build systems
• Experience working in multilingual documentation environments

Why This Role Matters

• Our product is replacing and redefining traditional industrial automation systems. The documentation must therefore bridge decades of industry expectations while supporting modern, software-driven workflows.