You meet every requirement. The skills section matches. You still get rejected. The cause is almost certainly a tacit disqualifier — something the job description implies without writing it down, and your résumé contradicts.
The five most common tacit filters
1. Reporting structure
A line like “you’ll partner with the Director of Engineering” tells you the role reports to a Director — not a VP, not a CXO. Your résumé pitching yourself as a peer of the C-suite will read as wrong altitude.
2. Team size context
“You’ll work with a pod of 4 engineers” implies: small team, no direct reports, hands-on. Your bullet “led a 12-person org” reads as overqualified within seconds.
3. On-call & operational expectations
“Prior on-call rotation experience preferred” — that’s not a nice-to-have. That’s a “this role requires you to wake up at 3 AM.” If your résumé reads as a strategic, planning-heavy profile, you’ll get filtered.
4. Default tooling
“Hands-on with SQL, Python, Mixpanel” — even if listed as nice-to-have. The team uses these daily; if your bullets show you delegated those to analysts, you read as the wrong tier.
5. Timezone & work mode
“Async-first,” “EU timezone preferred,” “must overlap with PST 9–11 AM.” These imply a real working pattern. A résumé without explicit timezone/location signal can read as “didn’t read the JD.”
Reading the JD for what’s not written
Three places to look:
- The “you will” section. This is verb density. Counts of “ship,” “write,” “triage” matter more than the bulleted requirements list.
- The “about the team” paragraph. This is where reporting structure, team size, and operational tempo hide.
- The “nice to have” line. Often more useful than “must have.” If a tool is “nice to have” but listed first, it’s effectively required.
The diagnostic does this read automatically and surfaces which tacit filters apply to your profile — see how the analysis works.
Why these matter more than keywords
ATS scanners count keyword overlap. They miss everything in this article. A 95% keyword match can still be a hard reject because the silhouette is wrong.
The fix isn’t to game the scanner harder — it’s to read the JD the way a recruiter does and match the implied shape.
Related reading
- How hiring managers actually read resumes — the 6-second decision and what it filters on.
- Team size and reporting structure cues on a resume — the specific bullets that signal scope at the wrong altitude.
- Resume filters beyond ATS keywords — the broader set of human filters that survive the keyword scanner.