All open roles
Internship
Technical Writer Intern
Documentation, handover guides, and training material. The work that decides whether a client's team can run what we built for them.
Apply for this role- Location
- Remote
- Commitment
- Part-time, flexible hours
- Intake
- Summer 2027 intake, rolling review
- Team
- Strategy & Delivery
- Level
- Student or recent graduate
About the role
We hand full source and IP to clients. That handover is worth very little without documentation someone can follow after we have gone.
You will write it: API references, admin guides, onboarding material, and the internal notes that stop the same question being answered four times.
What you will actually do
- Write and maintain product and API documentation.
- Turn an engineer's explanation into something a non-engineer can act on.
- Build training material and short screen recordings for client handovers.
- Keep the docs current when the product moves, which is the hard part.
What you need on day one
- Excellent written English, and an instinct for cutting words.
- Technical curiosity: willingness to install the thing and use it before writing about it.
- Markdown, and ideally Git.
Nice to have, genuinely optional
None of these are requirements. They are listed so you know what would be a head start, not so you can talk yourself out of applying. Apply if the list above fits.
- Any programming background at all.
- Docs-as-code tooling, or having maintained a README anyone else read.
- Screen recording and editing.
What you should expect to learn
- How to interview an engineer productively.
- Information architecture for documentation.
- How to write for someone who is stressed and in a hurry.