Technical writer, systems engineer, and documentation strategist with deep roots in healthcare IT and AI automation.
I'm a senior technical writer with 5+ years of experience building documentation systems and automating content operations. My work sits at the intersection of technical writing, systems engineering, and AI automation — I write clear documentation AND build the infrastructure to scale it.
I specialize in healthcare IT, where clarity is not just about user experience — it directly impacts clinical workflows and operational efficiency. I've worked across managed care operations, Medicare/Medicaid systems, and complex health information platforms. That domain expertise informs how I approach documentation: precision matters, context matters, and governance matters.
What excites me most is building systems that make documentation scalable. Rather than writing faster, I build pipelines that multiply output. AI-driven content review, automated gap analysis, self-healing infrastructure — these are the kinds of problems I solve.
I translate complex systems into clear, actionable documentation. Whether it's configuration guides, architecture diagrams, or troubleshooting procedures, the goal is reader understanding — not brevity for its own sake.
I see documentation as infrastructure. That means APIs, pipelines, automation, and governance. Building systems that support content creation is as important as writing well.
I build AI-driven workflows that evaluate content, identify gaps, and automate publication. Multi-agent systems, structured output, prompt engineering — this is where documentation and technology intersect.
I've led steering committees, worked with engineering, product, and support teams. Good documentation requires buy-in across the organization, and I'm skilled at building that consensus.
Style guides, quality rubrics, and templates aren't bureaucracy — they're force multipliers. When everyone knows the standards, documentation becomes faster and more consistent.
A configuration guide for admins is completely different from troubleshooting docs for support. I tailor documentation to the specific reader, not a generic "user."
Good documentation should reduce support tickets, speed up onboarding, and prevent customer escalations. I track metrics and iterate based on what actually works.
If you're doing the same documentation task manually twice, you should build a pipeline for it. Automation frees up time for strategic, high-value writing.
I'm part of the band Riskaverse, where I handle writing and production. Music is a creative outlet that keeps me sharp — much like documentation, it's about clear communication and precise execution.
I'm also working on the Kipple writing project, exploring narrative and form. Writing isn't just my job; it's how I think and create.
I'm interested in remote roles that value clear communication, systems thinking, and documentation strategy. If you're building something that matters, let's connect.
Get in Touch