Software Technical Writer

ppbWhat you will do /b /p /pliPlan, write, and maintain high-quality documentation for developer audiences: getting-started guides, how-tos, conceptual explanations, and release notes /li li pWork in a docs-as-code workflow — authoring in Markdown, submitting PRs, reviewing diffs, and running docs through the same CI pipeline as code /p /li li pUse AI tools to accelerate research, drafting, and content auditing — and take full ownership of the quality and accuracy of the output /p /li li pCollaborate with engineers to document new features accurately and on time, often working from specs, early builds, and code review comments /p /li li pVerify, and maintain code samples (in languages relevant to our integrations) to ensure they compile, run, and stay current with product changes /p /li li pAudit and improve existing documentation for accuracy, completeness, structure, and voice /p /li li pHelp evolve the team's style guide, information architecture, and content standards /p /li li pMentor other writers and serve as a technical resource for docs-adjacent questions from engineering /p /li ppbExperience you will need: /b /p /p liProven track record of creating technical content for developer audiences (provide portfolio/examples) /li li pFluency in a docs-as-code workflow: Markdown or similar markup, Git (branching, PRs, rebasing), and working inside a repo as a first-class collaborator /p /li li pStrong software development or DevOps background with proficiency in some programming languages /p /li li pFluency in a docs-as-code workflow: Markdown or similar markup, Git (branching, PRs, rebasing), and working inside a repo as a first-class collaborator /p /li li pComfort using AI tools (Claude, Codex, Copilot, etc.) to augment your workflow, with a clear-eyed approach to validating AI-generated content /p /li li pExperience working cross-functionally with engineering and product teams to ship documentation alongside features /p /li li pStrong instinct for information architecture: you know the difference between a tutorial, a how-to, a reference, and a concept and when to use them /p /li ppbbNice to Have /b /b /p /p li pSolid understanding of DevOps practices including CI/CD pipelines /p /li li pExperience writing documentation for the agentic SDLC /p /li li pExperience with code quality, security, and testing concepts including SAST, DAST, code coverage, and vulnerability management /p /li li pDemonstrated 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 /p /li ppbbIn-office culture /b /b /p /p pWe're intentional about this. We believe the best teams are built in the room together. Three anchor days — Mondays, Tuesdays, and Thursdays — create the collaboration rhythm that makes a hub office worth having. /p pCandidates need to be genuinely based in the location the role is posted — if that's not where you are today, we're happy to support relocation for the right person. /p ppbbWe value diversity, equity, and inclusion /b /b /p /p pAt Sonar, we believe that our diversity is our strength. We are a global company that values and respects different backgrounds, perspectives, and cultures. We are committed to fostering a diverse and inclusive work environment where everyone feels valued and empowered to contribute their best. We are proud to be an equal opportunity employer and welcome all qualified applicants, regardless of race, color, religion, gender, gender identity or expression, sexual orientation, national origin, genetics, disability, age, or veteran status. /p pIf you need any accommodation, please reach out to us at . /p pAll offers of employment at Sonar are contingent upon the results of a comprehensive background check and reference verification conducted before the start date. /p pApplications that are submitted through agencies or third party recruiters will not be considered. /p