Should You Even Apply? A 5-Minute Test That Saves 20 Wasted Applications
Applying to everything feels productive and is the most expensive habit in a job search. Here's how to decide in five minutes whether a posting is worth your evening.
There are two failure modes in a job search and almost everyone has one of them. Either you apply to everything, spreading a fixed amount of effort so thin that no single application is competitive — or you apply to almost nothing, because you keep finding one requirement you don't meet and deciding that settles it.
Both come from the same missing skill: you have no reliable way to tell, quickly, whether a given posting is worth your time. Here's a test that takes five minutes and is right most of the time.
Step 1: Sort the requirements into three buckets
A job ad presents its requirements as a flat list, which is why they feel equally binding. They aren't. Almost every posting contains three very different kinds of requirement, and only one of them is actually a wall.
Gates
Work authorisation, a legally required qualification, a regulated licence, a language the job is conducted in, a location you can't be in. Fail one of these and the application cannot succeed, no matter how strong the rest of you is.
Core
The three or four things the job consists of, usually visible in the first responsibility bullets rather than the requirements list. You need genuine, demonstrable evidence for most of these.
Wishes
The long tail: tools, extra languages, "experience in our industry preferred", nice-to-have certifications. Missing several is completely normal and rarely the reason anyone is rejected.
Most people mis-sort in one specific direction
They treat wishes as gates. "5+ years of Tableau preferred" is a wish; you have four and you use Power BI. That's not a reason to skip the posting — it's a reason to name the equivalence explicitly on your CV. Meanwhile the actual gate, buried in one line at the bottom ("must hold a valid Class C licence"), gets missed entirely.
Step 2: Score yourself honestly on the core
For each core requirement, ask a specific question: could I point to a bullet on my CV as evidence, and talk about it for two minutes? That's the standard, and it's higher than "I've done that" and lower than "I'm an expert".
| Your evidence | Score | What it means |
|---|---|---|
| Did it as a main part of a role, with a result | Strong | Lead with this; it's your case |
| Did it as part of a role, no clear result | Solid | Find the number before you apply |
| Did it adjacently, or in a different tool | Bridgeable | Name the equivalence explicitly — don't leave it implied |
| Learned it, never applied it | Weak | Fine for one core item, fatal for two |
| Never touched it | None | Two of these across the core means walk away |
The rough decision rule
Clear every gate, plus strong or solid evidence for most of the core = apply, and tailor properly. Clear the gates but bridgeable-or-weak across the core = apply only if it's a role you genuinely want, and invest in a real cover letter. Fail a gate = don't. The commonly repeated "apply if you meet 60%" is a decent instinct but useless without this weighting — 60% of the wishes and none of the core is not a 60% match.
Want the fast version? Build your CV with us and you can paste a job description to get a fit score with the specific gaps named — before you spend an evening on the application.
Build and check my fitStep 3: Read the four signals the ad gives away for free
Beyond requirements, a posting leaks a lot about whether it's worth applying to at all.
- 1How old is it? A posting live for eight weeks is often either filled, stalled, or an evergreen pipeline ad. Newly posted roles have the highest response rate — applying in the first week matters more than most people believe.
- 2Is the salary stated? Increasingly required in several markets, and an omission where it's normally shown is worth noticing. If it is stated and it's below your floor, the whole question is settled in ten seconds.
- 3Is the title inflated or deflated? A "Junior Analyst" role asking for six years and team leadership is under-levelled and probably under-paid. A "Head of" role with no reports is a title in place of money.
- 4Does the ad describe work or vibes? Postings that describe actual problems ("you'll own the migration off the legacy billing system") come from hiring managers who know what they want. Postings that are entirely about culture and perks often come from processes that haven't decided.
The reposting signal
A role that's been reposted two or three times in six months is telling you something — usually that the salary is below market for the requirements, or that the team has a retention problem. It's not automatically a no, but it's a reason to ask a pointed question early.
Step 4: Decide what this application costs you
The last input is your own budget. A job search has a fixed weekly capacity, and treating every application as equally expensive is what produces forty mediocre ones.
Cheap applications (10 min)
Strong fit, standard process, one-click or short form. Tailor the summary and skills line, send it. You can do several of these in an evening and should.
Expensive applications (1–2 hrs)
Roles you genuinely want, long forms, portfolios, written tasks. These deserve real research, a proper cover letter, and someone contacted inside the company. Budget two or three a week, no more.
The goal isn't to apply less. It's to stop spending expensive-application effort on cheap-application roles, and cheap-application effort on the jobs you actually want.
The five-minute checklist
- 1Scan for gates. Fail one → stop. (30 seconds)
- 2Identify the three or four core requirements from the top responsibility bullets. (1 minute)
- 3Score your evidence on each: strong / solid / bridgeable / weak / none. (2 minutes)
- 4Check posting age, salary, title level and whether the ad describes real work. (1 minute)
- 5Decide: cheap application, expensive application, or skip. (30 seconds)
And the case for applying anyway
Two exceptions are worth naming. If it's a role you'd genuinely love and you clear the gates, apply even on a mediocre core score — the downside is an hour, and hiring managers routinely stretch for candidates who make a specific, credible case. And if a posting is a stretch in exactly the direction you're heading, the application itself is useful practice for the one that counts.
The short version
- Split every posting's requirements into gates, core and wishes — only gates are absolute.
- Score the core on evidence you could talk about for two minutes, not on self-belief.
- Read the free signals: posting age, stated salary, title level, whether the ad describes real work.
- Classify each application as cheap or expensive and budget accordingly.
- Apply in the first week — timing beats volume more often than people expect.
Make every application you *do* send worth sending
Build a CV you can re-aim at each posting in minutes, so the roles that pass this test get a genuinely tailored application instead of a generic one. Free to build and preview.
Build my CV freeFree to build and preview. Pay only when you download.
Frequently asked questions
Should I apply if I only meet 60% of the requirements?
It depends which 60%. Meeting 60% of the wishes while missing the core skills is a weak application; meeting all the core requirements while missing several nice-to-haves is a strong one. Sort the list into gates, core and wishes first — the raw percentage on its own tells you almost nothing.
Is it worth applying to a job posted two months ago?
Sometimes, but it's a lower-yield application. Long-live postings are often filled, stalled, or evergreen pipeline ads. If it's a strong fit, apply — but prioritise fresh postings, because applying within the first week of a role going live consistently produces better response rates.
How many jobs should I apply to per week?
Five to ten well-matched, properly tailored applications is a sustainable and effective weekly target. What matters more than the number is the mix: two or three expensive applications to roles you genuinely want, and the rest cheap-but-tailored to strong-fit roles. Forty generic applications a week produces worse results and burns you out.
Should I apply if I don't have the required years of experience?
Years are usually a proxy for scope, not a gate. If you can demonstrate the scope — the size of what you ran, the complexity you handled — a shortfall of a year or two is routinely overlooked. Lead with scope rather than tenure. A genuinely regulated requirement (a licence, a certification) is a different matter and is a real gate.
What counts as a dealbreaker in a job ad?
Anything you cannot acquire before the hire: work authorisation for that country, a legally required licence or qualification, the working language of the role, or a location you can't be in. Everything else — tools, industry background, years, certifications you could obtain — is negotiable to some degree, and much of it is negotiable in the interview rather than on paper.