Developer Advocate

Most of what makes BatScrape worth using is invisible until someone explains it. Versioned contracts, golden vectors, cursor state in the core — each is a paragraph away from being obvious and a paragraph away from being ignored.

What you would work on

• Reference docs that stay correct because they are generated from the contract.
• Worked examples that run, in CI, on every release.
• Posts about the engineering, not about the company.
• Being the person who notices the API is confusing before a customer does.

What we look for

• You write code and you write prose, and you do not treat the second as the consolation prize.
• You have shipped developer documentation someone actually used.
• You can hold an opinion about an API design and argue it with engineers.

What this is not

A conference circuit. There is travel if you want it and none if you do not.