Page mistakes: gaps, parsing failures and personal data

The previous lesson dealt with what the lines say. The mistakes in this one are about what the page shows: the dates a reader scans, the layout a parser reads, and the personal details a resume should never carry.

Each of them is easy to fix and expensive to ignore. An unexplained gap invites the worst interpretation, a two-column layout can make you invisible in search, and a photo can remove you from the pile before anyone reads a line.

Gaps and tenure patterns

Career breaks and short stints are extremely common and much less damaging than most candidates fear. What damages you is leaving them unexplained.

Why silence is the problem

A reader scanning dates finds a fourteen-month gap. They do not know what it was, so they imagine something. The imagined version is usually worse than the real one — and unlike the real one, you cannot address it.

One clause removes the question:

Career break — Jan 2024 to Mar 2025 (full-time caregiving)Career break — Jun 2023 to Feb 2024 (redundancy; retraining in data engineering)

That is enough. No apology, no explanation of feelings, no elaboration.

Handling common situations

Short stints

A single short role is unremarkable. A pattern of them raises a real question: will this person leave in eight months?

If you have several, three things help:

1. Label the ones with a reason — contract, acquisition, layoff, funding failure.
2. Consider condensing very old ones. Roles from more than ten years ago can collapse into a single "Earlier experience" line.
3. Address it in the cover letter or the recruiter call, briefly and without defensiveness.

The framing rule

State the fact, do not editorialise. Compare:

Unfortunately I was let go during a difficult period for the company and struggled to find work for some time.

Career break — Jun 2023 to Feb 2024 (redundancy; completed AWS Solutions Architect certification).

The second is the same information, presented as a fact rather than as an apology.

Formatting that breaks parsing

A gap misleads the human reader. Bad formatting misleads the software before any human sees the page. The lesson on ATS parsing explained that the real ATS risk is being parsed badly. Here is the specific list of what causes it.

The offenders

Multi-column layouts. A parser reads in document order, which may not be visual order. Your skills column can end up interleaved with your experience, or attached to the wrong employer. This is the most common serious parsing failure, and two-column templates are everywhere.

Tables. Frequently used to align dates. Parsers handle them inconsistently; some flatten them into unreadable sequences. Use tab stops or right-alignment instead.

Text boxes. Content inside a text box is often skipped entirely. If your contact details are in one, you can be parsed with no email address at all.

Headers and footers. Many parsers ignore these regions. Never put contact details there.

Images and icons. A parser reads no text from a graphic. If your email is beside an envelope icon, fine — but the email itself must be real text, not part of the image.

Non-standard section headings. Where I've Been instead of Experience, or My Toolkit instead of Skills. Parsers look for conventional headings to segment the document. Be inventive somewhere else.

Unusual date formats. 03.24 – 06.25 is ambiguous. Use Mar 2024 – Jun 2025.

Scanned or image-based PDFs. No selectable text at all. Complete failure.

The check

The 60-second test from that lesson, repeated here because it catches nearly everything:

What is safe

• One column for the main content flow.
• Standard headings: Experience, Education, Skills, Projects.
• Real text throughout.
• Tab stops or right-alignment for dates.
• Simple bullet characters.
• Standard, widely available fonts.
• Bold and italic for emphasis.

This is not a restrictive palette. Every well-designed resume in Section 12 (Resume Templates) uses only these.

Photos, personal data, and regional norms

The last page mistake is what you reveal about yourself. The rules here genuinely differ by country, and applying the wrong region's convention can be costly.

The two conventions

Photo-free markets: the United States, Canada, the United Kingdom, Ireland, Australia, and New Zealand.

In these markets, including a photo or personal details such as age, gender, or marital status is a problem. Employers are exposed to discrimination claims if they can be shown to have seen protected characteristics before deciding, so some companies discard resumes with photos before review, or have recruiters strip them. The photo does not help you and can remove you.

Photo-conventional markets: parts of continental Europe, much of the Middle East, and parts of East Asia, where a photo and some personal details are traditional. Note that this is shifting — several European countries now actively discourage photos, and anonymised applications are increasingly common.

The safe default

What to never include, anywhere

That last row is worth emphasising. Never put current or expected salary on a resume, even if a form asks. It sets a ceiling before any conversation about your value has happened.

Where the personal details actually go

If a market or an employer genuinely requires this information, it comes later — on an application form, or in an equal-opportunities questionnaire that is deliberately separated from the hiring decision. That separation is intentional. Do not undo it by putting the same information on your resume.