Does an ATS score your resume? What actually happens when you apply

Search for resume advice and you will hit the same claim within about thirty seconds: an applicant tracking system scans your resume, scores it out of 100, and bins anything under 75. Tools offer to tell you that number. Some charge you for it.

That number does not exist.

Not in the sense that it is often inaccurate, but in the sense that the thing being measured is not a thing. There is no industry standard resume score. There is no pass mark. Understanding what an applicant tracking system genuinely does is the difference between optimising for a real process and optimising for folklore, and the real process is both less mysterious and more beatable.

What an applicant tracking system actually is

An applicant tracking system is a database with a workflow attached. Greenhouse, Lever, Workday, Taleo, SmartRecruiters, BambooHR: these are systems of record for hiring. Their core job is to take an application, parse it into structured fields, store it, and give recruiters a way to move candidates through stages.

The emphasis matters. An ATS is built for the recruiter's workflow, not to judge you. It is much closer to a customer database than to an examiner.

When you submit an application, roughly this happens:

1. Your file is parsed. The system extracts text and tries to map it into fields: name, contact details, employers, job titles, dates, education, skills.
2. That structured record lands in a database alongside every other applicant.
3. A recruiter opens a list of applicants, usually sorted by date received.
4. They search, filter, shortlist and read.

Notice what is missing from that sequence. Nowhere does the system compute a quality score and reject you on it. In most configurations of most major systems, automatic rejection based on the content of your resume is simply not switched on. The filters that genuinely do reject automatically are the knockout questions you answered in the application form, things like whether you have the right to work in the country, whether you hold a required licence, or whether you have a stated minimum number of years of experience. Those are your answers, not an analysis of your prose.

Where the myth of the resume score comes from

Three real things got compressed into one imaginary one.

Keyword search is real. Recruiters facing 400 applicants search the database. They type "Kubernetes" or "IFRS 16" or "paediatric nursing" and see who comes back. If your resume does not contain the words they search for, you are not in the result set, and being outside the result set is functionally identical to being rejected. This is real, and it matters more than almost anything else in this article. But it is a recruiter searching, not a machine scoring.

Match indicators are real, and misunderstood. Some systems show a relevance percentage to the recruiter when a job description is attached. It is a rough keyword overlap signal, shown to a human as a sorting aid. It is not a pass mark, it is not visible to you, and experienced recruiters routinely ignore it because they know how crude it is.

Parsing failure is real, and brutal. This is the origin of most "the ATS rejected me" stories. If your resume is a two column layout with your job titles in a sidebar, the parser may read your career in the wrong order. If your dates sit in a text box, they may vanish. If your name is in the header of a Word document, some parsers never see it. You do not get scored badly. You get recorded wrongly, and a recruiter searching for a Product Manager never finds the Product Manager sitting in the database with an empty job title field.

Blend those three together and you get the myth: a machine, judging you, with a number.

The part that really can reject you

Since parsing is the mechanism that actually loses good candidates, it deserves more attention than it usually gets.

A parser is trying to answer boring questions. Where does one job end and the next begin? Which line is a job title and which is an employer? Is that string a date? Design choices that look elegant to a human reader make those questions harder. Sidebars break reading order. Tables scramble cell sequence. Icons replacing the words "email" and "phone" leave a parser with no label. Text embedded in an image is invisible: to the database, that section of your resume is blank.

Test your own resume in two minutes

You do not need a paid ATS resume checker to find most of these problems. Try this instead, because it approximates what the parser sees:

1. Open your resume, select all, and copy.
2. Paste it into a plain text editor: Notepad, TextEdit in plain text mode, or any blank text box.
3. Read what comes out.

If your job titles appear in a sensible order, your dates sit beside the right roles, your contact details are present, and nothing is missing or interleaved strangely, your resume parses cleanly. If the output is scrambled, out of order, or missing entire sections, that is very close to what lands in the database.

This one test catches the large majority of ATS friendly resume format problems, and it costs nothing.

What recruiters actually do with the database

Once your record is stored correctly, a human takes over, and their behaviour is worth designing for.

A recruiter working a busy role does not read 400 resumes. They search, they filter to a manageable shortlist, and they skim. The first pass on your document is fast, often just a few seconds, and it is answering one question: does this person's recent experience look adjacent to this role? Job titles, employer names and dates carry that first pass, which is why the top third of page one is disproportionately valuable real estate.

If you survive that, you get a real read. Now the question changes to whether you actually did the work or merely sat near it. This is where specific outcomes beat responsibility lists decisively. "Managed the migration" tells a recruiter nothing your job title did not already imply. "Migrated 40TB across 12 services with no unplanned downtime" tells them what kind of person you are, and it gives an interviewer something to ask about.

