1Apply and see is a decision made with no information
The default pattern is browse, recognize a title, submit. The decision to spend an hour on an application gets made on two data points: the job title sounded right, and the company name was familiar. Everything that determines whether the application had a chance sits below the fold, in the requirements section nobody reads closely at 11pm.
That produces a specific kind of frustration. Volume is high, callbacks are low, and every rejection arrives with no diagnosis attached. You cannot tell a rejection caused by a seniority mismatch from one caused by a posting that was filled in March, because a rejection looks identical either way. Usually it is silence, which looks identical to everything.
The scoring habit fixes the input, not the output. It does not make you a stronger candidate. It tells you, before you spend the hour, which of the two things you are looking at: a role you could plausibly get, or one where the requirements rule you out on a line you skimmed past.
What you actually know at the moment you hit submit
Same posting, same candidate, two different decisions
Applying blind
Title recognition plus optimism
- Whether you meet the hard requirements
Unknown. You skimmed the bullets.
- Whether the posting is still live
Unknown. Age is rarely on the page you applied from.
- Which requirement is your weakest
Unknown, so nothing to address in the cover letter.
- Whether the level matches your career stage
Assumed from the title. Titles are not standardized.
- Time committed before you learn any of it45-60 min
Every rejection is a data point you cannot read.
Scoring first
Roughly 60 seconds, before the tailoring starts
- A 0-100 fit score across five weighted dimensions
- Ghost probability from posting age, salary disclosure, repost history
- The exact requirement costing you the most points
Named, with the point cost attached.
- Whether a disqualifier fired
Commission-only, agency listing, or a license you do not hold zeroes the score outright.
- Time committed before you learn all of it~60 sec
You still might apply. You just stop doing it by accident.
The habit is not about applying to fewer jobs. It is about knowing which of them you are choosing.
2What the engine checks in those 60 seconds
Scoring is not a keyword count. The engine reads the job description against your profile in a single pass and scores five dimensions on their own point scales: Skills Match out of 40, Experience out of 25, Seniority Fit out of 15, Industry Fit out of 10, and Culture and Logistics out of 10. The five sum to your number.
Skills Match carries the most weight because it splits two things a keyword scan cannot. It reads how deeply the role needs a skill against how deeply you have it, on a five-level scale from awareness to architect-grade, and it weights the job's core defining skill two to three times heavier than the secondary ones. A posting that mentions Python nine times and Terraform once is not asking for those equally.
A separate set of rules ignores the weighted total entirely and zeroes the score: commission-only and MLM roles, agency and staffing listings that hide the real employer, and roles gated behind a degree, license, or clearance you do not hold. No amount of skill overlap survives one of those. Seeing a zero is the fastest possible answer to should I apply.
3Building the habit in three weeks
What each week actually looks like
Week 1: score before you apply
- Every role gets scored before submission. Nothing under 65 gets an application. This will feel restrictive in a way that is hard to sit with: interesting roles will come back at 45, and applying anyway will feel like the braver choice.
- It is not. A 45 usually means a hard requirement is missing, not that the engine underrated you. Spend the reclaimed hour on the 78 you found the same evening.
Week 2: read the gap, not the score
- For every scored role, look at which of the five dimensions cost the most points. Write it down. After a dozen roles the pattern is usually unmistakable.
- Skills Match flagging repeatedly means the target role wants something your profile does not show. Seniority Fit flagging means the skills are right and the level is wrong, which is a different fix entirely: same search, one rung down or up, and the same profile suddenly scores 15 points higher.
Week 3: change the target, not the resume
- Two weeks of scores tell you whether you have a resume problem or a targeting problem. If Industry Fit sits under 60 across the board, no rewrite fixes it. If Skills Match is 75 while Seniority Fit is 45, your resume is fine and your search is aimed one level off.
- Make one change, then score ten new roles in the adjusted category. If the median moves up more than a few points, the diagnosis was right.
The habit takes about three weeks to stop feeling like an extra step. Week one builds the reflex, week two turns the scores into a diagnosis, and week three is where you act on what the distribution told you.
The three-week build
Roughly 20 to 30 scored roles is enough to read a pattern
- 1Days 1-7Week 1: score everything, apply above 65
Score before every submission, including roles you would not normally consider. The wide net is the point: you are mapping where your fit actually lands, not pre-filtering to confirm what you already believe.
- 2Days 8-14Week 2: read which dimension keeps flagging
Open the Why Not 100 breakdown on every score. One dimension will dominate the deductions. That repetition is the finding, not any individual score.
- 3Days 15-21Week 3: change one variable and rescore
Adjust the target the pattern points at, then score ten fresh roles in the adjusted category. Compare median score, not callbacks. Three weeks is too short to read callbacks; it is long enough to read fit.
Measure the median score of your target set, not your callback rate. Callback data at this sample size is noise.
4The thresholds, and what to do at each one
A score is a decision input, not a verdict. What changes across bands is how much of your evening the posting has earned, and whether tailoring can realistically close the distance.
The one asymmetry worth knowing: tailoring moves Skills Match and almost nothing else. If your deduction is concentrated in Experience or Seniority Fit, a better-worded resume does not move the number, because the gap is not about wording.
What each score band is actually telling you
Cold applications, no referral
Skip (0-59): A hard requirement is missing or a disqualifier fired. Tailoring does not close this. Archive it.
Quick apply (60-69): Real but distant. Ten minutes maximum, no custom cover letter. Worth a lottery ticket, not an evening.
Tailor it (70-84): This is where tailoring pays. You clear the bar; the work is showing you clear it. Spend the hour here.
Drop everything (85-100): Rare. Your strongest possible application, sent today, before the posting ages past two weeks.
A referral is worth roughly a band. With a real internal referral, 55 to 60 becomes worth the effort that 70 would otherwise require.
5What to do with the gap data
Gap analysis produces two kinds of finding, and confusing them wastes weeks. Short-term fixes are things already true about you that your resume failed to surface: a skill you use daily but never listed, a title that undersells the level you operated at, a certification sitting in a footer. Make the change, rescore the same roles, and watch whether the number moves. If it does not, the fix was cosmetic.
Long-term fixes are the ones the resume cannot solve. A missing skill the role treats as core, a seniority band you have not reached, an industry with no adjacency to yours. The move is to change the target and score ten roles in the new category, then compare medians. That comparison is cheap and takes an evening. Discovering the same thing through six weeks of silence is expensive.
6The habit is the product
Most job search advice sells a tactic: a resume format, a cover letter template, a networking script. Those all operate after the decision that actually matters, which is which postings deserve your evening at all.
Scoring first is a decision framework, and it fails safely. Worst case you spend a minute and apply anyway, having read the requirements more carefully than you otherwise would have. Best case you stop spending Sunday afternoons on postings that were filled in March, and you find out in week two that your search has been aimed one seniority rung off the whole time.
We are tracking our own outcome data on this and publishing it raw, including the sample sizes that are still too small to claim anything from. You can read exactly what we can and cannot yet demonstrate on the outcome data page.
Score a job before your next application and read the gap breakdown.
Score a Job FreeWritten by
Jesse Johnson
Founder, ShouldApply
Founder of ShouldApply. I write about job search strategy, hiring, and how to spend your time on opportunities that actually fit. Full bio →
Keep Reading
Frequently Asked Questions
65 for cold applications. Below 65, statistically few callbacks are produced regardless of how well the resume is tailored. For roles with referrals, you can apply with scores as low as 55 — the referral adds weight that the score doesn't capture. For dream roles at companies you're targeting strategically, 60+ with a strong cover letter can work. But cold applications below 65 rarely pay off.
Score broadly in week 1 — find 20–30 roles and score all of them, including ones you wouldn't normally consider. The goal is to understand the distribution of your fit across role categories, not to pre-select which ones are worth scoring. You'll discover fit categories you weren't considering and confirm mismatch in categories you thought would work.
Yes, that's one of its primary uses. Score 20 roles. Spend tailoring time on the top 5 by score — these are where tailoring will be most effective. For roles scoring 65–74, quick customize and submit. Below 65, skip or archive.
Not directly — the fit score reads your profile against the JD. If you have a strong referral at a company, the effective application probability is higher than the fit score implies. Use the score to understand the gap you're going in with, not as a binary pass/fail when you have a referral.
Related Posts
ShouldApply Outcome Data
The tracked-application data behind the argument, rates withheld until each band clears 50 applications.
Start scoring jobs
Score any job before you apply — fit score + ghost probability + gap analysis.
Should I apply? How to score any job
The 5-minute pre-application framework.
Your resume is fine — you're applying to the wrong jobs
When poor callback rates are a targeting problem, not a resume problem.
Close the gap: from 68 to 85 on any listing
Tactical edits that move borderline scores to strong ones.
Score before you apply.
The first week of the scoring habit shows you the distribution of your fit across role categories. That data is worth more than 3 weeks of untargeted applications.
Score a Job Now