Success Measures

• Every priority workflow is supported by an accurate, tested how-to guide
• Guides are maintained alongside each platform release
• Published guides can be referenced by training curriculum without recreating procedural content
• Documentation gaps and stale content are tracked through a visible backlog
• Product users can complete common workflows independently

Ownership and Collaboration

This role owns procedural, task-based documentation as the single source of truth for product guidance. Curriculum, training, and enablement content build on these guides rather than recreating them.

• Curriculum lead: Owns learning architecture, exercises, assessments, and trainer materials, and partners with this role to keep training content grounded in the published guides.
• Subject matter experts: Help develop and review new and updated guides, particularly within Delivery. Every guide requires their sign off alongside GTM leadership before publication.
• Product and Engineering: Provide the core engineering and product concepts needed to create clear, customer-facing guidance and incorporate new features as they ship.
• GTM leadership: Prioritises which user guide topics are needed.

Essential Experience

• Demonstrable experience in technical writing, developer relations, or documentation engineering
• Curriculum, training, or technical documentation experience
• Strong proficiency with Markdown, and ideally MkDocs or a similar tool
• Experience working in MD or AsciiDoc files
• Experience with version control via GitHub
• Comfortable with docs as code workflows and CI/CD integration
• Familiarity with the Diataxis documentation framework (tutorials, how-to guides, reference, explanation)
• Comfortable using company docs guidelines and agentic writing skills
• Ability to write clear, concise prose that respects readers' time

How You Work

• You can assess documentation from the target reader’s perspective and ensure technically literate non-specialists can understand and complete the documented workflows independently.
• You can verify technical accuracy independently, without relying on engineers to write the content for you.
• You are a systems thinker who builds coherent information architectures rather than documenting features in isolation.
• You are comfortable coordinating across a wide set of subject matter experts, particularly within user-enabling Delivery.

Desirable Experience

• MkDocs, or a similar tool such as Mintlify or Zensical, plus Markdown and Sphinx
• A physical industry background is preferred, for example simulation, machine learning, design, or manufacturing.
• Demonstrated experience documenting APIs, SDKs, or developer tooling is a plus given the platform's technical depth.
• Background in simulation or engineering workflows.
• Familiarity with scientific computing libraries such as NumPy and SciPy.
• Understanding of how AI agents consume documentation, for example structured descriptions and tool schemas.
• Prior freelance experience in this space, including candidates who could convert to a permanent role and start with no notice period.

We value diversity and are committed to equal employment opportunity regardless of sex, race, religion, ethnicity, nationality, disability, age, sexual orientation, or gender identity. We strongly encourage individuals from groups traditionally underrepresented in tech to apply. To help make a change, we sponsor bright women from disadvantaged backgrounds through their university degrees in science and mathematics.

We collect diversity and inclusion data solely for the purpose of monitoring the effectiveness of our equal opportunities policies and ensuring compliance with employment and equality legislation. This information is confidential, used only in aggregate form, and will not influence the outcome of your application.