Technical Writing & Documentation

I produce technical documentation that engineers respect and non-technical readers can actually follow: API documentation with endpoint references and worked examples, user manuals for software and hardware products, and SOPs and runbooks that operations teams in Dubai and Abu Dhabi can execute step by step. If your engineers have already written rough drafts, I rewrite them into plain English without losing technical accuracy.

I work docs-as-code by default: Markdown source, version-controlled alongside your codebase, published through GitBook or Docusaurus so documentation ships with the same review workflow as your software. For teams that prefer Word or Confluence, I adapt — the structure and clarity carry over either way. Annotated screenshots and architecture or flow diagrams are produced as part of the deliverable, not billed as extras.

Typical clients are UAE software companies, free-zone tech startups and mainland SMEs that need developer guides for partner integrations, onboarding manuals for new staff, or runbooks that keep operations consistent across shifts. Clear documentation reduces support tickets and onboarding time — a measurable AED saving, not a nice-to-have.

How it works

1. 1
   Scope call

   We review what exists today — code, drafts, tribal knowledge — and define the document set, audience and format.

2. 2
   Structure first

   You approve a full table of contents and a sample section before I write the rest, so the voice and depth are locked in early.

3. 3
   Write and verify

   I draft against the real product, test every procedure and API call I document, and flag anything that does not behave as described.

4. 4
   Review and handover

   Your subject-matter experts review, I incorporate corrections, and you receive the source files plus the published docs site.