How much does a technical writers make?

The median technical writers salary in the United States is $90,390 per year ($43.46/hour). Salaries range from $57,440 (10th percentile) to $145,270 (90th percentile). There are 45,500 technical writers jobs in the U.S. Source: Bureau of Labor Statistics OEWS.

Which state pays technical writerss the most?

The highest paying state for technical writerss is New Jersey at $122,320 median salary.

Is technical writers a good career?

Technical Writers employment is projected to grow 0.9% from 2024 to 2034 (slower than average). There are approximately 4,500 job openings per year. Typical education required: Bachelor's degree.

What certifications should technical writerss get?

Top-ROI certifications for technical writerss: STC CPTC (Certified Professional Technical Communicator) ($250-450 exam + $500-1,500 prep; 3-year renewal cycle with 45 CEU credits); AMWA Essential Skills + AMWA Advanced + AMWA CPD (Certified Professional in Medical Writing) ($200-500 per certificate + $500-2k prep; 3-year renewal with CE credit); RAPS RAC (Regulatory Affairs Certification) — US / EU / Global ($500-750 exam + $1-3k prep; 3-year renewal with 36 CE credits).

How do you negotiate a technical writers salary?

Anchor on documented market data (BLS median $90,390, p75 $115,510), specific outcomes you've delivered, and the specific band for your years of experience. Given 6 years as a Sr Technical Writer at Stripe on the Payments API team — the 2023 Payment Intents docs relaunch driving a 68% support-ticket reduction and 32% developer-time-to-first-integration improvement, STC CPTC...

Technical Writers Salary

Q: What interview questions are asked for technical writers roles?

Common technical writers interview questions include: "Walk me through the last documentation project you shipped end-to-end.", "Describe how you'd handle documentation for a feature the engineering team is still building.", "Describe a difficult documentation project — technical, cross-functional, or high-stakes.". Interview format at top employers ranges from behavioral panels (STAR method) to technical case rounds — for example Big Tech (Microsoft, Google, Amazon, Meta, Apple, Salesforce, Oracle, IBM) typically uses 5-7 rounds over 4-8 weeks.

Q: What is the career ladder for technical writerss?

The typical technical writers career ladder: Entry Technical Writer (0-4 yrs, $58-82k salaried + 8-12% bonus at Big Tech + $18-35k RSU/equity at Big Tech + full benefits) → Established / Senior Technical Writer (4-10 yrs, $85-155k salaried + 12-18% bonus + $45-95k RSU/equity at Big Tech + full benefits) → Staff / Principal Technical Writer or Documentation Manager (10-16 yrs, $155-265k+ TC (base $145-195k + RSU $35-95k + bonus $18-32k at Big Tech)) → Director / VP Documentation, Distinguished Technical Writer, or Product Content Design Leader (15-25+ yrs, $215-485k+ TC at Big Tech + high-growth SaaS + top pharma; $185-345k at mid-market + medical device).

The median technical writers salary in the United States is $90,390 per year ($43.46/hour). Salaries range from $57,440 at the entry level to $145,270+ for the top 10% of earners. There are 45,500 technical writers jobs nationwide. Employment is projected to grow 0.9% through 2034.

Last updated: June 2026 · Source: U.S. Bureau of Labor Statistics

Median Salary

$90,390

per year

Hourly Rate

$43.46

per hour

Employment

45,500

jobs in the U.S.

Salary Distribution

10th percentile

$57,440

25th percentile

$70,880

Median

$90,390

75th percentile

$115,510

90th percentile

$145,270

Job Growth (2024-2034)

+0.9%

Slower than average

Annual Openings

4,500

jobs/year (growth + replacements)

Education Required

Bachelor's degree

+ Less than 5 years experience

Training Needed

Short-term on-the-job training

Technical Writers Career Guide

Interview questions, resume templates, and a career ladder written specifically for technical writerss.

