AI resume screening: parse first, then a rank you cannot game

Casey works inbound claims intake at a regional auto insurer: headset, Guidewire ClaimCenter, 40–50 first notices of loss a shift, recorded-statement flags before the file goes to an adjuster. The national carrier posted “Claims Intake Team Lead” on a Workday career site that advertises “AI-powered matching.” An insurtech wants a similar lead in Greenhouse and writes blog posts about “AI screening.” A hospital patient-access req sits in iCIMS. None of those pages mean a model read Casey’s personality. They mean two stacked jobs, and the first job is still a database.

Layer 1 is the ATS you already know from how to pass ATS. Workday, Greenhouse, Taleo, and iCIMS extract text, hang it on fields — name, email, phone, employer, title, dates, education — and let a recruiter or sourcer search. If Casey’s Canva file parks the Gmail in a sidebar, Layer 1 stores an empty email. Search for “Guidewire” or “FNOL” returns nothing. That silence is a parse fail. It is not an AI judgment. A pretty PDF that never stores a phone has already failed before any model runs.

Layer 2 is optional and later. Some Workday tenants turn on skills inference or a matching widget. Some Greenhouse orgs generate a short summary for the recruiter. A few vendors sell a rank. Those features read whatever Layer 1 stored, or they read the text layer of the PDF. They do not invent two years of Guidewire. They do not override a knockout that says Casey cannot work Saturdays. They summarize and sort. If the extract is empty, the summary is empty. If the bullets are adjective soup, the summary is adjective soup. Writing for “the AI” without a selectable email is theatre.

Recruiters are not waiting for a magic score. They type “Guidewire” and “intake” and sort by date. You either appear with an email they can click, or you do not. That is why this page and ATS resume agree: extractable first, then relevant, then meaningful. A 94 on a random “AI resume score” that never saw this carrier’s Workday knockouts is entertainment, not a pass. For a rehearsal of Layer 1, use the ATS checker and the write-up on the ATS resume checker — both find parse and noun gaps, not a hiring decision.

If Casey’s store-brand intake tool is not named Guidewire, write both: the badge name and the posting’s noun, in one bullet, so search and honesty both survive. Layer 2 will quote that sentence if a tenant summarizes. It will not rescue a footer that repeats the whole qualifications block twelve times. For how to place nouns without lying, use resume keywords and tailor the resume to the job. The rest of this page is how the two layers fail in the wild, vendor by vendor, and what to type before Apply.

What “the AI rejected me” usually was

• Contact or dates never extracted — header, image, or two-column shuffle. Layer 2 had nothing to rank.
• Required knockout or questionnaire blank or contradicted the PDF.
• Recruiter searched a noun that exists only as an icon or a skill bar.
• You never submitted: account created, resume uploaded, Continue never clicked.

Workday wants First Name, Email, Phone, repeating Experience rows, Education, and Skills tags. Put those tokens in the body under Work Experience, Education, Skills. The optional “AI” layer in some tenants infers skills from the same text or shows a match widget to a coordinator. It cannot fill a blank email. Confirm is still a human job: read every autofilled field. Details for widgets live in Workday resume format. The upload click path is how to upload a resume to Workday. If the tenant shows a skills cloud Casey never claimed, delete the tag before Submit — Layer 2 guessed; Casey still owns the form.

Greenhouse is PDF-forward for hiring managers and search-forward for sourcers. The file has to be selectable when a human opens it, and the text has to be indexed when someone types “FNOL.” Some orgs turn on a recruiter summary or a score. That summary quotes sentences. “Hard worker, team player, Microsoft Office” becomes a useless paragraph. “Logged 40–50 FNOL calls per shift in Guidewire and flagged recorded-statement files before adjuster handoff” becomes a usable one. Same single-column file as Workday. Broader parse rules: ATS resume. For how Greenhouse stores the preview, Greenhouse resume if that sister page is in your reading list; the rule here is still select-all.

Taleo’s older extract is worse with tables: it may read the right column first and store a graduation year as an employer. It often makes you retype history. The attachment still has to be searchable when a recruiter opens it. Oracle marketing may say “AI.” The knockout on page one — license, weekends, years — still fires before any model. iCIMS mixes parse with long forms; years of claims intake and Saturday OT must match a sentence on the resume. A coordinator who sees “0–1 years” in the dropdown and “three years FNOL” on the PDF closes the file without asking a model. Greenhouse Easy Apply from a board is not the carrier’s tenant. Use the career URL in the posting.

File: .docx or selectable PDF. Select-all in Preview. If the intake dates do not highlight, Taleo will not tokenize them and a Layer 2 summary will not mention the role. Fonts: Calibri, Arial, Georgia, or Enhance CV’s system font. No skill bars. No photo in a US insurance or hospital pipeline. Dates as month and year beside the job: “Jun 2023 – Present.” “2023–now” in a header text box is how Present never becomes a checkbox. For visual rules, resume format. For PDF vs Word extract behavior, resume PDF vs Word. Two target families mean two files. LinkedIn can mention claims and patient access. The attachment to one requisition cannot.

