I'm a technical writer specializing in developer documentation, documentation engineering, and developer experience. I build scalable documentation systems that help engineering organizations understand wide-ranging systems and components to ship faster and with more confidence.
Currently, I'm the Lead (and only!) Technical Writer at GoDaddy, where I founded and architected an internal developer documentation platform (with the help of a few developers) serving ~2,000 engineers across 10+ technical domains. I focus on information architecture, tooling, and automation (in addition to writing), using CI/CD pipelines and AI tooling to make documentation scale.
I work at the boundary between documentation and engineering. I'm not a developer. I don't write or review production code by hand (though I do know a tiny bit of Python and JavaScript), but I have enough fluency with development tools, practices, and systems to build working tools and proofs of concept using LLMs. That means I can move from problem to prototype independently, then hand off to a developer for the last mile instead of waiting for engineering bandwidth to get started.
I'm pretty flexible on most things. I might have opinions, but I listen and can be swayed with good, fact-based arguments. The exceptions are the Oxford comma and FAQs. You're not going to convince me to not use an Oxford comma or that FAQs are acceptable in technical documentation (with one limited exception). There aren't many hills I'll die on, but these are two.