Software Technical Writer
See all open roles at sonarsource →
Likely real
- 114 open roles at this company in 30 days (mass-hiring blitz)
- no salary disclosed (correlates with ghost postings)
See your fit for this role and apply with a truthfully tailored résumé.
About the role
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
Nice to Have
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
Stop applying to ghosts.
OyaPilot surfaces only verified, real jobs, scores your fit, and tailors your application truthfully.