Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
How applicant tracking systems parse a file
Choosing a file format that survives parsing
Single column layout and reading order
Section headings, labels and the job schema
Contact details, headers and footers
Tables, text boxes and graphics
Typography, contrast and legibility
The experience bullet formula
Quantifying achievements honestly
Reading the job description for keywords
Where to place keywords and how often
Acronyms, synonyms and vocabulary matching
Skills sections and interview credibility
Scoring, knockout rules and ranking
Accessible document structure and markup
Reading order and tagged documents
Inclusive language and screening out bias
Legal and privacy constraints on resume content
Tailoring without rewriting every time
Tracking applications and iterating on the document
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
A parser turns a document into a flat text stream and then into fields such as contact details, employers, titles and dates, so anything it cannot extract does not exist in the system.
Both DOCX and PDF parse on current systems, and the difference is where the structure lives: DOCX carries headings and lists as XML a parser can read directly, while a PDF carries a page description that is only useful if it was tagged.
Reading order in an untagged document is a geometric guess that assumes a single top to bottom flow, so the layout a human finds elegant is the one that needs the most guessing.
A short set of section names recurs across products, and a heading outside that set usually lands in a catch-all free text field rather than a field you can be filtered on.
A header is often tagged as a decorative artefact and excluded from the reading order entirely, so contact details placed there may exist in the file and still not exist in the record.
A table is read cell by cell in the order the document declares, which is not the order a person reads a comparison, so a grid becomes a sequence that has to be reassembled.
Questions this pack covers
How does an applicant tracking system actually parse the file I upload?
Which sections of a resume does the parser turn into named fields?
Should I send a PDF or a Word document to a tracking system?
When does a plain text file actually beat a PDF for parsing?
Why do multi-column resume layouts scramble the reading order?
How do I convert a two-column template into one that parses?
Which section headings does a parser recognise without needing an alias?
How do I match the section names a posting uses in my own headings?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
