Elmer A. S.

👋 I’m a technical writer with a software development background who turns complex systems into clear, developer-ready documentation. I partner with SaaS and product teams to ship docs that are accurate, high-quality, testable, and easy to navigate — so users onboard faster and support teams field fewer “how do I…?” tickets. 💡 WHAT I BRING (Technical Writing for Software Teams) I’ve delivered API references, SDK guides, onboarding flows, and internal engineering docs across real products. Highlights include: ➜ API & DX: Lead docs for Bibendo (OpenAPI → ReadMe), API tutorials and reviews for Route4Me. ➜ Product & KB: End-user and support content for Panoply and LiveDocs. ➜ Process & Compliance: Internal engineering specs and traceability docs for Pitcher that supported ISO audit readiness. ➜ Content for Devs: Published technical articles for Joyfill (PDF SDK + automation). 🧾 DELIVERABLES I CAN OWN END-TO-END 1️⃣ Product documentation systems, user guides, release notes, and knowledge architecture 2️⃣ API references (OpenAPI/Swagger), SDK docs, onboarding tutorials 3️⃣ Knowledge base articles, FAQs, troubleshooting flows 4️⃣ Style guides, SOPs, and internal engineering specs 🧰 TOOLS & STACK ➜ OpenAPI / Swagger, Postman, curl, ReadMe, Docusaurus, Confluence, Zendesk, GitBook, Git, GitHub, Markdown, HackMD, HTML. ➜ Methods: Diátaxis; Microsoft / Google / IBM style guidance. ➜ Comfortable working with engineering teams across JavaScript, Ruby, Python, PHP, and SQL-based products. 🧠 HOW I WORK I write like an engineer (requests, examples, edge cases) and edit like a teacher (clarity, sequence, outcomes). I collaborate smoothly with PMs and devs, and I’m comfortable building from scratch or leveling up what you have. 🚀 Let’s make your documentation a product advantage. Share your goals and current state, and I’ll propose a concise plan with quick wins and a clear path to scale. 💼 For a deeper look at my background and sample projects, see my CV in the Portfolio section below.