Fictional resume example. Names, employment histories and results are illustrative, not an actual employee record.
Madison Sullivan
Technical Writer with experience in information architecture, developer clarity, adoption, and documentation quality. Practical work includes API documentation, Executable code examples, Migration guides, Information architecture.
Experience
Interactive Brokers
Greenwich · United States
Technical Writer
Mar 2022 - now
- Wrote API documentation for authentication, pagination, and error recovery, testing every Python example against a sandbox; fixed a sample that hid a required token scope.
- Used technical writing reviews with developer support to turn repeated integration questions into task-based guides; checked prerequisites and expected responses with a reader unfamiliar with the API.
- Ran every code sample against the documented SDK version, separated prerequisites from optional steps, and added migration notes for renamed API fields.
- Owned API documentation validation using Python and JavaScript examples, resolved obsolete parameters and completed every quickstart from a clean developer account.
- Published a technical-writing style guide using support-ticket evidence, reduced repeated setup questions by 28% in the next monthly support review.
Datadog
New York · United States
Technical Writer
Jan 2019 - Feb 2022
- Introduced content ownership and 90-day reviews for 64 critical pages. Prevented the same exception from recurring in the next review.
- Reviewed a proposed change against the existing interface contract, reproduced a reviewer’s edge case, and added the missing test or example before merging the change.
- Investigated a failure reported by a downstream team using the exact version and input they supplied. Reduced it to a reproducible test, delivered the fix with compatibility notes, and confirmed the original case passed before closing the report.
Selected project
Technical Writer — independent case study
Project owner
Feb 2024 - Jun 2024
- Observed 12 developers completing first-integration tasks and rewrote the quickstart
- Built an isolated fixture with normal, malformed and interrupted inputs; recorded the expected response before running the implementation so failures were distinguishable from a changed assumption.
- Packaged the reproduction steps, configuration and regression tests with the project; checked the instructions from a clean environment and documented the unsupported cases instead of claiming production readiness.
- Owned the independent regression fixture using isolated inputs, resolved a failing edge case and released a reproducible test package with expected outputs.
Education
University of Washington
Seattle, Washington · United States
B.S. Computer Science
Sep 2013 - Jun 2017
Relevant coursework: Algorithms, operating systems, databases, computer networks
Skills
Role expertise
API documentation · Executable code examples · Migration guides · Information architecture
Publications
- Published an independent technical note using the project’s before-and-after traces, explaining the failed assumption, regression coverage and cases the implementation does not support.


