Can an ATS Actually Detect AI Writing?
The short answer
Jobbris is an AI resume-tailoring tool that turns your documented experience into a truthful, job-specific resume in about two minutes. Short answer: no. The systems employers run do not try to work out who wrote your resume. They parse the file, match it to the posting and rank the pile, then a person reads the top.
Can an ATS actually detect AI writing?
Mostly no. No major platform ships an authorship detector. Workday, Greenhouse, iCIMS, SAP SuccessFactors, Lever and Oracle Taleo all build AI for matching and screening, not for guessing who typed your bullets. What gets called detection is usually a person reading a document that looks machine-made, or a third-party style tool applied by hand.
Vendor documentation is blunt about this. Jobscan's 2026 vendor map states that no major platform detects AI-generated resumes, and an administrator who has run several of those systems wrote in r/resumes that none of them detect or penalize content because AI created it. The viral claim that Workday shipped a writing detector has no vendor release behind it.
If it cannot detect AI writing, what does it do with your application?
It scores the match. The parser reads your file, pulls out titles, dates, skills and outcomes, then an AI layer compares that against the posting and puts you in a tier before any human looks. Jobscan puts 79.3% of Fortune 500 applications through a platform with active AI ranking.
That is a bigger change than it sounds. Matching used to mean keywords. Now the ranking layer reads the meaning of your work history and sorts you into a tier before a recruiter opens the file, with another roughly 16% of the market on lighter filtering and Greenhouse launching AI-assisted matching in February 2026. The parser also breaks on multi-column layouts, tables, headers and scanned PDFs before any scoring happens.
Why has no vendor built an AI writing detector?
Because it cannot be made accurate or safe. OpenAI shut down its own text classifier at 26% accuracy. The best-known academic result found detectors flagged 61.3% of human-written essays by non-native English speakers as machine-made. Add the EU AI Act, NYC Local Law 144 and EEOC guidance on algorithmic hiring, and the liability outweighs the feature.
Accuracy is the wall. A tool that is wrong more often than right on ordinary writing is not a filter, it is a random number generator with legal exposure attached. The best-known peer-reviewed result is a Stanford-led study of GPT detectors, and the false positives it measured landed hardest on non-native English writers. Meanwhile Oracle invites candidates to draft cover letters with the AI built into its own product, and Greenhouse's published position is that AI assistance on a resume is acceptable.
What can an employer actually detect?
Identity and behavior, not prose. The fraud layer sold to hiring teams checks device, network, location and whether the person on the video call is the same one who applied. Sardine's job application fraud product, launched in May 2026, screened 3,000+ high-risk applications in one month and found only 52 phone-country or address mismatches.
Sardine's job application fraud product plugs into applicant tracking systems over webhooks and scores each application as it is submitted, so the check runs inside the same workflow with no extra step for the candidate. In its own pipeline data the dominant signals were device and network, not word choice.
If the software cannot catch AI writing, why do recruiters reject so many resumes for it?
Because the detector is a person with a pile and a threshold. In one early October thread, a recruiter said they read every CV by hand and rejected all AI-generated garbage, calling it 30 to 50 percent of applications. Another said they rejected over 50 applicants in a single shortlisting session.
Two people in the same week gave opposite answers, and both were describing their own desk. An administrator working inside the software said no system penalizes AI content. A recruiter reading hundreds of documents said they manually rejected up to half of them for exactly that reason. The tell those readers describe is not clever prose. It is sameness, and the reader who distrusts your document reads it faster, not harder.
Why was I accused of using AI when I wrote my resume myself?
Usually because of the document, not the words. On a 132-point thread where an applicant was accused after a rejection, the accusation turned out to be about the look: the standard AI-produced Word layout and font combination. Plain formatting reads as human because it is what humans make.
One reader asked whether the complaint was simply that the resume used the same font as AI output, and the reply was that it was the whole combination, since a document generated as a Word file tends to arrive in a formal font and a layout nobody chose on purpose. If you were flagged, inspect the file first: fonts, columns, spacing, headers, whether it is a text PDF.
How do you use AI on a resume without the file reading as generic?
Change what you choose to show, not what happened. Keep titles, employers, dates and numbers identical everywhere. Let AI pull the relevant achievements forward and borrow the posting's vocabulary, then strip the adjectives and read every line out loud. If you cannot defend a bullet live, cut it.
Two readers look at your application and want different things. The ranking layer wants semantic overlap with the posting. The person wants evidence that a specific human with a specific history is on the other end. Wording can serve both, invention serves neither. Keep one column, standard fonts, no tables and a text-based PDF. If assembling that version eats your evenings, Jobbris returns a truthful, job-specific resume in about two minutes from a job link you send by WhatsApp.
Frequently asked questions
Can a third-party AI detector flag a resume I wrote myself?
Yes, and it happens to careful writers. Detectors are unreliable on professional writing, and the Stanford finding put false positives on non-native English writing at 61.3 percent. Some recruiters still run tools like GPTZero by hand, so the practical answer is to keep the document plain and be ready to talk through every claim.
Why do employers reject AI-written resumes when they screen with AI themselves?
Because the two systems do opposite jobs. Screening AI ranks your application against the posting, which the employer bought to save time on volume. A recruiter reading a pile rejects generic writing because it tells them nothing about you. The same tools they defend on their side read as cheating on yours, and that asymmetry is real.
What share of applications are AI-written now?
Hard to know, and quoted numbers are soft. Gartner's mid-2025 measure put AI use in applications at 29.3 percent of job seekers, up from 17.3 percent the year before. A recruiter in October 2026 estimated 30 to 50 percent of applications were machine-written. Both come from interested parties, so treat them as direction.
Tanul Tewari
Founder, Jobbris
Building Jobbris to fix the part of the job search nobody talks about: the hours of tailoring and the silence that follows.