Documentation Engineer

Lattice's API platform ships new endpoints faster than its reference docs can keep up, and an endpoint that shipped with documentation still wrong three weeks later is roughly how long stale docs tend to survive without one dedicated owner watching the gap.

You write and maintain reference documentation directly against the API surface, in Markdown, structured so a developer can find an answer without reading unrelated sections first just to locate one parameter. Information architecture takes up real time too: reorganizing navigation and cross-linking as the API grows, rather than letting new pages pile up wherever they were easiest to add. You also build small working examples that demonstrate each endpoint in context.

Required: hands-on API experience, strong Markdown-based writing skills, and an eye for information architecture rather than just clean prose. This is a mid-level seat, roughly three to five years of technical writing or documentation engineering experience, ideally including some API documentation specifically. Prior experience with this specific platform is not required — the first weeks are built around learning it from the inside.

The role is part-time at twenty hours a week. Based from Helsinki or remote within Europe, it coordinates asynchronously with the rest of the developer relations team. You report to the head of developer relations, and every documentation change now ships in the same pull request as the API change that prompted it, reviewed together rather than separately.