Skip to main content
Productivity•9 min read

Your Applicant Tracking System Is Full of AI Resumes

October 5, 2026•By Ajan Kanagalingam

Google paused part of its open source bug bounty programme last week, saying it had seen a significant rise in automated submissions, the vast majority of which were not valid. A company with Google's review capacity closed an intake channel rather than try to read its way through. Any business that posted a job in the last six months has been running a smaller version of the same experiment.

What the effort was doing

Nobody designed effort as a filter, which is why losing it is disorienting. A candidate who rewrote their covering letter for your role and mirrored the language in your posting had demonstrated something real: they read the posting, they wanted this specific job, and they were willing to spend time on it. None of that was stated anywhere in the document. All of it was inferred from the fact that the document existed.

Keyword matching in an applicant tracking system worked for the same reason. Matching your terms required reading your posting. The match was a proxy for attention, and the proxy held for twenty years because producing it any other way was slower than doing it properly.

Paste a job posting into a model today and you get a tailored application that mirrors every phrase, in under two minutes, with no reading required. The proxy now measures access to a tool. Everyone has the tool.

What changed and what to do

Old signalWhy it stopped workingWhat to use instead
Tailored covering letterFree to produce at scaleOne question in their own words
Keyword matchMirrors your posting automaticallyVerifiable specifics, dates, outcomes
Clean, confident writingEvery application now has itA short sample under a constraint
Volume of applicantsSays nothing about interestCompletion rate on a real step
Stated achievementsEasy to generate plausiblyA reference who can be reached

Every replacement in the third column has one property in common. It requires the candidate to do something at a specific moment, in response to something you chose, that cannot be prepared in advance in bulk. Effort has to re-enter the process somewhere, and after the application is the practical place left for it.

Detection is the wrong lever

The instinct is to buy a detector. The tools are unreliable enough that acting on their output is a legal exposure rather than a screening improvement, and the false positives are not randomly distributed. They fall on people writing in a second language and on candidates using accessibility tools, which turns a screening step into a defensible-practices problem. The broader bias and compliance picture around automated screening is in AI resume screening and hiring risk.

There is also no version of this where detection wins. The generated document gets better every quarter and the detector does not. Spending on the arms race buys a filter with a shelf life, and the money is better spent on an assessment step that does not care how the application was drafted.

Say how you expect AI to be used

A stated expectation in the posting does more work than a prohibition. Something close to: use whatever tools you like to draft and polish, the claims need to be yours, and we will go through the specifics in conversation. That is honest, it is enforceable at the interview rather than at the inbox, and it stops filtering for candidates who disadvantage themselves by following rules.

It also sets the tone for a job where the same tools will be in use. A candidate who used AI well to apply has demonstrated something relevant, and treating that as cheating sends an odd signal about how the work will be done.

Where AI belongs on your side

Using a model to summarise four hundred applications is reasonable and limited. It can extract dates, confirm whether a stated requirement appears, cluster candidates by background and flag the applications that answered your screening question with substance. Treat that as sorting rather than deciding, and keep a record of what it filtered out so the filter can be audited.

The review discipline matters more here than in most places, because a model reading uniformly fluent applications has no surface cues to work from, which is the problem described in quality assurance when AI writes the first draft. Sample what it rejected. A hiring funnel is one of the few workflows where the cost of a false negative is invisible and permanent.

A funnel that works at volume

The shape that holds up has three steps and no long form. The posting asks one specific question that requires looking at your business, answered in a few sentences. Candidates who answer it with substance get a short task with a real constraint, a few hours at most, with AI use declared. The task output is the basis for a conversation about how they did it.

That funnel is more work to design and considerably less work to run than reading four hundred polished documents. It also assesses the thing you are hiring for, which a covering letter did only by accident. If the underlying question is whether to hire at all, the comparison is in AI versus hiring an admin assistant, and the knock-on effect on junior roles is in hiring seniors and skipping juniors.

Frequently Asked Questions

Why is my applicant tracking system suddenly getting so many applications?

Producing a tailored application used to cost a candidate an hour or more, and that cost did most of your filtering before anyone read anything. Generating a well-structured, keyword-matched application now takes a couple of minutes, so a candidate can apply to forty roles in the time one used to take. Volume rising while your role stayed the same is the expected result, not a sign that your posting suddenly became popular.

Can an applicant tracking system detect AI-written resumes?

Detection tools exist and they are not reliable enough to decide anything with. False positives fall hardest on candidates writing in a second language or using assistive tools, which turns a screening step into a discrimination risk. The more practical path is to stop treating polish as a signal, since it no longer separates candidates, and to move your assessment to things a generated document cannot supply.

What still carries signal in hiring?

Anything tied to a specific verifiable instance. A short description of one decision the candidate made and what happened next. A reference who can be reached. A work sample produced under a constraint you set, with the AI use declared openly. Specifics about your particular business that could only come from someone who looked at it. Generic competence claims and keyword coverage carry almost nothing now.

Should we ban AI from job applications?

A ban is unenforceable and it mostly filters for candidates who follow instructions against their own interest. Stating how you expect AI to be used works better: say that using it to draft and polish is fine, that the claims have to be the candidate’s own, and that you will discuss the specifics in conversation. Then build the process so that conversation is where the decision actually happens.

How do we handle hiring volume without hiring a recruiter?

Change the shape of the funnel rather than scaling the reading. One well-chosen screening question answered in the candidate’s own words filters more effectively than a longer form. A short asynchronous task with a real constraint filters more again. Both move effort back to the point of application, which is where a filter has to sit if free generation is going to be the norm.

Redesign the first filter

We rebuild hiring intake around signals that still carry information, and set up the AI-assisted sorting that keeps the volume manageable.

Related Articles

Productivity

Root Cause Analysis: Where AI Helps, Where It Guesses

October 4, 2026Read more →
Productivity

Grant Writing With AI: What It Does Well

September 24, 2026Read more →
Productivity

Standard Operating Procedures an AI Can Follow

September 15, 2026Read more →
AK
Ajan Kanagalingam
Founder & ChatGPT Consultant, ChatGPT.ca

Ajan leads the ChatGPT.ca team: 200+ custom GPT builds and automation projects for 50+ businesses across 20+ industries. Based in Markham, Ontario. PIPEDA-compliant solutions.

Stay ahead of AI in Canada

Weekly case studies, new tools, and ROI playbooks for Canadian SMEs. One email, zero spam.