I write tutorials and docs for API‑first and AI‑infrastructure teams.

I'm Victor. I've worked as a software engineer for seven years and written for developers along the way. I build the sample app and run every request before I explain anything. Coding agents read your docs now too, so I test them with the agents your developers use.

Book a 30-minute intro call Read my writing

The check I run before I hand over a quickstart

I give the quickstart to a coding agent and watch where it gets stuck. A new developer usually gets stuck in the same place.

task: Follow docs.example.dev/quickstart and send a test request

pass  Step 1  Install the SDK      npm install @example/sdk
pass  Step 2  Create a client      new Client({ apiKey })
fail  Step 3  Send a request       401 Unauthorized
      The quickstart never says where the API key comes from.

  ## Step 2: Create a client
+ Create a key under Settings, API keys, then export it:+   export EXAMPLE_API_KEY=sk_test_...

What I write

Tutorials that get developers to a working result

New developers go from nothing to something that works with your product, and they leave with code they can keep. I write build-along tutorials, explainers and sample repos, and I run every step before it ships.

Docs that get developers to their first working call

Developers find the right page, follow it, and get a working call on the first try. I write API references, product docs and quickstarts, move docs sites to tools like Mintlify (I've done that for several teams), and keep your docs current as you ship.

Docs ready for launch day

Launching a new API or product without docs yet? I set up the docs, write the quickstart and API reference, and test every page the way a new developer would, and with coding agents, before you launch.

Writing

How OpenRouter Model Routing Works OpenRouter, 2026
How developers pick providers, set up routing and keep an LLM app running when a provider fails.
FastAPI RBAC: Full Implementation Permit.io, 2025
A contact-management app with role-based access control, with the source on GitHub.
AI Agents Need an Access Control Overhaul Permit.io, 2025
An authorization model for AI agents, built with PydanticAI, Claude, Permit and Docker.
Postgres RLS Implementation Guide Permit.io, 2025
Row-level security for a multi-tenant app, and what it costs in query time.
gdocs MCP Open source, 2026
An MCP server I built so Claude Code can read Google Docs comments and write fixes back. The README covers nine tools, OAuth setup and troubleshooting.

More of my writing

Docs projects

Taskize 2025 to now, through Hackmamba
API reference and product docs for a financial operations platform.
Mintlify migrations
For several teams, I restructured the docs, moved the pages to MDX and set up a pull-request workflow for future updates.
Drawstring 2021
A Docusaurus site for the platform's APIs, used by internal teams and outside developers.

How I work

Developers skip anything that sounds like marketing. They trust a page when the commands work the first time they paste them. So I test everything I write.

We agree on your goals and who your developers are, and you give me access to the product.
I use the product, read the code, and run every command and request myself.
I find where developers get stuck between signup and a working call, and plan the tutorials and docs that get them through.
I write each piece.
I give it to a coding agent and ask it to follow the steps from scratch. Wherever it gets stuck or guesses, I fix the page.
Your engineers review it, and you get Markdown or MDX, or a pull request if your docs live in a repo.

If this sounds familiar

If you've ended up here, something probably isn't working yet. Maybe you're launching soon and the docs are still a half-finished README. Maybe your engineers keep stopping real work to write tutorials, and it shows. Or you've watched people sign up, look around, and never make a second API call.

I've been on both sides of this. As an engineer, I've lost afternoons to a quickstart that skipped one step. As a writer, I've seen what happens when someone finally writes that step down: fewer questions in Slack, fewer tickets, and more developers who stay.

That's my job. I use your product the way a new developer would, find where they get stuck, and write the page that gets them through. Then I check it again with the coding agents they now use to read your docs.

Victor

Uma Victor, technical writer and software engineer

Book a call

Tell me about your product and the tutorial or docs you need. It's a 30-minute call.

Book a 30-minute intro call

Or email umavictor11@gmail.com. I'm also on LinkedIn and GitHub.