Not hearing back?
It is a queue, not a filter.

Almost never on its own. Jobscan, the largest vendor in the ATS-optimization category, writes that "contrary to popular belief, an ATS rarely 'rejects' a candidate automatically". Enhancv interviewed 25 US recruiters in late 2025 and found 2 of them, 8%, had configured any content-based automatic rejection. The other 92% had not.

The common exception is a knockout question a recruiter set up deliberately, such as work authorization or a required licence. You can see those, because you answer them yourself in the form.

A 2012 sales pitch. A company called Preptel used the figure to sell resume-optimization software and was out of business by 2013. No methodology was ever published with it.

The number outlived the company because it is useful to anyone selling a fix for it. It now circulates with no source attached at all, which is part of why it is so hard to argue with.

Usually because of a queue, not a filter. Greenhouse's March 2026 benchmark puts applications per open role at 244, up 111% since 2022, while recruiting teams shrank by 55%. A recruiter works from the top of a long list until there are enough candidates to move forward. The applications below that point were not rejected. They were not reached.

The second cause is that the posting was already gone. 16% to 29% of postings leave the employer's own board within two weeks, and job boards keep showing them.

Most job postings are still up a month later. Rechecked daily on employers' own career pages by JobShifu's crawl, 83% to 92% were still listed after a week, 71% to 84% after two weeks, and 56% to 69% four weeks after they first appeared. The full measurement and method.

The date shown on a job board is a weaker signal than the employer's own page, because boards keep listings up after the employer has taken them down.

Check the employer's own careers page rather than the board you found the posting on. Boards keep listings up after the employer has taken them down, and a posting that is reposted every two weeks reads as two days old for months.

JobShifu's free posting checker takes the employer's posting URL and reports when the crawl first saw it, whether it is still listed there, and whether the same role was reposted.

Yes, and this is the part of the worry that is genuinely right. Parsers mangle multi-column layouts, text boxes, tables, headers and footers, and graphics.

The consequence is not rejection, it is misfiling: your job title lands in the wrong field, or a whole role comes through as a jumble, so a recruiter searching their database does not find you. The fix is boring and free. A single-column file with real text, checked by looking at the plain text it becomes.

Which requirements in this posting your experience actually covers and which it does not. Whether the posting's terms appear in your bullets, where they are demonstrated, rather than only in a skills line, where they are merely listed. And what the plain text of your file looks like once the formatting is stripped.

All three are about the job in front of you. None of them is a number out of a hundred.

Sometimes, but the volume is itself the clue that it usually is not. Applications per open role reached 244 while recruiting teams shrank by 55%, so a recruiter works down a long list until enough candidates are in play and then stops. Hundreds of applications is hundreds of long lists, most of which nobody reached the end of.

What the resume decides is whether you are worth stopping at when someone does reach you, and that is a per-posting question rather than a property of the file. The three checks above are how to answer it for one job. Sending the same file into more queues is not.

There is no standard wait, but there is a useful boundary. As of the September 2026 measurement by JobShifu's own crawl, 16% to 29% of postings were gone from the employer's own board within two weeks of first being seen. The full measurement.

So silence in the first two weeks usually means the role is still live and the list has not reached you. Silence past two weeks on a posting that is still up is the same queue, not a verdict on your application. Silence on a posting that has come down is not a verdict either, because a posting comes down for reasons that have nothing to do with you.

There is no such score inside these systems. An applicant tracking system stores applications and lets a recruiter search them. It does not compute a rating of your resume and show it to anybody, so there is no number for a recruiter to have an opinion about.

Scores out of a hundred come from third-party checkers, and each one defines its own. The most a number like that can establish is that a parser read your file, which is worth knowing on its own. What is worth checking instead is which of this posting's requirements your experience covers, whether its terms are demonstrated or merely listed, and what your file looks like as plain text.

An applicant tracking system is a database with a search box over it. It receives applications, parses each file into fields such as employer, title, dates and skills, and lets a recruiter search and sort what it stored.

The parser is the only part doing anything like interpretation, and its work is reading a document's layout into those fields rather than forming a view about a candidate. That is why a mangled layout costs you something real, and why a score does not describe anything the system produces.

It does not run a detector. The file is parsed into fields and stored, and nothing on that path classifies text as generated.

The person reading it is a different matter, and generic writing is noticeable without any tool: interchangeable phrasing, achievements with no numbers attached, and the same handful of adjectives everyone else used. The answer is not disguise. It is a page that could only be yours, which means your own projects, your own figures and the decisions you actually made. Demonstrated rather than merely listed is the check that gets you there.