Why most resumes die before a human reads them

The uncomfortable truth: the majority of online job applications are rejected before a recruiter opens them. Not because the candidate lacks the skills — because the resume formatting confused the ATS parser, and the system either scored the application zero or failed to extract the data at all.

Applicant tracking systems are database tools, not intelligent readers. They ingest your document, attempt to extract structured data (name, contact details, job titles, dates, skills), and score the result against a keyword profile for the role. If the extraction fails — because you put your contact details in a header, used a table for your skills section, or saved the file in a format the system struggles with — the recruiter never knows you applied.

This is not a niche problem. Jobscan estimates that over 98% of Fortune 500 companies use ATS software. For senior and professional roles in the UK, adoption is similarly near-universal at large employers. Even mid-size companies using platforms like BambooHR or Teamtailor apply some degree of automated screening.

The fix is not complicated. It requires discipline, not design talent. An ATS-friendly resume is deliberately simple — and that simplicity is the point.

What ATS actually does (and does not do)

A common misconception is that ATS systems are sophisticated semantic engines that understand context. They are not, in most implementations. Most systems work at the keyword and phrase level: they look for the presence or absence of terms from the job description, weight them against an importance score, and rank candidates accordingly.

Some platforms — Greenhouse and Lever among them — use more sophisticated parsing, including semantic similarity matching. But “more sophisticated” is relative. Even the best systems struggle with:

• Multi-column layouts, where text from adjacent columns gets concatenated
• Tables, where cell contents merge into a string of numbers and words
• Text boxes, which are typically ignored entirely
• Headers and footers, which most parsers treat as document metadata rather than content
• Graphics substituted for text (skill bars, star ratings, logos)

The most expensive resume design in the world will not pass an ATS if it uses a two-column layout with a graphics sidebar. A plain, single-column document formatted in Calibri will outscore it every time.

When to use an ATS-friendly format

Online applications through career portals. Any time you click “Apply” on a company’s website or a job board (LinkedIn, Indeed, Reed, Totaljobs), assume an ATS is involved.

Recruitment agency submissions. Most large UK and US recruitment agencies use their own ATS to tag and search their candidate database. If you send your CV to a recruiter and it does not parse cleanly, you will not surface in searches.

High-volume hiring. Graduate schemes, entry-level tech roles, and any position that generates hundreds of applications will almost certainly be screened by ATS first.

When NOT to prioritise ATS formatting. If you are handing your resume directly to a hiring manager, presenting at a networking event, or applying to a small business that does not use HR software, a visually designed resume is fine. ATS optimisation is for digital portals, not in-person handoffs.

What your ATS resume must include

1. Contact details in the body of the document. Not in a header. Put your full name, phone number, email, and LinkedIn URL as plain text at the very top of page one.

2. Standard section headings. Work Experience (or Professional Experience), Education, Skills (or Technical Skills), Certifications. The system is looking for these exact terms. Clever alternatives (“Career Highlights”, “Where I’ve Been”) will not be recognised.

3. Reverse chronological order. Most recent position first. This is the standard that ATS parsers expect.

4. Dates in a consistent format. “Jan 2022 – Mar 2024” is fine. “2022-2024” is also acceptable. Avoid ordinal dates (“1st January 2022”) — some parsers choke on them.

5. Keywords from the job description. This is the highest-leverage action you can take. Match the exact phrases used in the posting wherever they apply to you. If the posting says “stakeholder management,” your resume should say “stakeholder management,” not “cross-functional collaboration.”

6. Quantified achievements. Numbers improve keyword density and provide concrete context: “reduced pipeline build time by 40%”, “managed a team of 12 engineers”, “grew organic traffic from 20k to 180k sessions/month.” Both humans and ATS scoring benefit.

Variants you will encounter

Chronological ATS resume. The standard format. Work history in reverse order, skills section, education. Suits most professionals with a consistent employment history.

Hybrid ATS resume. Leads with a prominent skills section before the work history. Useful for career changers or people returning from a career break, where leading with skills emphasises competencies over chronology. Still single-column.

Technical ATS resume. Extended skills and certifications sections, often with technology stacks listed by category. Common in software engineering, data, and DevOps roles. The skills section may be longer than a single line.

