Technical Writing as a Tech Career: $80–150K, Fully Remote, and Almost Nobody Competing for It

In 2022, I was building the scraper infrastructure for BirJob — writing Python, wrestling with Playwright, debugging async HTTP calls at 2 AM. At some point, I had to document the whole system: how each scraper works, what the data schema looks like, how to add a new source. I expected the documentation to take an afternoon. It took a week. And when I finished, I realized something uncomfortable: the docs might actually be more valuable than half the code I'd written that month. Anyone could read them and understand the system. Without them, the code was a black box that only I could operate.

That experience planted a seed. I started paying attention to the people who write documentation professionally — technical writers. And what I found surprised me: they earn $80,000 to $150,000+, they work remotely at higher rates than almost any other tech profession, and the field is chronically understaffed. Nobody's flooding bootcamps to become a technical writer. There's no "Learn Technical Writing in 12 Weeks" TikTok trend. It's one of the quietest, most underrated careers in all of technology.

This article is about why that gap exists, what the work actually looks like, and why it might be the best career move for a surprisingly wide range of people — from burned-out developers to English-fluent professionals in emerging markets looking for their way into the global tech economy.

The Numbers First

The Bureau of Labor Statistics reports the median annual wage for technical writers at $79,960 as of 2023, with the top 10% earning more than $128,000. The BLS projects 7% growth from 2022 to 2032, which is faster than the average for all occupations. But these numbers, as with most BLS data, significantly underrepresent the tech sector specifically.

Glassdoor puts the average technical writer salary in the US at about $85,000, with senior technical writers at tech companies earning $110,000–$150,000. At Big Tech companies, the numbers go higher: Levels.fyi shows Google technical writers earning $150,000–$250,000+ in total compensation (base + equity + bonus), though Google's tech writer roles are notoriously competitive and essentially require strong coding skills.

The Write the Docs annual salary survey, which is the most tech-writing-specific data source available, consistently shows median salaries of $90,000–$115,000 for US-based tech writers, with senior staff writers and documentation managers earning $130,000–$160,000+. The survey also reveals a crucial geographic detail: technical writers working remotely for US companies from outside the US report median salaries of $50,000–$80,000 — still excellent compensation in most countries.

For emerging markets specifically: a technical writer in Azerbaijan, Turkey, Poland, or Colombia working remotely for a US or European tech company can realistically earn $40,000–$90,000. That's not a typo. In a market where local developer salaries might be $15,000–$30,000, tech writing for international companies represents a genuine economic step change.

And here's the kicker: while software developer roles receive hundreds of applications per posting, technical writing positions at good companies often sit open for weeks or months. The LinkedIn job market consistently shows thousands of open tech writer positions in the US alone, with far fewer qualified applicants per role compared to engineering.

What Technical Writers Actually Do

"Technical writer" is a broad title that covers several distinct flavors of work. Let me break down the main categories, because the differences matter enormously.

1. API Documentation Writer

This is the highest-paid and most in-demand subspecialty. You write and maintain documentation for APIs — REST, GraphQL, gRPC, WebSocket. You create reference docs (endpoint descriptions, parameters, response schemas), tutorials ("How to authenticate and make your first API call"), and conceptual guides ("Understanding our pagination model"). Companies like Stripe, Twilio, and GitHub are famous for their excellent API documentation, and they employ dedicated writers to maintain it.

Skills needed: Understanding of HTTP, JSON, authentication patterns, basic coding ability (you need to write and test code samples), and familiarity with OpenAPI/Swagger specifications.

2. Developer Documentation Writer

Broader than API docs. You write guides, tutorials, quickstarts, and reference material for developer-facing products — SDKs, frameworks, CLIs, infrastructure tools. You might work at a company like Vercel (documenting Next.js), HashiCorp (Terraform docs), or Elastic (Elasticsearch guides).

Skills needed: Ability to use the product yourself, write clear step-by-step instructions, and understand developer workflows.

3. Product Documentation Writer

You document user-facing SaaS products — admin guides, feature descriptions, troubleshooting articles, knowledge base content. Think Salesforce, Zendesk, or HubSpot documentation. Less technical than API docs, but requires strong empathy for end users.

4. Internal Documentation / Knowledge Management

You document internal systems, processes, and architecture for engineering teams. Runbooks, architecture decision records (ADRs), onboarding guides, incident response procedures. This is often the least visible flavor of tech writing, but companies with strong engineering cultures (Stripe, Notion, GitLab) invest heavily in it.

5. Release Notes and Changelog Writer

A specialized niche: you distill each product release into clear, user-friendly release notes. This requires understanding the product deeply and translating engineering changes into user-facing impact. Some companies combine this with product marketing.

Why It's Chronically Undersupplied

