Technical Documentation and Content Engineer, Claude Docs

Anthropic · San Francisco, CA | New York City, NY · Technical Education · listed July 24, 2026

The shape of it

Seniority
Not stated
Where
Hybrid
Stated pay
$270,000 – $320,000 USD
Requirements listed
7
Length
1,275 words

In the posting’s own words

You will own the documentation for Claude apps . This role goes far beyond traditional technical writing. The docs estate of Claude Docs spans multiple product surfaces ( Claude.ai , Cowork, Claude Tag, Claude Science, etc.) written by many hands across many teams. You'll own the unification layer: the architecture, the standards, and — centrally — the engineered systems that keep quality high at scale.

What it asks for · 7

  • 5+ years at the intersection of documentation, user education, and software engineering
  • Knowledge of evaluation frameworks or observability for AI-powered systems
  • Experience guiding a documentation platform migration or redesign
  • Content analytics and experimentation experience
  • Modern software development practices: version control, CI/CD, testing
  • Excellent technical writing and editing — enough craft to set and standardize a high quality bar
  • Experience establishing editorial standards and information architecture for a substantial technical documentation site

Also a plus

  • Software engineering experience: you can design, build, ship, and maintain production tooling, with proficiency in Python and/or TypeScript/JavaScript
  • Experience building automated documentation or content systems — pipelines, CI checks, AI-assisted maintenance
  • Experience building AI applications or AI-powered tooling with LLMs

What the job covers

  • Own the information architecture, style, and editorial standards of the Claude Docs site as a single unified surface
  • Design, build, and run automated documentation systems: self-healing pipelines, AI-assisted review and maintenance, and quality guardrails that catch problems before readers do
  • Establish the conventions and tooling product teams adopt to keep their own documentation accurate and consistent
  • Establish and maintain the style guide, a standard set of content types, and clear workflows for creating, reviewing, and publishing documentation
  • Curate contributions from across the company: edit for clarity and consistency, prune what's stale, and shape how new content fits the whole
  • Define and track measures of content quality and discoverability, and use reader feedback and analytics to drive improvements

Tools and skills named

Ways of working
  • Technical writing18×
  • Testing2×
Languages
  • JavaScript2×
  • Python2×
  • TypeScript2×
Cloud & infra
  • CI/CD2×
  • Observability2×
Data
  • Experimentation2×
Models & research
  • LLM2×

Words the posting leans on

  • documentation15×
  • experience12×
  • content11×
  • systems8×
  • quality7×
  • standards7×
  • tooling7×
  • claude6×
  • docs6×
  • maintenance5×
  • set5×
  • ai-powered4×
  • analytics4×
  • automated documentation4×
  • design build4×
  • editorial standards4×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Anthropic

every open role at Anthropic

How this page was made

An automated read of a public job posting, fetched August 25, 2026 and last changed by Anthropic on August 21, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.