Weekly Padgett

No. 0491 min read

One master resume. The attachments don't get a vote.

My resume facts live in Markdown. Tailored PDF and Word files come out, keywords get checked, and a file on disk does not count as a job application, folks.

A crib filled with envelopes stands beside a desk with a computer, printer, and person handling papers.
File photoDramatization. No resume was harmed.

Which copy of your resume has the correct date? The company-specific PDF[1]Ref. 1PDF en.wikipedia.org has the better sentence, the Word[2]Ref. 2Word en.wikipedia.org file has the date correction, and the next application starts from whichever attachment you can find. You now have several slightly different careers to maintain.

I would rather maintain one. My resume facts live in master/MASTER_RESUME.md, and I generate the PDF and Word document from there.

That's the design documented in the resume directory's README. I'm describing what it's supposed to do here; I haven't claimed every generated file passed a fresh test today.

The master holds employment history and accomplishments, different role summaries, skills, and education. It can be looooong, because you aren't supposed to send the whole thing.

There are four documented technical profiles: billing mediation, DevOps[3]Ref. 3DevOps en.wikipedia.org, IT operations, and software engineering. The employers and dates stay put, and so does the meaning of a result. I can choose an accomplishment for an application without moving its number to a different employer and inventing myself a career.

The documented workflow starts with saving the job description under jd/. Then comes ats_check.py. The README describes a compatibility score and a keyword comparison against the posting. It can flag missing vocabulary, although I haven't got a tiny hiring manager living in Python[4]Ref. 4Python python.org.

A missing keyword gives me something to check. If I've done the work and the master doesn't say so, I can add truthful wording there. If I haven't done it, the gap stays.

After a master edit, the base versions get rebuilt. I'd still inspect the actual exports before sending them, including text order and page count. The renderer hasn't necessarily read our README.

Refusing to hand-edit an export feels fussy when it's just one word. But I've got enough attachments already, I don't need another one with its own idea of when I worked somewhere. I'll fix the master.

References

  1. PDF en.wikipedia.org ↩
  2. Word en.wikipedia.org ↩
  3. DevOps en.wikipedia.org ↩
  4. Python python.org ↩
resumeautomationcareer

More on this beat