There is an enormous amount of folklore about applicant tracking systems: that they auto-reject on keyword density, that they cannot read anything but Times New Roman, that a hidden white-text keyword block will get you through. Almost none of it is true, and some of it will get your application binned by the human who notices.

What an ATS mostly does is parse your document into fields and let a recruiter search and filter. The failures worth caring about are parsing failures — where your experience ends up in the wrong field or disappears entirely.

What actually breaks parsing

  • Multi-column layouts. The single most common cause of scrambled parsing. Text reads left to right across both columns and comes out as nonsense.
  • Text inside headers and footers. Many parsers skip them. Never put your contact details there.
  • Text inside images or graphics. Invisible to a parser. That includes skill "rating" bars and icon-based contact details.
  • Tables for layout. Sometimes fine, often not. Not worth the risk.
  • Non-standard section headings. "Where I have been" instead of "Experience". Parsers look for conventional labels.
  • Unusual file formats. Submit .docx unless a PDF is explicitly requested; PDF parsing has improved but .docx remains the safest.
  • Dates a parser cannot resolve. "Spring 2023" and "2023–" often come back empty. Use a month and a year, written the same way in every entry.

The eight seconds after parsing

Once a human opens it, three things get read: your most recent job title, the first bullet under it, and the company names. Everything else is scanned. Design for that.

The summary, if you include one

Three lines, and only if it says something a job title cannot. "Operations manager, 6 years, specialised in warehouse automation rollouts across 40+ sites" earns its space. "Results-driven professional with a passion for excellence" does not.

Bullets that carry weight

The formula is boring and effective: action verb + what you did + the scale + the outcome. Compare:

  • Weak: "Responsible for social media accounts."
  • Better: "Ran four social accounts (combined 80k followers); grew referral traffic 34% in 2025 by shifting from daily posts to two long-form posts a week."

The same operation on a duller line. Before: "Assisted with the monthly reporting process." After: "Rebuilt the monthly reporting pack for a 12-person commercial team, cutting the close from five days to two by replacing manual exports with a scheduled query."

Three things changed: a vague verb became a specific one, an unstated scale became a stated one, and an activity became a result with the mechanism named. Naming the mechanism is what makes a claim credible. Scale matters as much as outcome. Managing a £40k budget and a £4m budget are different jobs with the same verb.

Keywords, handled honestly

Read the posting and use its exact nouns for things you have genuinely done. If it says "stakeholder management" and you wrote "client liaison", change it. This is not gaming the system; it is speaking the same language as the reader. What you should not do is list tools you have touched once.

One page or two?

Under ten years of experience: one page. Over ten, or in academic, medical and some public-sector contexts: two, and follow the local convention. Regional differences still matter: photos and dates of birth are normal in parts of continental Europe and a liability in the UK and North America. Keep one version per convention rather than a compromise.

Tailoring in six minutes

Fully rewriting your CV for every application is unsustainable and mostly unnecessary. What works is a strong base document plus a short, fixed routine.

Change three things. Reorder the bullets under your most recent role so the ones matching the posting sit first, because the first bullet is the one that gets read. Rewrite the summary line in the posting's own language. Swap two or three entries in the skills list for the specific tools it names, where you have used them.

Leave everything else alone — sections, dates, older roles, formatting. Do not draft a new bullet in a hurry; that is where overclaiming gets in. Save each copy with the employer's name in the filename.

The safe structure

Single column. Name and contact details in the body at the top. Conventional headings in this order: Summary, Experience, Education, Skills. Dates formatted "Mar 2023 – Present" on the same line as the role. A standard font at 10–12pt.

When one CV serves a parser and a referral

Most advice assumes one reader. In practice the same file goes into a portal and, on a good week, straight to a hiring manager through someone who knows you. The system wants clean fields and conventional labels; the human wants to see why a friend passed your name on.

You do not need two documents, but the top third has to work twice. Make the summary a plain statement of what you do and at what scale, not a positioning line, and put the most relevant achievement as the first bullet of the most recent role.

What changes for a referral is the covering message, not the CV. Give the person referring you two or three sentences they can paste: what you do, why this role, one concrete result. A referral with a usable line of context gets forwarded; a bare attachment gets filed.

A CV does not get you the job. It gets you twenty minutes on a call. Optimise for that.

Before you send it

  • Save a copy as plain text and read it. If it is incoherent, so is the parsed version.
  • Name the file "Firstname Lastname CV.docx", not "cv_final_v7.docx".
  • Check the dates add up and that there are no unexplained multi-year gaps — a one-line explanation is always better than a hole.
  • Have someone outside your field read it. If they cannot tell what you do, neither can a recruiter screening 200 applications.