How an ATS actually screens your résumé (and what really rejects you)

Most advice about applicant tracking systems is written by people selling something to beat them. The result is a folk model that is roughly the opposite of the truth: a machine reads your résumé, gives it a score out of a hundred, and bins you before a human ever sees it.

That is not what happens in most of the systems used by companies hiring internationally. Understanding what does happen changes what you should spend your effort on.

What an ATS is

An applicant tracking system is, at its core, three things:

1. A form on the company's careers page that collects your details and files.
2. A database that stores every applicant against every job.
3. A workflow tool where recruiters move candidates through stages, leave notes, schedule interviews, and send rejections.

Greenhouse, Lever, Ashby, Workday and SmartRecruiters all do those three things. They differ enormously in how heavy the form is and how much configuration the employer can bolt on, but none of them is fundamentally an evaluation engine. The evaluation is done by people, using the system as a queue.

This matters because it tells you where the real bottleneck is: the recruiter's screen of a list, not a hidden scoring model.

The three things that genuinely filter you out automatically

There are automatic filters. They are just narrower and more boring than the folklore suggests.

1. Knockout questions

Almost every employer adds a handful of yes/no or multiple-choice questions to the application. The classic pair, for roles in the US, UK, EU and elsewhere:

• Are you legally authorised to work in [country]?
• Will you now or in the future require sponsorship for employment visa status?

Others include minimum years of experience, willingness to work from a particular office, ability to pass a background check, or a specific licence or certification.

These are the answers most likely to remove you without a human ever looking. Some systems disposition candidates automatically on the wrong answer; more often the recruiter filters the list by them in one click, which amounts to the same thing.

What to do: answer them accurately, and answer them deliberately. An honest "yes, I need sponsorship" costs you some applications and saves you the ones that were never real. Guessing or leaving them blank is worse than either answer.

2. Parsing failures

When you upload a résumé, the system tries to extract structured fields from it: name, email, phone, employers, titles, dates, education, skills. That extracted data is what fills the form, what is searchable later, and what appears in some list views.

Parsers are decent now, and PDFs are fine — the old advice to always send .docx is mostly obsolete. But parsers still fail on:

• Multi-column layouts, where text is read across the columns and comes out interleaved.
• Text inside tables, which frequently collapses into one run-on field.
• Content in headers and footers, which some parsers skip entirely — including, disastrously, your phone number and email.
• Text rendered as an image, including "skills" graphics and rating bars, which contain no text at all.
• Fancy glyphs and icons used instead of labels, so "✉ me@example.com" loses its meaning.

A parsing failure rarely rejects you outright. What it does is make you invisible to the recruiter's search and confusing in list view, and it forces you to retype everything by hand into the form.

What to do: keep one plain, single-column version of your résumé for applications. Real headings, real bullet points, dates in a consistent format, contact details in the body of the document rather than in the header. Design your beautiful version for humans you send it to directly.

3. Duplicate and re-application rules

Systems track that you have applied. Applying to the same job twice usually just merges into the same record. Applying to fifteen roles at the same company in a week is visible to the recruiter as fifteen rows with your name on them, and it reads exactly as it is.

Some employers configure a cooldown, so a fresh application to a role you were rejected for within some window is filed automatically without review.

What to do: pick the two or three roles at a company that you would genuinely take, and apply to those.

What is not usually happening

• You are not being given a match score that decides your fate. Some systems surface a score or a sort order to the recruiter as a convenience. It is one signal among many on a screen full of other information, and recruiters routinely ignore it.
• Keyword stuffing does not unlock a gate. Keywords matter because a recruiter searches the database for them, and because a human reads them and decides whether you look like the job. White text, keyword lists in tiny font at the bottom, and other tricks are visible in the parsed data and are read as exactly what they are.
• There is no universal "ATS-friendly" template. There is only "parses cleanly and reads well". Those are the same document.

The parts of the pipeline that really decide

Once your application is in the queue, the things that move it forward are unglamorous:

Whether you match the shape of the role. Not the keyword list — the shape. A backend role at a 60-person company wants someone who has shipped and owned things at a similar scale. If your last three roles are enterprise Java at a bank and the role is a Node service at a seed-stage startup, no phrasing rescues that.

Timing. Many roles are reviewed in batches, and many are effectively decided within the first week or two of posting. Applying in the first days of a posting is a real, if unromantic, advantage.

Whether the top third of your résumé answers the question. Recruiters give a first pass in seconds. If your current title, your last employer, your location and one or two strong lines about scope are visible without scrolling, you get the second look.

The screening question answers. Where an employer asks why this company or tell us about a project, that box is often read before the résumé, especially at smaller companies. Two specific sentences about their product beat five paragraphs of enthusiasm.

Referrals. They do not skip the process, but they route your application to a human quickly, which — given everything above — is most of the battle.

What this means for how you spend your time

If you accept that the ATS is a queue rather than a judge, the priorities reorder themselves:

• Spend your effort on which jobs you apply to, and on the first third of the résumé — not on formatting superstitions.
• Keep one clean, parseable master résumé, and adapt the top of it per role family rather than rewriting the whole thing per job.
• Answer knockout questions honestly and consistently, because inconsistency across applications at the same company is noticed.
• Apply early in a posting's life rather than perfectly late.
• Track what you sent and when, so that when something comes back three weeks later you know what it refers to.

None of that is a trick. It is just aiming at the part of the process that actually has a person in it.