Skip to main content

Tooling and automation

Context: Meta, Senior Documentation Engineer, 2025–2026
Audience: Documentation contributors and internal operating partners

Repeated documentation work included change review, stale-content checks, media lookup, submission checks, and task setup. I treated these as documentation problems first. I confirmed the manual workflow, defined the stable part, and then used AI-assisted development to build practical tools and checks.

My role​

I identified the problems, designed the workflows, directed AI-assisted implementation, checked the results, and maintained the tools.

How I built and validated the tools​

The method observes a manual documentation workflow, defines the stable step, directs an AI-assisted build, adds checks and tests, validates real results, and maintains the tool through continued feedback.
Documentation problem first. I used a repeatable loop to separate stable work from human judgment, direct implementation, validate results, and maintain each tool.

Representative work​

  • A wiki-change comparison dashboard that supported manual reconciliation of content changes.
  • An image-lookup tool for media stored in inconsistent CMS locations.
  • Review and submission checks that applied standards from real editorial feedback.
  • Workflow support for task setup, content synchronization, and change triage.

Scale and validation​

MeasureSupported scope
Internal tools10 documentation and workflow applications
Automated validationMore than 750 tests across the tool portfolio
Reusable workflow support30 AI-assisted skills and 10 commands
Review standardsMore than 50 patterns based on real review feedback

The broader automation program was estimated to save 466 hours per year and reduce administrative overhead by 76% in the relevant workflow.