Documentation Lead

About Artificial Help shape the future of specialty insurance At Artificial, we’re building the next generation of technology for the specialty (re)insurance market. Our mission is to transform how brokers and carriers operate in complex markets by removing operational barriers and enabling smarter, faster decision-making. We use modern technology to solve real challenges for some of the world’s leading brokers and insurers. By automating the repetitive and structuring the complex, we help our partners unlock new opportunities for innovation and growth. You’ll be joining a collaborative team that values curiosity, ownership, and continuous learning. We work in an environment where ideas are heard, support is built-in, and outcomes matter. Everyone here has the chance to make a tangible impact on our products, our customers, and the industry. We've just raised $45M (£33M) in Series B funding from lead investor CommerzVentures, new investor Move Capital, as well as all existing shareholders. This investment round gives us the room to grow with confidence, continue to innovate, and ensure that Artificial remains the first choice for brokers and carriers seeking a smarter way to trade digitally. Join us, and take the chance to be a part of something that will change the landscape of insurance for generations. About the role At Artificial, there are three primary sources of documentation we maintain: • Client-facing product documentation for insurance business users (brokers, underwriters and operations teams using our platform) • Our internal documentation site, which is our most heavily used documentation surface, built docs-as-code from the engineering repository and authored largely by engineers. • Our public API documentation, owned and authored by our Integrations team from auto-generated OpenAPI specifications. The below responsibilities break down how each of these three sources are to be managed. Responsibilities • Own the client-facing product documentation (1) end-to-end: strategy, information architecture, standards, tooling and content quality • Own the internal documentation gap backlog (2): • proactively identify potential gaps and triage incoming gap reports • route each one to the best-placed author and chase it to completion • write the content yourself where you're the right author • Steward the internal documentation site (2) and public API documentation (3): set the standards, information architecture and editorial bar for content authored by engineering and integrations teams, and keep the publishing pipelines healthy • Interview engineers about new features as they ship, and demystify them for non-technical readers before anyone has to ask • Act as editorial reviewer on documentation changes, catching duplication, misplacement and unclear writing before it ships • Write and maintain the highest-value client-facing content yourself: core product guides and release communications • Select, build and run the documentation toolchain, including docs-as-code workflows (static site generators, CI/CD, review gates) where they serve us best • Design and operate AI-assisted authoring pipelines that raise quality and throughput without sacrificing accuracy • Build the contribution model: templates, style standards and review processes that let product managers and engineers contribute content you curate rather than gatekeep • Partner with the Integrations team on API documentation: raise the quality of guides and examples around the auto-generated reference without taking authorship away from the experts • Partner with product and customer-facing teams so documentation ships with releases, not after them • Measure whether documentation is working: usage, search behaviour, support deflection and client fe