Technical writer CVs have two failure modes that cancel out otherwise strong candidates. The first is the missing portfolio link — technical writing is a portfolio-based profession, and a CV without a link to writing samples (a live documentation site, a GitHub repo with Markdown files, a published help centre, or a portfolio page) gives the recruiter nothing to evaluate the most important thing: whether the candidate can actually write. The second is tool mismatch: a CV listing MadCap Flare, RoboHelp, and Author-it as the primary tools for a role at a software company using Docusaurus, GitHub, and a Markdown pipeline signals a traditional authoring background in a docs-as-code environment — a gap that screens out experienced writers who simply haven't updated their tool vocabulary. The technical writing market in 2026 is divided between two distinct production workflows: traditional structured authoring (MadCap Flare, DITA/XML, Paligo) for hardware, aerospace, and regulated industries, and docs-as-code (Markdown, Git, static site generators like Docusaurus or MkDocs, CI/CD pipelines for deployment) for software and API documentation. Knowing which one the role requires — and signalling the right toolkit — is as important as the writing samples themselves.

What Technical Writer Job Descriptions Require in 2026

Technical writer JDs divide across three specialisations with significantly different tool and knowledge requirements:

Software and API documentation: The largest segment of software company technical writing. JDs specify: Markdown proficiency, Git and GitHub (writing in a docs-as-code workflow alongside engineers), a static site generator (Docusaurus, MkDocs, Sphinx, or Mintlify), API documentation experience (OpenAPI/Swagger specification authoring or developer portal documentation), and Confluence or Notion for internal documentation. Senior JDs add the ability to write code samples (Python, JavaScript, or cURL for every API endpoint), information architecture skills (structuring a documentation site for discoverability), and experience with tooling like ReadMe.io, Redoc, or Stoplight for developer portals. Increasing number of JDs mention Vale for automated prose linting in CI.

Structured authoring and regulated documentation: Technical writing for hardware manufacturers, aerospace, defence, medical devices, and industrial equipment. JDs specify: DITA XML authoring (DITA-OT, Oxygen XML), a CCMS platform (MadCap Flare, Paligo, Heretto, Ixia CMS), single-source publishing (producing PDFs, HTML, and print-ready output from a single source), and often industry standards knowledge (MIL-STD for defence, IEC 82079 for user instructions, ISO 17071, FDA requirements for medical device IFU documentation). These roles are content strategy plus engineering — DITA topic types, relationship tables, and conditional text filtering are technical skills, not just writing conventions.

Developer relations and developer experience (DevEx): Technical writing that overlaps with developer advocacy. JDs specify: ability to write and run code samples (the writer must be able to execute and verify every example), tutorial authoring for developer audiences (Getting Started guides, SDK integration guides, code-along tutorials), community engagement (maintaining GitHub repos, answering forum questions, writing changelog entries), and often a GitHub profile with real code. These roles blur the line between technical writer and junior developer.

Cross-type requirements: a documentation portfolio linked from the CV header, experience interviewing subject matter experts (SMEs), familiarity with a style guide (Google Developer Documentation Style Guide, Microsoft Writing Style Guide, or a custom company guide), and Jira or Linear for tracking documentation tasks in an engineering workflow.

Technical writer salaries in 2026: £35K–£55K UK; £55K–£85K for senior API documentation specialists. US: $75K–$115K; $100K–$155K for developer documentation engineers at platform companies.

ATS Keywords for a Technical Writer Resume

Technical writer ATS filtering uses tool names, content type names, and workflow terminology. "Experienced technical writer" as a standalone phrase is the weakest signal.

Essential ATS terms for a technical writer resume:

  • Title variants: Technical Writer, Senior Technical Writer, Technical Documentation Specialist, API Documentation Writer, Documentation Engineer, Developer Documentation Writer, Technical Communications Specialist, Documentation Manager, Content Designer, UX Writer
  • Content types: user guide, user manual, API documentation, API reference, release notes, help centre, knowledge base, SDK documentation, developer documentation, tutorial, quick start guide, installation guide, troubleshooting guide, runbook, DITA topic, IFU, operator manual
  • Docs-as-code tools: Markdown, AsciiDoc, Git, GitHub, GitLab, Docusaurus, MkDocs, Sphinx, Hugo, Mintlify, ReadMe, Gitbook, Confluence, Notion, Vale, static site generator, CI/CD
  • Traditional authoring tools: MadCap Flare, Adobe RoboHelp, Paligo, Heretto, Oxygen XML, Author-it, Ixia CMS, DITA, DITA XML, DITA-OT, single-source publishing
  • API documentation tools: OpenAPI, Swagger, REST API, Redoc, Stoplight, Postman, OpenAPI 3.0, developer portal, API reference
  • Diagram and visual tools: Mermaid, Draw.io, Lucidchart, Visio, PlantUML, Figma, Snagit, Camtasia
  • Style and quality: Google Developer Documentation Style Guide, Microsoft Writing Style Guide, Vale, LanguageTool, information architecture, style guide, content strategy
  • Localisation: Crowdin, Phrase, Transifex, translation management, localisation, i18n
  • Long-tail phrases: technical writer resume, technical writer cv, how to write a technical writer resume, API documentation writer resume, senior technical writer resume, technical writing portfolio, technical writer resume 2026, docs-as-code resume

