Technical Writer

What the work is

Documentation for the products we build and run — how a site configures Pacific POS, what a clinic does in its first week on the EHR, the API references our client work depends on, and the release notes that tell an existing site what changed this month. Most of it is read mid-task by somebody who is already busy, and that fact decides nearly everything about how it should be written.

You will get what you need by asking the engineers and the support side directly and by using the software yourself. Documentation written from a feature description rather than from the product is wrong in the way nobody notices for a year, and keeping existing pages true as the products change is as much of this job as writing new ones.

What we look for

Samples of software documentation — user-facing, API, or both — with an account of who you were writing for. Enough technical comfort to read code, run the product, and try the thing before you describe it.

It is worth being clear about what this role is not: it is not content marketing, and it is not a route into product management. It is a writing job about software that is in use, and if the writing itself is the appeal then it is a good one.

How to apply

Send a page you are pleased with and, if you have one, a page you would now rewrite. Tell us what changed your mind about the second.