Resume in PDF or Word
The PDF-versus-Word argument matters less than people think. The genuinely dangerous case is a third one: a file that looks perfect on screen and is a blank page to an applicant tracking system.
Updated
That third case first
A PDF with no text layer. It looks like any other PDF, opens normally, prints fine — and contains not one readable character. Instead of text there is an image.
It happens two common ways:
- a scan — someone printed the resume, signed it and scanned it back,
- an export from a design tool where the text was converted to outlines.
The result is the same and it is the worst possible one: the application form fills in no fields, and you enter the database as an empty record. Not „low in the ranking” — empty.
PDF: identical everywhere, reading order guessed
A PDF looks the same to everyone and nothing takes that away from it. The cost is inside: the file contains no document structure. There is no „this is a section heading”, no „this is the left column”. There is a list of text fragments with coordinates on the page.
Reading order therefore has to be reconstructed from numbers alone: whatever sits at a similar height gets joined into a line. With one column that works perfectly. With two, a line collects fragments from both at once, and out comes nonsense.
DOCX: structure written down
In a Word file a paragraph is a paragraph and a list item carries a list marker. Nothing has to be guessed from coordinates, so plenty of systems take a Word file apart more reliably than a PDF. It is an argument you rarely hear, and it is sometimes decisive.
The drawback is different: the document looks different to different people. Other fonts, another version of Word, another page break — a resume planned for one page can spill onto two.
And one trap: columns in Word are built with a table. Some systems read a table cell by cell and the columns unwrap themselves; others take it apart row by row — and back comes exactly the same nonsense as the PDF. A layout table is a bet on which system you land in front of.
What follows
- When the posting asks for a specific format, send that one. It is not an open question, and sending a PDF where the form wants DOCX gets rejected at the technical stage.
- When nothing is specified — a PDF with a text layer. It renders predictably and parses well, provided it is single-column.
- Keep both versions. One click, and the whole problem closes for good.
- Never a scan, and never a file from a design tool without checking that the text can be selected.
Format is not layout
Two things blur together in conversations about resumes. File format is PDF or DOCX. Layout is one column or two, standard headings or invented ones, contact details in the body or in the footer.
Layout weighs far more. A two-column PDF and a two-column DOCX both lose; a single-column PDF and a single-column DOCX both win. The choice of format only decides anything once the layout is already sound.
The file name
A detail that costs nothing. `anna-kowalska-resume.pdf` reads well in a recruiter's inbox; `CV_final_v3_revised(2).pdf` tells them something about you that you would rather not say. No spaces and no accented characters — some systems trip over them when saving.