← Back to context

Comment by prennert

3 months ago

Adding an example would be useful to see how it renders.

Obviously a cool side-project. but I dont understand why anyone would want automate CV generation for "production use".

CVs are personal, and get updated once a year or so. Each life is different, each CV is different. So it does not easily scale across people.

As someone who is reviewing CVs, I review CVs from two aspects:

1. does the person have the skills I need, and 2. can the person communicate and do they have professional pride

Its much easier to get 1 & 2 across if you craft your CV. Think about what message you want to get across and work very hard to get that message across on one page. Expand with more detail in pages 2 and following.

As a hiring manager I am filtering roughly in this order:

1. has core skills I need, if yes, then 2. has used core skills I need in enough projects to likely meet our bar, if yes, then 3. are the relevant projects close enough to what we are building?

Later in the interview process, interviewers will look at the CV more closely to prepare for the interview.

Anyway, if anything I would only start with automating from page 2 and beyond.

Thanks, adding an example output is a good idea.

I use it to customize my resume for each application, and this is an easy way for me to customize my 'source' then output files to share. Most folks I know do the same thing.

I've hired, but I'm no expert in hiring. Everyone does it differently, but I think this tool outputs ATS-friendly files, which is where most resumes go first these days.