available for contract work · q2 2026

DOCU
MENT
ATION

that developers actually read.

Jordan Voss — Technical WriterAPIs · Microservices · Developer Onboarding

scroll to review work

./credentials

8+years writing technical docs

40k+developers onboarded

127doc sets shipped

94%client retention

specialisms

›REST API reference docs

›Microservices architecture guides

›Developer onboarding flows

›SDK integration guides

›CLI tool documentation

›Internal runbooks & SOPs

toolchain

MarkdownDITAOpenAPIDocusaurusConfluenceStoplightReadMeGitSwaggerMkDocs

$ whoami — I write documentation that engineers trust and developers bookmark. Eight years embedded in engineering teams at Series B startups and Fortune 500s, I treat docs as a product: versioned, tested, and shipped with the same rigor as code. If your team can't find the answer in the docs in under 90 seconds, the docs are broken.

./work

Selected case studies

browse writing samples

[01]+ expand

−62%support tickets in 90 days

Payments API Reference Overhaul

Stripe-adjacent fintech · REST API · 47 endpoints

OpenAPI 3.1StoplightMarkdownGit

The existing API docs were a single 12,000-word Confluence page with no code examples. Rebuilt as a structured OpenAPI 3.1 spec with endpoint-level guides, error code tables, and runnable curl examples for every auth flow.

before

Single Confluence page · no code samples · 23% success rate on first auth attempt

after

Structured reference · 47 code examples · 89% success rate on first auth attempt

Code editor showing API documentation with syntax highlighting and structured endpoints

[02]+ expand

12kdevelopers onboarded in Q1

Developer Onboarding Portal

B2B SaaS · 12k developers · Q1 2024

DocusaurusMDXMermaidGitHub Actions

Designed and wrote the full onboarding documentation for a developer platform launching to 12,000 beta users. Zero-to-first-API-call in under 15 minutes, measured and validated.

before

No onboarding docs · avg time-to-first-call: 4.2 hours · 34% drop-off

after

Structured portal · avg time-to-first-call: 11 minutes · 8% drop-off

Developer documentation portal showing structured onboarding steps and code examples

[03]+ expand

−78%cross-team clarification requests

Microservices Architecture Guide

Platform team · 14 services · 6 engineering squads

DITAConfluenceMermaidMarkdown

Six engineering squads were building against undocumented service contracts. Wrote the definitive internal architecture guide: service topology maps, data flow diagrams, and contract specs for every inter-service boundary.

before

Tribal knowledge · 14 Slack threads/day for arch questions · 3-week new-hire ramp

after

Authoritative guide · 2 Slack threads/day · 4-day new-hire ramp to first PR

System architecture diagram showing microservices connections and data flow documentation

[04]+ expand

4.9/5developer satisfaction score

CLI Tool Documentation Suite

DevOps toolchain · 200+ commands · internal + external

man pagesPOSIXMkDocsPython

Full documentation suite for a CLI tool with 200+ commands — man pages, --help text, a searchable web reference, and a migration guide from v2 to v3. Rated highest-quality docs in company history by engineering survey.

before

--help text was 2 lines per command · no migration guide · 40% support ticket rate on v3 launch

after

Structured man pages · full migration guide · 6% support ticket rate on v4 launch

Terminal window showing well-formatted CLI documentation with command examples and flags

[05]+ expand

3×faster integration vs. prior SDK docs

SDK Integration Guide — 5 Languages

Developer platform · Python, JS, Go, Ruby, Java

ReadMeOpenAPIMarkdownStoplight

Wrote integration guides for five language SDKs from scratch: consistent structure, idiomatic code samples in each language, and a troubleshooting matrix covering the 40 most common integration errors.

before

Generic docs copy-pasted across languages · no idiomatic examples · avg integration: 3.4 days

after

Language-native guides · idiomatic samples · avg integration: 1.1 days

Code samples showing SDK documentation across multiple programming languages with clear structure

Jordan rewrote our entire API reference in six weeks. Our support ticket volume dropped by 40%. The docs are now the first thing we show in every sales demo.

Marcus Rivera

VP Engineering · Clearflow Payments

what engineering leads say

We went from zero onboarding docs to a portal that gets 94% developer satisfaction. Jordan thinks in systems — she doesn't write docs, she architects them.

Priya Nambiar

Head of Developer Relations · Axiom Cloud

Hired Jordan after our Series A when we realized no one could explain our product to developers. Three months later, we had a doc site that engineering leads send their friends.

Owen Blackwell

CTO · Stackframe Inc.

./audit_checklist.md

Is your documentation actually working?

8 diagnostic questions I run against every doc set before starting an engagement. If you can't answer yes to 6+, your docs are costing you support hours.

[01]Is every endpoint covered with a working code example?

[02]Can a developer reach their first successful API call in < 15 minutes?

[03]Are error codes documented with resolution steps?

[04]Is the doc site versioned and searchable?

[05]Do your SDK guides use idiomatic code per language?

[06]Is there a migration guide for every major version bump?

locked

[07]Are internal architecture decisions documented for new engineers?

locked

[08]Can support answer 80% of tickets using docs alone?

locked

download_checklist

Get the Documentation Audit Checklist

24 diagnostic questions. Free. No sequence, no drip. Just the framework I use with every new client.

Browse writing samples

Full-length hosted docs · live examples

browse →

available q2 2026

Currently accepting 1–2 new contract engagements. Typical engagement: 6–16 weeks.

jordan@redline.docs →

DOCUMENTATION

Selected case studies

Payments API Reference Overhaul

Developer Onboarding Portal

Microservices Architecture Guide

CLI Tool Documentation Suite

SDK Integration Guide — 5 Languages

Is your documentation actually working?

Get the Documentation Audit Checklist

DOCU
MENT
ATION