Technical writers (BLS SOC 27-3042) produce the documentation that lets engineers ship, users adopt, and regulators approve — API references, user guides, integration tutorials, medical-device labeling, pharma package inserts, industrial-equipment operator manuals, and regulatory-submission documents. Typical seats: software / SaaS documentation writer at Microsoft, Google, Amazon, Salesforce, Oracle, IBM, Meta, Apple, Stripe, GitHub, Atlassian, MongoDB, Snowflake, Databricks, Datadog, Twilio, HashiCorp; API documentation specialist working with OpenAPI / Swagger / Redoc against Stripe-style reference standards; medical-device technical writer producing labeling under FDA 21 CFR Part 801 at Medtronic, Abbott, Boston Scientific, Stryker, Johnson & Johnson MedTech, GE HealthCare, Siemens Healthineers, Philips Healthcare; pharma regulatory writer producing eCTD (electronic Common Technical Document) submissions to the FDA and EMA at Pfizer, Merck, Johnson & Johnson, AbbVie, Bristol-Myers Squibb, Eli Lilly, Novartis, AstraZeneca, Roche/Genentech; industrial-equipment technical writer producing operator + maintenance manuals at Caterpillar, John Deere, Boeing, Lockheed Martin, Raytheon, Cummins, GE Aerospace, GE Vernova; UX writer / product-content designer at consumer-software companies with UX Writing crossover to Product Design. BLS reports 45,500 employed with a median of $90,390, p10 $56,750, p90 $138,450+. Entry technical writers $58-82k; established $85-125k; senior / staff / principal $125-185k+; documentation manager / head of docs $155-265k+ base + equity at Big Tech. The single biggest earnings lever is stacking DITA XML + Markdown + Git + API-doc fluency (OpenAPI / Swagger) + a specialty (developer docs, medical-device, or pharma regulatory) — this triple stack moves a writer from $75k technical-communications-generalist seat to $155-185k+ Staff Technical Writer with equity at Stripe, Snowflake, Databricks, MongoDB, or Datadog.

Core Skills Hiring Managers Screen For

Structured authoring — DITA XML + Markdown + AsciiDoc + reStructuredText

DITA (Darwin Information Typing Architecture) — the OASIS-standard XML architecture for topic-based technical documentation; concept / task / reference topic types; DITA-OT (DITA Open Toolkit) for output publishing to PDF + HTML + WebHelp + EPUB. DITA is the enterprise + regulatory-industry standard (medical device, pharma, aerospace, defense, industrial equipment). Markdown — the developer-industry standard, particularly the CommonMark + GitHub Flavored Markdown flavors used by Docusaurus / MkDocs / Hugo / Jekyll / Gitbook / ReadTheDocs. AsciiDoc — used at some large enterprise open-source projects (Spring, Elasticsearch documentation) with better structured-doc features than plain Markdown. reStructuredText (RST) — Sphinx-based Python-community standard (Python docs, ReadTheDocs default).

API documentation — OpenAPI / Swagger / Redoc + Stripe-style reference standards

OpenAPI Specification (formerly Swagger) — the industry-standard machine-readable REST API description; OAS 3.0 + 3.1 are the current versions. Swagger UI + Redoc + Stoplight Elements + ReadMe.com auto-render OpenAPI specs into interactive documentation. Stripe API documentation is the widely-referenced gold standard — three-column layout (prose + endpoint reference + code samples in 7+ languages) with copy-paste-runnable examples. API-doc-specific workflows — spec-first (write OpenAPI YAML first, generate docs) vs code-first (annotate the source code with Swagger annotations, generate the OpenAPI spec). GraphQL documentation via GraphiQL / Apollo Studio / SpectaQL. gRPC / Protobuf documentation via Buf.build + protoc-gen-doc.

Static site generators + docs-as-code + Git workflow

Docusaurus (Meta open-source; React-based; used at Meta, Docusaurus itself, Redwood JS, Prisma) — the modern developer-docs default; MDX (Markdown + JSX) support for interactive docs. MkDocs (Python-based; used at Bank of America, MongoDB some products, most Python OSS projects) — simple Markdown-to-HTML; Material for MkDocs theme is the industry standard. Hugo (Go-based; used at Kubernetes docs, many static sites) — fastest build times. Jekyll (Ruby-based; used at GitHub Pages default, many older sites). Sphinx (Python-based; used at Python + ReadTheDocs + most Python OSS). GitBook + Gitiles + ReadTheDocs hosted platforms. Git workflow — feature branch + pull request review + CI-build preview + auto-deploy on merge; docs-as-code discipline means every documentation change is version-controlled and reviewed like source code.

Confluence + Notion + SharePoint + enterprise wiki + KB

Atlassian Confluence — the BigCo internal-wiki + knowledge-base standard; page hierarchy + labels + templates + macros; Cloud vs Data Center deployment models. Notion — the mid-market / startup internal-docs + KB standard; page hierarchy + database views + collaborative editing. SharePoint / Microsoft Loop / OneDrive — the Microsoft-ecosystem enterprise wiki + KB. Zendesk Guide / HelpScout / Intercom Articles / Salesforce Knowledge — customer-facing help-center KB platforms. Content-model discipline across all of these — page hierarchy, tagging, ownership + review cycle, deprecation + sunset workflow. Confluence + Zendesk API integration for content-syndication + one-source-multi-output publishing.

