Writing a CV that survives screening

You have just uploaded a résumé to a job portal and the next step is an invisible software scan. The system will pull text, compare it to the posting, and decide whether a recruiter ever sees your name. The difference between a file that passes that scan and one that gets discarded often comes down to a few formatting choices. The following guide shows which technical details matter, how to keep the document readable for both machines and humans, and how to adapt a master copy without starting from scratch.

How applicant tracking systems read text

Most applicant tracking systems (ATS) work by extracting plain text from the uploaded file and then running a keyword match. They reliably handle simple headings, bullet points, and single‑column layouts that use standard fonts. Complex elements such as text boxes, footers, or embedded objects tend to be ignored or scrambled, causing loss of crucial information. The parsing engine typically reads the document from top to bottom, stopping after a few hundred words if it encounters unreadable sections. Keeping the structure linear and avoiding hidden formatting ensures that the system captures the intended content.

Why columns, tables, and graphics break parsing

Columns and tables visually organize data for a human reader, but many ATS treat them as separate blocks and may drop everything after the first column. Headers and footers are also frequently skipped, so placing contact details there can make them invisible to the parser. Graphics, icons, and logos are ignored by most systems and can shift the text flow, leading to misplaced or missing words. The safest approach is a single‑column, text‑only layout with clear section headings and simple bullet points, which preserves both readability and machine compatibility.

Using the job description language without stuffing

Copying exact phrases from the posting signals relevance, but overloading the résumé with every keyword can make the text unreadable and trigger spam filters. Identify the core responsibilities and required skills, then weave those terms naturally into your achievements. For example, if the ad calls for “project coordination,” describe a specific project where you coordinated resources, using that exact phrase once or twice. This method satisfies the keyword check while keeping the narrative authentic and concise.

File format choices when the advert is silent

If the job listing does not specify a format, the safest option is a text‑based DOCX file. Most ATS can extract text from DOCX reliably, and the format preserves basic styling without embedding images. PDF files are acceptable only when they are generated from text, not scanned images, because image‑based PDFs prevent the parser from seeing any content. Avoid sending rich‑text formats such as RTF or ODT unless explicitly requested, as they may be misinterpreted by older systems.

Length, order, and what the parser reads first

Recruiters and ATS typically focus on the top portion of a résumé, often the first two hundred words. Place a concise summary or headline at the very beginning, followed by a short list of core competencies. Recent and relevant experience should appear next, with older roles further down. Keeping the document to one or two pages reduces the chance that important details are cut off by length limits and helps the parser prioritize the most pertinent information.

Tailoring quickly without rewriting the whole document

Maintain a master version that contains all of your experience and skills. When applying for a specific role, copy the master into a new file and then delete unrelated sections, adjust bullet points, and replace generic terms with the exact wording from the posting. Use the find‑and‑replace function to swap out company names or job titles, and reorder the most relevant achievements to the top. This process takes minutes and eliminates the need to draft a fresh résumé for each application.

Common questions