You've read the advert twice. Your CV looks about right. You hit apply, and nothing comes back.
The problem usually isn't that you're unqualified. It's that you checked your CV the wrong way. Most people scan the job description for keywords, spot a few that match, and call it a fit. A recruiter reads it differently: they look for proof that you can do the parts of the job that matter most.
This guide walks you through checking your CV the way a recruiter reads it. It takes about 20 minutes per role the first time, and gets faster with practice.
Why keyword matching is the wrong test
Matching keywords tells you whether your CV mentions the right things. It doesn't tell you whether your CV shows them.
Compare two lines for a role that asks for SQL:
| What the CV says | What a recruiter learns |
|---|---|
| "Skills: SQL, Python, Excel" | You've heard of SQL |
| "Built SQL models that cut weekly sales reporting from 6 hours to 40 minutes for a 12-person team" | You use SQL to solve real problems, at a known scale, with a measurable result |
Both lines contain the keyword. Only one is evidence. A CV full of the first kind of line passes a keyword check and still reads thin to the person deciding whether to call you.
Copying the advert's exact phrasing doesn't fix this either. Echoing the job description back without anything behind it is one of the easiest things for a screener to spot.
Step 1: Pull out the real requirements
Job descriptions mix what the role needs with what HR always writes. Your first job is to separate them.
Go through the advert and write down every requirement as a short line. Then sort them into two groups:
- Core requirements. These are the job. Look for words like "essential", "you will", "must have", anything in the first few bullets, and anything mentioned more than once.
- Nice-to-haves. Phrases like "ideally", "bonus", "desirable", or "experience with X would be an advantage".
Ignore the boilerplate: "team player", "fast-paced environment", "excellent communication skills". Everyone claims those, so they rarely decide anything on their own.
Most adverts boil down to five to eight core requirements. If your list is longer, you've probably split one requirement into several.
Step 2: Find your evidence for each one
Now take each core requirement and find the single best line on your CV that proves it. Not a line that mentions it, a line that proves it.
Good evidence usually has three parts:
- What you did. The action, in your own words.
- The scope. How big: team size, budget, users, volume, number of stakeholders.
- The outcome. What changed because you did it, ideally with a number.
If you can't find a line with at least the first two, write "none" next to that requirement. Be honest here. The whole point is to see your CV the way someone with no context sees it.
Step 3: Grade each requirement
Give each core requirement one of three grades:
- Met. You have a clear line of evidence with scope or an outcome.
- Partly met. You mention it, or you have related experience, but the proof is thin or indirect.
- Missing. Nothing on the page shows it.
Here's what that looks like for a mid-level product analyst role:
| Core requirement | Best evidence on the CV | Grade |
|---|---|---|
| SQL for reporting and analysis | Cut weekly reporting from 6 hours to 40 minutes with SQL models | Met |
| A/B testing | "Familiar with experimentation" in the skills section | Partly met |
| Working with product managers | Ran fortnightly reviews with 3 PMs on feature adoption | Met |
| Dashboarding (Looker or similar) | None | Missing |
| Presenting insights to leadership | Presented quarterly churn analysis to the leadership team | Met |
Be strict with "partly met". If you'd struggle to talk about it for two minutes in an interview, it's partly met at best.
Step 4: Weigh it and decide
Not every requirement counts the same. Missing a nice-to-have barely matters. Missing the thing the role exists to do matters a lot.
A simple way to decide:
- Apply if nearly all core requirements are met and nothing central is missing.
- Tailor first if the core is mostly met but one or two important requirements are only partly met. That's usually fixable in 15 minutes.
- Skip, or treat it as a stretch if a central requirement is missing and you can't honestly evidence it.
In the example above, the analyst has three of five core requirements met, one partly met, and dashboarding missing. That's a "tailor first": tighten the A/B testing line, and if they've built any dashboards at all, say so with scope.
Skipping isn't failure. With the UK average sitting at 27 applications for one interview (StandOut CV, 2026), spending your time on roles where you can show strong evidence is how you change that ratio.
Step 5: Fix the gaps that matter
Only fix what you graded as partly met or missing on core requirements. Polishing lines for nice-to-haves is the least useful tailoring you can do.
For each gap, work through these in order:
- Is the evidence already there but buried? Move it up. A strong line on page two might as well not exist.
- Is it there but vague? Add the scope and the outcome. "Improved onboarding" becomes "Rewrote onboarding for 40 new starters a quarter, cutting time to first sale from 6 weeks to 4."
- Have you done it under a different name? Use the role's language for something you have genuinely done. If they say "stakeholder management" and you wrote "worked with other teams", say what you did in their terms.
- Have you simply not done it? Then don't invent it. Note it, and be ready to talk about how you'd close the gap if it comes up in interview.
That last point matters. A CV that claims everything reads as padded, and anything you claim, you'll be asked about.
Common mistakes
- Treating every bullet as equal. Five nice-to-haves don't outweigh one missing core requirement.
- Chasing a perfect match. If every role you apply for is a perfect fit, you're only applying for jobs you've already done. A strong stretch application is a good bet.
- Tailoring for roles you'd skip anyway. Do the check first, then decide where your tailoring time goes.
- Checking once, then reusing everywhere. Two roles with the same title can have very different cores. Check each advert on its own.
Doing this for every application
The method works, but it takes time. If you're sending around 16 applications a week, the UK average (StandOut CV, 2026), checking each one properly by hand adds up to several hours a week before you've written a word.
That's what Application Strength in Trackr Pro does for you. It pulls the requirements out of the job description, weights them by how central they are, and checks your CV for evidence of each one. You get a score from 0 to 100, every requirement graded as met, partly met, or missing, and a clear call on whether to apply, tailor, or skip. Your personal details are stripped out before any AI reads your CV.
It's the same method as this guide, run in one pass, for every job you save. If you keep more than one version of your CV, each one is scored separately against the same role, so you can see which version of your story stands up best.
The score is a signal, not a verdict. It can't see who the hiring manager is or how many people applied. What it can do is show you, before you hit apply, whether your CV proves what the job actually asks for.