1 in 15 React Profiles Would Fail a React.js Filter. Add the Alias

A hiring manager says he applied to his own open role under a fake name, using essentially his own CV, and was auto-rejected in six minutes because the screen wanted "React.js" and his resume said "React." If you write software, you've probably done the same math since: how many of your applications died over a period and two letters? The answer is fewer than the internet suggests. The fix is still cheap, and it doesn't involve lying.

What actually happened in the React.js auto-rejection story?

According to the post, a manager of a nine-person team had a senior associate role open since April. He tested the pipeline with his own resume, and a screen that required "React.js" word for word rejected him. Nobody has independently verified the story, so treat it as a claim, not a case study.

Here's how the story goes, per Fast Company's Oct. 20, 2026 writeup by Jude Cramer and follow-ups from inkl and MobiDevices:

• HR kept telling him the pipeline was thin and applicants were failing screening.
• He "made a new email, changed my name, tweaked the dates, and applied to my own req with essentially my own CV."
• He was "auto-rejected in six minutes."
• It took him a week to learn why: the screen was filtering out any resume that didn't contain "React.js" verbatim.

His summary line is the reason the post spread:

A sourcing caveat. Some outlets credit r/recruitinghell. Distractify traces the post to a LinkedIn user, "Ram T," who describes himself as an architect and consulting partner for AI-powered SAP solutions. Either way, nobody has confirmed it. Recruiters picked it up anyway because the failure mode is plausible. As @randomrecruiter (Juicebox) put it on X: "React vs. React.js shouldn't be the difference between an interview and getting automatically rejected."

Do ATS filters really auto-reject on exact keywords?

Rarely, but when they do, it's literal string matching. In Enhancv's survey of 25 US recruiters, only 2 (8%) said their ATS rejects applicants automatically for anything other than knockout questions.

An applicant tracking system (ATS) is the software that collects applications and lets recruiters sort, search and score them. Most ATS setups don't reject anyone. They rank and filter for a human. The two content-based rejectors in Enhancv's sample ran Bullhorn and BambooHR, configured to reject resumes below a match or experience threshold. HR Gazette describes what those thresholds look like:

• "match less than 75%"
• "fewer than 7 of 10 required skills"

That second rule is where a missing spelling hurts. Under a "7 of 10" rule, failing to match "React.js" doesn't cost you a few points. It costs you a whole required skill you actually have. If you were sitting at exactly 7, you're now at 6 and out.

Greenhouse works differently. Per Jobscan, it never auto-rejects. Its Real Talent AI scores how well you match the job, and that score sets the order recruiters work through the pile. So a missing alias doesn't kill your application there. It moves you further down a queue that may never reach you.

Recruiters also search by keyword themselves. In Jobscan's survey of 384 recruiters, 99.7% use filters in their ATS. A recruiter typing "React.js" into a search box is running the same literal match as an automated screen, just with a person at the keyboard.

The more likely culprit: knockout questions

A knockout question is a yes/no or numeric question on the application form that disqualifies you automatically based on your answer. Examples: work authorization, minimum years of experience, willingness to relocate. These ATS knockout filters fire on what you type into the form, not on anything parsed from your resume.

They're blunt. HR Gazette reports that on technical roles, a single visa-sponsorship question eliminates about 30% of applicants. If you got rejected minutes after applying, a knockout answer is almost certainly the cause, not a resume keyword.

How many React resumes would fail a "React.js" filter?

About 1 in 15. In Refolk's index of US professional profiles, 23,703 people list "React" but not "React.js," which is 6.8% of everyone who lists the library at all.

Here's how US profiles spell it in the skills field:

The "both" and "React only" rows are derived from the first three counts (326,066 + 34,299 - 349,769 = 10,596). They assume the skill field is an exact string. Platforms may partly standardize skill lists, so read this as a signal about spelling habits, not about anyone's ability.

Six point eight percent sounds small until you remember who's in it. These aren't unqualified applicants. Every one of them claims the exact skill the filter is looking for.

Why is the longer spelling the safer one?

Because partial matches only work in one direction. A filter searching for "React" inside a longer string also catches "React.js," but a filter searching for "React.js" never catches plain "React."

That makes the fix mechanical. Write the most specific form first and put the alias next to it:

• React.js (React) passes an exact "React.js" filter, an exact "React" filter, and any partial match.
• PostgreSQL (Postgres) covers both the formal and the everyday name.
• Kubernetes (K8s) catches a search for either the full name or the shorthand.

You aren't adding a skill. You're spelling one skill so that every common search string finds it. A human reader sees one item with a familiar nickname. A parser sees two tokens that both match.

Why can using the official name hurt you?

Because the official name is the minority spelling. The React team's own site, react.dev, calls it "React," yet in Refolk's index "React.js" outnumbers "React" about 9.5 to 1, so a filter built around the popular form drops the people who write it the maintainers' way.

