Technical Writer

Tom Johnson Portfolio

Long-running technical writing blog "I'd Rather Be Writing," widely referenced in the technical writing community, covering API documentation, docs-as-code, and single-sourcing strategy in deep, practical detail.

API DocumentationDocs-as-CodeCommunity ResourceTechnical Writing Strategy

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Deep, practical strategy content, not just samples

Long-form posts on docs-as-code workflows and API documentation strategy demonstrate expertise in the discipline itself, not just individual writing samples.

2

Widely referenced within the professional community

Being a commonly cited resource among other technical writers is a strong peer-credibility signal beyond client testimonials.

3

A consistent multi-year publishing cadence

A long history of regularly published, dated posts shows sustained thought leadership rather than a one-time portfolio push.

What Technical Writers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Writing about your craft (workflows, tooling, strategy) alongside your actual samples builds thought-leadership credibility.

  • Consistent long-term publishing is itself a signal — a portfolio that's clearly been maintained for years reads differently than a fresh one.

  • If your writing on the discipline gets cited or referenced by peers, that's worth highlighting as a credibility marker.

Ready to build your portfolio?

Follow the Technical Writer roadmap — skills, projects, and timeline to get hired.

Technical Writer Roadmap