Senior Technical Writer • AI-assisted knowledge operations • Developer experience
That means finding where complex products lose users to confusion, then building the documentation systems, AI-assisted workflows, support-analysis loops, and docs-as-code operations that fix it. Deep experience across enterprise networking, cloud security, and developer-facing platforms.
What set him apart was how he thought about the work around the writing.
How I can help
Reusable AI-assisted workflows for documentation research, migration planning, auditing, review triage, and quality checks. Designed as operational infrastructure, not one-off prompts, so improvements to source material, workflow rules, and review criteria compound across future work.
Technical documentation for networking, cloud infrastructure, security, and developer platforms, built from real support data and user journey analysis. Troubleshooting architecture, decision guides, and content strategy designed to reduce support volume and improve self-serve outcomes.
Support-case analysis, escalation pattern identification, and content prioritization systems that surface where knowledge gaps are driving the most recurring tickets, and translate that signal into a content strategy with measurable outcomes.
Impact, by the numbers
Documentation systems, operational tooling, and support-driven workflows, with measurable outcomes.
Research reduced from days to ~60 minutes
Designed reusable AI-assisted workflows for research, auditing, migration planning, review triage, documentation quality checks, and structured drafting. The result was not just faster writing, but shared infrastructure for repeatable documentation work across multiple teams.
Read the full case study →695 files in 3 days
Reduced a projected multi-week migration into a 3-day operational workflow by automating documentation updates across 695 files, 349 URL mappings, and hundreds of supporting assets.
Read the full case study →High-volume support category
Analyzed support escalations across the product area's largest support category and built a four-guide troubleshooting suite for enterprise networking products, reaching thousands of views in the first three months.
Read the full case study →Weekly production digest
Built automated reporting workflows that surfaced stalled pull requests, tracked queue state, and improved review prioritization for the documentation team.
Read the full case study →In their words
The consistent theme in peer feedback: my value is not only the documentation I publish, but the systems, workflows, and judgment I bring to the work around documentation.
He's the kind of writer who is constantly pushing the envelope for what a technical writer can do. He built a full AI toolkit — agents, skills, custom commands — that connected MCP servers, documentation sources, and GitHub into workflows that let writers move through research, drafting, and publishing dramatically faster. Proactive, reliable, and completely unfazed by ambiguity. I'd work with Márcio again without hesitation.
He's proactive — for every feature I built, he asked about documentation needs before it even crossed my mind. He's organized, keeping careful track of release dates, and very good at quickly learning new tech all across our product suite. Márcio also invented workflows to use LLMs for large docs refactors that would have been tedious and error prone by hand. And to top it all off: he's one of the kindest people I've worked with — you want him on your team!
Featured writing
Selected posts on technical writing, AI workflows, and documentation systems.
After years of fighting clunky spreadsheets on my phone, I realized the problem wasn't the data, but the interface. Here is how I used AI orchestration to build a custom, mobile-first finance dashboard without writing traditional code.
A few days ago I wrote about how I built a tool to automate my job hunting process. The feedback I got was that it would be useful for others, so I made it available for anyone to use. Here's how I scaled my personal tool into a public one.
Stop scrolling, start applying. I built a system that scrapes job boards, filters out the noise with local LLMs, and only pings my phone when there is actually something worth my time. A look at my hybrid approach to using AI as a career tool rather than a replacement.
About
Developer documentation has moved from reference material to infrastructure. It is increasingly the interface that customers, support teams, internal tools, search systems, and AI agents use to understand products and make decisions. That means documentation needs to be intentionally architected for retrieval, clarity, reliability, and maintenance, not simply published. Most documentation systems are not designed for that reality yet.
At Cloudflare, I built the systems to close that gap: AI-assisted workflow tooling adopted across multiple teams, support data analysis pipelines that surfaced where customers were actually struggling, troubleshooting architecture redesigned from real escalation patterns, and operational infrastructure that compressed multi-week projects into days. The writing was one output. The systems thinking was the work.
I started in technology journalism, which trained the instinct that still shapes everything: the gap between what organizations know internally and what users actually understand. That gap is what I'm paid to close.
In practice, that means treating documentation as part of the product experience itself: something that directly affects adoption, support volume, developer trust, and how effectively both humans and AI systems can use a platform. The goal isn't better writing. It's better knowledge infrastructure.
Contact
I'm actively looking for my next role. I'm a strong fit for teams where documentation affects adoption, support volume, developer trust, or AI/search quality.
Best fit: complex technical products with fragmented knowledge, large documentation estates, recurring support friction, migration or restructuring needs, or early AI documentation workflows that need stronger source material, review systems, and operational discipline.