Ask most technical writers for writing samples and they cringe. What do you share? More importantly, how do you offer writing samples which prove your ability to engineer online documentation solutions for financial and software companies?

What I Can Share

Due to NDA restrictions, I won’t be sharing confidential samples. Instead, I’ll share details of projects which were designed to be public-facing.

Project: API UI rebuild and rewrite.
Target audience: developers.
Assignment details: rebuild API UI and rewrite content adhering to the TowerData style guide. I coded the three-column format using Ruby | Slate | Markdown to support code examples.

Project: Google Cloud BigQuery.
Target audience: developers new to BigQuery web UI.
Assignment details: rewrite Google’s BigQuery web UI Quickstart documentation. Then build the new content within a page using toggles.

Project: Spark Analytics whitepaper.
Target audience: professionals.
Assignment details: craft a blended white paper balancing technical jargon with definitive reasons data scientists should consider adopting Apache Spark.

Project: API documentation.
Target audience: programmers.
Assignment details: the Stripe project was a mix of helping developers blend a simplified UI with API code examples. My specific role was to solve the problem bridging the gap between developers and technical documentation to cut through complex connectivity blockers.

Project: craft engaging blog posts on technical writing topics.
Target audience: API tech writers and project managers.
Assignment details: write in-depth blog posts related to technical writing, technology and advice streamlining the hiring of technical writers.

Project: iMac Essentials user guide.
Target audience: new iMac users.
Assignment details: my contribution to the Apple iMac Essentials project was assisting the writing team by producing a visually appealing user guide. The challenge was factoring Apple’s use of white space into the text content. Especially by integrating Apple icons throughout the sentence structures.

Project: draft blog posts for VPs.
Target audience: Adobe followers.
Assignment details: Adobe engaged me to write blog posts for their VPs. The assignments were to dovetail creative approaches with Adobe tool solutions. Then craft the posts from the perspective of Adobe VPs. The constraints were taking creative liberties to represent the professional perspectives of the VPs.

Project: satirical blog posts.
Target audience: tech followers desperate for something soft to read.
Assignment details: the Incipio projects were intended to draft technology-related articles and add mild doses of humor. Because of the freedom to select my topics, I chose to delve into relevant newsworthy stories crafting engaging blog posts.