Brandi Hopkins Portfolio
Technical writer specializing in API reference documentation and OpenAPI/Swagger-based docs generation for developer platforms. Her portfolio shows structured reference docs alongside conceptual guides.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Tooling fluency stated explicitly
Naming specific docs-generation tooling (OpenAPI/Swagger) signals comfort with the modern docs-as-code toolchain that many engineering teams expect.
Both reference and conceptual content shown
Pairing dry API reference material with narrative conceptual guides proves range across the two very different registers documentation requires.
Developer-platform focus
A clear specialization in platform/API documentation signals immediate fit for developer-relations and platform teams specifically.
What Technical Writers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Name the specific docs tooling you're fluent in (OpenAPI, Swagger, docs-as-code pipelines) — engineering teams often screen for this directly.
Show both reference-style and conceptual/tutorial writing — they require different skills and proving both broadens your fit.
If you specialize in developer platforms specifically, say so; it's a distinct, high-demand niche within technical writing.
More Technical Writer portfolios
Ready to build your portfolio?
Follow the Technical Writer roadmap — skills, projects, and timeline to get hired.