Geneva

Salary
Posted
Jul 15, 2026
Location
Geneva
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A Senior or Staff Technical Writer role focused on developer-facing documentation for a suite of code quality and security products. Day-to-day work involves authoring conceptual guides, tutorials, and release notes in a docs-as-code workflow — using Markdown, Git, and CI pipelines — while verifying code samples and collaborating closely with engineering and product teams. The role also carries responsibility for shaping team-wide style, information architecture, and tooling standards, and suits someone with a strong software development or DevOps background.

Senior level · Austin-Round Rock-Georgetown, TX · Full-time

Must have (4)
MarkdownGitdocs-as-codeAI coding tools, LLM, Codex or GitHub Copilot
Nice to have (3)
CI/CDSASTDAST

“or” means any one of them counts — you don't need all of them.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

Why we read it this way (6)

Technical Writer roles do not map cleanly to a single SOC code. 15-1299 (Computer Occupations, All Other) is the best fit given the strong developer/DevOps background required and the docs-as-code, code-sample-verification nature of the work; 15-1252 (Software Developers) is a plausible runner-up given the expectation that the writer reads, writes, and debugs code.

The posting advertises the role as 'Senior or Staff' in the body text, but the title framing leads with 'Senior'; the level advertised in the title is set to Senior accordingly. The actual scope (owning tooling decisions, mentoring, shaping team standards) is consistent with a Senior-level individual contributor.

The role is explicitly in-office with three anchor days (Mon/Tue/Thu) at a hub location. The posting lists multiple global hubs (Austin, Bochum, Dubai, Geneva, London, Singapore, Tokyo, Washington D.C.) but no single location is specified for this posting; Austin is used as the primary US hub.

No compensation figures are provided in the posting.

AI tools (Claude, Codex, Copilot, etc.) are listed under required experience with firm language ('Comfort using AI tools… to augment your workflow'); specific tool names are captured as alternatives since any of them satisfies the requirement.

CI/CD, SAST, DAST, code coverage, and vulnerability management appear only under the 'Nice to Have' section.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