Applicant tracking systems collect a lot of bad advice. "The ATS auto-rejects you", "never use any formatting", "keyword-stuff or you are invisible". Most of it is wrong, and acting on it produces a CV that is dull to humans without being any friendlier to software.

Here is the accurate version. An ATS is mostly a database. It parses your CV into fields, stores it, and lets a recruiter search and filter. It does not score your personality or silently bin you. The real risk is narrower: if the parser misreads your CV, your experience lands in the wrong field or gets lost, and a recruiter searching for a skill you have will not find you. Format for the parser, and that risk goes away.

Use a single-column layout

This is the one that matters most. Many ATS parsers read top to bottom, left to right. A two-column layout, with a skills sidebar next to your experience, can be read in the wrong order: the parser interleaves the sidebar into the middle of a job description, and the result is scrambled.

A single column removes the ambiguity. Everything reads in one clear sequence. It is less visually striking, but a striking CV that parses into nonsense helps nobody.

Use standard section headings

The parser looks for headings it recognises to know where each block of content belongs. Use the plain ones: "Work Experience", "Education", "Skills", "Certifications".

Creative headings break this. "Where I have made an impact" might read well to a human, but a parser does not know it means work experience, so the content underneath may never be filed correctly. Save the personality for the bullet content, not the labels.

Keep dates and structure consistent

Write every date the same way throughout. Pick one format, "Jan 2023 – Mar 2025", and use it for every role. Mixed formats make the parser work harder and increase the chance it extracts a date wrong, which can make a recent job look old.

Give each role the same shape: job title, company, dates, then bullets. Predictable structure is easy structure to parse.

Avoid the elements that break parsers

A few specific things cause real trouble:

• Text inside images. A parser reads text, not pictures. A name or contact detail rendered as an image is invisible to it.
• Text boxes and tables for layout. These often get read out of order or skipped. Lay out with plain paragraphs and standard bullets instead.
• Headers and footers. Some parsers ignore the header and footer region entirely. Never put your phone number or email only in the header.
• Unusual fonts and symbols. Stick to common fonts and standard bullet characters. A decorative glyph can come through as a stray character.

Save it as the right file type

A modern, text-based PDF is read reliably by most current systems and keeps your layout intact. The exception is when the application form explicitly asks for .docx, in which case follow the instruction. Never submit a scanned or image-based PDF; to a parser that is just a picture with no readable text.

Use keywords honestly

Keywords matter, but not the way the myths claim. A recruiter searches the ATS for specific skills, so the words for skills you genuinely have should appear in your CV in plain language, ideally the same terms used in the job posting.

What does not work is stuffing: hidden white text, a wall of keywords, terms for skills you do not have. Modern systems and the humans behind them catch it, and an interview exposes the gap immediately. Match real skills to real words and stop there.

The goal of an ATS-friendly format is not to please a robot at the expense of a person. A clean single-column CV with standard headings and honest keywords reads well to both. Run your current CV against this list, fix the column layout first if it has two, and you have removed the most common parsing failure in one change. If you are rebuilding from scratch, Postulit generates a single-column, parser-safe CV from your LinkedIn profile as a starting point.