Four months out. Eighty applications in. Two rejections, seventy-eight silences, and not one phone screen. You’ve done everything they told you to do; you’ve been disciplined about it, and the scoreboard says nothing is working.
It’s probably not you. It’s probably not your background either. Most of the time it’s the math, and the math is doing exactly what you built it to do.
One resume times 100 is still one resume
If you send the same document to 100 postings, you didn’t take 100 shots. You took one shot, 100 times—same file, same screen, same result, over and over. The volume feels like effort because it costs you real hours, but it isn’t buying you any new information. You’re not learning anything from application 60 that you didn’t already know at application 6.
Volume is a symptom. It’s what people do when they can’t tell which postings are worth the work, so they treat them all as equally worth it. That’s an understandable response to a market that gives you almost no feedback. It’s just not a strategy.
When I was hiring cleared people in the federal government, I spent 10 years on the other end of those applications. The stack was never the problem. The stack was full of good people. What killed most of them was that, in the time I had, I couldn’t tell whether they matched what I was actually trying to fill. They may have matched. They just didn’t make it obvious.
What actually happens to your resume
Let me be blunt about the ATS, because the internet lies about it constantly. You’ve probably read that some huge percentage of resumes get auto-rejected by a robot before a human ever sees them. That number gets repeated everywhere, and it traces back to a vendor’s marketing pitch from over a decade ago, from a company that went out of business shortly after. There’s no study under it. Treat it as noise.
What the software usually does is rack and stack. It stores your resume, parses it, and ranks it against the req. A recruiter with a funded seat opens the system and searches it the way you’d search anything, by typing in the words that matter for that job. “TS/SCI.” “CI poly.” “Splunk.” “ISSO.” Then they work the top of the results, because there are only so many hours in a day and the req has been open for six weeks.
So you’re not usually being rejected. A weak match doesn’t get deleted; it sinks to the bottom of the stack, where a human technically can still find it but realistically never will. A lot of the time you’re not screened out. You’re just buried. Those are different problems with different fixes, and if you think a robot is deleting you, you’ll chase formatting tricks and white-text keyword stuffing instead of fixing what’s actually broken. The mechanics of how that parses and ranks really work, and what to do about it, are worth understanding in detail, and I’ve written the full breakdown of how ATS software handles a veteran’s resume for anyone who wants to go deeper than I can here.
The real automated knockouts are the ones the employer sets on purpose. Work authorization. Location. A required certification. A clearance level. Those are usually questions you answer in the portal, not a robot reading your prose.
Some of those reqs were never yours to win
This is the part that turns 78 silences from a personality flaw into a spreadsheet problem. A meaningful share of what you applied to, you were never going to get, and no amount of polish would’ve changed it.
The LCAT floor
In the cleared contracting world, many roles are tied to a labor category written into the contract. The LCAT spells out minimum education and years of relevant experience for the seat, and the contractor bills the government against it. That floor isn’t a preference, and it isn’t a recruiter’s opinion. If they put you in a billed seat you don’t qualify for, they’ve got a compliance problem, and in the worst case a False Claims Act problem. So when a posting says eight years, and you have five, a recruiter who genuinely likes you still can’t move you. Read the fine print, though. Many contracts allow substitutions, often experience in place of a degree, sometimes the reverse. If a substitution clause applies to you, say so plainly on the resume instead of hoping somebody does the arithmetic for you.
Contingent and pipeline reqs
Some postings are for work that hasn’t been won yet. The language gives it away: “contingent upon contract award,” “pending funding,” “future funded.” The company is building a bench so it can show the government a staffed team, and sometimes your resume goes into the proposal itself. That’s a legitimate practice, and it’s worth applying to, but understand what you bought. You bought a lottery ticket on a recompete that may not land for months, and may not land at all. If half your 80 applications were contingent reqs, your silence rate isn’t mysterious anymore.
Clearance mismatch
You already know your clearance better than I do, so I’ll keep this short. A funded seat that needs someone badged in next month usually needs someone who’s already at that level with the right poly on day one. Sponsoring an upgrade costs the company time and money it may not have. Applying to TS/SCI with full-scope work when you’re sitting on a Secret isn’t a character flaw; it’s just a low-probability ticket, and you should count it that way.
Aim the thing
The fix isn’t complicated; it’s just slower than what you’ve been doing, and slower is the whole point.
Pull up one posting you actually qualify for. Read the required section, not the nice-to-haves. Then read your resume next to it and ask a cold question: if someone searched for the exact words in that posting, would my document come back? Not “does my experience cover this.” Would the words match? If the req says “vulnerability management” and your bullet says “ran scans,” you did the work, and you still won’t show up. Use their words, not yours. Make the match easy to see.
The words vary a lot by where you’re aiming, and the vocabulary that gets you found in cyber isn’t the vocabulary that gets you found in logistics or program management, which is why I keep a set of ATS keywords broken out by industry rather than one generic list. Start from the posting, then check yourself against the industry set.
Then do the thing that beats all of it. In the cleared market, one warm intro to a recruiter who’s actually filling that req will usually do more than 50 portal submissions, because you show up as a person with a name attached instead of row 340 in a search result. Referred candidates tend to get looked at faster and hired at a much higher rate than job board applicants. Find the person. Go through the person.
If the tailoring is what’s stopping you, the friction is fixable. Building a base resume once and then aiming a real version of it at each posting is exactly what our military resume builder exists to make fast, so that “tailor every application” stops being advice you nod at and ignore.
The trade you’re actually making
Ten aimed applications will usually beat 80 sprayed ones. Not because ten is a magic number, and not because the universe rewards effort. It’s because each of those ten is a different shot, and eighty copies of the same document were always just one.
That’s not motivation. That’s arithmetic.
