Testing Google Docs Resume PDFs Against Open-Source Parsers
Testing Google Docs resume templates against an open-source parser reveals font, ligature, and PDF page-break issues candidates must know.
Stock photo for illustration only, not from the actual event
- Developer tests Google Docs resume templates using an open-source parser.
- Discovers font rendering issues, ligatures (fi, fl), and missing spaces in PDFs.
- Only 9 out of 32 tested fonts successfully passed all 46 verification fields.
Resume advice frequently emphasizes being ATS-friendly, yet it rarely shows what an actual parser extracts from a file. The creator of resume templates on ReadableResume sought to answer a narrow question: when someone fills out a template and clicks File > Download > PDF in Google Docs, which fields does a parser read correctly, and which does it get wrong?
Unable to test resumes directly against enterprise systems like Workday or Greenhouse, the creator built a repeatable local testing setup. A script downloads each template as a PDF and .docx using Google Docs public export URLs without requiring any login, with all resulting files stored directly in the repository.
Stock photo for illustration only, not from the actual event
For text verification, the tool checks for any ligature characters such as joined fi or fl glyphs, split words, out-of-order sequences, and leftover text. Additionally, python-docx inspects the exported .docx files to ensure bullet points remain proper list items rather than shifting to Symbol or Wingdings fonts, while filtering out unsupported elements like tables and text boxes.
When testing 32 different fonts applied to a single-page Jake's Resume layout on US Letter paper, exactly 9 fonts managed to pass all 46 fields cleanly: Arial, Book Antiqua, Calibri, Cambria, EB Garamond, Garamond, Georgia, Times New Roman, and Trebuchet MS, maintaining exact single-page constraint and accurate character rendering.
This experiment highlights hidden technical pitfalls that standard resume design advice often ignores. Even when a layout looks flawless visually inside Google Docs, cloud export engines can introduce subtle character-level anomalies like ligature substitutions or dropped whitespace. These minor flaws can severely impact automated Applicant Tracking Systems (ATS) used by employers, making standard font selection a critical first line of defense for job seekers.
A major obstacle discovered during testing was that 16 fonts stored letter pairs as single ligature characters, such as fi and fl, causing simple keyword-matching parsers to fail. Furthermore, whitespace dropped out entirely in several popular fonts including Lato, Lora, Raleway, and Roboto, resulting in failed validation checks across multiple fields.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment