Craig Wright Portfolio
Technical writer and content designer with enterprise software experience. His portfolio pairs long-form documentation samples with a clear explanation of the audience and use case for each piece.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Explicit audience framing per sample
Stating exactly who each document was written for (new admins, end users, integrators) shows deliberate audience analysis, not one-size-fits-all writing.
Enterprise-scale documentation experience
Long-form documentation for enterprise software signals comfort with complex, multi-stakeholder products.
Content design framing beyond pure writing
Positioning the work as content design (structure and UX, not just prose) broadens perceived scope beyond word-level editing.
What Technical Writers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
State the intended audience explicitly for each sample — audience analysis is a skill hiring managers specifically look for.
If you've worked on complex, multi-stakeholder enterprise products, say so — it signals you can handle documentation complexity.
Frame your work as content design (structure, findability, UX) when relevant, not just sentence-level writing.
More Technical Writer portfolios
Ready to build your portfolio?
Follow the Technical Writer roadmap — skills, projects, and timeline to get hired.