There is no separate “AI resume” personality. There is a readable file plus a finished form. Cover letters are often optional in these portals; do not spend the hour on a letter while the phone number is still an icon. If you send one, write the cover letter for this carrier, not a generic insurance paragraph. Desk filter while Casey edits: will the tenant store it, and will a human — or a summary — understand it at 8 a.m.?

A knockout is a required answer: Saturdays yes/no, 18 years of age, driver’s license, “can you work this location,” years of claims or call-center work. If Casey cannot work weekends, no parse score and no LLM rank will help. Answer the truth. A yes you cannot defend on Saturday one is worse than a skip. Workday and iCIMS store these next to the resume; a coordinator who sees “weekends: no” and a PDF about Saturday FNOL overflow will not schedule you. Taleo knockouts are often on the first page before upload — finish them. Greenhouse may hide them in a custom question after the PDF. Layer 2 never sees a knockout you already failed.

Easy Apply on a job board is not the carrier’s ATS and it is not the carrier’s model. It can send a snapshot without months or with the email still in a sidebar. Use the career URL in the posting. If you already Easy-Applied, go to the banner’s site, create the real account, and upload the parse-safe file. Status emails from the board are not the same as a Workday candidate ID. When the portal says under review for three weeks, check that your profile has a phone and that the req is still open. Then apply to the next intake-lead posting instead of rewriting “team player” for a ranker that was never turned on.

If iCIMS shows a parse warning after upload, fix the file the same night. A missing month on the intake job is a quieter fail than a missing adjective. Workday Confirm is the same rule: First Name, Last Name, email in the body, dates that match the PDF. Greenhouse “Resume updated” is not proof the Guidewire line landed — open the preview. Then submit. The ATS checker is for the file, not for knockout questions you already answered no on. A honest no on Saturdays saves the coordinator and Casey the screen nobody can hold.

Agency and TPA portals add another trap: you parse-check for the carrier’s Workday, then apply on a vendor Taleo that strips the PDF to an image. Ask which system the req actually uses, or apply from the career site URL in the posting, not a third-party “Easy Apply” that stores a snapshot. If the confirmation page has no email on the profile, you did not pass Layer 1 or Layer 2 — you created an account. Internal employees: replace the old attachment; last year’s intake PDF will not mention the overflow Saturday Casey started in March. Layer 2 will summarize the old file if that is what the tenant still holds.

Extractability is still the first writing job. One column. Standard headings. Selectable text. Name, city, phone, email in the body. Dates beside the role. Skills as a real heading with tools Casey can defend — Guidewire, FNOL, recorded statements, bilingual English/Spanish — not star ratings. That is the same file how to pass ATS already asked for. If a sourcer cannot search “Guidewire,” a summary cannot mention Guidewire. Layout rules that survive Workday and Greenhouse sit in resume format and ATS resume.

True nouns come second, and only for work Casey can defend. The posting names Guidewire, FNOL, recorded statements, Saturday overflow, and bilingual intake. Those nouns belong in the current role’s bullets. A footer that repeats the whole qualifications block is stuffing. Greenhouse search can treat that block as noise. A Layer 2 summary that quotes the footer will sound like the job ad, not like Casey. Workday Skills tags prefer a “Skills” heading with real tools. For placement without lying, resume keywords. For a twenty-minute pass per req, tailor the resume to the job.

Meaning is the Layer 2 job people skip. An LLM summary is a short paragraph built from your sentences. “Responsible for claims” gives it nothing. “Took 40–50 inbound FNOL calls per shift in Guidewire, assigned claim numbers, and flagged files that needed a recorded statement before adjuster handoff” gives it a story a coordinator can skim. Verb, volume or system, result. If Casey has no clean metric, use scope: queue, shift, language, handoff. Line patterns: resume bullet points. Do not paste the posting into the summary box and hope a model “sees the match.” The model sees the paste.

Stuffing hurts both layers. Repeating “team lead” twelve times does not create supervision. iCIMS can still store you. A ranker may even bump a noisy file. The interviewer will ask who Casey scheduled. Cut the repeats. Keep one crew-size line if a huddle happened. Hidden white text and keyword dumps now look like manipulation in more than one vendor’s spam heuristics — see resume red flags if that page is on your list; the rule here is the same: nouns in context, none in invisible ink. A checker that only counts overlap will cheer a dump. A human and a summary will not.

Two files when the nouns diverge. The hospital iCIMS wants eligibility, registration, maybe HIPAA if Casey has the training. The carrier Workday wants Guidewire and FNOL. Do not sprinkle HIPAA into the insurance file because a blog said “AI keywords.” Do not sprinkle Epic into a claims resume. LinkedIn can be broader. The attachment cannot. After you rewrite, paste resume and ad into the ATS checker. Read contact and heading misses first. Those fail Layer 1. Missing nouns fail search and fail a summary. A high overlap with a footer full of the ad is the wrong green light.

