Skip to content
Anthropic

Docs Lead, Platform

San Francisco, CA | New York City, NY; San Francisco, CAOnsite · United States
Staff · Engineering & Design - Product
POSTED 16 NOVVERIFIED 57M AGO
Apply Ask
Role
1 days opentrue age
Closes in ~69d at the median (70d)
Posted 16 Nov · n=128
Payats field
$365k–435kposted
▲ +67% vs market median $240k
$190k$445k
Market p25–p75
$205k–$284k
Anthropic p25–p75
$403k–$445kn=52
H-1B median · Software engineering
$190k
SF Bay Area · n=1188 · 365d to 15 Nov
CompanyAnthropic →
655open roles
Opened · 30d
+98
Closed · 30d
−133
Signal
● Steady−35 net
17d of snapshots · 30d window
Market
9,210open · Staff Software engineering
Opened · 7d
+6797% of open
All software engineering
75,001open
All tracked boards · live 18 Nov · n=9,210
Visa
191H-1B LCAs · FY26
Median wage
$190k
UK licensed sponsor
✓Worker (A rating)
LCAs FY26 · n=191 · to 2026-06-22
LLMs

About Anthropic

Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems.

About the role

As Platform Docs Lead at Anthropic, you will be the single-threaded owner of developer documentation for the Claude Platform. You'll own the information architecture, the content, and the overall experience of platform.claude.com/docs — from a developer's first quickstart to the reference page they keep open in a pinned tab.

This role sits on the DevX team and is closer to DevRel than to traditional technical writing. The job is taste, judgment, and end-to-end developer empathy in addition to strong writing skills: you'll be expected to build with the Claude API yourself, understand the product firsthand, and turn that understanding into documentation developers genuinely love.

You'll also own documentation written for AI agents and contribute to the skill that teaches Claude how to help developers use the Claude API. Writing for an LLM reader is a new craft, and you'll be one of the people defining what good looks like.

Key responsibilities

Set and hold the quality bar for every page on platform.claude.com/docs — clarity, correctness, completeness, voice

Own the information architecture: structure the docs so developers and agents find what they need on the first try, and restructure when the product evolves underneath it

Write and rewrite the highest-leverage pages yourself; review and edit contributions from product, engineering, and DevRel partners

Own docs for new launches end-to-end, from early PRD through GA

Write docs for agents as well as humans

Ship code on the Claude API regularly so your understanding of the developer experience is firsthand, not secondhand

Contribute to the claude-api skill, and author and maintain related docs-for-agents artifacts, defining how documentation should be written for LLM consumers

Act as the primary customer of our internal docs-automation tooling, with a calibrated point of view on where Claude accelerates docs work and where human judgment is the bottleneck

Build feedback loops from support tickets, community channels, and product analytics into docs improvements, and measure whether those improvements actually reduce confusion

Partner closely with the DevX engineers who own the docs platform to shape the reading experience, navigation, search, and in-product docs surfaces

Translate recurring developer friction into concrete product and API feedback when documentation alone can't fix it

Minimum qualifications

You've been the end-to-end owner (not just a contributor) of a developer-facing surface like docs, SDKs, quickstarts, or a content program: setting a quality bar, holding it without being chased, and saying no to things that don't meet it

You're an excellent technical writer. You can take a confusing page and make it clear, take a correct page and make it useful, and explain why each change made it better

You have strong information architecture skills and can articulate why a docs site is structured well or badly within minutes of landing on it

You're hands-on technical. You write and read code in at least one programming language, you've shipped working software on top of APIs, and you can hold your own in a design discussion with engineers

Preferred qualifications

Background in developer relations, developer experience, developer education, or API product teams

Experience owning docs or developer content at an API-first or developer-tools company

Genuine curiosity about building with LLMs and a calibrated, non-hype view of what they're good at today

Experience writing content intended for LLM consumption (skills, system prompts, retrieval corpora)

Background in information architecture, UX writing, or content design

Experience working with docs-as-code toolchains and contributing to docs infrastructure

Source · AnthropicFirst seen 16 NovOriginal ↗