ProductTechnical Writer

Write what assistants are told about building apps here, and what people read when they connect one.

All open roles
Function
Product
Region
Remote
Type
Full-time
Experience
3+ years
Apply for this role

About the role

Two audiences read our words. Assistants read the instructions our MCP server gives them when they connect, and the tool descriptions, and write every app from those. People read the website's docs, the directory listings and the screens that walk them through installing an app.

When the instructions are unclear, the app an assistant writes doesn't work, so writing here is product work: a sentence changed in what assistants are told shows up in what lands on people's phones.

What you'd do

  • Own the instructions and tool descriptions the app MCP gives assistants, and test changes against real assistants
  • Keep the docs page, the README and every directory listing accurate as the product changes
  • Write the reference for the runtime library when it ships (planned)
  • Hold everything to "only claim what ships"

What we need

  • Three or more years writing technical documentation for developers or developer tools
  • You can read TypeScript and HTML well enough to check a claim against the code
  • Plain, short writing, and a habit of cutting

Nice to have, not required

  • You've written prompts or instructions for AI models and measured whether they worked
  • API or protocol documentation

How we work

  • Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
  • Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by someone using it.
  • Private by default. A person's app data stays on their phone, and nothing we build may need to read it.
  • We only claim what ships. That applies to the product, the roadmap and the offer letter.

How hiring works

  1. 1A 30-minute call about something you've built and what was hard about it.
  2. 2A working session on a real problem from this codebase. You can drive, or we can pair.
  3. 3A conversation about how you make decisions when the evidence is thin.
  4. 4References, then an offer. We aim to answer within a week at every stage.

Apply: Technical Writer