UK CV format with ATS optimisation. UK CVs traditionally include a personal statement at the top, and UK employers do not typically expect or want a US-style objective statement. The ATS optimisation principles are identical; the content conventions differ slightly (UK CVs often include 2 referees at the end; US resumes do not).

Step-by-step: building the template

Step 1 — Choose your tool. Microsoft Word (.docx) is the safest choice. Google Docs is acceptable but export as .docx, not as .gdoc or .pdf, unless the posting specifies PDF. Avoid Canva, LaTeX, or InDesign — their export formats are inconsistent with ATS parsers.

Step 2 — Set up the single-column structure. Set margins to 0.75–1 inch. Use a standard font at 10–12pt for body text, 14–16pt for your name. Do not use text boxes, tables, or multiple columns.

Step 3 — Add your contact details in the body, not the header. Name on line 1 (slightly larger). Phone | Email | LinkedIn | Location on line 2. Plain text, no icons.

Step 4 — Write a tailored summary. Three to four sentences. Include your target job title, your years of experience, your top two or three skills, and what you are looking for. Rewrite this section for each application to mirror the role’s language.

Step 5 — Build your skills section. Divide into categories: Technical Skills, Tools, Methodologies (or whatever is relevant to your field). List each as plain text. No graphics, no bars, no dots.

Step 6 — Populate work experience. Company name, your job title, start and end month/year, location. Then three to five bullet points per role, each starting with a past-tense action verb, each including at least one number where possible.

Step 7 — Add education and certifications. Degree, institution, graduation year. Certifications: name, issuer, year. Keep it brief unless you are a recent graduate.

Step 8 — Run the paste test. Paste the entire resume into Notepad. If it reads cleanly and in order, you are done. If text is scrambled or missing, something in your source document is not parsing correctly.

Common mistakes

Mistake 1: Decorative design. The resume that wins design awards does not win job offers at large employers. Save the creative format for portfolio work.

Mistake 2: Contact details in the header. This is the single most common parsing failure. Move them to the body.

Mistake 3: Using the same resume for every application. A generic resume that does not mirror the job description’s exact language will score low on keyword matching. Minimum viable tailoring: rewrite the summary and adjust the skills section for each role.

Mistake 4: Omitting months from dates. “2021–2023” is ambiguous — it could mean January 2021 to December 2023 (almost 3 years) or November 2021 to January 2023 (14 months). Parsers infer dates differently. Use month abbreviations.

Mistake 5: Burying skills inside bullet points only. ATS systems weight dedicated skills sections heavily. Do not rely on skills appearing inside job descriptions to be counted — put them in the Skills section explicitly.

Worked example

Maya Iyer | maya.iyer@email.com | +44 7911 234567 | London, UK | linkedin.com/in/mayaiyer

Summary: Senior data engineer with 8 years building and maintaining large-scale data pipelines on AWS and GCP. Expertise in Python, Apache Airflow, dbt, Snowflake, and Terraform. Currently seeking a staff or principal data engineering role in fintech or climate tech.

Technical Skills: Python, SQL, dbt, Apache Airflow, Snowflake, AWS Redshift, AWS Glue, GCP BigQuery, Terraform, CI/CD, Docker, Kubernetes

Tools: GitHub Actions, dbt Cloud, Fivetran, Airbyte, Looker, Databricks

Work Experience:
Senior Data Engineer — Monzo Bank, London | Apr 2022 – Present

• Redesigned core transaction data pipeline reducing daily run time from 4 hours to 47 minutes (81% reduction) using Airflow 2.x DAG refactoring and dbt incremental models
• Led migration from on-prem Postgres to Snowflake for 1.2TB analytics warehouse, zero downtime
• Mentored 3 mid-level engineers through internal promotion process; all promoted within 12 months

Maya is applying through Workday for a role at a fintech. The job description uses “Airflow,” “dbt,” “Snowflake,” and “Terraform” — all present verbatim in Maya’s resume. No tables. No columns. Single-column .docx. The Workday parser will extract her data cleanly, and she will appear in the recruiter’s shortlist.

UK versus US resume conventions