Software Technical Writer
Position description
We're looking for a Senior or Staff Technical Writer to join the Sonar documentation team. We want someone who thinks like a developer, writes like a communicator, and builds documentation the same way engineers build software.
You'll own developer-facing content across the SonarQube product suite: conceptual guides, integration tutorials, and release documentation. You'll work directly alongside engineers and PMs, live in the same repos and PRs they do, and be expected to catch a broken code sample the same way you'd catch a grammatical error. You'll also shape how we think about documentation as a discipline - owning tooling decisions, defining style and structure, and raising the bar for the whole team.
As a Software Technical Writer, you will own developer-facing content across the SonarQube product suite. Your work will directly shape how practitioners using Sonar products-including developers, DevOps, and platform engineers-approach code quality and security. You will be the trusted expert, translating complex capabilities into practical knowledge. By crafting compelling, hands-on educational content, such as conceptual guides, in-depth tutorials, how-to-guides, etc, to help enable millions of practitioners to write high quality, secure code. You won't just explain features; you will define the developer's journey with our products, establishing Sonar as an essential part of their Agentic SDLC workflow. You'll also shape how we think about documentation as a discipline. You will influence tooling decisions, help define style and structure, and raise the bar for the whole team.
What you will do
- Plan, write, and maintain high-quality documentation for developer audiences: getting-started guides, how-tos, conceptual explanations, and release notes
Work in a docs-as-code workflow - authoring in Markdown, submitting PRs, reviewing diffs, and running docs through the same CI pipeline as code
Use AI tools to accelerate research, drafting, and content auditing - and take full ownership of the quality and accuracy of the output
Collaborate with engineers to document new features accurately and on time, often working from specs, early builds, and code review comments
Verify, and maintain code samples (in languages relevant to our integrations) to ensure they compile, run, and stay current with product changes
Audit and improve existing documentation for accuracy, completeness, structure, and voice
Help evolve the team's style guide, information architecture, and content standards
Mentor other writers and serve as a technical resource for docs-adjacent questions from engineering
Experience you will need:
- Proven track record of creating technical content for developer audiences (provide portfolio/examples)
Fluency in a docs-as-code workflow: Markdown or similar markup, Git (branching, PRs, rebasing), and working inside a repo as a first-class collaborator
Strong software development or DevOps background with proficiency in some programming languages
Fluency in a docs-as-code workflow: Markdown or similar markup, Git (branching, PRs, rebasing), and working inside a repo as a first-class collaborator
Comfort using AI tools (Claude, Codex, Copilot, etc.) to augment your workflow, with a clear-eyed approach to validating AI-generated content
Experience working cross-functionally with engineering and product teams to ship documentation alongside features
Strong instinct for information architecture: you know the difference between a tutorial, a how-to, a reference, and a concept and when to use them
Solid understanding of DevOps practices including CI/CD pipelines
Experience writing documentation for the agentic SDLC
Experience with code quality, security, and testing concepts including SAST, DAST, code coverage, and vulnerability management
Demonstrated ability to read, write, and debug code - whether through writing verified code samples in technical articles, a background as a developer or software engineer, or equivalent hands-on experience