Documentation strategy + information architecture + content-audit discipline

Every Page Is Page One (Mark Baker) principle — write topic-based documentation that stands on its own as a landing page from search. Diátaxis framework (Daniele Procida) — 4 documentation types (tutorials, how-to guides, reference, explanation) each with distinct purpose + writing style; used at Django, Google Cloud, Cloudflare, and many others. Information architecture — top-level navigation, product-taxonomy, cross-linking, tagging + faceted-search discipline. Content-audit process — inventory (URL + last-modified + owner + traffic), gap analysis (product features vs docs coverage), retirement (deprecation + sunset + redirect). Style guides — Chicago Manual of Style + Microsoft Manual of Style + Google Developer Documentation Style Guide + AP Stylebook + Read Me First! (Sun / Oracle DITA style guide).

Developer experience (DX) + UX writing + product content design crossover

Developer experience (DX) writing — READMEs + Quickstarts + tutorials + code-samples + API references + SDK docs + CLI docs + error-message + log-message writing; the crossover between technical writing and developer advocacy / DevRel. UX writing — in-product microcopy (button labels, error messages, empty-states, onboarding flows, notification copy) at consumer-software companies; often reports into Product Design rather than Documentation. Product content design — the modern discipline combining UX writing + content strategy + information architecture across a product surface; roles at Google, Meta, Netflix, Airbnb, Spotify, Uber increasingly have Product Content Designer titles at $185-315k+ TC.

Medical-device labeling + FDA 21 CFR Part 801 + IEC 62366 usability

FDA 21 CFR Part 801 governs medical-device labeling — indications for use, contraindications, warnings, precautions, adverse events, instructions for use (IFU). 21 CFR Part 820.30 design-controls integration — the IFU is a design-control document reviewed as part of the Device Master Record (DMR). IEC 62366 (Medical Devices — Application of Usability Engineering) — the international standard for usability engineering + human-factors testing; feed forward into the labeling. FDA guidance on Unique Device Identifier (UDI) labeling under 21 CFR §801.20. Global harmonization — IMDRF (International Medical Device Regulators Forum) and MDR (EU Medical Device Regulation 2017/745) drive parallel labeling requirements outside the US.

Pharma regulatory writing + eCTD + FDA / EMA submissions

eCTD (electronic Common Technical Document) — the ICH M4 harmonized submission format for FDA + EMA + PMDA (Japan) + Health Canada; 5-module structure (M1 regional administrative, M2 CTD summaries, M3 quality, M4 nonclinical study reports, M5 clinical study reports). Investigational New Drug (IND) submissions under 21 CFR Part 312. New Drug Application (NDA) submissions under 21 CFR Part 314. Biologics License Application (BLA) submissions under 21 CFR Part 601. Post-approval — Prescribing Information (PI) under 21 CFR §201.57 + Medication Guides under 21 CFR Part 208 + Risk Evaluation and Mitigation Strategies (REMS) under FDCA §505-1. Clinical Study Report (CSR) writing under ICH E3 guideline. Common Technical Document Quality Overall Summary (CTD QOS) discipline for the M2 summaries.

STC + AMWA + RAPS professional-community engagement

STC (Society for Technical Communication) — the primary US technical-writing professional society; STC Summit annual conference; STC CPTC (Certified Professional Technical Communicator) certification; local chapter engagement. AMWA (American Medical Writers Association) — the primary medical + pharma writing professional society; AMWA Essential Skills certificate + AMWA Advanced certificate + AMWA CPD (Certified Professional in Medical Writing) credential. RAPS (Regulatory Affairs Professionals Society) — the primary regulatory-affairs professional society; RAC (Regulatory Affairs Certification) credential is the gold-standard credential for pharma + medical-device regulatory writers. WriteTheDocs — the modern software-documentation professional community with 3 annual conferences (Portland, Prague, Australia) + strong developer-docs focus.

How to Become a Technical Writers

