Content Engineer
The Opportunity
We're looking for a Content Engineer to make Pydantic better, not just to describe it. When a concept is hard to write down or an API is hard to show in an example, that's usually a signal the product is wrong, and we want someone who fixes both.
For an open-source developer-tools company, docs aren't collateral bolted on after the fact. They are the product surface. Pydantic Validation is imported 500M+ times a month, Pydantic AI is the fastest-growing agent framework, and Pydantic Logfire is the observability platform the AI engineering ecosystem is converging on. Each is only as good as the docs that get a developer, or their coding agent, from zero to working.
This is not a technical-writing role in the traditional sense. Prose is the cheap part now; an LLM can draft it. The value is judgment: knowing what's true, deciding what to cut, and spotting where the product itself is the problem. We want an engineer who happens to write exceptionally well, ships to the same repos as everyone else, and has strong opinions about both the tooling and the product.
This role might appeal to you if you've worked as a:
- Content Engineer or Docs Engineer
- Developer Experience or DevRel engineer who kept drifting toward the product and the infrastructure
- Technical writer who taught yourself to code and started opening PRs against the thing you were documenting
- API or SDK owner who cares more about a developer's first hour than the fiftieth feature
You want to get in early at a company with genuine product-market fit, where the leverage on great docs, and on the product feedback that comes with them, is enormous.