What this changes about how you write

If you stop optimising for an imaginary score, some common advice falls away and better advice replaces it.

Stop stuffing keywords and start earning them

Keyword stuffing, which means pasting a wall of skills in white text or repeating "project management" nine times, is built for a scorer that does not exist. What it actually produces is a document that reads badly to the person who does decide, and white text is trivially visible the moment anyone opens the file properly.

The useful version is to make sure the genuine vocabulary of the role appears in your resume in context, attached to evidence. If the advert says "stakeholder management" and you have done it, that phrase should appear inside a bullet that shows you doing it, not floating in a skills soup at the bottom. You then pass the recruiter's keyword search and survive the read that follows.

Make the document boring to a parser

This is where a machine genuinely can hurt you, so it is worth being conservative:

• One column. Sidebars are the single most common cause of scrambled parsing.
• Real text, never images. A beautifully designed resume exported as a graphic parses as nothing at all.
• Standard section headings. Use "Experience", "Education", "Skills". Not "Where I've Made Magic".
• Consistent, conventional dates, on the same line as the role.
• Contact details in the body of the document, never in a header or footer.
• A .docx file or a text based PDF. Both parse fine in modern systems. What fails is a scanned or flattened file.
• Job titles that a human would recognise. More on this below.

None of that requires an ugly document. It requires a structurally simple one.

Translate an unrecognisable job title

If your real title is company specific, such as "Growth Ninja" or "Member Experience Consultant", you are invisible to a recruiter searching for the standard term. The honest fix is a clarifier rather than a rewrite: "Member Experience Consultant (Customer Success Manager)". You keep your real title, and you become findable.

A ten minute checklist

Before you send your next application, run this:

1. Copy and paste your resume into a plain text editor and confirm it reads correctly.
2. Confirm your contact details are in the document body.
3. Confirm every role has a recognisable title, an employer and dates on the same line.
4. Confirm the top third of page one speaks to this specific job.
5. Pull the five most important terms out of the advert and confirm each appears somewhere true in your resume.
6. Confirm your three strongest bullets contain a number.
7. Confirm you could defend every sentence under questioning.

That is the whole game. Findable by the search, legible to the parser, convincing to the person.

Common questions

Does an ATS automatically reject resumes?

Almost never on the basis of your resume's content. Automatic rejection is generally driven by the knockout questions you answer in the application form, such as work rights, required licences or a stated minimum number of years of experience. The far more common failure is that your resume parsed badly, so a recruiter's search never surfaced you.

What is a good ATS score for a resume?

There is no such thing. No mainstream applicant tracking system produces a quality score that gates your application, and the numbers offered by third party tools are that tool's own invention rather than anything a recruiter sees. Judge your resume on whether it parses cleanly, contains the genuine vocabulary of the role, and gives specific evidence.

Is a PDF or a Word document better for an ATS?

Both are fine in modern systems, as long as the PDF is text based rather than a scan or a flattened image. If an application form explicitly asks for one format, follow the instruction. If you are unsure, .docx is the safest default because every parser handles it.

Do ATS systems reject resumes with columns, tables or graphics?

They do not reject them, but they frequently misread them. Two column layouts are the most common cause of scrambled parsing, tables can scramble reading order, and any text inside an image is invisible to the parser. A single column layout with real text avoids all three problems.

How many keywords should I put in my resume?

There is no target count, and chasing one leads to stuffing. Aim to cover the genuine specifics of the advert, meaning named tools, standards, certifications and the standard vocabulary for the work, with each term sitting inside a bullet that demonstrates it. If you cannot attach a term to real experience, leave it out.

Does keyword stuffing work?

No. It is built for a scoring system that does not exist, it makes your resume read badly to the person who decides, and hidden text is easy to spot. It is a real risk with no matching benefit.

Why we built ResumeProofed this way

We deliberately do not show you an "ATS score", because we would have to invent it.

What we show instead is two things we can stand behind. A Proof Score measures how well every claim in your tailored resume is supported by facts you have confirmed about your own career. It is a truthfulness and evidence measure, not a guess about someone else's software. A Recruiter Scan emulates the market lens: the keyword and structure signals that a recruiter's search and first read will actually apply, computed transparently so you can see exactly what drove the result.

Neither pretends to be an official verdict from a system we do not have access to, and we think that distinction is the product. Your facts stay locked and true, the language adapts to the role, and nothing sits on the page because a mythical scorer might reward it.

ResumeProofed opens soon. Join the waitlist to be first in.