Placement: Portfolio URL in the CV header — mandatory, immediately below the name. Tool stack named explicitly for the specific workflow type of the role: if the JD mentions Docusaurus, name Docusaurus; if it says MadCap Flare, name Flare. Content types in the Skills section first line (API documentation, developer guides, release notes, DITA user manuals) — these are the primary ATS filter terms for technical writing roles.

Technical Writer CV Structure and Bullets That Show Documentation Scale and Tool Depth

Section order:

  1. Header — name, portfolio URL (mandatory), GitHub if relevant, LinkedIn, location
  2. Headline — "Technical Writer | API Documentation · Docs-as-Code · Docusaurus · OpenAPI · Git"
  3. Skills — Content Types / Authoring Tools / Workflow Tools / Audiences / Industries
  4. Experience — 4–5 bullets per role; content type, tool stack, audience, scale (page count, user sessions, document count), and measurable outcome per bullet
  5. Portfolio — if not listed in header, a dedicated section: 2–3 of your strongest documentation samples with a one-line description of what each covers and a live URL or PDF link
  6. Education — English, journalism, communications, computer science, or technical communication degree; certifications (STC Certified Technical Writer) at bottom

Two pages for 5+ years. Portfolio link in the header is not optional — it is the primary selection criterion for every technical writing role and must be the second line the recruiter reads.

Three elements make a technical writer bullet convincing: the content type and tool used, the scope and scale of the work (document count, page volume, audience size), and a measurable quality or outcome signal (review pass, adoption metric, load time, user feedback). Three examples:

  • Migrated a 4,200-page MadCap Flare help system to a Docusaurus docs-as-code architecture — converted all topics to Markdown, established a GitHub pull request review workflow with Vale prose linting enforcing the Google Developer Documentation Style Guide, and configured GitHub Actions CI/CD for automatic deployment to Cloudflare Pages; documentation site load time from 4.2s to 0.8s; engineering team adopted a weekly doc-PR habit within 3 months of launch
  • Wrote and maintained the REST API reference for a payments platform — 23 endpoints documented as an OpenAPI 3.0 YAML specification, published via Redoc on a ReadMe.io developer portal, with verified code samples in Python, JavaScript, and cURL for every endpoint and response variant; API documentation cited by 3 enterprise customers in post-sales calls as the primary reason for platform selection over comparable competitors
  • Produced the complete operator documentation set for an industrial IoT device manufacturer — 28 documents authored in DITA XML using Oxygen XML, covering installation, configuration, maintenance, and troubleshooting procedures; managed SME review workflow with 6 engineering subject matter experts across 3 time zones; documentation package passed ISO 17071 conformity review with zero major non-conformities and now supports product deployment in 14 countries

Technical writer interviews include a writing exercise (here is a rough spec or engineering note — write a brief user guide section), a portfolio review (walk me through your three strongest samples), and a tool knowledge discussion (how does your docs-as-code pipeline work?). Your CV's portfolio link and tool stack signal whether the interview focuses on your documentation quality or your ability to learn the company's authoring environment.

Three Technical Writer CV Mistakes That Lose the Portfolio Advantage

No portfolio link in the CV header. Technical writing is a portfolio profession — the CV is the index, the portfolio is the evidence. A hiring manager who cannot read samples within 30 seconds of opening a technical writer CV has no way to assess the quality of the candidate's actual work. This is not a secondary nice-to-have. It is the primary selection criterion, more important than tool lists or quantified metrics. If you have no public portfolio, create a GitHub Pages site or a free ReadMe.io project with 2–3 redacted or personal project documentation samples before applying. If your best work is under NDA, produce a personal documentation project — write the API reference for a public API, or document an open-source tool — and link to that.

Tool list optimised for a different workflow type. Technical writing divides between docs-as-code (Markdown, Git, Docusaurus, GitHub Actions) and traditional authoring (MadCap Flare, DITA, Paligo, Oxygen XML). Many technical writers have experience primarily in one and are applying to roles in the other without adjusting their CV. A CV listing MadCap Flare, RoboHelp, and Author-it for a software company role that mentions Docusaurus, GitHub, and Markdown in the JD will be screened out for tool gap even if the writing quality is excellent. Read the JD's tool requirements carefully and lead with the tools that match. If you have docs-as-code experience (even personal projects), it belongs on the CV before traditional authoring tools when applying to software company roles.

No audience or domain specified. "Technical writer with 7 years of experience producing documentation" is the equivalent of a developer saying "experienced programmer who has written code." The specialisation is the signal. Technical writing audiences and content types vary enormously — developer API documentation, aerospace maintenance manuals, medical device IFU, enterprise SaaS user guides — and the skills required for each are substantially different. Name your primary audience (software developers, field technicians, enterprise end users, regulatory reviewers) and your primary content types (API reference, DITA maintenance procedures, SaaS help centre, SDK tutorials) in your headline and Skills section. This specificity is what makes a technical writer CV relevant to a specific role rather than generically available.

If you are applying to technical writer or documentation engineer roles and want your CV rebuilt around the specific tool stack, content type, and audience requirements in a target job description, Resumegpt generates your technical writer CV from your work history in under 60 seconds — portfolio signals positioned, tool stack matched to the JD, domain expertise named, ATS-optimised, and exported as a PDF ready to submit.