Software Rarely Rejects a Resume by Itself
Most applicant tracking systems do not throw out a resume because of how it reads; the automatic rejections come from rules employers attach to application questions. A missed work authorization answer or a missing license can end an application at submission. Weak keywords usually just lower your place in a ranked list that a recruiter reads.
Where software does make screening calls, some laws now watch it. New York City requires a bias audit within 1 year before an employer uses an automated screening tool, and fines run up to $1,500 per later violation. So the useful question is not whether a robot read your resume, but which kind of screen you hit.
Parsing Comes Before Any Decision
An applicant tracking system first turns your file into fields. It pulls out your name, contact details, job titles, dates, and skills, then stores them so recruiters can search them.
Parsing failures are real, but they rarely produce a rejection notice. A two-column layout or text inside a header can scramble your work history. The result is a profile that looks thin when a recruiter opens it, not an automatic decline.
That distinction matters for what you fix. A parsing problem is fully in your hands, and a plain single-column document solves most of it. Our comparison of ATS resume checkers and AI resume builders covers which tool catches which parsing fault.
Knockout Questions Do the Real Auto-Rejecting
- ● Rules sit on application answers
- ● Work authorization and licenses are typical
- ● Some fire the moment you submit
The automatic rejections people fear do exist, but they live in the application form. Employers add screening questions and attach rules to the answers.
Greenhouse gives a concrete example in its own guidance on handling applicant surges. A driving role asks whether the applicant holds a Class A commercial license, and the system automatically rejects anyone who answers no. The same article suggests auto-tagging applicants by location so recruiters can filter nearby candidates first.
Ashby documents its version in more detail. Its auto-reject rules run only at the moment a candidate submits, and they check answers to application form questions. Conditions include whether a field is empty, equals a value, or contains certain text, combined with and, or, and not.
Two details from the Ashby docs change how you should read a rejection. The system applies rules in order, and once one condition rejects you it skips the rest. Employers can also delay the rejection email by a chosen number of business days, so a slow reply is not proof that a person read your file.
Every Way an Application Gets Screened Out
- ● Rules reject, rankings sort
- ● Filters hide, humans decide
- ● Only parsing is fully in your hands
Each screen has a different owner and a different fix. The table maps the common ones from the most automatic to the most human.
| Screening mechanism | Who sets it | Can your resume fix it | What to do instead |
|---|---|---|---|
| Knockout or screening question rule | Recruiter or hiring manager | No, it reads your answers | Answer accurately and skip roles you cannot qualify for |
| Required field left empty | Application form designer | No | Fill every required field, even if it repeats your resume |
| Recruiter search and filters | Recruiter, per search | Partly, through clear titles and skills | Use the exact job title and core skill words from the posting |
| Ranking or AI match score | Vendor model, tuned by employer | Partly | Tailor the summary and recent roles to the posting |
| Parsing errors | Your file format | Yes, fully | Use a single column with standard headings |
| Human review of the shortlist | Recruiter or hiring manager | Yes, through content | Lead with outcomes, not duties |
Only one row is fully in your control through the document itself. Two rows are not about the resume at all, which is why rewriting it often changes nothing.
Ranking and AI Matching Sort Rather Than Delete
Many systems now offer match scores or AI-ranked candidate lists. These features compare your profile with the job description and put stronger matches at the top.
A low score rarely means rejection on its own. It means a recruiter working from the top of a long list may never reach yours. In practice that feels the same as a rejection, which is where the folklore comes from.
Recruiters also run their own searches. If they filter for a certification or a job title you phrased differently, your profile drops out of that view without any rule firing. Plain, posting-matched wording for titles and core skills is the cheapest way to stay visible.
Match scanners such as Jobscan estimate how closely your wording tracks a posting. The Jobscan vs Teal comparison explains where a scanner helps and where a broader job-search workspace does more.
What New York City Requires From Automated Screening
New York City is the clearest example of a law aimed at automated screening. Local Law 144 of 2021 covers automated employment decision tools, and the city began enforcing it on July 5, 2023.
The city defines these tools as computer-based systems using machine learning, statistics, data analytics, or AI. They count when they substantially assist or replace a discretionary hiring or promotion decision. The FAQ from the Department of Consumer and Worker Protection says screening counts as an employment decision, not only the final offer.
Three requirements follow from the DCWP FAQ. Employers can rely on a bias audit for 1 year, so the tool must have been audited within the past year. A summary of the audit results must be public, and city residents must get notice 10 business days before the tool is used.
The notice has to say which qualifications or characteristics the tool will assess. It must also explain how to request a reasonable accommodation under other laws. For applicants, employers may post it on the careers section of their website instead.
Penalties are modest but they stack. The law text on the NYC Council site sets a civil penalty of up to $500 for a first violation. Each later violation costs between $500 and $1,500, and each day a tool is used unlawfully counts separately.
The law has limits. It does not cover scanning a resume bank or outreach to people who have not applied for a specific job. Complaints go to 311 or the DCWP website, and DCWP refers discrimination claims to the NYC Commission on Human Rights.
Where the 75 Percent Rejection Claim Falls Apart
Career advice often repeats that ATS software rejects about 75% of resumes before a human sees them. People share the claim widely, but they rarely cite a verifiable study behind it.
It also does not match how the documented features work. The vendor rules above reject on answers to questions, not on resume design. Ranking and filtering hide profiles from a particular search, and a recruiter can still open them later.
None of this means the system is harmless. Sitting far down a long ranked list is a real disadvantage. The point is that the fix for low ranking is relevance, while the fix for a knockout rule is answering honestly or choosing different roles.
What to Do Before You Click Submit
Read the screening questions before you start writing. If the posting requires a license, clearance, or onsite schedule you cannot meet, a resume rewrite will not get you past that rule.
Answer every question exactly as asked. Any question can carry a rule, including salary, experience, and relocation, and a vague or blank answer can trigger an automatic decline.
Keep the document simple enough to parse. One column, standard headings such as Experience and Education, and text that is not inside images or headers is enough. A list of AI resume builders that output ATS-friendly layouts can save time if your current file leans on heavy design.
Then tailor for ranking. Mirror the job title where it honestly fits, and name the two or three core skills from the posting in your most recent role.
Reading a Screening Form Like a Recruiter Would
Picture a posting for an operations coordinator that asks four questions before the upload button. Do you have work authorization, can you work onsite three days a week, what salary do you expect, and how many years of scheduling experience do you have?
Each of those questions can carry a rule. The first two are classic knockouts, because the role cannot work without them. The salary and experience answers may feed a rule, a tag, or nothing at all, and you cannot see which.
The safe reading is to treat every answer as if a rule sits behind it. If the posting asks for a number, give a number rather than writing “flexible” in a text field. Ashby lets employers match text with conditions such as “contains” or “starts with”, so an unexpected format can fail a rule a person would have waved through.
Honesty still beats gaming. A rule that rejects you on a true answer saves you an interview for a role you could not take. A rule you pass on a stretched answer simply moves the rejection to a later, more awkward stage.
Which Fix Fits Your Rejection Pattern
- ● Instant rejections point at answers
- ● Silence points at ranking
- ● Interviews without offers point elsewhere
Your rejection timing and pattern tell you which screen you are hitting. Match your situation to the most likely cause before changing anything.
- Situation: rejected within minutes of applying. A knockout rule almost certainly fired on one of your answers. Recheck work authorization, location, license, and experience questions rather than your resume.
- Situation: no reply from dozens of applications. You are probably ranking low or falling outside recruiter filters. Tailor titles and skills to each posting, and check that your file parses cleanly.
- Situation: rejections arriving days later in a uniform batch. This could be human review or a delayed automated email. Ashby lets employers delay rejection emails by business days, so timing alone cannot settle it.
- Situation: interviews but no offers. The tracking system is no longer the issue. Interview preparation and references matter far more at this stage than any resume tool.
- Situation: applying to New York City roles screened by AI. Look for an AEDT notice on the posting or careers page. If none appears and you suspect automated screening, the DCWP complaint route through 311 is available.
Reading Rejections as Data, Not a Verdict
A rejection from an applicant tracking system is rarely a judgment of your resume by a machine. More often it is a rule you could have read in advance, or a ranking you can improve.
Track when each rejection arrives and what the application asked. After ten or fifteen applications, the pattern usually points at one cause. Fixing that cause beats rewriting the whole document again.
If your resume itself needs work, start with parsing and relevance. If your answers are the problem, the fix takes minutes and costs nothing.
FAQ
Can an ATS reject my resume without a human seeing it?
Usually not on the strength of the resume alone. The automatic rejections that do exist mostly come from rules a recruiter attaches to application questions, such as work authorization or a required license. Keyword gaps and formatting tend to push you down a ranked list rather than delete the application.
What is a knockout question on a job application?
A knockout question is a screening question with a required answer. In systems such as Greenhouse and Ashby, the employer can set a rule that rejects any application whose answer misses that requirement, often at the moment you submit.
How can I tell if I was rejected automatically?
Speed is a clue but not proof. An instant rejection usually means a rule fired on one of your answers, while a rejection weeks later suggests a person reviewed the pile. Ashby lets employers delay the rejection email by a set number of business days, so timing can be misleading.
Is it true that 75% of resumes are rejected by ATS?
The figure circulates widely in career advice, but no verifiable study behind it is usually cited. Treat it as folklore. The rejections you can actually trace come from screening questions, filters, and human review of ranked lists.
Do I have any rights if AI screened me out?
In New York City, an employer using an automated employment decision tool must have had a bias audit done within the past year and must notify candidates who live in the city 10 business days before using it. You can file a complaint through 311 or the DCWP website if you think that did not happen.
Sources
- NYC DCWP: Automated Employment Decision Tools — checked 2026-10-08
- NYC DCWP: Automated Employment Decision Tools FAQ (PDF) — checked 2026-10-08
- NYC Council: Int 1894-2020 (Local Law 144 of 2021) — checked 2026-10-08
- Ashby Docs: Auto-reject applications — checked 2026-10-08
- Greenhouse: 5 tactics to help you manage a surge in job applicants — checked 2026-10-08
Some links may be affiliate links. We may earn a commission at no extra cost to you.
How this article was made: it was drafted with AI assistance from the official sources listed above, and its figures were checked against those pages on the dates shown. It is not based on personal hands-on testing.
Comments
Post a Comment