Remote Writing Jobs: Full-Time Roles at Async Companies

Most companies say they value good writing. A few are actually run on it. When a team is spread across time zones and can't rely on everyone being online at once, the document becomes the meeting, the changelog becomes the announcement, and the help article becomes the support call that never had to happen.

Remote writing jobs at those companies are full-time roles where writing is the product: technical writers and documentation engineers who explain how the software works, copywriters and content writers who explain why it matters, and the growing set of technical content roles in between. They pay real salaries, they hire on a portfolio rather than a pedigree, and they're some of the most natural fits for asynchronous work there are.

This post covers the role families, the pay, and how to get in. If you'd rather see what's open, writing roles on our board sit inside the remote marketing listings and the remote engineering listings, depending on whether the audience is customers or developers.

What Remote Writing Careers Look Like at Async-First Companies

To put it simply, at an async-first company most communication happens in writing that people read later rather than conversation that happens live. Decisions are made in documents with comment threads. Product updates are posted, not presented. A new engineer learns the system from the handbook, not from shadowing someone for a week.

That makes writing a core function rather than a service department. The technical writer isn't cleaning up someone else's notes after the fact; they're often the person who makes a feature understandable enough to ship. The copywriter isn't waiting on a brief from a meeting they weren't invited to; the brief is a doc they can read, question, and improve in the thread.

For you, that means a job where the thing you're good at is the thing the company runs on. It also means the interview is mostly a writing test — which is the best possible news if writing is what you do. If the model is new to you, what asynchronous communication is explains it from the ground up.

Types of Writing Jobs You Can Do Remotely

Four families cover nearly every full-time writing role on an async board. They differ mainly in who the reader is.

Remote Technical Writer Jobs

Technical writers turn how a product works into documentation people can actually follow: API references, setup guides, tutorials, release notes. The reader is usually a developer or a power user. You don't need to be an engineer, but you need to be comfortable reading code, running the product yourself, and asking precise questions in writing. Companies like Supabase and Tailscale have hired documentation and technical content roles exactly because their customers are developers who read before they ask.

Remote Copywriter Jobs

Copywriters write the words customers meet first: landing pages, product pages, emails, ads, onboarding flows. The reader is a buyer, and the measure is whether they understood and acted. At async companies the copywriter usually sits in marketing, works from a written brief, and ships through a review thread rather than a presentation. Remote.com, for instance, has listed copywriter roles across several regions at once — a sign that the work is defined well enough to be done from anywhere.

Remote Content Writing Jobs

Content writers produce the longer material that earns attention over time: blog posts, guides, newsletters, case studies, comparison pages. The best content roles at async companies are half writer, half analyst — you're expected to know what readers search for and whether the piece worked. This family overlaps heavily with SEO and content marketing; our remote marketing jobs post covers the wider team you'd join.

Documentation Engineer Jobs and Developer Content

A newer family sits between writing and engineering: documentation engineers, technical staff writers, developer-education content. PostHog has hired a technical staff writer for blogs and newsletters; Supabase has listed a documentation engineer. These roles want someone who can write clearly and build the small demo, run the query, or fix the docs site. They pay closer to engineering than to marketing, and they are the fastest-growing corner of writing work at developer-tool companies.

Technical Writer Salary and What Other Remote Writers Earn

Writing pay tracks the reader. Roles whose readers are developers pay more than roles whose readers are consumers, and roles that require reading code pay the most.

Role	Typical US pay band	What moves you up the band
Technical writer / documentation	$65,000–$110,000	API docs experience, comfort with code, ownership of a docs site
Copywriter / content writer	Starts around $55,000; senior content and SEO leads toward $80,000–$130,000	Measurable results, SEO fluency, owning a channel end to end
Documentation engineer / technical content	Pays like junior-to-mid engineering and rises with technical depth	Shipping working examples, not just prose

Two honest notes. Regional roles post regional bands, so a copywriter role open to several countries will pay differently in each. And because async companies work in writing, senior writers there are often paid like senior individual contributors, not like a support function — the ceiling is higher than most writing jobs advertise.

Remote Writing Jobs Entry Level: Getting In Without Bylines

Writing is one of the few fields where you can manufacture your own experience. Nobody can stop you from writing the thing, publishing it, and pointing to it.

Build a Writing Portfolio That Gets Replies

A writing portfolio for async companies is three to five pieces that match the job you want, not a scrapbook of everything you've ever written.

For technical writing: document a real open-source tool better than its own README does. Pick something you use, write the getting-started guide you wish existed, and publish it.
For copywriting: rewrite a real landing page and show before and after with a sentence on why each change helps. Three of these beat thirty ads.
For content: publish two or three pieces on a topic you know, on your own site or a platform, and be ready to talk about who they were for and how they performed.
For any of them: include one short piece of internal-style writing — a project update, a decision memo, a change announcement. That's the everyday writing async companies actually run on, and almost no candidate shows it.