1
Complete a Bachelor's — technical writing, computer science, English, journalism, or a science/engineering field
Common entry paths — B.S. in Technical Communication (Texas Tech, Michigan Tech, University of Central Florida, University of Washington, Metropolitan State Denver, RIT); B.S. in Computer Science with strong writing (top developer-docs candidates often come from CS backgrounds); B.A. in English + technical-writing minor; B.S. in a science / engineering field for medical-device or pharma work. Portfolio > degree at software companies — a strong GitHub-hosted portfolio of documentation samples matters more than the specific degree.
2
Build a portfolio — 3-8 documentation samples on GitHub or a personal site
Portfolio pieces that resonate with hiring managers — (1) an OSS project documentation contribution (submit a PR to a popular OSS project's docs; the merged PR is your credential); (2) a personal API-doc project using OpenAPI / Swagger / Redoc; (3) a Diátaxis-framework tutorial + how-to + reference + explanation set for a small tool you built; (4) a redesign proposal for an existing product's documentation with a specific improvement thesis; (5) a technical blog post explaining a hard concept clearly. Portfolio hosted on GitHub Pages + Netlify + Vercel + personal domain.
3
Start in an entry technical writer / documentation specialist seat at $58-82k + benefits
First seats — Technical Writer I / Documentation Specialist / Content Developer / Information Developer at Microsoft, Google, Amazon, Salesforce, Oracle, IBM, Meta, Apple, Stripe, GitHub, Atlassian, MongoDB, HashiCorp; or Medical Writing Associate at Pfizer / Merck / J&J / AbbVie / BMS / Eli Lilly / Novartis / AstraZeneca / Roche; or Regulatory Writing Associate at a medical-device or pharma CRO (IQVIA, Parexel, Syneos, ICON, Fortrea). Entry at Big Tech typically requires portfolio + interview loop; entry at pharma / medical-device typically requires science / engineering degree.
4
Get an STC / AMWA / RAPS certification appropriate to the track
STC CPTC (Certified Professional Technical Communicator) — the general technical-communication credential; $250-450 exam. AMWA Essential Skills certificate + AMWA CPD (Certified Professional in Medical Writing) — the medical-writing credential; $200-500 per certificate. RAPS RAC (Regulatory Affairs Certification) — the regulatory-affairs credential; $500-750 exam; the gold-standard credential for pharma + medical-device regulatory writers. WriteTheDocs conference attendance + local-meetup engagement + open-source docs contributions are the modern developer-docs credentials.
5
Specialize — developer docs vs medical-device vs pharma regulatory vs UX writing
Developer docs — deep API-doc + code-sample fluency; strong Git + Markdown + OpenAPI; ability to read code (Python / JavaScript / TypeScript / Go); crossover to DevRel + Developer Advocate track. Medical-device — 21 CFR Part 801 labeling + IEC 62366 usability + design-controls discipline; typical employer Medtronic, Abbott, Boston Scientific, Stryker, J&J MedTech. Pharma regulatory — eCTD + IND / NDA / BLA submissions + Clinical Study Reports; typical employer Pfizer, Merck, J&J, AbbVie, BMS, Eli Lilly, Novartis, AstraZeneca. UX writing — in-product microcopy + product content design; typical employer Google, Meta, Netflix, Airbnb, Spotify, Uber, Salesforce.
6
Advance to established / senior technical writer at $85-155k + equity at Big Tech
5-9 years in seat. Established Technical Writer / Sr Technical Writer / Content Developer II at Big Tech + SaaS + pharma. At Big Tech (Google, Meta, Microsoft, Amazon, Apple), Senior Technical Writer TC frequently clears $145-215k (base + RSUs + bonus). At mid-market SaaS (Stripe, Snowflake, Databricks, MongoDB, HashiCorp, Datadog, Twilio), Senior TC often clears $155-235k (base + equity + bonus). At pharma + medical-device, Sr Regulatory Writer / Sr Medical Writer TC $115-165k with strong benefits + LTIP.
7
Advance to Staff / Principal Technical Writer or documentation manager at $155-265k+ TC
10-16 years in seat. Staff / Principal Technical Writer — the IC-track ceiling before Distinguished; own an entire product-line's documentation strategy; scope 3-8 writers via influence not direct management. Documentation Manager / Head of Docs — the management-track step at $185-315k+ TC with equity; scope 6-25 writers direct + contract. At pharma + medical-device, Director Regulatory Writing / Sr Director Medical Writing $175-285k + LTIP.
8
Move to Distinguished Technical Writer / Director of Documentation / VP Documentation / Content Design at $215-485k+ TC
15-25+ years. Distinguished Technical Writer — the top IC-track at Big Tech; typically 2-6 seats per company. Director / VP Documentation at Big Tech + high-growth SaaS $315-585k+ TC with equity. Director / VP Regulatory Affairs at pharma + medical-device $285-485k+ base + LTIP. VP Product Content Design at consumer-software $385-685k+ TC. Some senior writers exit to independent-consultant + fractional-Head-of-Docs track at $185-385/hr day rates.

Career Progression

Entry Technical Writer

0-4 yrs$58-82k salaried + 8-12% bonus at Big Tech + $18-35k RSU/equity at Big Tech + full benefits

•Write and maintain API references, tutorials, how-to guides, and reference documentation under senior review
•Participate in docs-as-code workflow — Git branch + PR + review + merge; contribute to the CI / CD docs build
•Own the docs for 1-3 product-area features; partner with 2-5 engineers on shipping documentation with the release
•Support the docs-quality feedback loop — user analytics + support-ticket pattern analysis + docs-improvement backlog

Next: Sr Technical Writer / Technical Writer II at 4-7 years with product-area ownership + specialty depth.

Established / Senior Technical Writer

4-10 yrs$85-155k salaried + 12-18% bonus + $45-95k RSU/equity at Big Tech + full benefits

•Own the documentation for a full product area (Compute + Storage + Networking + Security + Identity depending on product taxonomy)
•Partner with 8-20 engineers + PMs + Support on release-cadence docs delivery + quality improvement
•Serve as a technical reviewer for junior writers' work; contribute to the style guide + information-architecture decisions
•Own the docs metrics for the product area — traffic, engagement, support-ticket reduction, developer-time-to-first-integration

Next: Staff / Principal Technical Writer or Documentation Manager at 10-14 years.

Staff / Principal Technical Writer or Documentation Manager

10-16 yrs$155-265k+ TC (base $145-195k + RSU $35-95k + bonus $18-32k at Big Tech)

•Staff / Principal — own strategy for an entire product line's documentation; influence 3-8 writers without direct management authority
•Documentation Manager — direct-manage 4-12 writers; own recruiting, career development, and documentation-team velocity metrics
•Own the docs-tooling strategy — Docusaurus vs MkDocs vs custom stack decisions; DITA vs Markdown migration decisions
•Represent Documentation at cross-functional leadership forums — Product Council, Engineering Council, DevRel Council

Next: Director / VP Documentation or Distinguished Technical Writer at 15-25 years.

Director / VP Documentation, Distinguished Technical Writer, or Product Content Design Leader

15-25+ yrs$215-485k+ TC at Big Tech + high-growth SaaS + top pharma; $185-345k at mid-market + medical device

•Own enterprise-wide documentation strategy — product docs + developer docs + KB + community docs + release notes
•Manage a documentation org of 20-100+ writers, content strategists, and information architects
•Own the docs-platform investment — content-management-system decisions, publishing-pipeline architecture, LLM-assisted docs discipline
•Represent Documentation to the CEO + Board on product-launch enablement, developer-relations impact, and support-cost-reduction outcomes

Interview Questions & Answers

5 free questions below. Career Kit unlocks 13 total plus resume bullets for every level.

Q1. Walk me through the last documentation project you shipped end-to-end.technical

Structured, with real detail. Example: 'Sr Technical Writer at Stripe on the Payments API team. Project: relaunch the Payment Intents documentation set with a new three-column layout (prose + endpoint reference + code samples in 7 languages) after Stripe's 2023 Payment Intents API GA. Pre-launch (10 weeks prior): partnered with 4 engineers on the Payments API team + 2 PMs + 1 solutions engineer to scope the docs deliverable — a Quickstart, 6 how-to guides for common payment flows, a full API reference for the Payment Intents endpoint set (14 endpoints, 60+ parameters, 8 webhook events), and a migration guide from the legacy Charges API. Content-authoring phase (6 weeks): wrote the Quickstart + how-to guides in Markdown; auto-generated the API reference from the OpenAPI 3.0 spec; wrote the migration guide with side-by-side code samples in JavaScript / Python / Ruby / PHP / Java / Go / .NET. Review phase (2 weeks): engineering technical accuracy review by 4 engineers; UX writing review from the design team; PM alignment on messaging + positioning. Launch (2 weeks): docs went live 3 business days ahead of the GA announcement; supported the launch-week docs-quality feedback via Twitter + StackOverflow + Support ticket triage. Result: 68% reduction in Payment-Intents-related support tickets over 90 days; a 32% increase in developer-time-to-first-integration completion rate against the Charges API baseline; called out in the Stripe engineering blog post for launch impact.' Interviewers want real product, real API surface, real metrics — not 'I wrote some docs.'

Q2. Describe how you'd handle documentation for a feature the engineering team is still building.situational

Structured. (1) Engagement timing — get involved at Product Spec + Engineering Design Doc stage, not at code-freeze. The best docs-writer relationships with engineers start 4-8 weeks before shipping. (2) Draft against the design — write a first draft from the design doc + API spec + UI mocks; this forces the engineering team to clarify their design where the docs can't be written cleanly. (3) Iterate in parallel — as the engineering team ships iterations behind a feature flag, revise the docs; use the shipping code as the source of truth (not the design doc) for the final API surface. (4) Bug reporting on behalf of docs — 'I can't write clear docs for this because parameter X and parameter Y both mean the same thing; can we consolidate?' Docs writers who file bug reports on API surface ambiguity are the ones who earn seat-at-the-design-review-table access. (5) Draft-vs-source pinning — every doc is pinned to a specific commit SHA of the source in the docs-as-code review; if the engineering team ships a breaking change post-doc-freeze, the docs-CI catches it. (6) Launch coordination — align the docs go-live with the feature GA announcement; do not publish docs for a feature that hasn't shipped. (7) Post-launch — capture the immediate customer feedback + support-ticket pattern and iterate quickly in week 1-2. Interviewers screen for writers who see themselves as part of the shipping team, not as downstream consumers of engineering work.

Q3. Describe a difficult documentation project — technical, cross-functional, or high-stakes.behavioral

STAR. Situation: Sr Technical Writer at Databricks on the Delta Lake team. Task: document the Delta Lake 3.0 Unity Catalog integration for the Databricks Runtime 14.0 GA, a cross-team surface spanning Delta Lake OSS, Unity Catalog, Databricks Runtime, and the Databricks SQL query engine — 4 engineering teams, 3 PMs, 2 developer-advocates, and a hard external launch commitment tied to a Q4 Databricks Data + AI Summit keynote. Action: (1) 8 weeks pre-launch, held a docs-scoping session with all 4 engineering-team tech leads + PMs; mapped the docs surface (Quickstart, migration guide, 12 how-to guides, full Unity Catalog admin reference, 20+ concept + explanation pages) against the release scope; (2) split the writing across 3 technical writers (me on the Unity Catalog admin reference + concept pages; 2 peers on the how-to guides + migration + Quickstart); (3) coordinated with the Databricks docs-tooling team on a new Docusaurus + MDX interactive-example rendering for the Unity Catalog RBAC configuration examples; (4) ran a Documentation Design Review with 8 engineers + 2 PMs + 1 developer advocate at week 4 with a full staging-environment walkthrough; incorporated 42 reviewer comments; (5) launched 5 business days ahead of the DAIS keynote with the full 60-page Unity Catalog documentation set live in production. Result: DAIS keynote demo went smoothly with docs as the audience-facing reference; +$18M ARR attribution to Unity Catalog GA in the following 6 months per PM analytics; 4.7 / 5.0 average docs-page rating in the first 90 days; called out in Databricks CEO's earnings-call remarks on the DAIS launch. Interviewers want real launch, real cross-functional coordination, real metrics.

Q4. Why technical writing rather than engineering, product management, or UX writing?culture

Honest answer that resonates. Multiple valid framings. (1) Writing + technical depth combination — 'I love the puzzle of taking a complicated technical thing and making it clear for the reader. Engineering builds the thing; writing shapes how the world sees the thing. At Big Tech + SaaS, that's a $155-215k Senior TC seat with equity, and Staff / Principal is $215-315k+ TC.' (2) Cross-functional impact — 'A technical writer sits at the intersection of engineering, product, support, and developer-relations. Well-shipped docs reduce support tickets 40-70% and improve time-to-first-integration 25-40%, which is more measurable business impact than most engineering seats produce.' (3) UX writing crossover — 'I'm actively building the product-content-design skill set because that's the emerging discipline at consumer software; the Product Content Design track at Google / Meta / Airbnb reaches $285-385k TC.' (4) Pharma / medical-device regulatory writing — 'The FDA / EMA submission work at Pfizer / Merck / J&J / Medtronic is high-stakes and high-comp; a Sr Regulatory Writer at $135-165k + LTIP with the RAC credential is a substantive-work career.' Interviewers screen for candidates who chose the discipline deliberately.

Q5. Where do you see your career in 5 years?closer

Show the fork clearly. Multiple tracks — Big Tech / SaaS IC track (Sr Technical Writer → Staff Technical Writer → Principal Technical Writer → Distinguished Technical Writer at $215-485k+ TC); manager track (Sr Technical Writer → Documentation Manager → Director / VP Documentation at $315-585k+ TC); UX writing / product-content-design track (Sr UX Writer → Content Design Lead → Director Product Content Design at $315-585k+ TC at consumer software); pharma / medical-device regulatory track (Sr Medical Writer → Director Regulatory Writing at $285-485k+ base + LTIP). I'm on the developer-docs IC track. I've completed my STC CPTC + WriteTheDocs conference speaking, I'm currently a Sr Technical Writer at Stripe on the Payments API team with strong DX + OpenAPI + Docusaurus fluency, and I'm 6 months into leading the Payments Foundation docs strategy across 4 engineers + 2 PMs. Within 24-36 months I'd like to promote to Staff Technical Writer at Stripe or a lateral Staff move at Snowflake / Databricks / MongoDB / HashiCorp / Datadog at $195-265k TC. Longer-term target: Principal Technical Writer at $265-345k TC.

Resume Template — Established / Senior Technical Writer (4-10 yrs)

Copy these bullets into your resume as a starting point. Career Kit includes bullets for every level of the ladder.

Established / Senior Technical Writer (4-10 yrs)

▸Sr Technical Writer at Stripe on the Payments API team; led the 2023 Payment Intents docs relaunch with a new three-column layout + 7-language code samples covering 14 endpoints + 8 webhook events.
▸Delivered a 68% reduction in Payment-Intents-related support tickets over 90 days and a 32% increase in developer-time-to-first-integration completion rate; called out in the Stripe engineering blog for launch impact.
▸Own the docs-as-code workflow for the Payments API surface — Docusaurus + MDX + OpenAPI 3.0 auto-gen + Redoc reference-page rendering + GitHub Actions CI-build preview + auto-deploy on merge.
▸STC CPTC certified + WriteTheDocs 2023 speaker on API-doc DX. BS Technical Communication (Michigan Tech). $165k base + $65k RSU annual grant + 15% target bonus + full benefits.

What Gets You Rejected

✗Portfolio-thin candidates at software / SaaS seats — hiring managers screen for a GitHub-hosted portfolio of 3-8 samples; no portfolio at Big Tech + high-growth SaaS is close to automatic screen-out.
✗Weak Git + Markdown + Docusaurus / MkDocs fluency at developer-docs seats — docs-as-code is table stakes; a writer who can't do a pull request + resolve merge conflicts is not competitive at Big Tech.
✗Inability to read code (Python / JavaScript / TypeScript / Go) at API-doc + developer-docs seats — writers who won't read the source to verify docs accuracy drive up engineering-review time.
✗No specialty depth after 5+ years — a technical-communications-generalist without a developer-docs or medical-device or pharma-regulatory or UX-writing specialty is capped at $95-125k mid-career.
✗History of docs shipped after the product launch — 'launch-shipping' cadence is the modern standard; a writer who chronically misses launch cadence is not viable at Big Tech + high-growth SaaS.
✗Weak analytics + metrics fluency — the modern technical writer is measured on docs traffic, engagement, support-ticket reduction, and developer-time-to-first-integration; writers who don't use analytics data are stuck at the IC-2 ceiling.
✗Poor engineering-partnership signals — engineers who report the writer 'doesn't understand our work' or 'writes docs that don't match our design' block promotion pathways.

Salary Negotiation Levers

✓Developer-docs specialty premium — deep API-doc + OpenAPI + Docusaurus + Markdown fluency at Big Tech + high-growth SaaS commands 25-45% above technical-communications-generalist for the same title. Stripe, Snowflake, Databricks, MongoDB, HashiCorp, Datadog, Twilio pay the developer-docs premium most aggressively.
✓Medical-device + pharma-regulatory specialty premium — RAC (Regulatory Affairs Certification) + eCTD + FDA submission experience at Pfizer / Merck / J&J / Medtronic / Abbott commands 15-30% above generalist tech-writing at the same title.
✓UX writing / product-content-design premium — consumer-software product-content-design roles at Google / Meta / Airbnb / Spotify / Uber / Netflix pay 20-40% above traditional technical-writing at the same tenure.
✓Big Tech equity — RSU grants at Google, Meta, Microsoft, Amazon, Apple, Salesforce typically add $45-135k / year to Senior TC and $95-265k / year to Staff / Principal TC. This is the single biggest earnings lever above the base + bonus.
✓High-growth SaaS pre-IPO equity — Stripe, Snowflake, Databricks, MongoDB, Datadog, HashiCorp, Twilio pre-IPO grants can be worth $185-485k+ over 4 years at strong outcomes.
✓Metro premium — SF Bay / NYC / Seattle / Boston / Austin / LA pay 15-30% above US median for the same seat.
✓Sign-on bonus — Big Tech + high-growth SaaS moves routinely negotiate $25-95k sign-on to offset unvested equity at the prior employer.
✓RSU refresh cadence — the annual RSU refresh at Big Tech + high-growth SaaS is the retention lever; ask for the annual refresh target, not just the initial grant, at Sr Technical Writer + Staff Technical Writer levels.
✓Documentation-team-lead / Documentation Manager premium — moving from Senior IC to first-line management adds 15-25% base + LTIP but caps overtime + focused-work time; the math often favors IC track until Staff / Principal ceiling.
✓External speaking + WriteTheDocs + STC / AMWA / RAPS presence — visible external work at conferences and in the docs-community accelerates the Staff / Principal / Distinguished IC-track and opens external-Director-of-Docs offers.

Already a Technical Writers? Grow From Here

Free playbooks on what actually gets you promoted and raised — not motivational advice, the real mechanics.

How to Ask for a Raise The Promotion Playbook — What Actually Gets People Promoted How to Write a Self-Review That Positions You for Promotion How to Build a Promotion Packet Your Committee Can't Ignore

Technical Writers Resume Review — $29

Personalized resume review from someone who has hired technical writerss. Purchase, email your resume to support@weblabra.com, and receive detailed written feedback within 7 days.

✓ Occupation-specific critique (not generic)
✓ Rewrite suggestions for weak bullets
✓ Missing skills / keywords flagged
✓ Formatting + ATS-readability feedback
✓ 7-day turnaround, 100% refund if we miss it

Technical Writers Career Kit — $19

✓ All 13 interview questions with expert answers
✓ 8 real questions aggregated from Glassdoor, Blind, Reddit, LinkedIn
✓ Interview format intel for 8 top employers
✓ 3 copy-paste salary negotiation emails
✓ Resume bullets for every level of the career ladder
✓ 30–60–90 day plan for your first role
✓ Cover letter templates specific to this occupation
✓ Detailed salary negotiation script
✓ Ranked list of certifications with cost + ROI
✓ Downloadable PDF for offline access
✓ Instant access, no expiration, no subscription

✓ 7-day money-back guarantee — no questions asked

One-time purchase. 7-day refund guarantee.

Sample reviews — real customer reviews will appear here as they come in.

“The interview question bank saved me. I got the exact question about 'walking through a DCF' at my Goldman Sachs superday, verbatim.”

— Anonymous, Financial Analyst

“Copy-paste negotiation emails are worth the price alone. I used the 'accepting with counter' template and got an extra $8k signing bonus.”

— Anonymous, Software Developer

“The 30-60-90 day plan for a new grad RN was better than the orientation my hospital gave. Wish I'd bought this in nursing school.”

— Anonymous, Registered Nurse

Technical Writers Career Growth Kit — $29

Already working as a technical writers? This kit is for building your case for the next promotion or raise — not for getting hired.

✓ Self-review draft mapped to technical writers competencies
✓ Promotion packet outline with evidence appendix structure
✓ 30–60–90 day evidence-collection plan
✓ Promotion committee anticipation guide
✓ Tenure and pay reference bands by level
✓ Downloadable PDF for offline access

✓ 7-day money-back guarantee — no questions asked

One-time purchase. 7-day refund guarantee.

Technical Writers Salary by State

Best Cities (cost-adjusted) →

Salary Map — Click a state for details

$61K

$122K■ No data

Top Paying States

Vertical line = national median. Click a state for full details.

State	Median	vs. National	Employment
New Jersey	$122,320	+35.3%	1,550
District of Columbia	$117,810	+30.3%	440
Massachusetts	$109,200	+20.8%	1,850
Washington	$104,070	+15.1%	1,620
California	$104,000	+15.1%	5,280
Rhode Island	$102,360	+13.2%	150
Connecticut	$101,870	+12.7%	770
Maryland	$100,990	+11.7%	1,780
Colorado	$100,610	+11.3%	1,320
New York	$98,310	+8.8%	1,610

Showing 1–10 of 45

Technical Writers Salary by Metro Area

Metro Area	Median	vs. National
San Jose-Sunnyvale-Santa Clara, CA	$140,700	+55.7%
San Francisco-Oakland-Fremont, CA	$135,470	+49.9%
Santa Rosa-Petaluma, CA	$129,590	+43.4%
Kennewick-Richland, WA	$119,160	+31.8%
Trenton-Princeton, NJ	$117,130	+29.6%
Boston-Cambridge-Newton, MA-NH	$111,750	+23.6%
New York-Newark-Jersey City, NY-NJ	$111,050	+22.9%
Seattle-Tacoma-Bellevue, WA	$107,580	+19.0%
Bridgeport-Stamford-Danbury, CT	$106,900	+18.3%
Boulder, CO	$105,840	+17.1%

Showing 1–10 of 137

Data Source: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics (OEWS). Data reflects the most recent annual survey.

How does this compare to pro athletes?

A technical writers earning $90,390/year would need 659 years to match Stephen Curry's NBA salary, or 708 yearsto match Patrick Mahomes' NFL contract.

See all sports & celebrity salaries →

📈 See how technical writers salaries have changed over the past decade.

View Technical Writers salary trend (2011–2024) →