The Resume as Code Philosophy
Treating career data as structured, queryable truth rather than prose to be rewritten for each application.
The Problem with Traditional Resumes
Traditional resume management is document-centric, creating chaos and duplication.
Resume_v1.docx Resume_v2_tech.docx Resume_v2_tech_final.docx Resume_v2_tech_final_FINAL.docx Resume_for_Google.docx Resume_for_Amazon.docx ...
No Single Source of Truth
Accomplishments exist in dozens of slightly different documents. Which version has that metric you calculated? Was it 40% or 47%?
Duplicate Effort
Every job application means opening a document, copying bullets, rewording, reformatting, and hoping you didn't forget something.
No Version Control
Documents get renamed, overwritten, and lost. No history, no diffs, no collaboration without "Resume_v2_Josh_edits.docx" chaos.
Lost Accomplishments
That achievement from three jobs ago might be in one version but not another. Over time, your best work gets buried in the document graveyard.
The Resume as Code Solution
Resume as Code inverts the traditional model: data is truth, resumes are generated.
| Traditional | Resume as Code |
|---|---|
| Documents are the source of truth | Data is the source of truth |
| Resumes are edited | Resumes are generated |
| Each application starts from scratch | Each application is a query |
| Accomplishments scattered | Accomplishments centralized |
| No history | Git-native history |
Core Concepts
Work Units: The Atomic Unit
The Work Unit is the fundamental building block — not jobs (too coarse) and not bullet points (too fine). Each Work Unit is a complete accomplishment:
- What problem existed
- What actions you took
- What results you achieved
- What skills you demonstrated
- What metrics prove the impact
The PAR Framework
Every Work Unit follows the Problem-Action-Result framework, ensuring every accomplishment tells a complete story:
Resumes as Queries
Here's the key insight: Your capability graph is fixed — what you've done doesn't change. Your Work Units are immutable facts about your past.
Each job description is a query against that graph. Different jobs want different subsets of your experience.
# This is a query against your capability graph resume plan --jd senior-platform-engineer.txt # Output shows matches with relevance scores: Selected Work Units: ✓ [0.87] wu-2024-06-15-cicd-pipeline ✓ [0.82] wu-2024-03-22-security-audit ✓ [0.75] wu-2023-11-08-team-scaling
You're not editing a document — you're selecting from a pre-existing pool of accomplishments.
Benefits
Never Lose an Accomplishment
Every Work Unit is a permanent record. Even if you don't include it in a particular resume, it exists in your repository. Years later, you can still find that metric or project description.
Consistent Quality
Schema validation ensures every Work Unit meets minimum standards. You can't create a half-baked bullet point — the system enforces completeness.
Targeted Applications
The ranking algorithm finds Work Units that match each job description. You're not guessing what to include — the relevance is calculated.
Full Audit Trail
The manifest shows exactly what was included in each generated resume. You can always explain why something was or wasn't included.
AI-Ready
Structured data is machine-readable. AI assistants can suggest improvements, help draft new Work Units, identify gaps, and generate cover letters.