A technical writer who codes. I turn real, deployed products — like FamNest (Next.js · Supabase · Groq Llama 3.3 70B) — into IEEE-standard architecture docs, requirements specs, and developer guides.
I also build things → virginia-mwega.vercel.app
On Hashnode I'm the engineer. On Medium I'm the founder.
How to make webhook handlers safe to retry without double-charging or duplicating data.
Read post →A full architecture walkthrough of an AI wellness coach for burned-out parents.
Read post →What I shipped, what broke, and what 74 real parents taught me about wellness tech.
Read post →The wellness industry sells calm. Parents need 4-minute interventions that fit real life.
Read post →Real IEEE-standard docs, written from a live codebase.
Full architecture of a live AI product: components, data model, AI safety controls, HIPAA / MOH-aligned design (not certified).
View PDF →18 functional requirements plus non-functional and compliance requirements, specified to IEEE standard.
View PDF →Five production REST endpoints documented from the route handlers: auth patterns, request/response shapes, rate limiting.
View PDF →An annotated walkthrough of FamNest's live payment webhook handler — signature verification, re-verification, idempotency.
View PDF →Full-time or contract · remote · async by default.
I'm looking for a technical writing or documentation engineering role where I can write from the codebase outward — API references, architecture docs, requirements specs, and developer tutorials for real, shipping products. I'm based in Kenya (EAT) and work async across time zones.
API docs, SADs & SRSs to IEEE standards, developer tutorials, and audit findings — written from live code, not templates.
I read the codebase, extract the real behaviour, and formalise it. I can also build — FamNest is my own live Next.js · Supabase · Groq (Llama 3.3 70B) product.
TypeScript · Next.js · React · Node · PostgreSQL · REST APIs · webhooks · Groq (Llama 3.3 70B) · HIPAA / MOH-aligned design (not certified).
Need freelance work instead? See freelance services & rates →
I started writing because most engineering posts are too clean. Everything works on the first try. Nobody mentions the wrong turns. I wanted to publish the other version — the one with the bugs, the bad assumptions, and the moment you realize you've been solving the wrong problem.
On Medium I write about FamNest, the AI wellness coach I'm building for parents who are too tired to meditate but still need to get through Tuesday. On Hashnode I write about how I'm building it. Field Notes is where they meet — a weekly email that's half build log, half what 74 real parents are teaching me.
I also code what I write about. FamNest is a live, deployed product (Next.js · Supabase · Groq Llama 3.3 70B), and the documentation I produce — system architecture documents, requirements specs, audit findings — is written to IEEE standards from that real codebase, not from a template. That combination is why teams hire me for documentation, not just blog posts.
I read everything. Writing inquiry, guest post pitch, podcast invite, question about anything I've published, or just hi — all fine.