Victory N.

Engineer-turned technical writer for AI and developer tools. I authored a 5,000+ learner agentic AI certification and helped grow Memori from 1K to 12K+ GitHub stars in 4 months. I test every workflow before I document it. Most AI, SaaS and API companies don't have a documentation problem. They have a translation problem. I started as an AI engineer, building RAG apps, agents and FastAPI backends, so I understand the product before I write about it. I read the code, call the endpoints and work with your engineers directly instead of writing from tickets. WHAT I DO → API & SDK documentation: REST, OpenAPI/Swagger, webhooks, authentication, reference docs and code samples → Developer docs & portals: quickstarts, integration guides, tutorials and onboarding → AI/LLM documentation: agents, RAG systems, LLM apps, AI SDKs and agentic workflows → DevRel content: technical articles, demo apps and tutorials that drive adoption → Docs audits: finding the gaps that cost you support tickets and signups → Docs-as-code: GitBook, Mintlify, Docusaurus, MkDocs, Markdown and GitHub SELECTED RESULTS ✓ Ready Tensor: led and authored a 3-month Agentic AI Developer Certification (LLMs, RAG, agents) reaching 5,000+ learners ✓ Memori (Studio1): grew the repo from 1,000 to 12,000+ GitHub stars in 4 months through tutorials, 10+ demo apps and ecosystem partnerships ✓ Gaffa: technical writer and DevRel engineer for a web-scraping API, covering the developer portal, API reference, browser actions and case studies ✓ 50+ technical articles, API docs and LLM guides for AI and SaaS startups ✓ Top Rated, 100% Job Success WHY NOT JUST USE AI? AI can write a decent first draft. What it can't do is notice when an endpoint quietly changed, or when an explanation is technically true but misleading in practice. I use AI for speed and my engineering judgment for accuracy, and I stay accountable once the docs ship. HOW I WORK 1. Audit what you have and flag what's costing you 2. Plan the structure so the docs scale with the product 3. Write and test against the real product 4. Deliver on a clear timeline with regular updates 5. Keep the docs current as you ship (for ongoing work) TOOLS: OpenAPI, Swagger, Postman, Redocly, Mintlify, Docusaurus, GitBook, MkDocs, Git, GitHub Actions, Python, JavaScript, TypeScript, FastAPI, LangChain, Pydantic AI, OpenAI, Hugging Face I work on UK hours, so I overlap with UK/EU teams and US East Coast mornings. If you want docs your developers actually use, send me a message and tell me what you're building.