Senior Technical Writer | Documentation Systems & IA | AI-Enabled Workflows
I write documentation for complex enterprise software and design the systems around it.
For over a decade, I’ve worked on documentation for enterprise SaaS products across identity, cloud, and IoT. Today, as a Senior Technical Writer at Okta, I focus on documentation systems, content workflows, and practical ways AI can improve how technical information is created and maintained.
When I’m not writing, you’ll find me recording music, exploring the city on my bike, or wandering the woods.
Built a Claude Code skill that finds stale and missing docs and proposes fixes for writer review. Next, it becomes an agent that runs on a schedule.
Read case study
Led documentation for high-priority product launches, as the single point of contact for 4–5 writers and eight partner teams.
Read case study
Led the documentation workstream of a company rebrand, consolidating a retiring developer portal into the primary docs platform with new information architecture, navigation, and search.
Read case study
Most conversations about AI in documentation are about what to automate. The harder question is what the automation is allowed to do, how a reviewer knows it was right, and who is accountable when it wasn’t. Six controls that answer it.
We can train an AI system to behave in ways we prefer. The harder question is how we would know the training worked, and whether it will hold when things change.
Human review is often treated as the fail-safe for AI agents. But when a reviewer can’t understand what happened, or doesn’t have the time to check, approval becomes a formality, and the controls that don’t depend on catching the mistake start to matter more.
When an AI system causes harm, responsibility rarely sits in one place. A look at the operational and security side of AI safety: who controls which safeguards, and who is in a position to reduce the risk.