Résumé as Code

My résumé, treated like software: plain-text source kept in version control that compiles to the PDF I actually send out.

It’s built on the Awesome CV LaTeX template, compiled with XeLaTeX so the custom fonts render correctly. The content is modular — resume_cv.tex wires together individual files under cv-sections/ (experience, education, skills), with separate cover-letter variants I tailor per application. Presentation (the document class, the fonts, the FontAwesome icons) stays cleanly separated from the words, so changing how it looks never means touching what it says.

The point is treating a career document with the same discipline as code. Every edit is a reviewable diff instead of an opaque overwrite, the PDF is reproducible from source on any machine, and a version tailored to a specific role is a branch rather than a folder full of resume_final_v3.docx. It’s the same rigor I bring to everything else here — applied to the one document that’s meant to represent it.