If you keep getting rejected minutes after applying, you've probably been told two opposite things: that the ATS ate your resume, or that ATS auto-rejection is a myth. In a story that was trending on X by October 21, 2026, a team lead applied to his own job posting under a fake name and got rejected in six minutes because his resume said "React" and the filter wanted "React.js." Both of those claims turn out to be half right, and the fix is a formatting habit you can start using on your next application.
What happened with the React.js rejection?
A team lead says he was automatically rejected from his own team's opening within six minutes, because a required-skill filter matched "React.js" and his resume said "React." He posted it on r/recruitinghell, dev.ua wrote it up, and by October 21, 2026 it was trending on X.
Here's what he described:
- He runs a nine-person team. The opening was for a senior associate and had been unfilled since April.
- HR kept telling him there were no suitable candidates.
- He set up a new email address, used a made-up name, shifted the dates a little, and sent what was basically his own CV. He had written the job description himself.
- He got an automatic rejection six minutes later.
In his words: "It took me a week to figure out why. The filter was set to require the candidate to have "React.js," and my resume had "React.""
Treat this as one person's unverified account. The coverage says he "claimed" it happened. Still, the way he describes it lines up with how the major systems let recruiters configure screening. The Random Recruiter (@randomrecruiter) summed up the reaction on X: "React vs. React.js shouldn't be the difference between an interview and getting automatically rejected."
Does the ATS reject you on its own, or does a recruiter's rule?
Usually the software doesn't decide anything by itself. A recruiter sets up a rule, and the rule runs blindly on every application. That's why the "ATS auto-rejection is a myth" camp and the "I got auto-rejected instantly" camp can both be right.
Some terms first:
- An applicant tracking system (ATS) is the software employers use to collect, store, and sort job applications (Greenhouse, Workday, iCIMS, Bullhorn, BambooHR, Ashby).
- A knockout question is a screening question where one particular answer rejects the applicant automatically.
- A required-keyword rule is a filter a recruiter types in by hand, telling the system to reject or bury any resume that doesn't contain a specific string.
What the "myth" survey measured
In Enhancv's survey, 92% of recruiters said their ATS doesn't auto-reject candidates for formatting, content, or design. That's the number behind most "the ATS isn't rejecting you" posts. It has limits:
- Only 25 recruiters took part.
- 2 of the 25 (8%) did have content-based or match-score rejection turned on. They were using Bullhorn and BambooHR.
- The headline is about formatting and content. It doesn't cover knockout questions, and separate 2026 data puts knockout-question use at 84% of recruiters.
- In the same Enhancv write-up, 44% of recruiters said they use the ATS's AI to rank candidates. Ranking decides which resumes a person ever opens.
Alexander Troutner's Substack rebuttal, "Yes, You ARE Getting Auto-Rejected," makes that last point. A resume ranked near the bottom of the pile never gets read, so it might as well have been rejected.
How the rules get set up
Systems handle this differently:
- Greenhouse lets a recruiter attach an auto-reject rule to any yes/no, single-select, or multi-select question, and the rule "fires within seconds of submission."
- Ashby says it does not auto-reject.
- Workday turns your resume into editable skill tags during the apply flow. If the parser misses a skill, that tag stays missing unless you add it.
- iCIMS skill matching depends on how each customer configures it, so plan for plain-text keyword matching.
Better parsers know that "React.js" and "ReactJS" are the same framework and that "Postgres" means PostgreSQL. A recruiter's hand-typed required keyword skips that step entirely. If someone types "React.js" into a required field, the software looks for exactly those characters. Jobscan's data shows why this matters: 76.4% of recruiters search and rank candidates by skills pulled straight from the job description. So for an ATS exact keyword match, the posting's wording is effectively the spec.
Why getting rejected minutes after applying points to a rule
A rejection that arrives within minutes almost always means a rule fired. A person working through a queue doesn't open your application and turn it down six minutes after you submit, especially for a role that has sat open since April.
Here's a rough way to read the timing:
| When the rejection arrives | Most likely cause | What to check |
|---|---|---|
| Seconds to minutes | Knockout question or required-keyword rule | Your answers to screening questions, exact skill strings |
| Days later | AI ranking, a person's review, or a timed email | How closely your skills section mirrors the posting |
There's one catch. Some companies hold rejection emails and send them on a timer, so a slow rejection doesn't prove a human read your resume. A fast one is much stronger evidence. If you're getting auto-rejected instantly on roles you're clearly qualified for, look at your knockout answers and your skill spellings before you rewrite your whole history.
React vs React.js: 327,223 resumes against 34,378
In Refolk's index of US professional profiles, "React.js" outnumbers "React" by about 9.5 to 1, and only about 3% of people list both. So a filter set to either spelling throws out a large group of real practitioners.
| Skill string on profile | US profiles |
|---|---|
| "React.js" | 327,223 |
| "React" | 34,378 |
| Either spelling | 350,957 |
| Both spellings (derived) | ~10,644 |
| React.js to React ratio (derived) | ~9.5 : 1 |
| Share listing both (derived) | ~3% |
In Refolk's index, roughly 97% of React developers pick a single spelling and rely on the filter to agree with them.
Why the split exists
The more common spelling isn't even the official one. The framework's own site, react.dev, calls it "React." Part of the gap is probably Refolk's own skill list steering people toward "React.js," which may inflate that count. That's the point, though. Each system has a default spelling, and people take whatever their platform suggested. Then a recruiter types whatever their own habit is.
A rule that requires "React.js" drops everyone who wrote only "React," and that's how the team lead got caught. A rule that requires "React" would drop far more. Guessing the "right" spelling doesn't solve this, because nobody agrees on one. Writing both does.
There is no right spelling to guess. There is only the posting's spelling, with yours next to it.
Why the filter makes the pipeline look empty
Exact-match rules hide their own mistakes. Candidates rejected by a string mismatch never show up in any pipeline report, so HR sees a thin funnel and decides the market has no talent. That's how a senior associate role can sit open from April while qualified people keep getting rejected.
Gaurav Chatterjee of Rakuten Mobile made the same point on LinkedIn and gave the fix on the employer side: "Map aliases so React, ReactJS and React.js count as one skill." Most recruiters haven't done that, and you can't make them. So from your side the cost looks like this: you send strong applications, get form rejections back, assume you're the problem, and never find out that a one-word spelling difference decided them.
How to list skills on a resume for ATS without guessing
Copy the posting's spelling exactly, then put the common variant in parentheses next to it, like "React (React.js)." That covers a literal required-keyword rule, a parser that normalizes synonyms, and a human reader, all in one line.
The routine for each application
- Pull every named tool from the posting. Copy the exact strings, punctuation included: "React.js," "PostgreSQL," "Power BI," "GA4."
- Lead with their spelling. If the posting says "React.js," your skills line starts with "React.js," even if you usually write "React."
- Add the variant in parentheses. "React.js (React)." One alias per skill is enough.
- Use the posting's spelling once more in a bullet. For example, "Rebuilt the checkout flow in React.js," followed by your actual result. That ties the keyword to evidence.
- Check the parsed result. On Workday, open the skill tags after the parser fills them and add anything it missed. A tag it skipped stays missing.
- Answer knockout questions literally. If you've used the tool, say yes. Don't let a spelling difference make you second-guess an honest answer.
Doing this for every posting gets tedious. It's the part Refolk does for you: paste the posting, and Refolk rewrites your resume from your own history using that posting's spelling for every tool you actually know.
Common aliases by field
I only have counts for React. I didn't find data on how ATS filters handle the others, so take these as common variant pairs worth covering, not measured failure rates.
| Field | Write it like this | Why |
|---|---|---|
| Engineering | React.js (React) | ~9.5 : 1 split in Refolk's index |
| Engineering | PostgreSQL (Postgres) | Parsers may normalize, typed rules won't |
| Analytics | Power BI (PowerBI) | Spacing differences break literal matches |
| Marketing | GA4 (Google Analytics 4) | Acronym vs full product name |
| Design | Match the posting's tool names exactly | Same logic applies to any named product |
If a posting abbreviates, spell it out in parentheses. If it spells it out, put the abbreviation in parentheses.
Is listing both spellings keyword stuffing?
No. Keyword stuffing means claiming skills you don't have. Writing "PostgreSQL (Postgres)" makes one true claim in two strings, and it's no different from writing a company's legal name next to its brand name.
The line is simple:
- Aliasing (fine): "React.js (React)" when you've shipped React. "GA4 (Google Analytics 4)" when you've run GA4 properties.
- Stuffing (not fine): Adding a framework because the posting mentions it and you've read the docs once. Pasting the posting's whole requirements list into white text.
- Gray area (skip it): Listing every possible variant, like "React, React.js, ReactJS, React JS." One alias covers it, and four looks like you're gaming the system to a human reader.
The harder question is whether a missing keyword is a spelling problem or a real skills gap. If the posting names a tool you've never used, putting it in parentheses next to a different tool you have used is a lie, not an alias. Refolk scores how well you actually fit each posting, which helps you separate "I spelled it differently" from "I don't have this," and decide whether to tailor the application or skip it.
FAQ
Should I write React or React.js on my resume?
Write whatever the posting uses first, and put the other in parentheses: "React.js (React)" or "React (React.js)." In Refolk's index of US profiles, 327,223 list "React.js" and 34,378 list "React," with only about 3% listing both. Any filter set to one spelling misses many real React developers, so covering both is the only safe choice.
Am I being auto-rejected instantly by the ATS itself?
Probably by a rule a recruiter set up, not by the software deciding on its own. In Enhancv's 25-recruiter survey, 92% said their ATS doesn't auto-reject on formatting or content, but that excludes knockout questions, which 84% of recruiters use, and Greenhouse auto-reject rules fire within seconds of submission. A rejection within minutes is the clearest sign a rule fired.
Don't modern parsers already know React and React.js are the same?
The better ones do, and they also map "Postgres" to PostgreSQL. A recruiter's hand-typed required keyword skips that matching, though, and iCIMS matching depends on each customer's setup. On Workday, check the parsed skill tags before you submit, because a tag the parser missed stays missing.
How many skill variants should I list?
One alias per skill, in parentheses after the posting's spelling. That covers the literal rule and the human reader. More than that starts to look like gaming the filter, and anything you haven't actually used doesn't belong on the resume in any spelling.