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

20
valon/paul-halvorsen-valon-cover-letter.md Normal file
View File

@@ -0,0 +1,20 @@
# Cover Letter: Paul Halvorsen — Software Engineer at Valon
Dear Hiring Team,
I'm writing to express my strong interest in the Software Engineer role at Valon. After following your work in fintech and regulated industries, I'm genuinely excited about the opportunity to contribute to ValonOS and help transform how the mortgage industry operates.
Throughout my 15+ years as a backend engineer, I've spent most of my career building infrastructure for systems that require uncompromising reliability—the kind where failures cascade and impact customers directly. I've built distributed systems handling billions of events daily, engineered APIs serving Fortune 500 companies, and optimized systems that reduced resource consumption by 80-90%. But what excites me most about Valon isn't the scale problem itself—it's that you're solving it *within a regulated industry*. The complexity of federal, state, and agency requirements is a fundamentally different challenge than traditional tech, and that's exactly what I want to learn and master.
What draws me to Valon specifically is your approach. Most companies try to bolt technology onto broken legacy systems. You built your own mortgage servicing business first—not as a feature, but as a way to deeply understand the problem space. That thinking resonates with me. I've always believed that understanding your domain completely is table stakes for building great software. Your transformation from 0% to 60%+ margins proves that philosophy works. And seeing a team from Stripe, Jane Street, Meta, and Google building something in fintech tells me you've recruited for both technical excellence and the ability to learn complex new domains.
I'm confident I can succeed in this role. I learn quickly—I've worked across Python, Go, Rust, and C; built systems on Kubernetes, Docker, and GCP; and shipped complex features in distributed systems repeatedly. More importantly, I'm genuinely curious about regulated industries and excited to spend the next few years diving deep into mortgage servicing. I want to be part of a team that's rewriting the playbook for an entire industry.
I'd love the opportunity to discuss how my background in building reliable, scalable infrastructure can contribute to Valon's mission.
Thank you for considering my application.
Warm regards,
Paul Halvorsen
paul.halvorsen@pm.me
+1-410-236-4665