Technical Writer Jobs, Remote or Not: Titles and How to Search
If you've been searching for technical writer jobs, remote ones especially, and finding almost nothing, you're not imagining it. Documentation teams are small, titles vary, and many roles are tied to an office city. This guide covers what technical writers do in tech companies, the titles to track, what our own snapshot showed, and practical ways to widen the search without giving up on the field.
What a technical writer does in a tech company
In a software company, a technical writer makes the product understandable to the people who use it. Depending on the product, that means:
- API and developer documentation: reference pages, quick-starts, code samples, SDK guides.
- User guides and help centres for non-technical users.
- Release notes and changelogs.
- Internal documentation: runbooks, architecture overviews, onboarding guides for engineers.
- Docs infrastructure: in many teams docs live in Git as Markdown, go through code review and are built by a static site generator. This is often called "docs as code".
Most of the job is research, not writing: reading code and specifications, asking engineers the right questions, trying the product yourself and noticing where a new user would get stuck.
The titles
| Title | What it usually means |
|---|---|
| Technical Writer | The standard title, from user guides to API reference |
| Documentation Engineer, Docs Engineer | Docs as code: tooling, build pipelines, doc sites, plus writing |
| API Writer, Developer Documentation Writer | Focus on developer-facing docs |
| Developer Educator | Tutorials and courses; often part of DevRel |
| UX Writer | Interface text: buttons, errors, empty states |
| Content Designer | Interface text and content structure, usually inside a design team |
| Information Architect | How documentation and content are organised and found |
UX Writer and Content Designer are genuinely different jobs from technical writing. They sit in design teams and work on product screens, not manuals. But the skills overlap enough that many writers apply to both, and it's worth knowing that postings for them often land in the same search results.
What our snapshot showed
In our September 2026 snapshot of the boards Hot Jobs checks, Technical Writer had zero remote postings, both in the column open to Europe and in the column for any region. That's one moment, on 390+ company career pages and two remote boards, and it says nothing definite about the market as a whole.
It does fit what you might expect. Documentation teams are usually a handful of people even at large companies, so openings come up rarely, and when they do, some are on-site or hybrid in the company's main offices. A remote-only search will simply show little.
How to widen the search
1. Add cities
If you'd work hybrid or on-site somewhere, add those cities to your search: the city you live in and any you'd realistically move to. Roles that aren't remote tend to draw a smaller pool of applicants, and they won't show up on a remote filter at all. We explain the difference between the formats in hybrid, remote-first and remote-friendly.
2. Track every title in the table
Documentation Engineer and Docs Engineer are easy to miss if you only type "technical writer". If you have design-team experience, add UX Writer and Content Designer, and read job alerts for designers for how design-side hiring tends to be posted.
3. Look at neighbouring roles
Developer relations teams produce a lot of written content and sometimes hire writers under DevRel titles. See developer relations jobs for those titles.
4. Pick companies whose product is its docs
Developer-tool companies depend on documentation more than most. Among the boards Hot Jobs checks are Supabase, Sentry, PostHog, Vercel, Netlify, GitLab, Grafana Labs, Twilio and Algolia. We don't know when any of them will open a writing role, but for a rare role, watching the right career pages is more useful than scrolling general boards. A written target company list helps keep that focused.
5. Use other channels too
LinkedIn, general job boards and writing communities such as Write the Docs all post writing roles that company boards alone won't show you. Rare roles are worth watching from several directions.
Build a portfolio that matches the posting
In technical writing, samples carry a lot of weight. Useful ones:
- A short API quick-start written for a public API, with working code.
- A before-and-after rewrite of a confusing help page.
- A merged pull request to an open-source project's documentation. This also shows you can work with Git and code review.
- A small docs site you built yourself, if the role mentions docs as code.
Keep each sample short and say what problem it solved. Hiring managers read samples to see how you think, not how much you can produce.
How to read a technical writer posting
- Who are the readers? Developers, administrators or end users need very different writing.
- Docs as code or a CMS? Git, Markdown and static site generators versus a help-centre tool.
- One writer or a team? Being the only writer means owning style, tooling and priorities alone.
- What's the product area? APIs, infrastructure, fintech and consumer apps all need different background knowledge.
- Is there a writing test? Many companies set one. It's reasonable to ask how long it should take.
Searching in Hot Jobs
In Hot Jobs, the Technical Writer role matches titles containing Technical Writer, Documentation Engineer, UX Writer or Content Designer. Titles such as Docs Engineer or Technical Content Writer don't contain those exact words, so check them separately. Combine the role with the cities you'd work in, not only a remote option, so hybrid and on-site roles reach you too.
Hot Jobs checks 390+ company career pages every 30 minutes, plus two remote boards, and sends matching roles to Telegram, including up to 5 that are open right now when you first connect. €3, paid once. Connect the bot