Staff Technical Writer | Remote | Germany

There are more than 700,000 active installations of Grafana around the globe, monitoring everything from beehives to climate change in the Alps. The instantly recognizable dashboards have been spotted everywhere from a SpaceX launch and Minecraft HQ to Wimbledon and the Tour de France. Grafana Labs also helps companies including Bloomberg, JPMorgan Chase, and eBay manage their observability strategies with full-stack offerings that can be run fully managed with Grafana Cloud, or self-managed with Grafana Enterprise Stack. The Grafana stack has grown to include more open-source projects, including Grafana Loki (for logs) and Grafana Tempo (for traces) and Grafana Mimir (for metrics).

We’re looking for a Staff Technical Writer to create documentation and learning content that helps people adopt and master Grafana’s observability products. You’ll work with engineers, product managers, and the Grafana writing team to produce content for a range of products and audiences, from first-time users to experienced practitioners. Because our products and priorities evolve, we’re looking for someone who learns new technical domains quickly.

AI is part of how this team works. We use AI-assisted workflows and tools throughout the content lifecycle, from research and drafting to review, validation, and maintenance. You’ll use these tools every day and help the team get better at using them.

• →Plan, research, write, and maintain documentation and learning content (concepts, tasks, tutorials, references, and in-product learning) that supports adoption and long-term product mastery.
• →Use AI tools and workflows to work faster and at a higher quality: drafting, structuring, technical validation, consistency checks, and keeping content current. You apply human judgment to everything AI produces and take responsibility for its accuracy.
• →Contribute to the team’s shared AI workflows and skills, and look for ways to improve and automate how we create and maintain content as tools and models evolve.
• →Partner with engineers, PMs, and other stakeholders to understand product requirements, interview subject matter experts, and turn complex technical detail into clear, accurate content.
• →Test what you document. Run the software, follow your own procedures, and flag product and UX gaps you find along the way.
• →Let data guide your priorities. We have strong docs and learning analytics. You’ll use them, along with user feedback, to find content gaps, prioritize your work, and show the impact of what you ship.
• →Work with the documentation manager and other writers to improve information architecture, voice, and consistency across our docs, and to make information easy to find for both people and AI-driven search and assistants.
• →Manage several projects at once, using judgment to prioritize and communicate clearly when the plan changes.
• →Mentor teammates and share practices that raise the quality of the team’s work.

What experience would make someone be successful in this role?

• Experience writing or documenting enterprise or developer-facing software, with a portfolio or writing samples that show technical depth.
• Hands-on experience using AI tools and models in your writing workflow (such as LLM assistants, agentic coding tools, or custom prompts and skills), and the ability to explain how you evaluate and verify their output.
• Experience working with docs-as-code: command-line Git, GitHub (pull requests and reviews), Markdown, and common IDEs.
• Comfort working in technical environments. You can set up, run, and troubleshoot software yourself to verify what you write (for example, command line, containers, or Kubernetes, or a willingness to learn quickly).
• Experience collaborating with engineers and product managers to get accurate technical information.
• Experience working remotely and asynchronously on a distributed team.

• Curiosity about AI as a craft. You treat AI workflows as a professional skill. You experiment, share what works, and know where AI helps and where it doesn’t.
• Technical credibility. You care about accuracy, you learn new technical domains quickly, and you ask questions until you understand them.
• Strong judgment and editing skills. You can tell good content from plausible-sounding content, and you hold the line on quality.
• Ownership. You manage multiple projects and work well both independently and collaboratively.
• Clarity. You write concisely and plainly for readers of all experience levels.
• Bonus: Experience with observability, monitoring, or cloud-native tooling, or contributing to open source documentation.