Then apply in the same register. Your application email is a writing sample whether you intend it to be or not. Keep it short, specific, and structured, and link to the portfolio rather than attaching it.

How to Become a Technical Writer From an Adjacent Role

Most technical writers didn't start as writers. They came from support, QA, engineering, or teaching, and they were the person who kept writing things down. If that's you, the move is smaller than it looks.

Own the docs where you are. Fix the internal wiki. Write the runbook. Turn the recurring support answer into a help article. Every one of those is a portfolio piece.
Learn the tooling. Docs-as-code — Markdown, Git, a static-site generator — is standard at developer-tool companies. It's learnable in a weekend and it removes the biggest hiring objection.
Read code, even slowly. You don't need to write production software. You need to follow an example, run it, and notice when it's wrong.
Target async-first companies. They value documentation because they depend on it, and they judge candidates on a written exercise you can actually prepare for.

The Trade-Offs of Work From Home Writing Jobs

With everything in life there are trade-offs, and writing for a living remotely has a specific set.

Drawbacks:

Fewer openings than the search volume suggests. Writing roles are a small share of any async board — a handful of companies at a time, not dozens. Expect to apply patiently.
Feedback arrives in writing, all at once. A doc full of comments can sting more than a conversation would. Async writers learn to read a thread as information, not judgment.
The job is measured. Docs get feedback scores; content gets traffic; copy gets conversion. If you want to write without anyone counting, this isn't that.
Quiet can tip into isolated. Long stretches of solo work are the appeal, but you'll want to build in human contact on purpose — a recurring one-on-one, a writers' channel, a walk at lunch.

Benefits: deep, uninterrupted work; a company that treats your craft as infrastructure; evaluation on the page rather than on presence; and hours you can arrange around your own best writing time, whether that's 6 a.m. or after the kids are in bed.

Writing Jobs From Home: Where to Find Full-Time Openings

Search by the company's communication style, not just by the job title. A company that publishes its handbook, keeps a public changelog, and explains decisions in an engineering blog is a company where writing is valued — and where a writing role, when it opens, will be a real one.

What to look for in a listing:

A described reader ("developers integrating our API," "customers on the pricing page") — vague audiences make vague jobs.
A writing exercise in the process. Its absence is a yellow flag for a writing role.
Ownership language: "own the docs," "run the blog." Support-function language ("assist the team with content") usually means a smaller job than the title.
Stated time-zone expectations. Async-first listings keep required overlap minimal and say so.

What to avoid: per-word rates dressed up as jobs, "unlimited earning potential," and any role that asks you to write a full article as an unpaid test before a single conversation. A fair exercise is short, scoped, and often paid.

Every listing on our board links straight to the employer's careers page, and each company profile shows how that company actually communicates. You can also check any employer's stated practices against the async policy rubric before you invest an afternoon in the application.

Frequently Asked Questions

What remote writing jobs are there?

Four full-time families cover most of them: technical writers and documentation roles for developer readers, copywriters for landing pages and product marketing, content writers for blogs, guides, and newsletters, and documentation engineers or technical content roles that blend writing with light engineering. At async-first companies they sit in marketing or engineering depending on the audience.

How much do remote writing jobs pay?

US technical writers typically earn $65,000–$110,000. Copywriters and content writers start around $55,000, with senior content and SEO leads reaching $80,000–$130,000. Documentation engineers pay like junior-to-mid engineering roles and rise with technical depth. Regional roles post regional bands.

Can I get a remote writing job with no experience?

Yes, if you build the experience yourself: publish three to five pieces that match the role, including one piece of internal-style writing like a project update or decision memo. Async companies hire on a portfolio and a written exercise, so published work counts.

Do remote writing jobs require a degree?

Rarely. Writing roles at async-first companies are portfolio-driven; a clear docs sample or a rewritten landing page says more than a diploma. Technical roles care more about whether you can read code and run an example than about your major.

Are remote writing jobs full-time?

The ones on our board are. Async-first companies hire technical writers, copywriters, content writers, and documentation engineers as full-time staff with salaries and benefits, because the writing is core to how the company operates rather than an occasional need.

Write Where Writing Runs the Company

If you write well, the best place to do it for a living is a company that would grind to a halt without good writing. Async-first companies are exactly that. Build the portfolio, apply in the same voice, and let the page make the case.

→ Browse full-time roles at async-first companies

→ See remote content and copy openings

→ Read why written-first work suits quiet people

Your words are the work. Get paid for them.