Read enough job postings and you'll notice that the lines in them are not all the same kind of thing. Most lines describe what the employer values: lead programs, communicate with executives, manage vendors. Your evidence can answer those, strongly or weakly, and a strong answer to a high-priority line moves you forward.
But a few lines are different. Requires an active security clearance. Must be licensed in this state. On-site five days a week in Denver. Bachelor's degree in accounting required.
Those are gates. And the defining property of a gate is that evidence cannot argue with it.
The category mistake
Here is the expensive mistake: treating a gate like a requirement. A requirement invites a response; you look at "lead cross-functional programs" and start assembling proof. So when people see "must be located in Denver," the same instinct fires. Surely a strong enough résumé makes them flexible. Surely the rest of my experience compensates.
Sometimes a stated preference really is soft. But a true gate is usually attached to something your résumé cannot touch: a legal constraint, a licensing regime, a budget approved for one location, a clearance process that takes a year. The recruiter reading your application does not have the authority to waive it, no matter how good page one is.
Which means every hour you spend tailoring evidence for a role you're gated out of is your best work spent on your least possible outcome. That is not a writing failure. It is a reading failure, and it happens in the first thirty seconds of deciding to apply.
Those hours are not abundant. The average spell of unemployment in the US has recently run upward of six months, and anyone searching while employed is working from evenings and weekends. A search is a fixed budget of attention. Spending it on applications that were never winnable is the most expensive mistake available, and it is invisible, because a role you were gated out of rejects you the same silent way as one you merely lost.
Read for gates first
So invert the order. Before you analyze anything else in a posting, find the gates: the license, degree, clearance, location, work authorization, and travel lines. For each one, answer honestly: do I pass this, yes or no?
Three outcomes are possible. You pass every gate, and the real analysis can begin. You fail a gate that is genuinely hard, and you've just saved yourself hours, spend them on a posting you can actually win. Or you fail a gate that might be soft, in which case the move is to find out first, not to apply harder: the question costs a sentence, the tailored application costs an afternoon.
What this is not
This is not "don't apply unless you're perfect." Most lines in a posting are not gates, and partial evidence against real requirements wins jobs constantly. The 60% match who can prove their 60% beats the 90% match who can prove nothing.
The discipline is narrower than that: know which kind of line you are reading before you respond to it. Requirements deserve your evidence. Gates deserve a yes or a no, and the honesty to act on it.
Standing Proof's Job Lab separates gates from requirements as part of dissecting any posting, so the decision gets made before the effort is spent. See how the method reads a posting.