Engineering the Perfect Resume Workflow

As a Product Manager, I couldn’t just “write” a resume. I had to architect a pipeline. After battling file formats and prompt hallucinations, here is the technical breakdown of my “Resume as Code” workflow.

Status: Active Prototype. While I currently manage this via local Python scripts, the roadmap includes migrating this schema to a true Headless CMS (Sanity or WordPress) to fully decouple the content model from the build pipeline.

The CI/CD Pipeline

I treat my career history like a software product. It goes through a build process before deployment.

1. Source Control (Main Branch): The “Master Resume” Google Doc. Never sent, only referenced.
2. Feature Branch (Tailoring): XML-bounded AI prompts used to “merge” specific skills into the narrative.
3. Build Script (Python): prep_resume.py handles versioning and file conversion.
4. Deployment (Release): SEO-optimized PDF sent to the recruiter.

The Editorial Experience

Before the data hits the database, the “Authoring Experience” is defined by these strict governance rules to ensure quality and consistency.