A sentence that serves both layers

• System or queue named in roman text, not an icon.
• A number or scope you can defend on a screen.
• Handoff or outcome in plain words a summary can quote.
• No pasted qualifications block under Skills.

These rewrites are from claims-intake drafts, not from an ICU or a warehouse lead. Steal the pattern. In all three, the employer stays the regional insurer; only the language becomes searchable and quotable.

If Casey has run a five-person standup when the lead called out, that is the lead bullet — with the crew size. If not, apply as a senior intake specialist and keep the title honest. Layer 2 will repeat whatever title you typed. For more line patterns, resume bullet points. For the upload confirm step, pair this page with how to pass ATS and the ATS checker before you submit.

Stop optimizing a public “AI score.” Optimize whether a stranger can find your email, your last employer, and one true Guidewire sentence after a hostile extract. Then read the live form. That is the only rank that counts for this carrier.

Timer: 45 minutes including the portal. Have the posting, the master resume, and the Enhance CV export. Build in a known layout if the current file is a flyer. Ignore the career-site badge that says “AI matching” until Layer 1 is clean.

1. Circle the posting’s required nouns and any number (calls per shift, years, weekends, license).
2. Duplicate the master. Name the file Last_ClaimsIntakeLead.pdf — not ResumeFinal.
3. Contact in the body. Select-all test. Fix headers before you touch adjectives or “AI keywords.”
4. One column, headings Experience / Education / Skills. Delete icon rails and keyword footers.
5. Rewrite three to five bullets on the intake role with verb + volume or system name.
6. Skills line from nouns you can defend. No star ratings. No pasted qualifications block.
7. Title honest: Claims intake specialist, plus a parenthetical only if lead work is true.
8. Export selectable text. Open on a phone. Email tappable, dates readable.
9. Paste resume and ad into the ATS checker. Fix contact and heading misses first.
10. Create the portal account with the resume email. Upload. Wait for parse or retype in Taleo.
11. Match questionnaire numbers to bullets. Weekends, years, license — same story as the PDF.
12. Submit. Open the confirmation. If the tenant shows parsed warnings, read them and re-upload.

Step 11 is the silent killer. People parse-check and then rush the dropdowns. Coordinators compare. Layer 2 does not repair a “0–1 years” answer next to a three-year PDF. For Workday-specific widgets after upload, use the Workday format click path. For a general writing sequence, how to write a resume. For what a checker can and cannot score, ATS resume checker.

People invert steps 3 and 9. They paste a designed Canva export into a checker, celebrate noun overlap, and never notice the phone is an icon. Parse first. Nouns second. Meaning third. Form last. A Layer 2 summary of an icon is still an empty profile.

Stuffing. Repeating “team lead” or “AI” twelve times does not create supervision or a model preference. iCIMS can still store you; a ranker may even like the noise for a minute. The interviewer will ask who you scheduled. Cut the repeats. Keep one crew-size line if it happened. If the posting and your sentence are identical, pull a number back into your own words so a summary does not sound like the ad.

Two jobs. Claims intake lead and hospital patient access are different files. Workday at the hospital will search Epic or registration nouns; Casey does not have Epic. Do not sprinkle Epic into the insurance resume “for the AI.” The hospital file can emphasize phones, queues, eligibility questions, and weekend OT as transfer-adjacent — without fake charting. Two folders with clear file names save the next apply night. LinkedIn can mention both. Each attachment cannot.

When screening is not the problem. The carrier hired internally. The req needed 12 months of lead work. Casey applied after the close date. A clean parse and a tidy summary cannot reopen a filled job. Check the posting date and the required years before another rewrite. Then ship. The Enhance CV home page returns you to builder and checker. Internal employees: replace the old attachment; last year’s intake PDF will not mention the Saturday overflow you started in March. Greenhouse “Resume updated” does not always overwrite — read the preview.

Agency, TPA, and franchise-style portals add a fourth trap: you parse-check for the banner’s Workday, then apply on a vendor Taleo that turns the PDF into an image. Ask which system the req actually uses. Apply from the career URL in the posting. If the confirmation page has no email on the profile, you did not pass anything yet. The same trap is Workday “use last application” that revives an intake PDF without the standup line. Layer 2 will happily summarize last year’s file.

Last pass before Apply: file name with last name and role; phone with area code; one email in the body, none in the footer for the parser to swap. Then submit. Waiting a week to “perfect” adjectives for a model is how the intake-lead req fills with someone whose file was merely readable on Tuesday. Read the confirmation mail. If the tenant names parse warnings, reload the file the same night. The ATS checker is a rehearsal. The live form is the test. No page on this site, including this one, can promise an interview.