u/groundedpicses

ok so this one genuinely made my stomach drop when i figured it while stalking my recruiter friend out and i haven't seen anyone talk about it clearly so here goes.

everyone knows recruiters search for keywords. "Senior Data Analyst" AND "SQL" AND "Python." your resume has those words, you show up. it doesn't, you don't. fine, most people kind of get that part by now.

what nobody mentions is the other side of that search. the NOT.

recruiters also filter OUT. they type things like "Senior Data Analyst" AND "Python" NOT "Junior." and the system hides every single resume that contains the word Junior anywhere on the page. not just in your current title. anywhere. a bullet point from 2018. a project name. a certification level. a previous role you listed six jobs ago. doesn't matter when or where it appears. one match and you're gone.

so you've been a senior analyst for four years. fully qualified. but you listed "Junior Data Analyst" as your first job out of college at the bottom of page two and you have no idea that word is quietly making you disappear from searches you should absolutely be showing up in.

same thing happens with other filters. "NOT contract." "NOT intern." "NOT part time." if any of those words live anywhere on your resume, a recruiter who runs that filter never sees you. even if everything else is a perfect match.

and here's what got me. this isn't something recruiters are doing maliciously. they're trying to cut a pile of 600 down to something manageable. the NOT filter is the fastest way to do it. but nobody tells candidates it exists, so you're getting filtered out by a word you didn't know was a problem.

go look at your resume right now with this in mind. not just your current title. every role, every description, every single line. what words are in there that could be a NOT filter for the roles you're going for?

i found three on mine. three words i'd never have thought to remove. changed them and i'm not saying it fixed everything but the silence got a little less silent.

the whole process of auditing every word across your entire career history is exhausting though. if you're already burned out from job hunting here is a quick tip for you, tools like CVnomist or (other competitors) can flag these kinds of keyword mismatches automatically while you focus on the bigger picture.

Happy to answer your Questions in the comments!

I spent a stupid amount of time figuring out why my resume was invisible. I talked to maybe a dozen recruiters over coffee, on calls, in DMs. They all told me versions of the same thing. The machine reads your resume before the human does. And the machine is dumb.

Here is what actually happens when you click submit

The five steps where things break

Your file goes through a pipeline. Ingestion, extraction, tokenization, mapping, storage. Sounds fancy. It's not.

Ingestion just checks if you're a PDF or DOCX and if you're under the file size limit. Boring.

Extraction is where it gets messy. The system pulls the text layer from your PDF. Not what you see. What the machine reads. These are different things. I learned this when a recruiter showed me my own resume in their system. Half my bullet points were gibberish. My beautiful custom font rendered perfectly on screen but encoded so badly the parser choked on it.

Tokenization breaks your text into searchable chunks. "Cross-functional" might become "cross" and "functional." Or "crossfunctional." Depends on the parser. A recruiter searching "cross-functional" might not find you if your resume got split weird.

Mapping is the worst step. The system guesses what's your name, what's your job title, what's a date. It gets this wrong constantly. I saw a resume where "Senior Product Manager | Google" parsed as title="Senior" and company="Product Manager." That person never showed up in any search for Product Manager.

Storage is just dumping everything into a database. If the previous steps broke, you're in there but unfindable.

Test your resume right now

Open your PDF in Chrome. Ctrl+A, Ctrl+C. Paste into Notepad. What you see is exactly what the machine sees.

If your skills section is blank? The parser couldn't read it. If your dates are missing? The parser stripped them. If sections ran together into one blob? Your layout broke the reading order.

This test takes 30 seconds. Most people never do it.

Encoding failures that kill you

Smart quotes from Word. Those curly " and ' characters. They often become or ™ or just vanish. Use straight quotes. Always.

Em-dashes and en-dashes. Copy-pasted from job posts usually. They disappear or split words. Replace with hyphens.

Fancy bullets. Arrows, checkmarks, diamonds. They become ? or blank space. Use hyphens or asterisks.

Accented characters. José, François. Sometimes work, sometimes become "Jos" depending on which ATS version the company bought. I saw this break search at a major provider.

Tables and columns. Multi-column layouts read left to right across both columns, line by line. Your skills on the left and experience on the right become "Python Senior Engineer SQL Google." Nonsense.

Headers and footers. Some parsers strip them entirely. Others dump them into random body text. Never put your contact info there.

The PDF vs DOCX thing

I tested both. A lot.

PDF keeps your formatting locked. Looks consistent everywhere. But text extraction fails more often, especially with design tools.

