Technical Writer · API Docs · Docs‑as‑Code · Developer Portals

I write clear, developer‑friendly documentation and tutorials for modern APIs. I collaborate closely with product owners, architects, and engineers, and I maintain a developer portal where content is kept accurate, useful, and easy to navigate. I treat docs as code and I love turning complex topics into simple, actionable guides.

• API documentation & standards — create, review, and evolve guidelines for consistent, high‑quality docs.
• Developer tutorials — design “first‑success” flows and task‑oriented guides that reduce time‑to‑value.
• Developer Portal ownership — curate content, measure usage, and ship small JavaScript enhancements.
• Cross‑functional collaboration — work with POs, architects, and devs to keep product and docs aligned.
• Quality & governance — PR reviews, style‑guide enforcement, and continuous content improvements.

• Languages & markup: Markdown/MDX, AsciiDoc (ADoc), YAML, JSON
• OpenAPI & docs tooling: Redocly Workflow & Reunite, Redoc, (linting & build pipelines)
• Version control: Git, GitHub, Bitbucket
• Collaboration: Jira, Slack
• Code: JavaScript (small features, automations, docs UX)

• Recent courses & topics: OpenAPI: Beginner to Guru, Technical Writing for Software & API Docs, JavaScript Developer (ALX)
• Interests: automating example validation, improving OpenAPI DX, and making portals more discoverable.

• CDQ Developer Portal — content ownership, curation and UX improvements → https://developer.cdq.com/
• Articles & how‑tos — practical guides about data, APIs, and developer experience (selected pieces are pinned on my profile).

When I’m not writing, you’ll find me playing drums, travelling, or exploring the outdoors through survival/off‑road adventures. These hobbies keep my creativity sharp and my writing grounded.

• GitHub: @Sysdrummatic
• LinkedIn: Profile

Thanks for dropping by — and if you’re working on something that needs clear, developer‑focused docs, I’d love to help. ✍️🚀

P.S. I’m always happy to review a spec, triage a docs backlog, or prototype a better getting‑started path. Ping me!