Stefan Mueller Senior Technical Writer
Vienna, Austria • stefan.mueller.docs@gmail.com • +43 660 555 0192
Profile Summary
- Senior Technical Writer with 9 years of experience writing for developers on a developer-facing email and notification API used by web and mobile engineering teams across developer tooling, email infrastructure, and SaaS APIs, specializing in API reference, task-based IA, and docs-as-code workflows.
- Hands-on coverage across docs platform (Docusaurus with MDX), style guide (the Microsoft Writing Style Guide), IA approach (task-based information architecture), and primary audience (developers integrating an HTTP API for the first time), credentialed through B.A. in Technical Communication, FH Joanneum Graz.
- Deep craft in user-guide and conceptual writing tuned for first-touch readers, API reference docs generated from OpenAPI with hand-tuned examples, task-based IA that maps headings to what readers came to do, and docs-as-code workflows with Git PRs, prose linting, and CI-tested samples, applying methods such as SME interviews paired with hands-on dogfooding of the product and quarterly docs audits driven by search-term and ticket data to deliver docs that get a developer to a working integration in one read.
- Engaged collaborator working cross-functionally with Engineering, Product, Support, DevRel, and Localization inside a documentation team embedded with the API and developer platform org, contributing to weekly docs reviews, SME walkthroughs, and the release planning that ties new features to docs deliverables.
- Mentor who shares craft and fosters a culture of every code sample in the docs is tested in CI before it ships and docs health tracked on search success, ticket deflection, and reader satisfaction through paired drafting and editorial review, while running a monthly docs review with Engineering and a Vienna technical-writing meetup and publishing internal documentation playbooks the rest of the team picks up.
Technical Skills
- Documentation Authoring:
- Docusaurus with MDX, user guides and how-tos, conceptual overviews, API references, quickstarts, tutorials and walkthroughs, release notes, glossary and terminology pages
- API & Developer Docs:
- OpenAPI and Swagger, API reference auto-generation, curl, Node, and Python code samples, webhook and event payload docs, authentication and rate-limit guides, sandbox and try-it consoles, changelog and deprecation notes
- Information Architecture:
- task-based information architecture, task-based navigation, progressive disclosure, taxonomy and tagging, cross-linking strategy, breadcrumb and sitemap design, search-first information architecture
- Docs-as-Code & Tooling:
- Markdown and MDX, Git and GitHub Pull Requests, Docusaurus, MkDocs, and Hugo, Confluence and Paligo, MadCap Flare and ReadMe, Vale for prose linting, CI checks on every PR
- Editing & Style:
- the Microsoft Writing Style Guide, Microsoft and Google style guides, plain-language editing, terminology consistency, tone and voice calibration, inclusive-language review, editorial calendars
- Visual & Multimedia:
- architecture and sequence diagrams in Mermaid, Figma annotated screenshots, flowcharts in Whimsical and Excalidraw, animated GIF walkthroughs, Loom and screen recordings, alt text and accessibility review
- Versioning & Localization:
- versioned doc trees with redirects, deprecation and sunset notices, localization workflows with Crowdin and Lokalise, translation memory upkeep, docs audits and quarterly content reviews, archive and unpublish policies
- Analytics & Feedback:
- Google Analytics and Plausible page-view review, Algolia DocSearch query mining, support-ticket deflection tracking, user feedback widgets, docs satisfaction surveys, A/B tests on quickstarts and landing pages
- Credentials & Education:
- B.A. in Technical Communication, FH Joanneum Graz, Society for Technical Communication (STC) member, prior editorial and content design experience at a developer-platform company
Education
FH Joanneum University of
Applied Sciences
B.A. in Technical
Communication
Work Experience
Resend
Senior Technical
Writer
- Owned end-to-end documentation for the Resend API docs, SDK guides, and integration tutorials across the email platform reaching 220,000 monthly docs readers across 380 live pages, paired with 6 engineering and product leads on the docs roadmap, release planning, and the reader-facing surface of every new feature.
- Wrote and maintained the API and SDK reference around API reference auto-generated from OpenAPI with hand-tuned examples and try-it consoles, documenting 64 endpoints with copy-paste samples in 5 languages, and shipping 18 quickstarts tied to the most common integration paths.
- Reshaped the information architecture around a task-based IA with conceptual, how-to, and reference splits mapped to the integration journey, organizing 14 top-level taxonomy categories at a maximum nav depth of 3 levels, and lifting search-driven findability from 54% to 82% on the most-trafficked reader queries.
- Built the docs-as-code workflow on a docs-as-code pipeline with Markdown PRs, Vale prose linting, and code samples tested on every build, standardizing the site on Docusaurus, cutting CI build time under 4 minutes on every preview deploy, and shipping 540 docs pull requests in two years.
- Translated engineer-speak into reader tasks through weekly SME interviews paired with hands-on dogfooding to translate engineer-speak into reader tasks, logging 120 SME interviews across the engineering org, mapping 42 reader tasks to dedicated how-tos, and closing each new page in a median of 2 rounds of editorial review.
- Shipped visual and multimedia content with Mermaid diagrams, Figma annotated screenshots, and short Loom walkthroughs embedded inline with the prose, producing 72 architecture and sequence diagrams, recording 180 minutes of walkthroughs, and shipping 240 annotated screenshots tied to the live UI.
- Closed the feedback loop with Algolia search queries, page-view review, feedback widgets, and a quarterly docs audit fed by support tickets, mining 3,400 a quarter docs search terms, lifting support-ticket deflection from 38% to 62% on the rewritten quickstarts, and moving reader satisfaction from 3.8 to 4.5 out of 5 on the inline feedback widget.
Bitmovin
Technical
Writer
- Owned the editing and style standards around a custom in-house style guide built on Microsoft conventions, with Vale rules in CI for every PR, writing and maintaining a 78 pages living style guide, curating a glossary of 320 product and video-encoding terms, and editing 420 docs pull requests from engineers and product managers.
- Wrote release notes and conceptual overviews around release notes, conceptual overviews, and migration guides written from changelog and SME walkthroughs, shipping 96 release notes across the encoder, player, and analytics products, publishing 48 conceptual pages on streaming protocols and codec choice, and covering 3 reader types from broadcast engineers to web developers.
- Ran versioning and localization on versioned doc trees with deprecation notices and a Crowdin localization pipeline tied to translation memory, maintaining 4 active product versions side by side, shipping the docs in 6 locales, and pushing 280k words through the localization pipeline each year with translation memory upkeep.
- Partnered with SMEs and ran user-tested writing through paired SME interviews and user-tested task flows that broke long reference walls into scannable how-tos, collaborating with 9 engineering partners, shipping 56 task walkthroughs, and lifting reader task completion from 61% to 84% on the rewritten integration pages.