Resume Formatting That Survives Parsing

Most advice here is unhelpfully absolute: no columns, no colour, no design. That is not true, and following it produces resumes nobody enjoys reading.

The real constraint is narrower. A parser needs to pull structured fields out of your file. Five habits break that, and none of them require you to give up a template you like.

1. Contact details in the header

Some parsers never read the header or footer region of a .docx at all. Your email and phone number then simply do not exist.

Move them into the body of the document, in the first few lines.

2. Mixed date formats

"Mar 2021", "03/21" and "2021-03" in the same document will produce inconsistent employment records, and sometimes none at all.

Pick one format and use it for every role, including the current one.

3. Reading order in multi-column layouts

Two columns are fine if the underlying document orders them sensibly. They are not fine when the file was built with text boxes, because the extracted order interleaves the columns into nonsense.

If you are unsure which you have, save a copy as plain text and read it. What you see is roughly what the parser sees.

4. Text living inside images

A job title set as part of a graphic is invisible. So is a skills wheel, an infographic, or a name rendered as a logo.

Anything that matters must exist as real text.

5. Invented section headings

"Where I have been" is charming and unparseable. Use Experience, Education, Skills, Projects. Save the personality for the sentences.

The check that takes two minutes

Save your resume as plain text, open it, and read it top to bottom. If your name, contact details, employers, titles and dates are all present and in a sensible order, your formatting is fine — whatever it looks like on screen.