Even the project hedges. Wikipedia lists it as "React (also known as React.js or ReactJS)," and its official X handle is @reactjs. Being correct is no defense against a string match. Whatever the canonical name is, the version on the job posting is the one to copy.

That's the real finding here. Listing both spellings is honest, takes no space, and almost nobody does it.

Why is inventing keywords the wrong fix?

Because a fake keyword gets you past the filter and then fails you in the interview. In a Greenhouse survey released Oct. 21, 2026, 40% of job seekers said they had added skills or keywords they don't have.

The broader numbers from that survey of 2,800+ job seekers in the US, UK, Ireland, Germany and Australia:

• 62% have tried tactics to get past automated screening.
• 54% have used AI to work out what the system is looking for.
• 40% have added skills or keywords they don't actually have.
• A third of those have added hidden text aimed at an AI reviewer.

Recruiters are watching. Greenhouse also reports that 91% of recruiters have run into candidate deception, and resume exaggeration (63%) is among the most common forms. Enhancv found 76% of recruiters prize natural keyword use and count keyword stuffing as a turn-off.

Greenhouse's Chief People Officer Sharawn Tipton summed up the candidate's side: "The application used to be a front door. Now, too often, it's a dead end." The response to a dead end isn't to fake a key. A correct alias gets you through the same door with nothing to defend afterward. "Kubernetes (K8s)" holds up when an interviewer asks about your cluster. A pasted "Kubernetes" you've never touched doesn't.

How do you match job description keywords without lying?

Copy the posting's exact spelling for skills you really have, keep your usual name in parentheses, and leave out anything you couldn't defend in an interview.

Step by step

1. Pull the skill nouns from the posting. Highlight every tool, language, platform and certification exactly as written, including punctuation and capitalization.
2. Cross off what you can't defend. If you couldn't answer a follow-up question about it, it stays off.
3. Swap in the posting's spelling. Where the posting says "React.js" and you wrote "React," change it to "React.js (React)."
4. Put matches in two places. List the term in your skills section and use it once in a real bullet ("Rebuilt the checkout flow in React.js"). Recruiters searching by hand see context. Parsers see the token.
5. Recheck every application. The next posting may say "ReactJS" or "React." Your spelling should follow each one.

Step 5 is where people quit, because redoing a resume for every posting is tedious. That's the exact work Refolk takes off you: paste the posting, and I rewrite your own resume to use its spelling for skills already in your history, without adding ones that aren't.

Build a short alias list for your stack

Keep a personal list of the skills you actually use, each with its formal name and common aliases. Here's a starting set from common stacks:

The rule from the React data applies to every row: lead with the longest, most specific form, because it contains the short one for partial-match purposes. Then let the posting decide which form goes first when they differ.

Marketers and ops people need this as much as engineers do. A posting that asks for "SFDC" and a resume that says "Salesforce" fail the same literal match as React.js and React.

Check fit before you rewrite

Spelling fixes close gaps that shouldn't exist. They don't close gaps that do. If a posting lists ten required skills and you honestly have five, no alias gets you to a "7 of 10" threshold. Refolk scores how well you actually fit a posting before you spend an evening on it, so you can tell a spelling problem from a skills problem.

FAQ

Should I write React or React.js on my resume?

Write "React.js (React)" unless the posting uses a different form, in which case lead with the posting's spelling. In Refolk's index, 6.8% of US React profiles list only "React" and would fail a verbatim "React.js" filter. Writing both closes that gap without adding anything untrue.

Do ATS systems actually auto-reject resumes for missing keywords?

Most don't. In Enhancv's survey, only 2 of 25 recruiters (8%) used content-based auto-rejection, on Bullhorn and BambooHR setups with thresholds like "fewer than 7 of 10 required skills." Greenhouse never auto-rejects but ranks applicants by match score. Knockout questions on the application form cause most instant rejections.

I was rejected minutes after applying. Was it my keywords?

Probably not. Check your form answers first: work authorization and sponsorship, minimum years of experience, and willingness to relocate. Knockout questions on those fire on what you type, and HR Gazette reports a single visa-sponsorship question removes about 30% of applicants for technical roles. If those answers were honest and correct, fix your skill spellings for next time and move on. With only 8% of recruiters in Enhancv's sample auto-rejecting on content, a mismatched spelling usually costs you rank or a missed recruiter search rather than an instant no.

Is listing skill aliases considered keyword stuffing?

No, as long as each alias names a skill you actually have and appears once. Keyword stuffing means repeating terms or listing tools you can't use, which 76% of recruiters in Enhancv's research said they dislike. "PostgreSQL (Postgres)" is one skill with its common nickname, and any reader will take it that way.