Head of Documentation
Job description
About the role
We are seeking a Head of Documentation / Lead Documentation Engineer to define and own the documentation system, tooling, and processes for Mujin OS, a complex software product in the industrial automation and 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. The hire will own documentation as a system and act as the single accountable owner for documentation structure, tooling, and quality. The ideal candidate brings extensive writing experience and 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, shaping how Mujin communicates its automation technology to the world.
Key facts
What you'll do
Define and execute a comprehensive documentation strategy for Mujin OS, including structure, standards, tooling, and long-term maintainability across all document types.
Own the information architecture and documentation ecosystem, defining audiences, document types, and logical flows for developer docs, operator manuals, API references, conceptual guides, and internal documentation.
Act as the single accountable owner for documentation quality, consistency, discoverability, and usability across the product lifecycle.
Design, implement, and maintain a docs-as-code workflow using Markdown or AsciiDoc, git-based authoring, and CI-driven builds and previews to enable scalable and versioned documentation.
Select, configure, and evolve documentation tooling, including static site generators, linters, preview environments, and versioning strategies aligned with software release practices.
Integrate documentation into the software development lifecycle by enabling PR-based documentation changes, release documentation, and versioned documentation tied to product milestones.
Define what documentation should be written manually, authored by engineers, or automatically generated from source artifacts such as APIs, schemas, configurations, and code.
Set up and maintain pipelines for generated documentation using tools such as OpenAPI, Sphinx, Doxygen, or custom tooling, ensuring outputs are usable and integrated into the overall documentation set.
Collaborate closely with engineers, product managers, and UX designers to extract and validate technical information and define documentation responsibilities per component or feature.
Enable and guide engineers to contribute documentation through templates, contribution guidelines, review processes, and clear ownership models embedded in the development workflow.
Write and edit high-impact documentation where structure, clarity, or system-level understanding is critical for complex automation scenarios.
Review and improve API documentation, tutorials and onboarding materials, troubleshooting guides, release notes, and UI text, warnings, labels, and onboarding flows for the web-based controller UI.
Define and maintain documentation standards, style guides, terminology, and voice/tone guidelines to ensure coherent communication across all materials.
Establish review and quality assurance processes for documentation changes, balancing modern software documentation practices with industrial documentation expectations, including safety-related content where applicable.
Design documentation workflows that support internationalization and localization, and collaborate with localization teams or vendors to ensure technical accuracy across languages.
Prepare the documentation system to scale with increasing product complexity and team growth, creating the foundation for a potential documentation team.
Requirements
Candidates must have extensive writing experience and hands-on experience setting up docs-as-code systems in a software development context.
The hire must be capable of partnering closely with engineers to enable documentation authorship, review, and maintenance across multiple teams using version-controlled workflows.
You must be able to define documentation audiences, document types, and information architecture for both technical and operational readers in an industrial automation environment.
Experience designing, implementing, and maintaining documentation tooling and pipelines is essential, including familiarity with static site generators and CI-driven documentation builds.
You should have a strong understanding of documentation standards, style guides, terminology, and versioning, and be able to balance modern software practices with industrial documentation expectations.
The role requires ownership of documentation quality, consistency, and discoverability, including the ability to establish review and quality assurance processes for documentation changes.
Experience working with generated documentation from source code and APIs, and integrating those outputs into a cohesive documentation system, is required.
You must be comfortable working in an English-language environment at Mujin headquarters in Tokyo, Japan, and be able to collaborate effectively with distributed engineering and product teams.
Nice to have
Experience contributing to or enabling engineering documentation culture within technology-driven organizations.
Familiarity with industrial automation, robotics, or safety-critical systems and relevant documentation practices.
Knowledge of localization workflows and tools that support internationalization of technical documentation.
Experience with modern documentation platforms, static site generators, and automated documentation generation from APIs and code.
Practical notes
This role is based at Mujin HQ in Tokyo, Japan and requires full-time engagement in English.
Travel, visa, or specific hour requirements are not detailed in this source material.