tldr
- A CV defined in YAML using the YAMLResume spec
- Rendered into a pdf using rhe YAML Resume CLI
- Accessabile via an API using FastAPI
Links
Why?
Long answer
Before LLMs were mainstream and people involved with hiring process read CVs, I made my CV fit on one page. Save the person time, gain brownie points. However with the rise of using Ai to process CVs faster this approach failed as I had to cut out a lot of content from the CV to fit it on one page.
The last iteration of my CV contained a robots.txt section to combat Ai reviewing of CVs by adding a list of keywords I imagined the Ai was set to monitor. This was an approach from a defensive standpoint.
With the progression of Ai technologies and my exposure to that, I wanted to switch to an offensive approach. Use the Ai for my CV. I had an idea for something like an Ai Agent or MCP for my CV that I could use to build tailored CVs for job applications. And the first step in that, is an API.
Short answer
For fun
Reasoning
YAMLResume or JSONResume
- YAML is nicer to write and maintain
FastAPI or Flask
- Open API docs out of the box allowing for easier integration with an Agent