Head of Documentation / Lead Documentation Engineer

Mujin is a global leader in industrial automation, redefining supply chain efficiency through MujinOS—our intelligent operating system for robotics. At our core is Machine Intelligence (MujinMI), a unique approach that leverages real-time digital twins and advanced perception, planning, and control algorithms to achieve fully autonomous operations.

Our flagship product, MujinController, empowers users with a highly configurable, no-code interface. By integrating cutting-edge motion planning and computer vision, it enables seamless automation for complex applications such as palletizing, picking, and truck unloading.

Headquartered in Japan with a growing presence in the US, China, and Europe, we invite you to join a dynamic environment where you can shape the future of automation.

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