Technical Writing

🛠️ What I Do

I write clear, structured documentation—ranging from technical procedures and product specs to business case reports and internal guides. My focus is always on making complex information easy to understand for both technical and non-technical readers.

🧰 Tools I Use

  • Figma and Miro (for structured planning)

  • Confluence, Markdown, and LaTeX (for formatting and collaboration)

  • Zotero and BibTeX (for citation management)

  • Git and detailed logbooks (for version control and traceability)

📁 Projects I’ve Worked On

  • Technical Descriptions – breaking down system components for product or engineering teams

  • Business Case Writing – communicating research-backed recommendations for decision-makers

  • Technical Procedures – step-by-step instructions with supporting visuals and references


➡️ Explore my writing samples below

Technical Description

Technical Procedure

Research Notes

Sample ANA- Business Case

Sample DDS- Business Case

Sample Business Case

Outcomes

Outcomes

Outcomes

  • Clarified system architecture for cross-functional teams by writing modular technical descriptions tailored to diverse audiences.

  • Accelerated stakeholder decisions through well-researched business cases grounded in credible, cited sources.

  • Streamlined onboarding with visual, step-by-step technical procedures that reduced training time.

  • Improved documentation traceability using Git-backed versioning and structured logbooks.

  • Facilitated cross-team alignment by integrating early-stage planning tools (Figma, Miro) with final documentation workflows.

  • Ensured citation accuracy and reusability with Zotero and BibTeX for academic and business documentation.

Links.

© 2025 • Snehasini M Antonious

unsplash.com/@reddfrancisco

Create a free website with Framer, the website builder loved by startups, designers and agencies.