6.6 KiB
6.6 KiB
name, description, type, arguments, output
| name | description | type | arguments | output | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| build-resume | Generate tailored resumes and cover letters for specific job applications using Paul's detailed resume as context | skill |
|
|
build-resume Skill
Generate tailored resumes and cover letters for specific job applications.
Quick Start
/build-resume [paste job description or provide details]
Output Structure
Creates organized directory structure:
applications/
└── company-name/
└── job-title/
├── paul-halvorsen-resume.md
├── paul-halvorsen-resume.pdf
├── paul-halvorsen-cover-letter.md
├── paul-halvorsen-cover-letter.pdf
└── job-breakdown.md (analysis)
Examples: applications/zapier/backend-engineer/, applications/stripe/senior-backend-engineer/
YAML Metadata Format
IMPORTANT: Use quoted strings for contact info to avoid YAML parsing issues.
Template
---
name: Paul Halvorsen
keywords: key1, key2, key3
left-column:
- "Email: paul.halvorsen@pm.me"
- "Phone: +1-410-236-4665"
right-column:
- "GitHub: github.com/malwhile"
- "LinkedIn: linkedin.com/in/paul-halvorsen"
- "Blog: flow.halvo.me"
fontsize: 10pt
fontenc: T1
urlcolor: blue
linkcolor: magenta
numbersections: false
---
Contact Info Guidelines
- Always include email and phone
- Include GitHub link
- Include LinkedIn (preferred over "Remote" keyword)
- Blog link is optional
- Do NOT include "Citizen of the United States" in right-column for job resumes
- Use format:
"Label: value"(quoted entire string)
Dates Formatting
Use the \resumedate{} macro to make dates smaller than headers:
### Job Title | Company
\resumedate{**January 2026 – Present**}
Building PDFs
Classic Template
make resume FILE_NAME=company/job-title/paul-halvorsen-resume
make resume FILE_NAME=company/job-title/paul-halvorsen-cover-letter
Modern Template (Recommended)
make resume-modern FILE_NAME=company/job-title/paul-halvorsen-resume
make resume-modern FILE_NAME=company/job-title/paul-halvorsen-cover-letter
Awesome-CV Template
make resume-awesome FILE_NAME=company/job-title/paul-halvorsen-resume
make resume-awesome FILE_NAME=company/job-title/paul-halvorsen-cover-letter
Resume Customization Strategy
- Lead with relevant technical skills from job description
- Reorder work experience (most relevant first)
- Highlight metrics from roles that match JD requirements
- Frame gaps honestly in cover letter (e.g., "I haven't worked with X, but...")
- De-emphasize Sr/Staff titles when applying to mid-level roles
CRITICAL: No Fabrication Rule
BLOCKING REQUIREMENT: All numbers and metrics must come from paul-halvorsen-resume-detailed.md.
Pre-Write Checklist
For every bullet point with a number:
- Is this in
paul-halvorsen-resume-detailed.md? - If NO: remove it or rephrase without the number
- If YES: use the exact number/metric
Allowed
- Reordering existing information
- Reframing for clarity
- Removing less relevant details
- Using exact metrics from detailed resume
Not Allowed
- Inventing metrics
- Making up achievements
- Exaggerating scales or customer counts
- Creating statistics not documented
Examples
- ✓ "Performance improvements: reduced CPU usage ~90%" (IS in detailed resume)
- ✓ "10 auto-scaling clusters" (IS in detailed resume)
- ✓ "Customers: thousands of Fortune 500 endpoints" (IS in detailed resume)
- ❌ "$9 trillion in assets" (NOT in detailed resume)
- ❌ "40+ engineers" (NOT in detailed resume)
Cover Letter Approach
- Be upfront about gaps (e.g., "I haven't worked professionally with C#")
- Emphasize transferable skills and learning ability
- Address company mission (e.g., travel industry, fintech, etc.)
- Frame intentional career moves (e.g., moving away from on-call work to sustainable roles)
- Keep tone professional, confident, and honest—not defensive
Key Clarifications from Paul's Background
CompTIA Security+ Certification
- Status: Expired 04/04/2024 (no longer active)
- Note: Do NOT list as active in resumes
NSA Experience - Database Scale
- Database: Thousands of records (not hundreds of thousands)
- Use in resume: "thousands of records" or similar
Language Learning Capability
- Paul has mastered 5+ languages (Rust, Python, C, GoLang, Java)
- Use when applying to roles with unfamiliar tech stacks
- Frame as evidence of quick learning ability
Tech Stack Preferences
- Primary: Backend, systems programming, security
- Secondary: Full-stack if learning opportunity (new languages/frameworks)
- Avoid: Emphasis on junior mentoring, heavy management
ATS Optimization
- Aim for 75-85% keyword match with job description
- Include role-specific technologies in skills section
- Use exact terminology from JD where possible
- Avoid creative formatting that breaks ATS parsing
Application Workflow
- Use
/build-resume [job description]to generate customized documents - Review job-breakdown.md for fit assessment and strategy
- Update applications_tracker.md to log the application
- Build PDFs using appropriate template
- Verify position on company careers page
- Submit through company site (not job board)
- Connect with hiring manager on LinkedIn
File Locations
- Resume source:
/home/paul/Public/resume/paul-halvorsen-resume-detailed.md - This skill:
/home/paul/Public/resume/.claude/skills/build-resume/ - Workflow guide:
/home/paul/Public/resume/.claude/skills/build-resume/BUILD-RESUME-WORKFLOW.md - Job boards:
/home/paul/Public/resume/JOB-BOARDS-TO-SEARCH.md - LinkedIn guide:
/home/paul/Public/resume/LINKEDIN-OPTIMIZATION.md - Job search dashboard:
/home/paul/Public/resume/job_search.html - Application tracker:
/home/paul/.claude/projects/-home-paul-Public-resume/memory/applications_tracker.md
Notes for Implementation
- Update
paul-halvorsen-resume-detailed.mdwith any role clarifications (scale, tech, responsibilities) - Detailed resume serves as source of truth for customized versions
- LinkedIn URL: linkedin.com/in/paul-halvorsen (without https://)
- GitHub URL: github.com/malwhile
- Email: paul.halvorsen@pm.me
- Phone: +1-410-236-4665