About the role
You own a developer's first hour with our protocols: the SDK, the sample app, the docs, and the loop back from everyone who tries to build on them. The measure is how long it takes somebody to get a working integration, and every confusing doc you fix instead of answering twice moves it.
What we need to see
- You have grown a developer community around an open protocol or SDK
- You write code and prose to the same standard
- You would rather fix a confusing doc than answer the same question twice, and you do
- Genuine interest in agent interoperability rails such as MCP and A2A
Nice to have
- You have maintained a widely used open-source library
- Conference speaking
- Experience turning community feedback into specification changes
What winning looks like
- Time from a developer's first read to a working integration
- External implementations and contributions
- Documented issues that turn into spec fixes rather than support tickets
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.