we are a modern, full-stack observability monitoring platform transforming how businesses process and understand their data. Our unique architecture powers in-stream analytics without reliance on expensive indexing or hot storage. We specialize in comprehensive monitoring of logs, metrics, trace, and security events with features such as APM, RUM, SIEM, Kubernetes monitoring, and more, all enhancing operational efficiency and reducing observability spend by up to 70%.
The role, in one line: You'll own real areas of the company documentation end to end – and you'll do it with a modern, AI-augmented toolchain that lets one writer move like a small team.
What you'll actually do
Own areas end to end. You take a product surface – OpenTelemetry, RUM, a query language – and own its docs and their structure: landing pages, tiles, wizards, navigation. Not just published, but accurate, current, trusted, and held to a measurable bar through review and automated eval suites.
Turn complexity into clarity, in every medium. You distill dense, jargon-heavy material into content users follow on the first read, edit until nothing is wasted, reach for diagrams, screenshots, or GIFs when words can't, and shape in-product UI copy so the whole experience reads as one coherent voice.
Work docs-as-code, with AI as a force multiplier. You write in Markdown, live in Git (branches, PRs, reviews), and ship to a static site. You build and use custom AI tooling – skills, doc-generation from PRs, evals, linting – and help shape the workflows and infrastructure behind it.
Make docs readable by machines, too. Our content feeds LLMs and AI assistants as much as humans. You'll help drive our LLM-readiness work – llms.txt, the docs MCP server, and structuring content so AI tools consume it accurately. It's a genuine differentiator of this role.
Go to the source and close the loop. You read specs, proto definitions, and code to verify what's true and use the product yourself rather than trusting secondhand summaries. You turn support tickets and customer-success conversations into improvements, and partner with engineers, PMs, and writers across teams and cultures to keep docs aligned with what's shipping.
The role, in one line: You'll own real areas of the company documentation end to end – and you'll do it with a modern, AI-augmented toolchain that lets one writer move like a small team.
What you'll actually do
Own areas end to end. You take a product surface – OpenTelemetry, RUM, a query language – and own its docs and their structure: landing pages, tiles, wizards, navigation. Not just published, but accurate, current, trusted, and held to a measurable bar through review and automated eval suites.
Turn complexity into clarity, in every medium. You distill dense, jargon-heavy material into content users follow on the first read, edit until nothing is wasted, reach for diagrams, screenshots, or GIFs when words can't, and shape in-product UI copy so the whole experience reads as one coherent voice.
Work docs-as-code, with AI as a force multiplier. You write in Markdown, live in Git (branches, PRs, reviews), and ship to a static site. You build and use custom AI tooling – skills, doc-generation from PRs, evals, linting – and help shape the workflows and infrastructure behind it.
Make docs readable by machines, too. Our content feeds LLMs and AI assistants as much as humans. You'll help drive our LLM-readiness work – llms.txt, the docs MCP server, and structuring content so AI tools consume it accurately. It's a genuine differentiator of this role.
Go to the source and close the loop. You read specs, proto definitions, and code to verify what's true and use the product yourself rather than trusting secondhand summaries. You turn support tickets and customer-success conversations into improvements, and partner with engineers, PMs, and writers across teams and cultures to keep docs aligned with what's shipping.
Requirements:
3+ years writing technical documentation in a fast-paced, agile software environment.
Impeccable writing and an keen eye for detail – you make complex topics simple and you don't let errors through.
Driven and genuinely curious. You explore tools independently, experiment to understand how they work, and chase down the why. You can read and reason about code – not a developer, but completely at home in technical conversations.
Comfort working alongside engineers in a developer-first product culture – you understand how they think, speak, and work.
Independent and self-driving. You initiate change rather than wait for it, you take ownership, and you raise the bar for the people around you.
Great to have
Prior SaaS and observability experience.
Hands-on knowledge of OpenTelemetry (OTEL).
Familiarity with SQL (or a comparable query language) under your belt.
Deep product understanding – the kind that lets you anticipate what a user needs before they ask.
Proven experience with advanced AI tooling – and using it to improve documentation infrastructure and processes, not just to draft prose.
Developer experience of any kind is a bonus.
A relevant technical degree (CS, technical writing, data science).
The toolchain
Git MkDocs / Docusaurus Jira / Atlassian Notion Slack AI tooling (Claude Code and custom skills).
3+ years writing technical documentation in a fast-paced, agile software environment.
Impeccable writing and an keen eye for detail – you make complex topics simple and you don't let errors through.
Driven and genuinely curious. You explore tools independently, experiment to understand how they work, and chase down the why. You can read and reason about code – not a developer, but completely at home in technical conversations.
Comfort working alongside engineers in a developer-first product culture – you understand how they think, speak, and work.
Independent and self-driving. You initiate change rather than wait for it, you take ownership, and you raise the bar for the people around you.
Great to have
Prior SaaS and observability experience.
Hands-on knowledge of OpenTelemetry (OTEL).
Familiarity with SQL (or a comparable query language) under your belt.
Deep product understanding – the kind that lets you anticipate what a user needs before they ask.
Proven experience with advanced AI tooling – and using it to improve documentation infrastructure and processes, not just to draft prose.
Developer experience of any kind is a bonus.
A relevant technical degree (CS, technical writing, data science).
The toolchain
Git MkDocs / Docusaurus Jira / Atlassian Notion Slack AI tooling (Claude Code and custom skills).
This position is open to all candidates.
