Technical Writer Resume Example (2026 Guide)
Technical Writer resume example
A complete sample in the Modern template FitMyRole exports. The person and employers are fictional; the structure, skills and bullet style are what to copy.
Aisha Jallow
[email protected] • (555) 015-2836 • Raleigh, NC • linkedin.com/in/aishajallow
Professional Summary
Technical Writer with 4 years of experience writing API references, developer guides and end-user documentation for B2B software and payments products. Owns the developer portal for a data integration platform used by about 1,200 customer engineers: REST API reference for 85 endpoints, quickstarts and SDK guides published from a docs-as-code pipeline. Cut integration-related support tickets by 31% in a year by rewriting the authentication and webhooks guides from ticket analysis and usability sessions. Works inside the engineering workflow, reviewing pull requests, writing from OpenAPI specs and testing every code sample before it ships.
Skills
- Documentation Types: API documentation, developer docs, SDK guides, quickstarts and tutorials, user guides, release notes, knowledge base articles, standard operating procedures
- Docs-as-Code & Authoring Tools: Markdown, Docusaurus, Git and GitHub, GitHub Actions, Vale linter, MadCap Flare, Confluence, Zendesk Guide
- API & Developer Tools: OpenAPI 3.0, Swagger, Postman, REST APIs, JSON, cURL, Python and Node.js basics
- Writing & Technical Editing: Technical editing, Google developer documentation style guide, information architecture, topic-based authoring, plain language, terminology management
- Research & Measurement: Usability testing, support ticket analysis, Google Analytics 4, docs feedback widgets, content audits
- Collaboration: Engineering pull request reviews, SME interviews, Jira, sprint planning, cross-team content reviews
Education & Certification
- Coursework focus: Technical Communication, Writing for the Web, Document Design, Introduction to Python and Database Systems.
- Course completion covering active voice, list and table design, and documenting code samples.
Work Experience
Technical WriterJanuary 2024 – PresentPinecrest Cloud Software, Durham, NC
- Reduced integration support tickets by 31% in 12 months by rewriting the authentication, pagination and webhooks guides after tagging 400 Zendesk tickets by topic with the support team.
- Moved the developer portal from a Confluence space to a docs-as-code site built with Docusaurus, Markdown and GitHub Actions, so documentation ships in the same pull request as the code change.
- Publish REST API reference for 85 endpoints generated from OpenAPI 3.0 specs, adding descriptions, error codes and request examples that engineers review in GitHub before each release.
- Wrote quickstarts for the Python and Node.js SDKs that cut median time to a first successful API call from 47 minutes to 12 in moderated usability sessions with 8 customer developers.
- Test every code sample in the docs against the staging API with a Postman collection run nightly in CI, catching 23 broken samples before customers found them in the past year.
- Edit release notes and in-app UI text for four product squads every two weeks, enforcing a style guide based on Google’s developer documentation style with Vale lint rules in each pull request.
- Built a docs analytics dashboard from Google Analytics 4 and on-page feedback widgets, using searches that returned no results to plan the next quarter’s 15 new articles.
Associate Technical WriterJune 2022 – December 2023Bellhaven Payments, Raleigh, NC
- Wrote and maintained 60 help center articles for merchant users of the payments dashboard, covering refunds, disputes, payouts and user permissions in Zendesk Guide.
- Shortened average handle time on payout calls by about 2 minutes by adding step-by-step user guides with annotated screenshots that support agents linked in their replies.
- Documented 30 endpoints of the merchant API by interviewing engineers and reading the OpenAPI spec, then reviewing every page with the owning developer before publication.
- Produced release notes for 18 monthly releases from Jira tickets and sprint demos, explaining each change in terms merchants and partner developers could act on.
- Created a reusable topic template and terminology list in Markdown that the three-person docs team adopted, cutting technical editing rounds on new articles from three to one.
Documentation InternMay 2021 – August 2021Oakmont Medical Devices, Morrisville, NC
- Updated 12 standard operating procedures for a manufacturing line under engineer review, following the company’s document control process and FDA quality system formatting rules.
- Converted 40 legacy Word work instructions into structured topics in MadCap Flare, adding numbered steps, cautions and photos taken on the production floor.
- Wrote a 25-page user guide for an internal calibration tracking tool by shadowing technicians and testing each procedure, and it became the training document for new hires.
- Tracked document change requests in Jira and routed redlines to quality engineers, closing 35 requests over the 14-week internship.
Want yours to read like this? Upload your resume and a job posting, and FitMyRole rewrites it for that job in this template.
Tailor my resumeWhy This Resume Works
- Every bullet names the type of document and its audience (REST API reference for 85 endpoints, SDK quickstarts for customer developers, help center articles for merchants), which avoids the vague "wrote documentation" line recruiters skip.
- The impact is measured in what documentation changes: support tickets down 31%, time to a first successful API call cut from 47 minutes to 12, and editing rounds cut from three to one.
- Docs-as-code is shown, not claimed: Docusaurus, Markdown, GitHub Actions, Vale lint rules and docs shipping in the same pull request as the code, the exact phrases developer-docs postings use.
- An early-career writer still shows range: an internship writing regulated SOPs in MadCap Flare, a payments role with user guides and API docs, and a current role owning a developer portal.
- The Skills section splits documentation types from tools and API skills (OpenAPI 3.0, Postman, cURL), so an ATS matching "API documentation" or "Markdown" finds both in one line.
Common Resume Mistakes
- No metrics (pages, tickets reduced, adoption).
- Missing API or docs-as-code keywords.
- Generic "wrote documentation" without type or audience.
Keywords Recruiters Look For
- Technical writing
- API documentation
- Documentation
- Markdown
- User guides
- Developer docs
- Technical editing
- Docs-as-code
Get more interviews. Tailor your resume automatically
Want to tailor your resume to the job you want? Use FitMyRole to analyze your resume and rewrite it for the role. Before sending your next application, run your resume through FitMyRole to tailor it to the job description.
Try FitMyRole free