I started my career as a writer — curious about how complex things worked and obsessed with explaining them clearly. That instinct led me into technical writing, where I discovered something more interesting than writing itself: the systems underneath the words.

Documentation lives inside processes. A knowledge base is only as good as the information architecture holding it together. A tutorial only makes sense if the product workflow it describes actually works. The more I wrote, the more I found myself redesigning the systems I was documenting.

Over the past five years, that instinct has taken me from writing API references and developer guides to building the operational infrastructure that organisations run on — CRM pipelines, workflow automations, progress-tracking systems. I've come into early-stage companies and created the structure that didn't exist yet: the frameworks, the tools, the processes, the documentation.

Along the way I interned on what's considered the best-selling technical writing manual of all time at Boffin Education, contributed to open source documentation projects including MindsDB and The Good Docs Project, and have been a regular contributor to KnowledgeOwl — writing about documentation strategy and knowledge base design.

I think of myself as someone who connects the dots. I take a complex system, ask why it isn't clearer, and build something that makes it so. I'm at the stage of my career where I want to go deep — to join a team with real structure, bring everything I've learned, and grow into the best version of what I do.