DOCX parses cleaner because there's no extraction layer. The system reads it natively. But formatting shifts between Word versions. And some systems flag macros.

My numbers: PDFs got 15% more callbacks for design-heavy roles. DOCX got 8% more for traditional text-heavy formats. Default to PDF unless they specifically ask for DOCX.

The hidden confidence score

A recruiter told me about this. Most ATS systems assign a confidence score to parsed resumes. Low confidence means you go to the bottom of the pile. Or a manual review queue that nobody checks.

What tanks your score? Weird section headers like "My Journey" instead of "Experience." Missing expected fields. Extraction errors. Mixed date formats. Inconsistent bullet styles.

High confidence means you surface first. Be boring. Be predictable. Be parseable.

The semantic search lie

Some ATS vendors sell "AI-powered semantic search." It understands concepts, not just keywords.

I tested it. Uploaded a resume with "data visualization." Searched for "data storytelling." No match. Searched "Python" against "PySpark." No match. Searched "project management" against "PMO." No match.

The AI is marketing. Recruiters use boolean keyword search because it's reliable. The system finds what they type. Not what they mean.

What I actually do now

I rebuilt my resume for mechanical readability. Standard headers. Consistent dates. Hyphen bullets. Single column. Arial or Calibri. Saved from Word, not Google Docs. I run the Notepad test on every version.

This is tedious. I spent months obsessing over character encoding and tokenization patterns. I had dreams about PDF text layers. The burnout was real.

I eventually started using tools that handle the mechanical optimization. CVnomist, Resumaniac, and Claude for specific tasks. They pull keywords from job posts, match them to my experience, and keep the output parseable. I review and send. Five minutes.

Don't use generic ChatGPT for this. It adds fancy formatting that breaks extraction. Smart quotes. Creative headers. It doesn't know about text layers or encoding. The specialized tools do.

Your checklist

Test your PDF. Ctrl+A, Ctrl+C, paste to Notepad. Fix anything broken.

Use standard section headers. "Experience" not "My Journey."

Use one date format. Never mix them.

Use simple bullets. Hyphens only.

Use standard fonts. Nothing custom.

Put critical info in the body, not headers or footers.

If all of this is clean, you are findable. Then you can worry about keywords and titles and all the other stuff.

The machine is dumb, make it easy for it.

let me preface this by saying i am not a career coach. i'm just a guy who's been unemployed for 16 months, has sent somewhere north of 400 applications, and accidentally ran an experiment on himself.

around month 8 i hit a wall. not the emotional wall, i'd already hit that one three times. this was the practical wall where i genuinely could not spend another two hours rewriting my resume for a role that would ghost me in four days. so i stopped. i built one clean generic resume and just blasted it. for about six weeks i probably sent 60 something applications with that same file.

total callbacks that month: one. and i'm pretty sure that one was a mistake because the recruiter opened with 'hi is this jennifer."

so i went back to tailoring. but this time i actually paid attention to what i was changing and why, instead of just rewriting random lines hoping something would stick. and the next month i got six callbacks. same market, same experience level, same types of roles. six versus one.

the thing i figured out is that there's tailoring that exhausts you for no reason, and there's tailoring that actually does something. i was doing the first kind for months. rewriting whole paragraphs, reworking my whole summary, moving sections around. none of that is what matters. what matters is much more boring and mechanical and honestly once i understood why it worked it took me about 15 minutes per application instead of two hours.

the short version is that the system doesn't read your resume the way a person does. it runs a search. and your resume either contains the words that search is looking for or it doesn't. so tailoring isn't about sounding good, it's about matching. and the posting hands you the exact words you need to match, for free, every single time.

i know that probably raises more questions than it answers and i'm happy to get into the specifics, the what i actually change, the what i don't touch, the how i read a posting to find the keywords that matter versus the filler. i can also talk about what i do when i'm applying at volume and don't have 15 minutes for every single one, because there's a version of this that gets faster the more you do it.

also want to be realistic about the part that still suck. even doing this right, even when i know my resume matched and i know it was seen, i still get ghosted constantly. the callback rate going up doesn't make the silence easier. it just means the silence is no longer about the resume, and weirdly that's both better and worse. better because at least i know what's working. worse because now i have to figure out what's happening in the interviews.

anyway. if you're in tech and you're in the grind right now, what are you struggling with most? the getting seen part or the getting past the first call part? because the fixes are pretty different and i've been burned by both.