Lead developer documentation for the Claude Platform, ensuring clarity and usability for developers.
Posted by employer 1 day ago
First seen on Joblaze 1 day ago
Last verified on the company career page 1 day ago
Skills & Technologies
What you'll build
Must have
Nice to have
Practical constraints
Requirements
Not disclosed in this posting: years of experience.
Benefits
Joblaze summary
In the role of Platform Docs Lead at Anthropic, the individual will manage the developer documentation for the Claude Platform, ensuring clarity and usability from quickstart guides to detailed reference materials. This position requires strong technical writing skills, a solid understanding of information architecture, and hands-on experience with APIs and coding. It is well-suited for someone with a background in developer relations or experience in API-focused environments, who can effectively translate complex concepts into accessible documentation. The role emphasizes collaboration with the DevX team to enhance the overall developer experience.
Joblaze insights
Quick facts
From the original posting
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.
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
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
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
Public writing that demonstrates your voice (blog, newsletter, talks, open-source docs)
The annual compensation range for this role is listed below.
Standard company text repeated across Anthropic's postings is omitted here.