Associate Technical Writer

We're looking for an Associate Technical Writer who's comfortable working in a docs-as-code environment and can partner with AI tools (e.g., Claude) for all aspects of the work — not just writing, but operating within an automated documentation pipeline. This is an opportunity to own documentation end-to-end within a modern, AI-assisted workflow, working closely with engineering, product, and support stakeholders to keep a shared source of truth accurate and consistent.

Create and maintain user documentation using a docs-as-code workflow — Markdown/YAML source files, Git-based version control, and CI-driven publishing (e.g., Jekyll). Independently own small documentation tickets and projects end-to-end, from research through PR merge. Use AI-assisted tools (Claude or equivalent) to draft, summarize, restructure, or QA content, while critically reviewing and editing AI output rather than publishing it as-is. Conduct research and gather technical information from product specs, engineering discussions, and existing docs to fill knowledge gaps. Follow and help enforce documentation standards, style guides, and metadata conventions (e.g., structured fields for error messages, FHS-style rule sets) across a shared source of truth. Work in Git-based workflows: branching, raising PRs, responding to review comments, and triggering automation for doc builds/publishing. Collaborate with engineering, product, and support stakeholders to validate technical accuracy before publishing. Flag ambiguous, unverified, or inferred content rather than publishing unconfirmed information.

Strong written English and ability to simplify technical concepts for end users. Basic familiarity with Markdown, Git (clone/branch/commit/PR), and a willingness to use docs-as-code tooling. Comfort using AI writing/review tools as part of a daily workflow (prompting, verifying, editing output), including the ability to create and manage Claude skills. Ability to read and interpret product UI, API docs, or basic YAML/JSON structures well enough to document them. Detail-oriented, especially around consistency (terminology, tone, formatting) across a large, distributed content set. 0-2 years of experience in technical writing, content, or a related field; internships or academic writing experience acceptable. Exposure to a ticketing/PM tool (Jira, Confluence) and Slack-based collaboration. Intermediate AI skills creation.