The supply-demand imbalance in technical writing has persisted for over a decade, and it's getting worse, not better. There are structural reasons for this.

Nobody aspires to be a technical writer at age 18. Kids dream of being developers, designers, data scientists. "Technical writer" isn't a career that shows up in university marketing materials or bootcamp ads. Most technical writers stumble into the role accidentally — they were developers who preferred writing, English majors who picked up enough technical knowledge, or documentation enthusiasts who turned a side interest into a career.

There's no standard educational path. According to a Society for Technical Communication (STC) survey, technical writers come from an extraordinary range of backgrounds: computer science, English literature, journalism, linguistics, engineering, and even fine arts. There's no "technical writing bootcamp" pipeline producing thousands of graduates per year the way coding bootcamps do for developers.

The "docs-as-code" movement raised the bar. Modern technical writing at tech companies increasingly requires competence with tools like Git, Markdown, static site generators, CI/CD pipelines, and version control workflows. According to the 2023 Write the Docs survey, over 60% of tech writers now use docs-as-code toolchains. This means the role now demands a blend of writing skill and developer tooling fluency that further narrows the talent pool.

Companies underinvest in docs until it hurts. Many companies don't hire technical writers until their documentation has become a genuine liability — customer complaints, developer confusion, support ticket overload. By then, they need someone urgently, and there aren't enough candidates. The World Economic Forum's Future of Jobs Report 2023 doesn't specifically name technical writing, but it highlights "content creation" and "technical communication" as growing skill demands across industries.

The Docs-as-Code Movement: Why It Favors Developers

If you're a developer reading this, here's why you should pay special attention.

Traditional technical writing happened in Word documents, Confluence pages, or proprietary content management systems. The modern approach — docs-as-code — treats documentation like source code: written in Markdown or reStructuredText, stored in Git repositories, reviewed via pull requests, built by CI/CD pipelines, and deployed to static sites.

The toolchain will feel immediately familiar:

A developer who's comfortable with Git, Markdown, and basic web tooling already has 60–70% of the technical skills needed for modern tech writing. The remaining 30–40% is writing craft: structure, clarity, audience awareness, and the discipline to explain things simply without dumbing them down.

This is why the docs-as-code movement is a massive opportunity for developers. The barrier to entry for the technical side is almost zero. The barrier on the writing side is moderate but learnable. And the competition? Almost nonexistent compared to engineering roles.

Who Thrives as a Technical Writer

I've talked to enough tech writers to identify three distinct "persona archetypes" who tend to succeed and enjoy the work.

The Developer Who Prefers Writing

You're a decent programmer — maybe mid-level, maybe senior — but you've always gravitated toward the documentation side. You're the person who writes detailed PR descriptions when everyone else writes "fixed bug." You maintain the team wiki. You enjoy writing design documents more than writing code. You find yourself wishing you could spend more time explaining systems and less time debugging them.

Salary expectation: $100K–$150K at a good tech company, because your technical depth gives you an edge over non-technical writers. API documentation and developer docs will be your sweet spot.

The English-Fluent Non-Developer

You studied English, journalism, linguistics, or communications. You write well. You've picked up some technical knowledge — maybe you've learned HTML/CSS, dabbled in Python, or simply spent years absorbing technical concepts by proximity. You don't want to be a developer, but you want to work in tech.

Salary expectation: $70K–$110K, growing as you build technical depth. Product documentation and user-facing guides will be your entry point, with potential to move into developer docs as your skills grow.

The Career Changer

You're coming from an entirely different field — teaching, academia, science, healthcare — and you have strong writing skills plus domain expertise. A former chemistry teacher who can document a biotech company's API. A former lawyer who can write compliance documentation. A former teacher who can structure learning paths and tutorials better than anyone.

Salary expectation: $65K–$100K initially, rising to $100K–$130K as you establish yourself. Your domain expertise is your differentiator.

Remote Work: The Hidden Superpower

