paul/resume
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Organize resumes by company in subdirectories

Browse Source 
- Create subdirectories for each company (files/, valon/)
- Move company-specific resumes and cover letters to their directories
- Update Makefile to support FILE_NAME paths (e.g., files/resume-name)
- Improve clean target to recursively find .log files
- Update CLAUDE.md with new directory structure documentation
- Add examples for building PDFs from subdirectories
- Document cover letter placement and usage

This improves organization as more job-specific resumes accumulate.
Files can now be organized by company for easier management.

Makefile usage:
  make resume                                    # root directory (default)
  make resume FILE_NAME=files/paul-halvorsen-files-backend-engineer
  make resume FILE_NAME=valon/paul-halvorsen-valon-software-engineer

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
This commit is contained in:
paul
2026-03-05 16:07:43 -05:00
parent 649f84aff7
commit 697312036f
8 changed files with 226 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
CLAUDE.md
View File

@@ -8,29 +8,50 @@ This is a resume builder using Pandoc to convert Markdown resumes with YAML meta
## Build and Development Commands
**Build the resume PDF:**
```bash
# Build default resume
make resume
# Build a custom resume with a specific filename
make resume FILE_NAME=paul-halvorsen-acme-senior-backend-engineer
**Directory Structure:**
Resumes are organized by company in subdirectories for easy management:
```
.
├── paul-halvorsen-resume.md (default/main resume)
├── files/
│ ├── paul-halvorsen-files-backend-engineer.md
│ └── paul-halvorsen-files-backend-engineer.pdf
├── valon/
│ ├── paul-halvorsen-valon-software-engineer.md
│ ├── paul-halvorsen-valon-cover-letter.md
│ └── paul-halvorsen-valon-software-engineer.pdf
└── [company]/
└── paul-halvorsen-[company]-[role].md
```
The `FILE_NAME` variable defaults to `paul-halvorsen-resume` but can be overridden to use any markdown file in the directory (without the `.md` extension). The Makefile will:
**Build the resume PDF:**
```bash
# Build default resume (root directory)
make resume
# Build a custom resume from a company subdirectory
make resume FILE_NAME=files/paul-halvorsen-files-backend-engineer
make resume FILE_NAME=valon/paul-halvorsen-valon-software-engineer
# Build a new resume (can be in any directory)
make resume FILE_NAME=[company]/paul-halvorsen-[company]-[role]
```
The `FILE_NAME` variable defaults to `paul-halvorsen-resume` but can be overridden to include a path. The Makefile will:
1. Build the Podman image if it doesn't exist
2. Convert the markdown file to PDF using the default LaTeX template
3. Output a PDF with the same name as the input markdown file (but with `.pdf` extension)
3. Output a PDF with the same filename (but with `.pdf` extension) in the same directory
**Example workflow for custom resumes:**
```bash
# Create a customized markdown resume
# Create a customized markdown resume in company directory
mkdir -p acme
# paul-halvorsen-acme-senior-backend-engineer.md
# Build it
make resume FILE_NAME=paul-halvorsen-acme-senior-backend-engineer
make resume FILE_NAME=acme/paul-halvorsen-acme-senior-backend-engineer
# Output: paul-halvorsen-acme-senior-backend-engineer.pdf
# Output: acme/paul-halvorsen-acme-senior-backend-engineer.pdf
```
**Clean commands:**
@@ -115,16 +136,19 @@ To build a different version, either:
The detailed resume (`paul-halvorsen-resume-detailed.md`) contains comprehensive information across all roles and projects. To create a customized resume for a specific job application:
1. **Get job description** - Copy the job posting or description
2. **Provide to Claude Code** - Share the job description with Claude Code along with a request to create a customized resume
3. **Output format** - Claude will create a new markdown file using the naming convention:
2. **Provide to Claude Code** - Share the job description with Claude Code along with a request to create a customized resume (and optionally a cover letter)
3. **Output format** - Claude will create markdown files in a company subdirectory using the naming convention:
```
paul-halvorsen-[company-name]-[role-title].md
[company]/paul-halvorsen-[company-name]-[role-title].md
[company]/paul-halvorsen-[company-name]-cover-letter.md (optional)
```
Example: `paul-halvorsen-stripe-senior-rust-engineer.md`
Example:
- `stripe/paul-halvorsen-stripe-senior-rust-engineer.md`
- `stripe/paul-halvorsen-stripe-cover-letter.md`
4. **Build the PDF** - Generate the PDF using:
4. **Build the PDF** - Generate the PDF(s) using:
```bash
make resume FILE_NAME=paul-halvorsen-stripe-senior-rust-engineer
make resume FILE_NAME=stripe/paul-halvorsen-stripe-senior-rust-engineer
```
5. **Expected result** - A 1-2 page resume tailored to the job requirements with:
@@ -132,5 +156,9 @@ The detailed resume (`paul-halvorsen-resume-detailed.md`) contains comprehensive
- Emphasized skills and metrics matching the job description
- Highlighted relevant accomplishments and projects
- Customized summary/intro focused on the role
- Optional: A compelling cover letter explaining interest in the company/role
**Note on Cover Letters:**
Cover letters are stored as markdown files in the same company directory as the corresponding resume. They can be included when submitting applications through platforms that support them, or converted to PDF by saving as plain text/PDF from a markdown editor.
The detailed resume includes proficiency levels, performance metrics, specializations, and comprehensive technical details that allow Claude Code to intelligently match your background to specific job requirements.