Does an ATS Reject CVs? The Truth Looks Different

2026-09-11

Short answer: no. No ATS I’ve ever worked with, Element included, has a function that reads a CV and automatically rejects a candidate. What an ATS actually does is index the CV text and let a recruiter search for candidates by keyword. The decision to reject, meaning the status change and the notification, is always made by a person.

This myth is worth clearing up, because it works against candidates: instead of fixing a CV so it’s easier to find, many people give up, convinced that “the algorithm will reject me anyway.”

Where the "rejecting ATS" myth comes from

A candidate sends a CV, hears nothing back, and looks for an explanation. “The system rejected me” sounds less personal than “the recruiter didn’t think my experience was strong enough,” or, more often, “my CV sat in the database and nobody ever searched for the right term.” The second scenario is a far less satisfying story, so the myth of an intelligent, judging algorithm keeps circulating in the press and on candidate forums.

Language adds to the confusion. “ATS” (Applicant Tracking System) gets conflated in the media with the recruiting systems used by large, mostly American, corporations, some of which do run automatic screening questions. More on that below, since it’s the one real exception to the rule.

What an ATS actually does with your CV

An ATS reads the text of a CV and stores it so a recruiter can find it in the candidate database by typing keywords, a job title, a skill, a technology. That’s the entire “intelligence” on the system’s side: text parsing and a search engine. I wrote about this at length in the article about the keyword cloud.

Nobody on the system side judges whether a candidate is “a good fit” for a role. That judgment is always made by a person: the recruiter who reviews the search results, opens a CV, and decides what happens next. Changing a candidate’s status to “rejected” in a system like Element is always a manual click by the recruiter.

When a CV really does "disappear," and why that's not the same as rejection

This is where candidates’ real frustration comes from, and it’s worth naming precisely. I suspect most complaints about a “rejecting algorithm” are really CVs that simply became invisible: they didn’t contain the keywords the recruiter searched for, so they sat in the database and nobody found them, because the recruiter was searching for different terms.

The difference matters in practice: rejection implies someone, or something, evaluated the CV and judged it insufficient, while a lack of visibility means nobody ever looked at it. That’s good news for the candidate: the fix is usually the vocabulary in the CV, something you can solve without rewriting your resume from scratch, as I described in the guide to the keyword cloud.

The one exception worth knowing: screening questions

Some systems, mostly large corporate platforms popular in the US market, do have a feature for automatic screening questions (knockout questions) in the application form. An example: “Are you authorized to work in Poland?” with “Yes” as the only accepted answer. A candidate who answers “No” can get automatically flagged as not matching, before a recruiter ever opens the CV.

Even so, this is still a business rule that a person configured in advance for one specific criterion, not the system reading and evaluating a CV’s content. This feature is rarely used on the Polish market, and where it does exist, it usually covers hard, formal conditions: work authorization, location, availability, not a subjective read on someone’s experience.

What this means for you as a candidate

If you’re sending applications and hearing nothing back, check these three things before you blame the algorithm: your CV may not contain the words a recruiter is searching for; the file format may make the text hard to extract; or, most simply, the recruiter already closed the role or is prioritizing other applications. The first two are fixable on your own. Check both in the guide to preparing a CV for ATS and in the guide to writing a CV and LinkedIn profile.

Element, and a decision that always stays with a human

At Element, we made a deliberate choice not to build a feature that rejects candidates automatically based on CV content. The system helps a recruiter find and organize candidates faster: search, tags, AI preselection that only suggests. A person is the one who moves a candidate to the next stage or ends the process. Read more about how Element treats an ATS as a tool, not a judge, on our ATS guide page.