Here's a stat that should make everyone pay attention: according to the Write the Docs 2023 salary survey, approximately 75–80% of technical writers work remotely, either fully or primarily. That's higher than software developers (~60% remote per Stack Overflow's 2023 survey), higher than product managers, higher than designers, and dramatically higher than most other tech roles.

Why? Several factors converge:

• Documentation is asynchronous by nature. Writers don't need to pair-program or whiteboard in real-time. They research, draft, review, iterate — all activities that work perfectly in distributed settings.
• The output is text. Unlike design (where you might need calibrated monitors and collaborative whiteboarding) or engineering (where you might need access to specific hardware), writing requires only a laptop and internet access.
• The talent shortage forces flexibility. When there aren't enough tech writers in San Francisco, companies have to look everywhere. Remote hiring becomes a necessity, not a perk.
• Many tech writing teams are small. It's common for a company to have 1–3 technical writers embedded across multiple engineering teams. There's no "writing bullpen" that benefits from physical co-location.

For people in emerging markets — Azerbaijan, Georgia, Turkey, Eastern Europe, Latin America, Southeast Asia — this remote-first nature is transformative. You can earn US-level or near-US-level salaries while living in a market with a fraction of the cost of living. A technical writer earning $60,000–$80,000 remotely from Baku or Tbilisi is living extremely well.

Salary Comparison: Tech Writer vs. Developer (Adjusted for Reality)

The raw salary comparison between technical writers and software developers looks unfavorable for writers at first glance. But when you adjust for working conditions, the picture changes dramatically.

When you calculate effective hourly rate (salary divided by actual hours worked, including on-call, incident response, and weekend debugging), many senior technical writers are earning comparable to mid-senior developers. And the quality-of-life difference is significant.

That said, the salary ceiling is genuinely lower. You're unlikely to earn $300K–$500K as a technical writer (except at Google or a few other companies with unusually generous tech writer comp). If maximizing total compensation is your primary goal, engineering or management is still the path. But if you're optimizing for compensation relative to stress, hours, and quality of life, technical writing is remarkably efficient.

How to Break In: Practical Entry Points

1. Contribute to Open-Source Documentation

This is the single best way to build a portfolio with zero gatekeeping. Almost every major open-source project has documentation that needs improvement. Find a project you use, read their docs, identify gaps or unclear sections, and submit a pull request.

Projects that actively welcome documentation contributions:

• Kubernetes — massive docs with constant need for updates
• Python — always needs tutorial improvements
• Rust — the Rust Book is community-maintained
• MDN Web Docs — the web's reference documentation

After 5–10 merged documentation PRs, you have a concrete, verifiable portfolio that demonstrates your skills far better than any certification.

2. Google Season of Docs

Google Season of Docs is an annual program that pairs technical writers with open-source organizations. You get paid ($5,000–$15,000 stipend), mentored, and published. It's specifically designed as an on-ramp for new tech writers, and it looks excellent on a resume.

3. The Write the Docs Community

Write the Docs is the global community for documentation professionals. They run conferences (Portland, Prague, Australia), maintain an active Slack workspace with thousands of members, publish a job board, and host local meetups. If you're serious about tech writing, this is your home base.

4. Start a Documentation Blog

Pick a technology you know well and write the documentation you wish existed. "A Complete Guide to Setting Up PostgreSQL Replication" or "Understanding OAuth 2.0 Flows with Diagrams" — these kinds of pieces demonstrate exactly the skills hiring managers look for. Publish on your own blog, Medium, Dev.to, or Hashnode.

5. Internal Documentation at Your Current Job

If you're currently a developer, volunteer to own your team's documentation. Write the onboarding guide. Document the deployment process. Maintain the API reference. This builds your portfolio, makes you invaluable to your current team, and gives you real tech writing experience to reference in applications.

Tools of the Trade

Here's what a modern tech writer's toolkit looks like, and how it maps to the docs-as-code workflow:

The total investment to become proficient with this entire stack is 4–8 weeks of focused learning. Compare that to the years required to become a proficient full-stack developer. The ROI on learning these tools, relative to the career they unlock, is exceptional.

Misconceptions and Controversies

"Technical writing is boring"

This is the most common misconception, and it's understandable. If you imagine technical writing as writing dry instruction manuals for printer drivers, yes, that sounds boring. But modern tech writing at software companies is intellectually engaging. You're learning new technologies constantly, solving communication puzzles ("how do I explain distributed consensus to a developer who's never used it?"), and directly shaping how people experience a product. The best tech writers I know describe their work as "teaching at scale."

"AI will replace technical writers"

This is the controversy du jour, and it deserves a nuanced answer. AI tools like GPT-4 and Claude can generate decent first drafts of documentation. But here's what they can't reliably do: verify technical accuracy against a live product, understand the user's context and frustration, maintain consistency across thousands of pages, navigate internal politics about what should and shouldn't be documented, and make editorial judgments about what matters most.

According to a 2023 Write the Docs survey, about 40% of technical writers report using AI tools in their workflow — primarily for first drafts, rephrasing, and brainstorming. But very few report that AI has reduced headcount on their team. The consensus in the community is that AI makes individual writers more productive (you can cover more ground), but it doesn't eliminate the need for human judgment, technical verification, and editorial oversight.

My honest take: AI will change technical writing, not replace it. Writers who learn to use AI tools effectively will be more valuable, not less. Writers who refuse to adapt will struggle. This is the same dynamic playing out across most knowledge work.

"You need a CS degree"

You absolutely do not. For API documentation and developer-facing docs, you need technical competence — but that can be acquired through self-study, bootcamps, or on-the-job learning. For product documentation, you need product understanding, not computer science theory. The Write the Docs salary survey consistently shows that writers with English/communications degrees earn comparably to those with CS degrees, especially at the senior level where writing quality matters more than technical pedigree.

"There's no career progression"

This used to be true. A decade ago, "technical writer" was often a dead-end title with nowhere to go. Today, the career ladder at good tech companies looks like:

• Technical Writer → Senior Technical Writer → Staff Technical Writer → Principal Technical Writer (IC track)
• Technical Writer → Documentation Manager → Director of Documentation → VP of Developer Experience (management track)
• Technical Writer → Developer Advocate → Head of Developer Relations (adjacent track)
• Technical Writer → Content Strategist → Head of Content (content track)

Companies like Google, Stripe, Microsoft, and GitLab have formal tech writer career ladders with defined levels and compensation bands. The "no career growth" argument is outdated.

What I Actually Think

Technical writing is the most underpriced career in tech relative to its supply-demand dynamics, quality of life, and remote work accessibility. I say "underpriced" even though the salaries are already good, because the shortage of qualified writers means that employers are chronically unable to fill roles — and yet, somehow, the profession still doesn't get the attention it deserves.

I think there are three groups of people who should seriously consider this path:

First: mid-level developers who are burning out. If you've spent 4–7 years coding and you're starting to dread sprint planning, if you find yourself gravitating toward documentation and design docs, if you're the person who writes the best README on the team — you have the skills to be an excellent tech writer, and you'll probably earn 70–90% of your current salary with a dramatic improvement in work-life balance.

Second: English-fluent professionals in emerging markets. If you're in Azerbaijan, Turkey, Georgia, the Balkans, or similar markets, and you have strong English writing skills plus any level of technical understanding, you are sitting on an opportunity that most people around you don't see. Remote technical writing positions for US/EU companies can pay $40,000–$80,000 — which is life-changing money in most of these markets. And the competition is far less fierce than for remote developer roles.

Third: career changers with strong writing skills. Former teachers, journalists, academics, lawyers — if you write well and you're willing to spend 2–3 months learning technical tools and concepts, you can transition into a career that pays well, offers remote flexibility, and has genuine demand for your skills.

The main reason I'm bullish on this career is simple math: the supply isn't growing, the demand is increasing (more software = more documentation needed), and the docs-as-code movement is raising the value of each individual writer. That's a seller's market, and it's likely to stay that way for at least another decade.

Decision Framework: Should You Pursue Technical Writing?

Getting Started This Week

If this article has convinced you to explore further, here's a concrete action plan:

1. This week: Join the Write the Docs Slack and introduce yourself. Read three API documentation sites (Stripe, Twilio, GitHub) and note what makes them good.
2. Week 2: Pick an open-source project and submit a documentation pull request. Even fixing a typo counts as a first contribution.
3. Week 3–4: Write a tutorial for a technology you know well. Publish it on Dev.to or your own blog. Share it for feedback in the Write the Docs Slack.
4. Month 2: Learn Docusaurus or MkDocs. Build a small documentation site for a personal project or an open-source tool you use.
5. Month 3: Apply to your first tech writing role. Target companies whose products you've used. Include your portfolio (blog posts, open-source contributions, documentation site) in your application.

Three months from zero to your first application. That's the timeline. No bootcamp required. No $15,000 tuition. Just writing, learning, and building in public.

Sources

• Bureau of Labor Statistics — Technical Writers
• Glassdoor — Technical Writer Salary Data
• Levels.fyi — Technical Writer Compensation
• Write the Docs — Annual Salary Survey
• Write the Docs — Community Hub
• Write the Docs Slack
• Google Season of Docs
• Google Developer Documentation Style Guide
• Society for Technical Communication (STC)
• Stack Overflow Developer Survey 2023 — Work Arrangement
• World Economic Forum — Future of Jobs Report 2023
• Haystack Analytics — Developer Burnout Data
• Docusaurus
• MkDocs
• Vale — Linter for Prose
• ReadMe — API Documentation Platform
• Redocly — API Documentation
• Stripe API Documentation
• Twilio Documentation
• GitHub REST API Documentation

I'm Ismat, and I build BirJob — a job aggregator that scrapes 91+ sites across Azerbaijan so you don't have to check them all. If you're exploring tech careers, remote opportunities, or looking for your next move, BirJob is where the search begins.

You might also like

• The Remote Work Backlash: Why Companies Are Forcing Return-to-Office and What It Means for Your Career
• AI Engineer vs ML Engineer: What Actually Changed and Why It Matters
• Remote Work from Azerbaijan: The Complete Guide for Professionals and Companies
• Tech Salaries Compared: Baku vs Tbilisi vs Istanbul vs Dubai